Editing 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, [[Object Configuration (Draft)#Cataloguing Configurations|'''Cataloguing Configurations''']], Processing, and Provenance.

== <span style="color: #BBCE00">Cataloguing Configurations</span> ==

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 [[Object Configuration (Draft)#Table 1|'''Table 01''']]. As shown in the table, the combination of these basic configurations allows supporting different cataloguing processes.

<div style="background-color: #fcfcfc; border-radius: 5px; border: 1px solid #ccc; padding: 10px;">
{| class="wikitable sortable" style="width: 85%; margin: auto;"
|+<span id="Table 1">Table 1</span>. Basic Cataloguing Processes
|-
! 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'''
|-
| 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'''
|}
</div>

This section define set of seven independent cataloguing services that support each process on [[Object Configuration (Draft)#Table 1|'''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 (Draft)|'''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.

=== <span style="color: #BBCE00">Store Asset Configuration</span> ===

{| style="width: 85%;"
|-
| 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,  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.

{| class="wikitable"
|-
! <div style='text-align: left;'>'''<span style="color: #BBCE00">Name:</span>'''</div>
| Store Asset
|-
! <div style='text-align: left;'>'''<span style="color: #BBCE00">Process:</span>'''</div>
| Store an asset (e.g. dataset) with metadata sufficient for cataloging purposes
|-
! <div style='text-align: left;'>'''<span style="color: #BBCE00">Resources</span>'''</div>
| 
* asset 
* metadata
|-
! <div style='text-align: left;'>'''<span style="color: #BBCE00">Outputs</span>'''</div>
| 
* asset [registered]
* metadata [registered]
* asset pid [registered]
|-
! <div style='text-align: left;'>'''<span style="color: #BBCE00">Options</span>'''</div>
| 
* collect data from sensors
* import data from external source
* assign global unique pid
|}
| style="width: 35%; vertical-align: top; padding: 10px 10px 10px 25px"|
[[File:EVCSStoreAsset.png|320px]]
|}

=== <span style="color: #BBCE00">Discover 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 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.

{| 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>
| 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)
|-
! <div style='text-align: left;'>'''<span style="color: #BBCE00">Resources:</span>'''</div>
| 
* query parameters (metadata)
|-
! <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">Options:</span>'''</div>
| 
* faceted discovery (filtering of results)
|-
! <div style='text-align: left;'>'''<span style="color: #BBCE00">Correspondences</span>'''</div>
| Technology Viewpoint: [[Catalogue Discovery Object (Draft)|'''Catalogue Discovery Object''']]
|}
| style="width: 35%; vertical-align: top; padding: 10px 10px 10px 25px"|
[[File:EVCSDiscoverAsset.png|320px]]
|}

=== <span style="color: #BBCE00">Download Asset Configuration</span> ===

{| style="width: 85%;"
|-
| 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  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.

{| class="wikitable"
|-
! <div style='text-align: left;'>'''<span style="color: #BBCE00">Name:</span>'''</div>
| Download Asset
|-
! <div style='text-align: left;'>'''<span style="color: #BBCE00">Process:</span>'''</div>
| Download an asset based on 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 (copy)
* metadata
** asset pid
** asset reference (publishable)
** asset description
|-
! <div style='text-align: left;'>'''<span style="color: #BBCE00">Options</span>'''</div>
| 
* download complete
* download partial
|}
| style="width: 35%; vertical-align: top; padding: 10px 10px 10px 25px"|
[[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:  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.

{| 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:  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.

{| 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:  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.

{| 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:  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.

{| 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)]]