We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
According to Project Open Data, a data catalog should list itself. See:
http://project-open-data.github.io/catalog/#inclusion-of-the-public-data-listing-as-a-record
The requirements for this are somewhat unclear. POD's example shows the general format to use:
{ "title": "Data Catalog", "description": "Version 1.0", "keyword": ["catalog"], "modified": "2013-05-09", "publisher": "US Department of X", "contactPoint": "John Doe", "mbox": "john.doe@agency.gov", "identifier": "1", "accessLevel": "public", "distribution": [ { "accessURL": "http://agency.gov/data.json", "format": "application/json" } ] },
...but the requirements are a bit confusingly documented. We are waiting for a response on project-open-data/project-open-data.github.io#307 to move forward.
The text was updated successfully, but these errors were encountered:
Most of the fields in the example are easily generated from existing variables... but where would the contactPoint for the data catalog come from?
Sorry, something went wrong.
This issues is now being addressed in our Open Data Schema Map module.
References and endpoints for dataset properties and dynamic API routi…
be785f0
…ng (#129)
dafeder
No branches or pull requests
According to Project Open Data, a data catalog should list itself. See:
http://project-open-data.github.io/catalog/#inclusion-of-the-public-data-listing-as-a-record
The requirements for this are somewhat unclear. POD's example shows the general format to use:
...but the requirements are a bit confusingly documented. We are waiting for a response on project-open-data/project-open-data.github.io#307 to move forward.
The text was updated successfully, but these errors were encountered: