Difference between revisions of "Object Configuration (Draft)"
(5 intermediate revisions by the same user not shown) | |||
Line 11: | Line 11: | ||
! style="padding: 10px"| <span style="color: #BBCE00">'''Processes (User Stories/Requirements) (Stage 1 Description)'''</span> !! <span style="color: #BBCE00">'''Configuration Name'''</span> | ! style="padding: 10px"| <span style="color: #BBCE00">'''Processes (User Stories/Requirements) (Stage 1 Description)'''</span> !! <span style="color: #BBCE00">'''Configuration Name'''</span> | ||
|- | |- | ||
− | | 1. Store an asset (e.g. dataset) with metadata sufficient for cataloging purposes; || '''Store Asset Configuration''' | + | | 1. Store an asset (e.g. dataset) with metadata sufficient for cataloging purposes; || [[Object Configuration (Draft)#Store Asset Configuration|'''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''' | + | | 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); || [[Object Configuration (Draft)#Discover Asset Configuration|'''Discover Asset Configuration''']] |
|- | |- | ||
− | | 3. Download an asset based on metadata || '''Download Asset Configuration''' | + | | 3. Download an asset based on metadata || [[Object Configuration (Draft)#Download Asset Configuration|'''Download Asset Configuration''']] |
|- | |- | ||
− | | 4. Select/project an asset in situ location accessed via metadata || '''Select Asset Configuration''' | + | | 4. Select/project an asset in situ location accessed via metadata || [[Object Configuration (Draft)#Select Asset Configuration|'''Select Asset Configuration''']] |
|- | |- | ||
− | | 5. Move (selected parts of) asset to location accessed via metadata || '''Move Asset Configuration''' | + | | 5. Move (selected parts of) asset to location accessed via metadata || [[Object Configuration (Draft)#Move Asset Configuration|'''Move Asset Configuration''']] |
|- | |- | ||
− | | 6. Compose (selected parts of) asset into workflow accessed via metadata || '''Compose Asset Configuration''' | + | | 6. Compose (selected parts of) asset into workflow accessed via metadata || [[Object Configuration (Draft)#Compose Asset Configuration|'''Compose Asset Configuration''']] |
|- | |- | ||
− | | 7. Update an asset and/or metadata || '''Update Asset Configuration''' | + | | 7. Update an asset and/or metadata || [[Object Configuration (Draft)#Update Asset Configuration|'''Update Asset Configuration''']] |
|} | |} | ||
</div> | </div> | ||
Line 36: | Line 36: | ||
|- | |- | ||
| style="width: 65%; vertical-align: top; padding: 10px 10px 10px 10px"| | | style="width: 65%; vertical-align: top; padding: 10px 10px 10px 10px"| | ||
− | The configuration for storing a new asset depends on six BEOs: catalogue service, data transfer service, raw data collector, data importer, | + | The configuration for storing a new asset depends on six BEOs: [[Engineering Objects (Draft)#catalogue service|'''catalogue service''']], [[Engineering Objects (Draft)#data transfer service|'''data transfer service''']], [[Engineering Objects (Draft)#raw data collector|'''raw data collector''']], [[Engineering Objects (Draft)#data importer|'''data importer''']], [[Engineering Objects (Draft)#pid manager|'''pid manager''']], and [[Engineering Objects (Draft)#data store controller|'''data store controller''']]. |
− | The figures on the right shows the configuration of the service using the recommended | + | The figures on the right shows the configuration of the service using the recommended [[Container Structure (Draft)|'''Container Structure''']]. |
This configuration shows a self contained service which already contains the required objects for three possible service variations: collect from sensor, import from another repository, and assign global unique pid. | This configuration shows a self contained service which already contains the required objects for three possible service variations: collect from sensor, import from another repository, and assign global unique pid. | ||
Line 76: | Line 76: | ||
|- | |- | ||
| style="width: 65%; vertical-align: top; padding: 10px 10px 10px 10px"| | | style="width: 65%; vertical-align: top; padding: 10px 10px 10px 10px"| | ||
− | The configuration for discovering an asset depends on three BEOs: | + | The configuration for discovering an asset depends on three BEOs: [[Engineering Objects (Draft)#catalogue service|'''catalogue service''']], [[Engineering Objects (Draft)#pid manager|'''pid manager''']], and [[Engineering Objects (Draft)#data store controller|'''data store controller''']]. |
− | The figures on the right shows the configuration of the service using the recommended | + | The figures on the right shows the configuration of the service using the recommended [[Container Structure (Draft)|'''Container Structure''']]. |
This configuration shows a self contained service which already contains the required objects for supporting the discovery process. | This configuration shows a self contained service which already contains the required objects for supporting the discovery process. | ||
Line 117: | Line 117: | ||
|- | |- | ||
| style="width: 65%; vertical-align: top; padding: 10px 10px 10px 10px"| | | style="width: 65%; vertical-align: top; padding: 10px 10px 10px 10px"| | ||
− | The configuration for storing a new asset depends on five BEOs: catalogue service, data transfer service, data exporter, pid manager, and | + | The configuration for storing a new asset depends on five BEOs: [[Engineering Objects (Draft)#catalogue service|'''catalogue service''']], [[Engineering Objects (Draft)#data transfer service|'''data transfer service''']], [[Engineering Objects (Draft)#data exporter|'''data exporter''']], [[Engineering Objects (Draft)#pid manager|'''pid manager''']], and [[Engineering Objects (Draft)#data store controller|'''data store controller''']] |
− | The figures on the right shows the configuration of the service using the recommended | + | The figures on the right shows the configuration of the service using the recommended [[Container Structure (Draft)|'''Container Structure''']]. |
This configuration shows a self contained service which already contains the required objects for supporting the discovery process. | This configuration shows a self contained service which already contains the required objects for supporting the discovery process. | ||
Line 152: | Line 152: | ||
[[File:EVCSDownloadAsset.png|290px]] | [[File:EVCSDownloadAsset.png|290px]] | ||
|} | |} | ||
+ | |||
+ | === <span style="color: #BBCE00">Select Asset Configuration</span> === | ||
+ | |||
+ | {| style="width: 85%;" | ||
+ | |- | ||
+ | | style="width: 65%; vertical-align: top; padding: 10px 10px 10px 10px"| | ||
+ | The configuration for selecting an asset depends on five BEOs: [[Engineering Objects (Draft)#catalogue service|'''catalogue service''']], [[Engineering Objects (Draft)#coordination service|'''coordination service''']], [[Engineering Objects (Draft)#process controller|'''process controller''']], [[Engineering Objects (Draft)#pid manager|'''pid manager''']], and [[Engineering Objects (Draft)#data store controller|'''data store controller''']] | ||
+ | |||
+ | The figures on the right shows the configuration of the service using the recommended [[Container Structure (Draft)|'''Container Structure''']]. | ||
+ | |||
+ | This configuration shows a self contained service which already contains the required objects for supporting the discovery process. | ||
+ | |||
+ | {| class="wikitable" | ||
+ | |- | ||
+ | ! <div style='text-align: left;'>'''<span style="color: #BBCE00">Name:</span>'''</div> | ||
+ | | Select Asset | ||
+ | |- | ||
+ | ! <div style='text-align: left;'>'''<span style="color: #BBCE00">Process:</span>'''</div> | ||
+ | | Select/project an asset in situ location accessed via metadata | ||
+ | |- | ||
+ | ! <div style='text-align: left;'>'''<span style="color: #BBCE00">Resources</span>'''</div> | ||
+ | | | ||
+ | * asset pid (precondition: discovery) | ||
+ | * filtering parameters (metadata, optional) | ||
+ | |- | ||
+ | ! <div style='text-align: left;'>'''<span style="color: #BBCE00">Outputs</span>'''</div> | ||
+ | | | ||
+ | * asset (processed view) | ||
+ | * metadata | ||
+ | ** asset pid | ||
+ | ** asset reference (publishable) | ||
+ | ** asset description | ||
+ | ** asset view details | ||
+ | |- | ||
+ | ! <div style='text-align: left;'>'''<span style="color: #BBCE00">Options</span>'''</div> | ||
+ | | | ||
+ | * select | ||
+ | * project | ||
+ | |} | ||
+ | | style="width: 35%; vertical-align: top; padding: 10px 10px 10px 25px"| | ||
+ | [[File:EVCSSelectAsset.png|290px]] | ||
+ | |} | ||
+ | |||
+ | === <span style="color: #BBCE00">Move Asset Configuration</span> === | ||
+ | |||
+ | {| style="width: 85%;" | ||
+ | |- | ||
+ | | style="width: 65%; vertical-align: top; padding: 10px 10px 10px 10px"| | ||
+ | The configuration for moving an asset depends on seven BEOs: [[Engineering Objects (Draft)#catalogue service|'''catalogue service''']], [[Engineering Objects (Draft)#data transfer service|'''data transfer service''']], [[Engineering Objects (Draft)#data exporter|'''data exporter''']], [[Engineering Objects (Draft)#pid manager|'''pid manager''']], [[Engineering Objects (Draft)#data store controller|'''data store controller''']], [[Engineering Objects (Draft)#coordination service|'''coordination service''']], and [[Engineering Objects (Draft)#process controller|'''process controller''']]. | ||
+ | |||
+ | The figures on the right shows the configuration of the service using the recommended [[Container Structure (Draft)|'''Container Structure''']]. | ||
+ | |||
+ | This configuration shows a self contained service which already contains the required objects for supporting the move asset process. | ||
+ | |||
+ | {| class="wikitable" | ||
+ | |- | ||
+ | ! <div style='text-align: left;'>'''<span style="color: #BBCE00">Name:</span>'''</div> | ||
+ | | Move Asset | ||
+ | |- | ||
+ | ! <div style='text-align: left;'>'''<span style="color: #BBCE00">Process:</span>'''</div> | ||
+ | | Move (selected parts of) asset to location accessed via metadata | ||
+ | |- | ||
+ | ! <div style='text-align: left;'>'''<span style="color: #BBCE00">Resources</span>'''</div> | ||
+ | | | ||
+ | * asset pid (precondition: discovery) | ||
+ | * filtering parameters (metadata, optional) | ||
+ | |- | ||
+ | ! <div style='text-align: left;'>'''<span style="color: #BBCE00">Outputs</span>'''</div> | ||
+ | | | ||
+ | * asset (partial or completely relocated) | ||
+ | * metadata | ||
+ | ** asset pid | ||
+ | ** asset reference (publishable) | ||
+ | ** asset description | ||
+ | |- | ||
+ | ! <div style='text-align: left;'>'''<span style="color: #BBCE00">Options</span>'''</div> | ||
+ | | | ||
+ | * move complete (delete original) | ||
+ | * move partial (delete partial) | ||
+ | |} | ||
+ | | style="width: 35%; vertical-align: top; padding: 10px 10px 10px 25px"| | ||
+ | [[File:EVCSMoveAsset.png|320px]] | ||
+ | |} | ||
+ | |||
+ | === <span style="color: #BBCE00">Compose Asset Configuration</span> === | ||
+ | |||
+ | {| style="width: 85%;" | ||
+ | |- | ||
+ | | style="width: 65%; vertical-align: top; padding: 10px 10px 10px 10px"| | ||
+ | The configuration for composing existing assets depends on seven BEOs: [[Engineering Objects (Draft)#catalogue service|'''catalogue service''']], [[Engineering Objects (Draft)#data transfer service|'''data transfer service''']], [[Engineering Objects (Draft)#data exporter|'''data exporter''']], [[Engineering Objects (Draft)#pid manager|'''pid manager''']], [[Engineering Objects (Draft)#data store controller|'''data store controller''']], [[Engineering Objects (Draft)#coordination service|'''coordination service''']], and [[Engineering Objects (Draft)#process controller|'''process controller''']]. | ||
+ | |||
+ | The figures on the right shows the configuration of the service using the recommended [[Container Structure (Draft)|'''Container Structure''']]. | ||
+ | |||
+ | This configuration shows a self contained service which already contains the required objects for supporting the compose asset process. | ||
+ | |||
+ | {| class="wikitable" | ||
+ | |- | ||
+ | ! <div style='text-align: left;'>'''<span style="color: #BBCE00">Name:</span>'''</div> | ||
+ | | Compose Asset | ||
+ | |- | ||
+ | ! <div style='text-align: left;'>'''<span style="color: #BBCE00">Process:</span>'''</div> | ||
+ | | Compose (selected parts of) asset into workflow accessed via metadata. | ||
+ | |- | ||
+ | ! <div style='text-align: left;'>'''<span style="color: #BBCE00">Resources</span>'''</div> | ||
+ | | | ||
+ | * asset pid (precondition: discovery) | ||
+ | * filtering parameters (metadata, optional) | ||
+ | * destination parameters | ||
+ | * scheduling parameters | ||
+ | |- | ||
+ | ! <div style='text-align: left;'>'''<span style="color: #BBCE00">Outputs</span>'''</div> | ||
+ | | | ||
+ | * asset (copy, partial or complete) | ||
+ | * metadata | ||
+ | ** asset pid | ||
+ | ** asset reference (publishable) | ||
+ | ** asset description | ||
+ | |- | ||
+ | ! <div style='text-align: left;'>'''<span style="color: #BBCE00">Options</span>'''</div> | ||
+ | | | ||
+ | * compose complete | ||
+ | * compose partial | ||
+ | |} | ||
+ | | style="width: 35%; vertical-align: top; padding: 10px 10px 10px 25px"| | ||
+ | [[File:EVCSComposeAsset.png|320px]] | ||
+ | |} | ||
+ | |||
+ | === <span style="color: #BBCE00">Update Asset Configuration</span> === | ||
+ | |||
+ | {| style="width: 85%;" | ||
+ | |- | ||
+ | | style="width: 65%; vertical-align: top; padding: 10px 10px 10px 10px"| | ||
+ | The configuration for discovering an asset depends on four BEOs: [[Engineering Objects (Draft)#catalogue service|'''catalogue service''']], '''annotation service''', [[Engineering Objects (Draft)#pid manager|'''pid manager''']], and [[Engineering Objects (Draft)#data store controller|'''data store controller''']]. | ||
+ | |||
+ | The figures on the right shows the configuration of the service using the recommended [[Container Structure (Draft)|'''Container Structure''']]. | ||
+ | |||
+ | This configuration shows a self contained service which already contains the required objects for supporting the discovery process. | ||
+ | |||
+ | {| class="wikitable" | ||
+ | |- | ||
+ | ! <div style='text-align: left;'>'''<span style="color: #BBCE00">Name:</span>'''</div> | ||
+ | | Discover Asset | ||
+ | |- | ||
+ | ! <div style='text-align: left;'>'''<span style="color: #BBCE00">Process:</span>'''</div> | ||
+ | | Update an asset and/or metadata | ||
+ | |- | ||
+ | ! <div style='text-align: left;'>'''<span style="color: #BBCE00">Resources</span>'''</div> | ||
+ | | | ||
+ | * asset pid | ||
+ | * update parameters (metadata) | ||
+ | * asset (complement or replacement) | ||
+ | |- | ||
+ | ! <div style='text-align: left;'>'''<span style="color: #BBCE00">Outputs</span>'''</div> | ||
+ | | | ||
+ | * metadata | ||
+ | ** asset pid | ||
+ | ** asset reference (publishable) | ||
+ | ** asset description | ||
+ | |- | ||
+ | ! <div style='text-align: left;'>'''<span style="color: #BBCE00">Optionsup</span>'''</div> | ||
+ | | | ||
+ | * update metadata only | ||
+ | * annotate asset | ||
+ | * annotate metadata | ||
+ | * update global pid | ||
+ | |} | ||
+ | | style="width: 35%; vertical-align: top; padding: 10px 10px 10px 25px"| | ||
+ | [[File:EVCSUpdateAsset.png|320px]] | ||
+ | |} | ||
+ | |||
[[Category:Engineering Viewpoint (Draft)]] | [[Category:Engineering Viewpoint (Draft)]] |
Latest revision as of 00:45, 29 March 2020
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.
Contents
Cataloguing Configurations[edit]
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.
Store Asset Configuration[edit]
The configuration for storing a new asset depends on six BEOs: catalogue service, data transfer service, raw data collector, data importer, pid manager, and data store controller. The figures on the right shows the configuration of the service using the recommended Container Structure. This configuration shows a self contained service which already contains the required objects for three possible service variations: collect from sensor, import from another repository, and assign global unique pid.
|
Discover Asset Configuration[edit]
The configuration for discovering an asset depends on three BEOs: catalogue service, pid manager, and data store controller. The figures on the right shows the configuration of the service using the recommended Container Structure. This configuration shows a self contained service which already contains the required objects for supporting the discovery process.
|
Download Asset Configuration[edit]
The configuration for storing a new asset depends on five BEOs: catalogue service, data transfer service, data exporter, pid manager, and data store controller The figures on the right shows the configuration of the service using the recommended Container Structure. This configuration shows a self contained service which already contains the required objects for supporting the discovery process.
|
Select Asset Configuration[edit]
The configuration for selecting an asset depends on five BEOs: catalogue service, coordination service, process controller, pid manager, and data store controller The figures on the right shows the configuration of the service using the recommended Container Structure. This configuration shows a self contained service which already contains the required objects for supporting the discovery process.
|
Move Asset Configuration[edit]
The configuration for moving an asset depends on seven BEOs: catalogue service, data transfer service, data exporter, pid manager, data store controller, coordination service, and process controller. The figures on the right shows the configuration of the service using the recommended Container Structure. This configuration shows a self contained service which already contains the required objects for supporting the move asset process.
|
Compose Asset Configuration[edit]
The configuration for composing existing assets depends on seven BEOs: catalogue service, data transfer service, data exporter, pid manager, data store controller, coordination service, and process controller. The figures on the right shows the configuration of the service using the recommended Container Structure. This configuration shows a self contained service which already contains the required objects for supporting the compose asset process.
|
Update Asset Configuration[edit]
The configuration for discovering an asset depends on four BEOs: catalogue service, annotation service, pid manager, and data store controller. The figures on the right shows the configuration of the service using the recommended Container Structure. This configuration shows a self contained service which already contains the required objects for supporting the discovery process.
|