You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A recommendation for the format of the data is Project Open Data, which is a Federal standard for structuring and sharing open data. This leads to a suggested metadata schema of:
Title: Human-readable name of the asset. Should be in plain English and include sufficient detail to facilitate search and discovery
Description: Human-readable description (e.g., an abstract) with sufficient detail to enable a user to quickly understand whether the asset is of interest.
Keyword: Tags help users discover your dataset; please include terms that would be used by technical and non-technical users.
Modified: Most recent date on which the dataset was changed, updated or modified.
Publisher: The publishing entity and optionally their parent organization(s).
Contact Name and Email: Contact person’s name and email for the asset.
Identifier: A unique identifier for the dataset or API as maintained within an Agency catalog or database.
Public Access Level: The degree to which this dataset could be made publicly available, regardless of whether it has been made available. Choices: public (Data asset is or could be made publicly available to all without restrictions), restricted public (Data asset is available under certain use restrictions), or non-public (Data asset is not available to members of the public).
Bureau Code: Federal agencies, combined agency and bureau code from OMB Circular A-11, Appendix C (PDF, CSV) i
n the format of 015:11.
The text was updated successfully, but these errors were encountered:
JeanneHolm
changed the title
New Data to Contribute
Suggested Metadata Standard
Jun 29, 2016
A recommendation for the format of the data is Project Open Data, which is a Federal standard for structuring and sharing open data. This leads to a suggested metadata schema of:
n the format of 015:11.
The text was updated successfully, but these errors were encountered: