Skip to content
New issue

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

Recommendation on specifying dateModified for Datasets #67

Closed
datadavev opened this issue Dec 20, 2019 · 2 comments · Fixed by #137
Closed

Recommendation on specifying dateModified for Datasets #67

datadavev opened this issue Dec 20, 2019 · 2 comments · Fixed by #137
Assignees
Labels
accepted decision Issues on which a decision was accepted for release. enhancement New feature or request Update Documentation updates to the guidance docs
Milestone

Comments

@datadavev
Copy link
Collaborator

Knowledge of when a SO:Dataset resource or any of the components have changed is helpful for consumers to keep up to date with content changes. Harvesters should receive modification information early in harvesting workflows to make determinations of further work required. An end user of a Dataset should be informed of when a specific component of a Dataset might have been updated.

Modification dates can be specified in several locations, for example:

  • Sitemap feed, e.g. <lastmod>2019-01-01T21:14:10+00:00</lastmod>
  • Schema.org markup, e.g. "dateModified":"2019-01-01T21:14:10+00:00"
  • Within referenced SO:Dataset components, e.g. somewhere in ISO metadata: <gco:DateTime>2019-01-01T21:14:10+00:00</gco:DateTime>

A suggested guideline for publishers:

  1. Specific metadata date modified properties stored in data set components should be indicative of the modification date of the resource.
  2. If specific components of a dataset are referenced by a SO:Dataset, then a dateModified property should be included in the reference to the resource. For example:
...
"@type":"Dataset",
"subjectOf":{
  "@id":"./metadata.xml",
  "@type": "MediaObject",
  "dateModified": "2019-01-01T21:14:10+00:00",
  "contentUrl": "https://mydata.org/dataset/metadata.xml",
  ...
}
...
  1. The lastmod entry in a sitemap should be indicative of the most recent modified date that appears in the SO:Dataset
  2. Header information returned in the HTTP request for the sitemap should be indicative of when the sitemap was last updated.

In all cases, dates should include timezone information.

@mbjones mbjones added enhancement New feature or request Update Documentation updates to the guidance docs labels Jan 7, 2020
@mbjones mbjones added this to the ESIP Winter Meeting milestone Jan 7, 2020
@ashepherd
Copy link
Member

Decision at ESIP Winter Meeting to add dateModified to the guidance docs for Datasets and all related data and metadata files.

See: https://docs.google.com/document/d/1ycG9Dlt6xRr9wxjqkQrPkJQJvm83E34eue_cxkrSGUI/edit?ts=5e1503e3#bookmark=id.d98whfcn9b84

@mbjones mbjones modified the milestones: ESIP Winter Meeting, v1.2 Feb 28, 2020
@fils
Copy link
Collaborator

fils commented Mar 2, 2020

@datadavev , it would be good if this date in the JSON-LD was something the facility could use directly in creating the site. I see you mentioning just that.. but I just wanted to add my +1 to this point.

Sitemaps follow:
https://www.w3.org/TR/NOTE-datetime

This way facilities could use this for generating the sitemaps.

@ashepherd ashepherd self-assigned this Apr 6, 2020
@mbjones mbjones added the accepted decision Issues on which a decision was accepted for release. label Jan 22, 2021
@mbjones mbjones linked a pull request Jan 28, 2021 that will close this issue
@ashepherd ashepherd mentioned this issue Jan 29, 2021
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepted decision Issues on which a decision was accepted for release. enhancement New feature or request Update Documentation updates to the guidance docs
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants