You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »


This functionality can be used to limit the # of granules which are allowed to be ordered for a given collection in EDSC.  This limit can be configured by the provider as needed in order to ensure that large orders do not adversely impact provider operations.

Step-by-step guide


  • Generate an ECHO token. ( the id field in the response is the token)


curl -XPOST \
  https://cmr.earthdata.nasa.gov/legacy-services/rest/tokens \
  -H 'cache-control: no-cache' \
  -H 'content-type: application/xml' \
  -d '<token>
    <username>--ask task lead--</username>
    <password>--ask task lead--</password>
    <client_id>--ED Login client ID. Look it up in EECS or services.yml.erb--</client_id>
    <user_ip_address>--a valid IP address, can be anything. For example, 127.0.0.1--</user_ip_address>
</token>’


  • Create a new tag with name edsc.limited_collections, if it doesn't already exist.


curl -XPOST -i -H "Content-Type: application/json" -H "Echo-Token: <token from first step>" https://cmr.sit.earthdata.nasa.gov/search/tags -d \
'{"tag_key": "edsc.limited_collections", "description":"give an optional description"}'


  • Associate collections to the tag
    • associate a single collection to the tag with limit set in the data field:

      curl -XPOST -i -H "Content-Type: application/json" -H "Echo-Token: <token from first step>" https://cmr.earthdata.nasa.gov/search/tags/edsc.limited_collections/associations -d '[{"concept_id":"C12345-DAAC_NAME", "data":{"limit":2000}}]'


Note, if you want to associate the tag to multiple collections, you will have to find all the concept_ids first and then do it one at a time.


There are real examples in ticket EDSC-1591 - Getting issue details... STATUS

  • No labels