![]() ![]() The header Concept-Id is an alias for Cmr-Concept-Id. The CMR should normally generate the concept id. This should normally not be sent by clients. The Cmr-Concept-Id header allows specifying the concept id to use when saving a concept. If the revision id specified is not the latest a HTTP Status code of 409 will be returned indicating a conflict. The Cmr-Revision-Id header allows specifying the revision id to use when saving the concept. The Cmr-Pretty Header set to true or using the alias &pretty=true URL parameter will tell CMR to format the output with new lines and spaces for better readability by humans. If no UMM JSON version is provided, the latest version will be used. Like charset, it is appended with a semicolon ( ). UMM JSON accepts an additional version parameter for Accept header. ![]() application/json can be specified if the preferred responses is JSON. The Accept header specifies the format of the response message and defaults to XML for the normal Ingest APIs. More information on getting access to Launchpad tokens can be found on this guide Accept Header The token should be specified using the Authorization header followed by the Launchpad token. For more information on obtaining an EDL bearer token, please reference the documentation here.Īn example for generating a Launchpad token can he found here. The token should be specified using the Authorization: Bearer header followed by the EDL bearer token. Authorization HeaderĪll Ingest API operations require specifying an EDL bearer token or a Launchpad token.Īn EDL Bearer token can be obtained from Earthdata Login (EDL). Note: For all values of Content-Type, data sent using POST or PUT should not be URL encoded. UMM JSON version is required.įor an example, the following means version 1.16.2 of the UMM JSON format: application/+json version=1.16.2 Note: UMM JSON accepts an additional version parameter for Content-Type. Content-TypeĬollection, granule, variable, service, subscription, tool Ingest supports the following content types for ingesting metadata. Content-Type HeaderĬontent-Type is a standard HTTP header that specifies the content type of the body of the request. This defines common headers on the ingest API. This defines conventions used across the Ingest API. GET - Granule bulk update status by task-id.POST - Create a subscription with a provided native-id.POST - Create a subscription without specifying a native-id.PUT - Create or update a variable with association.See the CMR Client Partner User Guide for a general guide to developing a CMR client. One example of provenance metadata could be the "Revision history" section of a Wikipedia page.See the CMR Data Partner User Guide for a general guide to utilizing the CMR Ingest API as a data partner. Provenance metadata: This applies to data that is frequently modified or replicated.This metadata keeps a record of who has owned or altered the digital object, and preserves the data's rights, permissions, and specific instructions to gain access. Administrative metadata: This type is also sometimes called preservation metadata.This kind of metadata could, for example, help inform an influencer what time of day is best to post on Instagram. Use metadata: Another type of metadata is "use" metadata, also known as tracking metadata, which is the data that keeps record of when and how often a user interacts with a piece of digital data.The metadata described in the Microsoft Word example above is known as "descriptive" metadata. Descriptive metadata: You can think of descriptive metadata as a type that sheds light on the basic biography of a piece of data - details like the title, date published, and who the creator is.The following are several of the most common types of metadata, with "descriptive" being the most common. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |