Discussion #2333

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

Use Case C - Extend existing codelist

Added by Christian Ansorge over 4 years ago. Updated over 4 years ago.

Status:New
Priority:Normal
Assignee:Christian Ansorge

Description

Use Case C builds on the already finished search process which identified codelists which still needs adoptions to fit for purpose. The goal of this use case is to register a extended or updated code list within the registry federation which is referable for the creating data provider but also for other users.

 

Use Case C - Extend existing codelist

Name Extend existing codelist
Primary Actor INSPIRE Data Provider
Goal Update or extend an existing codelist within a register.
System under consideration WFS and/or predefined dataset; Registry federation
Importance high
Description A data provider can reuse an existing codelist within the registry but still has to update or extend it. For that purpose the provider accesses a registry entry point to extend the codelist, link it with other codelists and to refer to it from its data sets. 
Pre-Condition Registry federation is operative; Suitable codelists discoverable (Use Case A)
Post-Condition Data provider refers within it's data sets to newly extended codelist 

 

Use Case C - Flow of Events
Step 1

Data provider enters registry entry point

Step 2 Codelist is identified and accessed within a registry of the federation
Step 3 Codelist is extended or updated
Step 4 Extended or updated codelist is stored within the registry
Step 5 Data Provider receives identification and location of updated or extended codelist
Step 6 Data provider refers within it's data sets to newly extended codelist 

History

#1 Updated by Michael Lutz over 4 years ago

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

Also available in: Atom PDF