Discussion #2331

Discussion #2318: MIWP-6 - Identification and documentation of use cases for Registries and Registers

Use Case G: Automated propagation/dissemination of registry content updates

Added by Norbert Pfaffinger over 5 years ago. Updated over 5 years ago.

Status:New
Priority:Normal
Assignee:-

Description

 

There are the EU INSPIRE registers and the Member State registers. Based on the member state registers INSPIRE data providers may operate additional registers or "local copies". I.e., there is a tree branching down from the INSPIRE registers.

 

For code lists, further down in the tree there may be:

  • An identical copy of a parent node code list
  • A code list that is an extension of a parent code list
  • Additional code lists

When there are changes in a code list on some top level node, such as in the EU INSPIRE register, it is important to propagate such changes down the tree in a timely and efficient manner, in order to avoid data inconsistencies.

 

Not only should it be possible to automate the process of propagating registry content updates  - this prerequiste is already met. Above that, there should be clear rules and instructions on the automation of propagation - this has to be considered in the technical architecture. Without explicitly addressing this topic, there is the danger of unstable systems (unwanted amounts of polling, inconsistent and/or inefficient ways of implementation, etc.).

 

Use Case G - Automated propagation of registry content updates

Name

Automated propagation/dissemination of registry content updates

Primary Actor Member State registry operator or INSPIRE Data Provider
Goal Connect a register to a "parent" register such that certain updates in the parent register are automatically propagated into the child register
System under consideration Registry federation
Importance Medium
Description In order to enable propagation of changes in code lists or other registers applied at a higher level, such as EU INSPIRE registers, to lower levels, such as Member State registers in a timely and efficient manner, means of automation or semi-automation are provided, and there are clear rules on how to implement such automation. Child registers can be connected to parent registers such that they changes applied to the parent register are automatically propagated into the child register.
Pre-Condition Registries operative, code lists published
Post-Condition Registries are interconnected, and code lists updates (or other changes) are automatically propagated from the parent node to the child node

 

Use Case G - Flow of Events
Step 1

Member State registry operator or INSPIRE Data Provider activates automated or semi-automated propagation of changes from a parent register to a child register.

 

 

History

#1 Updated by Michael Lutz over 5 years ago

  • Project changed from Re3gistry development & testing to MIWP-6: Registers
  • Parent task set to #2318

Also available in: Atom PDF