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.

The presentation is divided in three parts: Basic Service Configurations, 

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 EVOCTable01 Table 01. As shown in the table, the combination of these basic configurations allows supporting different cataloguing processes.

This section define set of seven independent cataloguing services that support each process on  EVOCTable01. 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).

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

The configuration for storing a new asset depends on six BEOs:  Engineering Objects (Draft)#catalogue service,  data transfer service ,  Engineering Objects (Draft)#raw data collector,  Engineering Objects (Draft)#data importer,  Engineering Objects (Draft)#pid manager, and  Engineering Objects (Draft)#data store controller. 

The figures on the right shows the configuration of the service using the recommended  Container Structure (Draft).

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

The configuration for discovering an asset depends on three BEOs:  Engineering Objects (Draft)#catalogue service,  Engineering Objects (Draft)#pid manager, and  Engineering Objects (Draft)#data store controller. 

The figures on the right shows the configuration of the service using the recommended  Container Structure (Draft).

This configuration shows a self contained service which already contains the required objects for supporting the discovery process.

Download Asset Configuration

The configuration for storing a new asset depends on five BEOs:  Engineering Objects (Draft)#catalogue service,  data transfer service ,  Engineering Objects (Draft)#data exporter Engineering Objects (Draft)#pid manager, and  Engineering Objects (Draft)#data store controller 

The figures on the right shows the configuration of the service using the recommended  Container Structure (Draft).

This configuration shows a self contained service which already contains the required objects for supporting the discovery process.

Select Asset Configuration

The configuration for selecting an asset depends on five BEOs:  Engineering Objects (Draft)#catalogue service,  coordination service ,  Engineering Objects (Draft)#process controller,  Engineering Objects (Draft)#pid manager, and  Engineering Objects (Draft)#data store controller 

The figures on the right shows the configuration of the service using the recommended  Container Structure (Draft).

This configuration shows a self contained service which already contains the required objects for supporting the discovery process.

Move Asset Configuration

The configuration for moving an asset depends on seven BEOs:  Engineering Objects (Draft)#catalogue service,  data transfer service ,  Engineering Objects (Draft)#data exporter Engineering Objects (Draft)#pid manager,  Engineering Objects (Draft)#data store controller,  coordination service , and  Engineering Objects (Draft)#process controller,

The figures on the right shows the configuration of the service using the recommended  Container Structure (Draft).

This configuration shows a self contained service which already contains the required objects for supporting the move asset process.

Compose Asset Configuration

The configuration for composing existing assets depends on seven BEOs:  Engineering Objects (Draft)#catalogue service,  data transfer service ,  Engineering Objects (Draft)#data exporter Engineering Objects (Draft)#pid manager,  Engineering Objects (Draft)#data store controller,  coordination service , and  Engineering Objects (Draft)#process controller,

The figures on the right shows the configuration of the service using the recommended  Container Structure (Draft).

This configuration shows a self contained service which already contains the required objects for supporting the compose asset process.

Update Asset Configuration

The configuration for discovering an asset depends on four BEOs:  Engineering Objects (Draft)#catalogue service, Engineering Objects (Draft)#ann,  Engineering Objects (Draft)#pid manager, and  Engineering Objects (Draft)#data store controller. 

The figures on the right shows the configuration of the service using the recommended  Container Structure (Draft).

This configuration shows a self contained service which already contains the required objects for supporting the discovery process.