Object Configuration (Draft)
Object Configuration illustrates how the engineering objects are used for supporting the functionalities commonly shared among more than one RI such as Identification and Citation, Curation, Cataloguing Configurations, Processing, and Provenance.
Cataloguing Configurations
There are seven cataloguing processes (D8.3) which need to be supported using EV objects. These basic EV configurations are mapped to these processes in Table 01. As shown in the table, the combination of these basic configurations allows supporting different cataloguing processes.
| Processes (User Stories/Requirements) (Stage 1 Description) | Configuration Name |
|---|---|
| 1. Store an asset (e.g. dataset) with metadata sufficient for cataloging purposes; | Store Asset Configuration |
| 2. Discover an asset using the metadata – the richer the metadata and the more elaborate the query the greater the precision in discovering the required asset(s); | Discover Asset Configuration |
| 3. Download an asset based on metadata | Download Asset Configuration |
| 4. Select/project an asset in situ location accessed via metadata | Select Asset Configuration |
| 5. Move (selected parts of) asset to location accessed via metadata | Move Asset Configuration |
| 6. Compose (selected parts of) asset into workflow accessed via metadata | Compose Asset Configuration |
| 7. Update an asset and/or metadata | Update Asset Configuration |
This section define set of seven independent cataloguing services that support each process on Table 01. This clearly separates the functionalities vertically and shows how the BEOs interact with each other. The structure of the following configurations is based on the Container Structure.
In addtion to the EV BEOs all the configurations require a management component object and a catalogue system object. These engineering objects together with the collection of configurations conform the complete catalogue service.
