Discussion #2330

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

Use case A: Search for existing codelist

Added by Michael Lutz over 5 years ago. Updated about 5 years ago.

Status:New
Priority:Normal
Assignee:Christian Ansorge

Description

The general motivation for Use Case A, B and C comes from the INSPIRE Directive which requires from data providers to publish their data according to the INSPIRE Data Themes and following the INSPIRE Implementing Provision on Interoperability of Spatial Data Sets and Services. Depending on the data theme the use of extendable codelists might be required. In this case the data provider first has to discover already existing codelists, created by other providers, to decide for either direct reuse, adoption or newly creation of codelists.

Use Case A is therefore focusing on the discovery of codelists registered within a registry federation. This builds on the assumption that codelists has already been created by other users and the data provider aims at reusing them in the first place.  

Use Case A - Search for existing codelist
Name Search for existing codelist
Primary Actor INSPIRE Data Provider
Goal To provide INSPIRE Data with reusable and semanticly fitting description (codelist values)
System under consideration Registry federation
Importance high
Description A data provider wants to provide a dataset according to the INSPIRE data specifications which requires a extendible codelist. For that purpose the provider accesses the registry federation to discover codelist extensions (including their values) published and used by other provider before. 
Pre-Condition Registry federation is operative; Codelists of interest have been published
Post-Condition Code lists best fitting to actual content has been discovered and data provider refers to it from it's data set

 

Use Case A - Flow of Events
Step 1

Data provider enters search request in a registry entry point  

Step 2 Search request is being distributed within the registry federation and processed
Step 3 Search results are returned to the user
Step 4 Data provider evaluates results and take decision if they fit for purpose (reuse of existing codelists) or not (creation of new codelist) 
 

History

#1 Updated by Michael Lutz over 5 years ago

  • Project changed from Re3gistry development & testing to MIWP-6: Registers

#2 Updated by Christian Ansorge over 5 years ago

  • Description updated (diff)

#3 Updated by Christian Ansorge over 5 years ago

It was discussed on the last MIWP-6 web-meeting that we would distinguish between search on National and International level. But I am hesitating to create 2 different (but still almost identical) use cases based on that.

The use cases addressing the national registry search would either

  1. use the national registry entry point and therefore be out of scope as use case for the registry federation
  2. use the registry federation entry point and the national characteristic would be simply an additional search criteria within the registry

The same pattern would then consequently apply to the extension (C) and creation (B) use case as well. My suggestion is there to add another step in the existing use cases, regarding the creation of and search for certain metadata elements like the country of origin.

#4 Updated by Christian Ansorge over 5 years ago

 

Update taking into account comment #3 and the use cases on UML model / Feature Catalogue items (#2334 and #2335). :

 

Use Case A - Search for content

Name Search for existing registry content
Primary Actor INSPIRE Data Provider
Goal To discover content published within the registry federation (codelists, UML model items, feature catalogue items)
System under consideration Registry federation
Importance high
Description A data provider wants to provide a dataset according to the INSPIRE data specifications which requires among others features with are published within registries (e.g. codelists, feature catalogue or UML model items). For that purpose the provider accesses the registry federation to search for and to discover the items it is looking for. Furthermore the data provider might filter for characteristica such as the publishing country, language or the date of creation. 
Pre-Condition Registry federation is operative; Content of interest has been published; Attributes for filtering elements are available
Post-Condition Registry content the data provider was looking for has been discovered and data provider uses it to publish its data set

 

Use Case A - Flow of Events
Step 1

Data provider enters search request in a registry entry point. The search request might contain search criteria, among others the country of origin, language or date of creation.

Step 2 Search request is being distributed within the registry federation and processed
Step 3 Search results are returned to the user
Step 4 Data provider evaluates results and take decision if they fit for purpose (reuse of existing registry content) or not (creation of new codelist or feature catalogue item) 
 

#5 Updated by Michael Lutz about 5 years ago

Dear Christian, please find a number of comments on the search use case below:

  • The actor does not have to be an INSPIRE data provider. It could also be e.g. a solution provider. So we suggest to generically call the actor "registry (federation) user"
  • It is not quite clear whether you propose full text or faceted searches (based on specific fields) (or both)
  • We would suggest including some example queries and the expected results. For this we may need to define example content and register federation set-up, either based on real data (e.g. Land cover code lists) and/or dummy data (e.g. an extension of the INSPIRE themes register)
  • The queries will be different depending on where they are posted - the register of registers or a local register

Also available in: Atom PDF