SDMX Registries and duplicate artefact identifiers

[dbarr99]

Create a guideline recommendation to at least:

• avoid having the same identifier for different artefacts in different registries
• recommend where to store different types of artefacts (global, shared, local)
• provide guidance on how to document artefacts for user-friendly documentation in registries

Previous drafts on this issue:

• (2015) Recommendations on Avoiding Duplication of Content in Multiple SDMX Registries https://community.oecd.org/message/32716#32716
• (2018) ISSUE NOTE ON SDMX REGISTRIES https://community.oecd.org/thread/19882

[dbarr99]

Proposal solution (all 3 required):

1. the local MA artefacts in the GR being moved to the local registry and referenced from there, not duplicated in the GR. Any collisions will presumably be detected on upload to the local registry
2. changing the MA of the GR artefact to the project’s ownership group
3. MA ID needs to be globally unique and assigned to a specific registry

[dbarr99]

Zlatina will post the ECB information on how they deal with this

[dbarr99]

Have a "best-fit" solution when MA IDs cannot be changed.