NMDC Runtime Search API

Help below

{% for attr in doc_links.study_set[0].entity_attrs %} {{ attr.attr_name }}{% if not loop.last %}, {% endif %} {% endfor %}

Indexed attributes (for faster filtering):

Copy-and-paste Examples:

{% for attr in doc_links.biosample_set[0].entity_attrs %} {{ attr.attr_name }}{% if not loop.last %}, {% endif %} {% endfor %}

Indexed attributes (for faster filtering):

Copy-and-paste Examples:

{% for attr in doc_links.data_object_set[0].entity_attrs %} {{ attr.attr_name }}{% if not loop.last %}, {% endif %} {% endfor %}

Indexed attributes (for faster filtering):

Copy-and-paste Examples:

{% for cname in activity_collection_names %} {{ doc_links.activity_set[cname][0].entity_name }}{% if not loop.last %}, {% endif %}
{% for attr in doc_links.activity_set[cname][0].entity_attrs %} {{ attr.attr_name }}{% if not loop.last %}, {% endif %} {% endfor %}
{% endfor %}

Help with searching for activities

Indexed attributes (for faster filtering):

Copy-and-paste Examples:

Help

Filters are of the form attribute:spec, that is, an attribute followed by a colon (:) followed by a specification of value.

The attributes available depend on the collection resource(s) being filtered.

Some attributes that are of type string (i.e., not numbers) may be annotated with .search to indicate that the specification of value is to be interpreted as a full-text search of the field.

The specification may be:

You can combine filters by separating them with a comma (,).

Searching for Activities

The Activities endpoint searches each of the following collections: Activities search results are combined and returned. Each result will have a type field to let you know what kind of document it is.