Discussion #2435

Use case A-1: Retrieve (the ids of) all known extensions of a given register (item)

Added by Christian Ansorge over 4 years ago.

Status:New
Priority:Normal
Assignee:-

Description

Use case A-1: Retrieve (the ids of) all known extensions of a given register (item)

Name     Retrieve (the ids of) all known extensions of a given register (item)
Primary Actor  A federation user
Goal     Find out which extensions to a given register (item) exist within the whole federation.
Importance high
Description The federation user submits the unique identifier of a register (item) to the federation registry (or the registry containing the given register (item)) and requests the list of known extensions of that register (item).
Pre-Condition The register (item) has previously been registered in the federation.
Post-Condition (none)
Retrieve (the ids of) all known extensions of a given register (item) - Flow of events (request against the federation register)
Step 1 The federation user submits a request for all known extensions of a register (item) including the register (item)'s unique identifier to the federation registry. The request can be submitted through the registry's user interface or API.
Step 2 The federation registry returns a list of unique ids and access points and basic metadata (label, description, register manager) of the extensions of the given register (item).

Retrieve (the ids of) all known extensions of a given register (item) - Alternative flow of events (request against the registry containing the register)

Step 1 The federation user submits a request for all known extensions of a register (item) including the register (item)'s unique identifier to the registry containing the register. The request can be submitted through the registry's user interface or API.
Step 2

The registry forwards the request to the federation registry and retrieves the list of unique ids and access points and basic metadata (label, description, register manager) of the extensions of the given register (item). 

 

Alternatively, the registry can regularly harvest and locally cache extension information from the federation registry, in order to avoid having to request this information every time there is a request

Step 3 The registry returns the list of extension information to the requester.

Also available in: Atom PDF