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

temporalCoverage congruence #16

Open
gastil opened this issue Jul 13, 2018 · 0 comments
Open

temporalCoverage congruence #16

gastil opened this issue Jul 13, 2018 · 0 comments

Comments

@gastil
Copy link
Collaborator

gastil commented Jul 13, 2018

There is already a suggested check in the spreadsheet (https://docs.google.com/spreadsheets/d/14r-74onIKdq2oUmn5U7itX5bfBkfJ16_BhaqTEaul74/) sticky row 82 for endDate not being in the future. This is different. I suggest comparing the range of dates in dataTables (of dateTime data type) to the asserted temporalCoverage calendarDate beginDate and endDate to warn if these are not congruent.

See for example https://portal.lternet.edu/nis/metadataviewer?packageid=knb-lter-sbc.101.1 has beginDate of 1884-03-23 where Margaret meant 1984-03-23. A warn would have caught that typo.

This check could get over complicated. A simplified scope might be to only apply this check when a single pair of beginDate and endDate are provided at the entity level, comparing to the union of all dataTables. Or only warn when a dataTable exceeds the range, not just does not fill the range of dates. In that case knb-lter-sbc.101.1 would not have been flagged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant