wmo-im / tt-nwpmd

2 stars 2 forks source link

Notification mechanism on updated data #9

Closed hhaddouch closed 10 months ago

hhaddouch commented 1 year ago

Need to clarify the mechanism of notification for a new version of a data file (e.g. in case published data files need to be replaced). The idea is to identify how users can be notified that a new version (corrective) version of data is published. On the GTS for observation data, we have this information(corrective) in the header. In WIS2 we can mention something like "correction" in the message!!

26 Juin 2023

DECISION

sebvi commented 1 year ago

The versioning will be part of the additional metadata but not part of the hierarchy. We could use version=1, version=2, etc.

amilan17 commented 1 year ago

@sebvi additional metadata can live in the notification message or in WMO Core Medata (WCMP2)

ThomasColemanBoM commented 1 year ago

The versioning will be part of the additional metadata but not part of the hierarchy. We could use version=1, version=2, etc.

I agree that numeric version would be better than a string. There may be situations where the same fields could be sent multiple times with updates.

yhe-wmo commented 1 year ago

@sebvi suggested that apart from the keyword on versioning, it will be helpful to have another keyword to say what was the problem in the previous version.

tomkralidis commented 1 year ago

FYI PR in https://github.com/wmo-im/wis2-notification-message/pull/48 to add an operation type to identify if a resource has been created (default), updated or deleted.

amilan17 commented 11 months ago

for WNM approach: wmo-im/wis2-notification-message#47 and https://wmo-im.github.io/wis2-notification-message/standard/wis2-notification-message-DRAFT.html#_links

for WCMP2 approach: https://wmo-im.github.io/wcmp2/standard/wcmp2-DRAFT.html#_properties_record_update_date

golfvert commented 10 months ago

Close ?

yhonda21 commented 10 months ago

NWPMD meeting on 2023.09.14