GDC - Clarification of the scope of functions

[antje-s]

Currently, I would assume that the publication flow for new metadata is as follows:
VARIANT A

1. WIS2 Node creates new metadata
2. WIS2 Node makes metadata file available via web service (at least for GC addresses)
3. WIS2 Node publishes notification of the new metadata file to its own, local MQTT broker under topic ‘origin’
4. Global Broker (GB) receives notification from the local broker and distributes the notification to subscribed Global Caches (GC)
5. GC loads metadata file from local web service into its cache and publishes customised notification under "cache" topic to its own MQTT broker
6. Global Broker (GB) receives notification from the local GC broker and distributes the notification to subscribed Global Discovery Centres
7. GDC loads metadata file from GC web service, validates and imports it and sends a report under “monitor” topic to center-id from metadata file
8. In my opinion, GDC should then also publish a notification (with rel=update) for the adjusted metadata file under topic “origin” to the local GDC broker
9. GB receives this notification and the subscribed GC receive it like this
10. GC loads the customized metadata record from the GDC into its cache and sends a notification under “cache” topic to the local GC broker
11. GB receives the “cache” notification from the GC broker and distributes it
    OR
    VARIANT B
    Only 1) to 7) from VARIANT A
    In this case, only GDCs and GCs should be allowed to subscribe to topic metadata and
    access to metadata via GC data servers should be restricted so that only GDCs are allowed to download it

Under
https://wmo-im.github.io/wis2-guide/guide/wis2-guide-DRAFT.html#_2_7_5_global_discovery_catalogue
the sentence
"The Global Discovery Catalogue advertises the availability of datasets and how to access them or subscribe to updates."
part "...or subscribe to updates" revised accordingly - depending on the variant.

[antje-s]

related to wmo-im/wis2-global-services-testing#27

[antje-s]

Alternatively, instead of the real local MQTT broker endpoint in the links (rel=‘items’), we could simply use a specified fake string, which is then replaced by the GDC with the GB endpoints. then the original metadata does not have to be specially protected