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

Consideration of properties.datetime in duplicate checking #70

Open
josusky opened this issue Oct 10, 2024 · 0 comments
Open

Consideration of properties.datetime in duplicate checking #70

josusky opened this issue Oct 10, 2024 · 0 comments

Comments

@josusky
Copy link

josusky commented Oct 10, 2024

I am not sure if this is the right place to mention the issue, but it was raised during testing so let's start here. The current test for Global Cache expects that a a notification with the same pubtime but different datetime is considered a duplicate. I think that this is not in line with the WIS Manual on WIS, APPENDIX E: WIS2 NOTIFICATION MESSAGE. The section "1.7 Properties / Publication time" contains except other the following statement:

Ensuring pubtime is properly managed for updates and deletions is important for data and metadata download workflows. For example, an out-of-date pubtime can lead to errors for clients when managing updates or deletions in their local copies of data. An update with newer pubtime and identical datetime indicates a newer version of the data or metadata.

Moreover the section "1.11 Properties / Temporal description" makes it even clearer:

The datetime property identifies the date and time of the data (for example, when a measurement was observed). When a data or metadata is updated or deleted, this value should identify the original data or metadata, which can be significantly different from the current time.

My conclusion is, that a notification about a data instance can be a duplicate only if it has the same datetime and the same or older pubtime.

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