Introduction to DOIs
There is an online tool that can generate a citation by entering the doi and selecting the appropriate journal and language.
For example, the 10.5067/AURA/HIRDLS/DATA101 for the American Geological Union in American English:
Zwally, H. J. and Schutz, Bob (2012), GLAS/ICESat L1B Global Elevation Data (HDF5), , doi:10.5067/ICESAT/GLAS/DATA106. [online] Available from: http://dx.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 archives. 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 referenced in a publication.
Existing metadata structures can accommodate the addition of EOSDIS 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 EOSDIS 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 ECHO. 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
DOI Name, the Identifier which is a unique string that identifies a resource.
The name of person(s) or data center who created the product.
List of name(s)
Product name, a name or title by which a product is known.
Title of the product
The name of the data provider that archives and/or distributes the data products.
Name of the organization that distributes the data.
The year when the data was or will be made publicly available.
YYYY, four digits of the year
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 "http://dx.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".
- No labels