Closed jmckenna closed 5 months ago
We passed an example dataset landing page with embedded JSON-LD/schema.org through the schema.org validator.
Here's the full address: https://www.ncei.noaa.gov/access/metadata/landing-page/bin/iso?id=gov.noaa.nodc:276264
We spotted a few issues to fix/improve
Things to improve/fix:
spatialCoverage
values that are keywords or terms from a vocabulary, consider using DefinedTerm
. parentOrganization
which is more sensible.@Organization
JSON-LD document with its own PID and linking off to it. It would be wise to do this only when there's a commitment to maintain these documents in perpetuity. For the moment, it's probably best to keep the repeated metadata in each @Dataset
record.distribution
property seems to be misapplied: one would include URLs to directly download the dataset itself, along with metadata on the type of file, size, etc. Right now they take one to a landing page, which is somewhat redundant with the url
property. These links exist, and look like this: https://www.ncei.noaa.gov/archive/archive-management-system/OAS/bin/prd/jquery/download/276264.1.1.tar.gz Closing, moved this to the new repo for templates instead: https://github.com/iodepo/odis-in/pull/18