Registry Workshop 2024‐01‐23

Agenda

Question about what "registry-sweepers" is
- Reviewed Registry Sweepers README on GitHub
How the transition from current registry to multi-tenant is going to happen ? For some time both are going to run in parallel and be synchronized, until the older version will be stopped, at which point the node will need to have their registry tools (harvest, registry-mgr) to be updated.
What is the reference to identify missing products in the registry ? It is the legacy registry managed by Richard Chen at Engineering Node. The legacy registry will be maintained for at least one more year.
At GEO node, the versions of the products are incremented in place (they override the existing label) and Dan says they might miss loading some versions because there might be multiple increments in between one registry load cycle. Jordan says the original copy should be preserved (i.e. not only in the registry). Nucleus should help to trigger the loading process whenever a product is updated.
Some products are in lean resolution status, when we loaded it but we know the product needs update. The definition of archive status is extensible but there is not standard/agreement on what it is. So far we manage the information useful for the registry to handle the publication of the products (staged, archived, certified).
Tickets of Pat on harvest. Jordan is going to triage them.