Versions Compared

Old Version 36

changes.mady.by.user Unknown User (efinn)

Saved on

compared with

New Version Current

changes.mady.by.user Heather Weir

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
 

Introduction to DOIs

A Digital Object
Identifiers (DOIs) for EOSDIS

ESDIS Project is investigating methods for adding Digital Object Identifiers to EOSDIS standard product metadata. The DOI® system provides an Internet resolution service for unique and persistent identifiers of digital objects.

More information about DOIs can be found at http://www.doi.org/.

Citation using DOI

A data citation using a DOI takes the form of:

The Creator may be a person or organization. The Publication Date is when the dataset was first available through the Publisher. The Title is free-form name of the dataset and may include other qualifying information such as processing level, resolution or version. The Publisher is the distributing organization. The Access Date is when the data was obtained from the Publisher.

Through the DOI system, the identifier will always resolve to the location of the data (i.e., to the URL where the data can be found).

Identifier or DOI is a unique alphanumeric string used to identify an digital object and provide a permanent link online.  DOIs are often used in online publications in citations.  DOIs are assigned and regulated by the International DOI Foundation (IDF). 
DOIs are alphanumeric strings in the following format:
–doi:[prefix]/[suffix]
Prefix – 10.[number] where [number] identifies registrant agent.  5067 has been assigned for NASA ESDIS.
Suffix – uniquely identifies the data item and it’s format is assigned and managed by the registrant agent.
DOIs provide persistent identification, enabling easier access to research data.  Citation of data products increase when the DOI is stored in the product's metadata thereby increasing its value.  

DOIs are resolved by entering the full DOI name into https://dx.doi.org/.  Entering the DOI name into the text box and clicking "Submit" will take the user to the product landing page that corresponds to the product that goes with that DOI.

DOI Citation

Below is an example of the EOSDIS citation guidelines for GESDISC MEaSURE data using a doi:

There is an online tool that can generate a citation by entering the

doi

DOI and selecting the appropriate journal and language.

http

https://crosscite.org/

citeproc/

For example,

the doi:10.3334/ORNLDAAC/1099 for

the 10.5067/AURA/HIRDLS/DATA101 for the American Geological Union in American English:

DOI Structure

A DOI consists of two part alphanumeric string: doi:[prefix]/[suffix] which can serve as a permanent data identifier for citation in publications. In the hypothetical DOI: ‘10.5067/123’, the prefix ‘10’ identifies the DOI registry and is followed by ‘5067’, which identifies the Registrant Agent. The number ‘5067’ has been assigned for NASA ESDIS. The suffix alphanumeric string ‘123’ uniquely identifies the data item, and is otherwise free for the RA to assign and manage. DOIs are case insensitive, generally coded in all capital letters.

DOI Suffix Model

The following are models for a standard DOI suffix string vocabulary; they will be used as guidance in assigning DOIs. Forward slash is used to represent containment. The purpose is to characterize the data product.

[mission]/[instrument]/data[m][n]

[campaign]/[platform group]/data[m][n]

[campaign]/[measurement group]/data[n]

[program]/[measurement group]/data[n]

[measurement group]/[data[n]

[instrument]/[shortname.version]

In the above syntax, the processing level of the product is depicted by [m] where ‘m’ ranges from 1 through 3 for products from satellite instruments. (i.e., NASA satellite products are generally depicted as belonging to a Level of processing, Level 1 being calibrated/geolocated radiances through Level 3 being global grids of derived geophysical values). When a Level designation isn’t appropriate [m] is dropped from the syntax.

Keyword "DATA" is placed in the DOI to distinguish raw and processed data collections from research papers.

A sequence number is assigned on a first-come-first-serve basis, represented by [n].

Putting DOIs in Product Metadata

DOIs have additional value when stored in product metadata
Zwally, H. J. and Schutz, Bob (2012), GLAS/ICESat L1B Global Elevation Data (HDF5),  doi:10.5067/ICESAT/GLAS/DATA106. [online] Available from: https://doi.org/10.5067/ICESAT/GLAS/DATA106

Putting DOIs in Product Metadata

It is ESDIS policy to embed DOIs in the metadata of its science data products where applicable. Researchers that acquire product data files should be able use the DOI to find the definitive documentation from NASA’s Scientific and Technical Information (STI) archives.

Adding DOIs to product metadata will also enable tools for provenance tracking – help find more information about the creation

Also, when stored in the product metadata, a DOI can increase the verification and validation of scientific results thereby, enabling provenance tracking and the discovery of information regarding the life cycle of the data product

. This link takes you to a page that explains the conventions we want to use and evaluate: DOIs in the Metadata

DOI Projects

The following projects have begun the process of creating and registering DOIs. The table below gives a status of each project. The links go to the project's page where there is information about the DOIs they have begun to create.

Project# Reserved DOIs# Registered DOIsTotal DOIs
AIRS73340
AMSR-E15217
Aquaris606
GLAS41115
HIRDLS404
MEaSUREs - GOZCARDS01111
MEaSUREs - GPCP101
MEaSUREs - Herman19019
MEaSUREs - McPeters01818
MEAaSUREs - Robinson606
MEaSUREs - Shie01313
MEaSUREs - Wentz43236
MEaSUREs - WVCC033
MODIS01818
MOPITT10010
Nimbus729
SeaBASS066
SMAP16016
Suomi-NPP033
Total DOIs99152251
    

Additions since 7/1/13

61016

A reserved DOI is one that has been created by the project but not registered or publicly available due to lack of certain requirement metadata. In most cases, the product landing page is missing.

A registered DOI is one that has been reserved with the project and registered on EZID and is publicly available.

Navigate space

Page Tree Search

Page Tree

recently-updated

referenced in a publication. 

Existing metadata structures can accommodate the addition of ESDIS product and file level identifiers in multiple ways. The purpose of this technical review is to examine various aspects of each and a combination of multiple implementations.


The product data files will contain a file level attribute for the DOI. The global file-level attribute is required for the user convenience (e.g., viewing with standard exploratory tools).

The associated ESDIS core metadata and metadata files should also contain a Product Specific Attribute (PSA) for the DOI (e.g., to enable applications).

DOI Attribute Name

The tag to use in the metadata, i.e., the attribute name, will be "identifier_product_doi". This syntax was chosen to support a standard way of handling multiple kinds of identifiers, and both file-level and product-level identifiers. The same attribute name will be used for both file-level (i.e., global) and PSA constructs.

We are able to set DOI values in both the collection-level and granule-level metadata for the same ESDT (Earth Science Data Type, structure used for ingesting products into ECS archives). A value for the "identifier_product_doi" PSA will be coded into the collection-level metadata section of an ESDT descriptor file so that it will be exported to to other systems as required. Adding a value for the "identifier_product_doi" PSA is a simple collection-level metadata change in the ESDT descriptor file, and can be done after the ESDT's granules have been produced.

The production software will put the "identifier_product_doi" PSA and its value in the granule metadata files and in the HDF files.


Data Product Attribute

Definition

Allowed Values

Identifier

DOI Name, the Identifier which is a unique string that identifies a resource.

DOI name

Creator Name

The name of person(s) or data center who created the product.

List of name(s)

Title

Product name, a name or title by which a product is known.

Title of the product

Publisher

The name of the data provider that archives and/or distributes the data products.

Name of the organization that distributes the data.

Publication Year

The year when the data was or will be made publicly available.

YYYY, four digits of the year

URL

URL for the landing page that has the current location of the information of the data product.

Web URL format


DOI Attribute Name Authority

An additional attributed would define the authoritative service for use with DOI values in resolving to the URL location. Adding this attribute to HDF metadata will allow more complete mapping to netCDF and to ISO standard metadata structures.

The most valuable place for this attribute is in the HDF files, so it should be added at the file level as well as the PSA level.

It is best if the attribute name for the DOI authority is similar to the name for the DOI identifier i.e., similar to "identifier_product_doi" so we are asking providers to add an attribute name = "identifier_product_doi_authority". This would help users (and code) find it in the metadata.

The value of the attribute would be "https://doi.org/"

Lower case attribute naming convention for netCDF CF

It has been pointed out that the common practice for netCDF CF is to define attribute names in all lower case, using underscores to separate key words. This has been generally extended for non-standard attributes (such as "identifier_product_doi"). If upper case letters are used there will need to be special code in translators and testing with netCDF tools. So as of this writing, we want to use an all lower case attribute name "identifier_product_doi" and attribute naming authority "identifier_product_doi_authority".


Panel
borderColorblue

Children Display
depth1
pageDigital Object Identifiers (DOIs) for ESDIS



Hide comments