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

DCAT-US modified element missing when data do not contain update date #286

Open
hmaier-fws opened this issue Sep 13, 2023 · 1 comment
Open
Assignees
Labels
discussion Issue for discussion by stakeholder group writer:dcat-us Data.gov DCAT-US Schema

Comments

@hmaier-fws
Copy link

hmaier-fws commented Sep 13, 2023

Modified element missing as test data did not include revisions or updates, only
original publication. This is a required field therefore logic should probably include
whatever date is there for the primary citation if there are no revisions or updates.

Originally posted by @dwalt in #264 (comment)

@hmaier-fws hmaier-fws added discussion Issue for discussion by stakeholder group writer:dcat-us Data.gov DCAT-US Schema labels Sep 13, 2023
@hmaier-fws
Copy link
Author

@dwalt I agree. The DCAT-US modified field is described as:

Most recent date on which the dataset was changed, updated or modified.

Since DCAT-US does not distinguish between an initial creation date and any subsequent modification dates, then a creation date would be a valid choice.

Although, not all dates might be valid choices. The dateType codelist contains items such as: "next update", "unavailable", and a few others.

We might want to consider applying a preferential hierarchy to a selected subset of date types. E.g.:

  • lastUpdate, description: "date identifies when resource was last updated
  • revision, description: "date identifies when the resource was examined or re-examined and improved or amended"
  • creation, description: "date identifies when the resource was brought into existence"
  • others??

I'm also guessing that many staff will use (inappropriately) lastRevision which should be used since that "date identifies when resource was last reviewed", which does not imply that an update was actually made. Not sure what we want to do with that. (my preference is for fairly strict adherence to definitions)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion Issue for discussion by stakeholder group writer:dcat-us Data.gov DCAT-US Schema
Projects
None yet
Development

No branches or pull requests

3 participants