Status and Distribution¶

Status and Maintenance¶

Status¶

Use this field to describes the progress or development phase of the dataset or project. Use the dropdown to select the term that best describes the status of your dataset. The most appropriate terms for your dataset are likely ‘Ongoing’, ‘Completed’, or ‘Archived’.

For a full list of progress code values and definitions, see the Progress Code table.

Resource Maintenance¶

Use these fields to document how often the dataset will be updated, who will updated the dataset the person responsible, and to provide any additional information about how the resource will be updated or maintained.

Field	Best Practice	Example
Update Frequency	Select the frequency code value from the dropdown that most closely matches any plans for how regularly any maintenance services or content updates will be applied to the dataset or resource	Annualy, As Needed, Not Planned, Unknown
Maintenance Contact	This field should provide name and contact information for the person(s) or organizational position(s) responsible for future maintenance or any updates to the dataset	CTD Technician UAF SFOS Fairbanks AK sfos+technician@sfosfakeaddress.edu
Update Notes	Use this field to describe any planned maintenance or updates to the resource or dataset, as well as any effects of those updates on the applicability or validity of the existing dataset	Annual updates to the data will include additional data from 3-4 cruises, which will be added as a new table formatted identically to existing years. Updates to data from prior years are not planned but will be noted if they occur.

Publication Date and Other Dates¶

Use these fields to describe any dates important in the life of the dataset. The temportal extent of the dataset, or the collection and coverage dates, should be described on the Time Period(s) page of the editor.

Field

Best Practice

Example

Publication Date

This field is used to document the date that the dataset or resource was officially released for as a finalized product.

2017 11 20 -09:00

Additional Dates

This field is used to document any other important dates in the lifecycle of the dataset. To document such dates, enter the date information in the ‘Date’ field and select the appropriate date type from the ‘Date type’ dropdown.

Date type terms are definied in the Date Type Code table.

Creation,
Publication,
Validity Ends

Distribution Information¶

Use these fields to document where the dataset or resource is available, in which formats it is available, and any processes or fees related to distribution. Click the ‘+’ at the bottom of the screen to add a new distribution object for each distributor or distributed version.

Use the Online Distributor tab to describe where and from whom the dataset is available via any of the common data services (THREDDS, ERDDAP, etc.) or fancy internet protocols (http, ftp, etc.).

Offline Distributor should be used to describe distribution options for distributing or accessing datasets that need to be physically distributed. Why do people still need to physically distribute datasets or related products? Well, there may be physical items that exist in the real world. As a common example, especially large datasets are sometimes more efficient to distribute on physical hard drives rather than over the internet.

Specific fields related to distribution are described in the table below.

Field	Best Practice	Example
Distributor	Use this field to provide the name and contact information for the person or organizational position responsible for distribution of the resource.	John Q Distributor Axiom Data Science 1016 W 6th Ave, Ste 105 metadata+johnqdistributor@axiomdatascience.com
Distibuted Format	Use these ‘Format’ and ‘Format Version’ fields to document the file format and version of that format (if applicable) in which the dataset is distributed	Format: netcdf3 Format Version: CF-1.7 compliant netCDF-3 Format: csv Format Version: not applicable
Transfer Options	For Online Distribution: Use these fields to provide links and descriptions of the websites or service endpoints from which the data is distributed. Best practices for describing links are described on the Additional Fields page. For Offline (Physical) Distribution: Use this field to document the type and formatting of the medium on which the resource is distributed, as well as to provide any other notes on the distribution of the physical resource.	Online Online URL: http://thredds.axiomdatascience.com/thredds/dodsC/Aquarius_V3_scat_wind_speed_Weekly.nc.html URL Label: Aquarius V3 scat wind weekly.nc URL Description: Aquarius V3 Scatterometer Wind Speed Weekly Offline Physical Resource Notes: Though these model results are available to the public, they are large enough that it is impractical to deliver them over the internet. To receive these data, please mail a 2TB or larger ext3+ formatted hard drive to us at the address below. Before mailing you drive, contact metadata+distribution@axiomdatascience.com to coordinate shipments.
Order Processes	These fields are used only for Offline Distribution. These fields describe dates, fees, typical turnaround times, and any other instructions related to ordering physically distributed resources.	Availability Date: 2018 04 22 Access Fees: cost of return postage for the hard drive Ordering Instructions: Contact metadata+distribution@axiomdatascience.com to coorinate shipment

Identifiers¶

The identifier fields provide places to describe any unique identifiers that have been assigned to your dataset or files. Identifiers are typically assigned near the completion of a project, when datasets and files are in their final, quality-controlled and ready-to-be-published format. In the event that a dataset has been assigned multiple identifiers, perhaps from multiple identifier systems or schemes, please add each identifier to the metadata.

Code¶

Use the code field to document the identifier itself, or the string that uniquely identifies the dataset (or other resource) in some identifier system. Such a system is typically a published identification scheme, like DOI or LSID, but might also be a locally controlled namespace. Typically, an identifier is assigned to a resource as part of a publication or usage workflow, once datasets have become fixed in their final states after collection, actively development, and analysis are complete.

Field	Best Practice	Example
Code	Enter the identifier in its recommended form, with a namespace whenever appropriate	http://doi.org/10.24431/rwfakedoisuffix com.axiomdatascience.fakelocalidentifier

Authority¶

The fields in the Authority section describe the organization or entity responsible for maintaining the identifier system. Provide as much information about the authority as you can.

Field	Best Practice	Example
Identifier System Name	Enter the complete name and any commonly used acronym for identifier scheme.	Digital Object Identifier (DOI) Object Identifier (OID) Archival Resource Key (ARK) Life Science Identifiers (LSID) Universal Resource Identifier (URI)
Identifier System Publication Date	Publication or issue date of the version of the identifier scheme used.	2011 11 16 -09:00
Point of Contact	Provide the name and contact information for the organization responsible for maintaining the identifier scheme from which the identifier was taken.	See Contact Information for a description of the contacts fields
Links	Provide a link to the source or home page of the identifier schema.	See Online Resources for a description of the sub-fields in this section.

Constraints¶

The constraints fields are where you can include information you want to provide to others regarding the access rights and any use constraints for the resource described by the metadata. For example, perhaps the data is public access, but you or your institution requests that anyone using the data contact you before they publish results using the data. This is also the place to put any specific text that might be required for an acknowledgement or citation when the data is used.

It’s best to be aware that there’s no real way of enforcing these constraints. It’s best to think of these as requests to data users to obey certain community norms and as encouragement for data creators to release their data as openly and permissively as is possible.

Field	Best Practice	Example
Use Limitations	Describe any general limitations or constraints on how the resource can be used.	Disclaimer - While every effort has been made to ensure that these data are accurate and reliable within the limits of the current state of the art, NOAA cannot assume liability for any damages caused by any errors or omissions in the data, nor as a result of the failure of the data to function on a particular system. NOAA makes no warranty, expressed or implied, nor does the fact of distribution constitute such a warranty. Source
*Legal Constraints*	Document the legal restrictions of requirements on the use of the resource or metadata.	Under development.
Legal Restrictions	Use this field to provide a brief textual description of any legal restrictions that apply to the dataset or project.	Under development.
Access Restriction	Select from the drop-down the most appropriate description of any limitations on access to the dataset or metadata. If none match, don’t bother selecting one.	Under development.
Use Restriction	Select from the drop-down the most appropriate description of any limitations on the use of the dataset or metadata. If none match, don’t bother selecting one.	Under development.
Other Constraints	Whenever `Other Restrictions` is selected from either the ‘Access Restrictions’ or ‘Use Restriction’ drop-down, use this field to document those other restrictions.	Under development.
*Security Restrictions*	Document the restrictions on the access or use of the resource or metadata related to precting security concerns.	Under development.
Security Restrictions	Use this field to provide a brief textual description of any restrictions that apply to the dataset or project for the purpose of protecting security concerns.	Under development.
Security Classification	Select from the drop-down the classification term that describes the handling restrictions on the resource or metadata.	Under development.
User Note	Provide a brief textual description of the classification term applied to the resource or metadata.	Under development.
Classification System Name	Enter the name of the security classification system that dictates the terms for accessing, handling, and using the dataset or metadata.	Under development.
Handling Information	Use this field to add a textual description of the secruity restrictions on handling the dataset or metadata.	Under development.

Specific Uses¶

These fields are used to describe any specific uses for which the resource has been applied, any specific limitations on resource use as determined by creators or other users, and information about use dates and user contact information. These fields can be used to provide feedback on data

Field	Best Practice	Example
Specific Uses	Describe the how the dataset was used, for example, in a synthesis product or real world application.	This archive of stream flow data was used as an input in a hydrological model of the Anchorage bowl.
Usage Date	Add the date (and time, if appropriate) of the first use of the dataset	2016-03-15
User Determined Limitations	Describe any applications determined by users or creators of the dataset for which the dataset is not suitable.	Bathymetric data is not recent enough or of fine enough resolution to be used for navigation.
Specific User	Provide the name and contact information for the person or organization that applied the data in the specific use or user-determined limitation described above.	See Contact Information for examples of the individual contact info fields.