Difference between revisions of "Engineering Objects (Draft)"
Line 164: | Line 164: | ||
|- | |- | ||
| Computational || [[CV Component Objects#Data exporter|'''data exporter''']] | | Computational || [[CV Component Objects#Data exporter|'''data exporter''']] | ||
+ | |} | ||
+ | |} | ||
+ | |||
+ | === <span style="color: #BBCE00">data importer</span> === | ||
+ | |||
+ | A basic engineering object for importing assets into the data stores. A data importer should provide six functions: retrieve asset, update records, export metadata, export asset, deliver asset. | ||
+ | |||
+ | {| style="width: 85%;" | ||
+ | |- | ||
+ | | style="width: 55%; vertical-align: top; padding: 10px 10px 10px 10px"| | ||
+ | data importer functions | ||
+ | {| class="wikitable sortable" | ||
+ | |- | ||
+ | ! '''<span style="color: #BBCE00">Function</span>''' !! '''<span style="color: #BBCE00">Description</span>''' !! | ||
+ | |||
+ | '''<span style="color: #BBCE00">Type</span>''' | ||
+ | |- | ||
+ | | retrieve asset || function provided to enable requesting data from a designated data store (inherited from [https://confluence.egi.eu/display/ERMdev/CV+Component+Objects#CVComponentObjects-data_transporter '''data transporter''']). || client | ||
+ | |- | ||
+ | | update records || function provided to inform downstream resources about impending asset transfers (inherited from [https://confluence.egi.eu/display/ERMdev/CV+Component+Objects#CVComponentObjects-data_transporter '''data transporter''']). || client | ||
+ | |- | ||
+ | | acquire identifier || function provided for requesting new persistent identifier to be associated with the data being transferred. Generally, identifiers are requested when importing new data into an infrastructure. || client | ||
+ | |- | ||
+ | | update catalogues || function for populating the catalogues with the metadata associated to the imported data assets. || client | ||
+ | |- | ||
+ | | import asset || function provided for receiving assets from a designated data store || consumer | ||
+ | |- | ||
+ | | deliver asset || function provided for delivery of assets to a designated data store. || producer | ||
+ | |} | ||
+ | | style="width: 45%; vertical-align: top; padding: 10px 10px 10px 40px"| | ||
+ | data importer correspondences | ||
+ | {| class="wikitable sortable" | ||
+ | |- | ||
+ | ! '''<span style="color: #BBCE00">Viewpoint</span>''' !! '''<span style="color: #BBCE00">Correspondence</span>''' | ||
+ | |- | ||
+ | | Science || [https://confluence.egi.eu/display/ERMdev/SV+Community+Roles#SVCommunityRoles-roles_acqRolesintheDataAcquisitionCommunity '''data acquisition subsystem'''] (role) <br>[https://confluence.egi.eu/display/ERMdev/SV+Community+Roles#SVCommunityRoles-roles_curRolesintheDataCurationCommunity '''data curation subsystem'''] (role) | ||
+ | |- | ||
+ | | Computational || [[CV Component Objects#Data importer|'''data importer''']] | ||
|} | |} | ||
|} | |} |
Revision as of 20:26, 28 March 2020
The objects described by the engineering viewpoint directly support research data management functionalities which are commonly shared among more than one RI (Identification and Citation, Curation, Cataloguing, Processing, and Provenance) [1], [2].
The engineering objects are grouped in the four top packages shown in the figure to the right: identification, catalogue, processing, and provenance, in line with the support needed for the four common data management functionalities. Two additional groups are defined to accommodate supporting objects which are needed for any working configuration: storage and data transfer. The objects included are defined as Basic Engineering Object (BEO) and provide functionalities described by CV Objects, this means that each BEO maps one to one to a CV Objects.
The grouping is not strict, these objects can be deployed side by side on a single physical machine or be distributed across network and institutional limits.
The engineering objects coupled with the Container Structure, are used to further define how the engineering objects can support the data management functionalities in different Object Configuration.
The definition of the basic engineering objects are given as follows. All of the definitions with the exception of pid manager and provenance service, are derived from the definitions of the corresponding computational viewpoint objects.
|
|
Contents
annotation service
A basic engineering object that supports the ability associate annotations (free texts and semantic) with the assets managed by a research infrastructure. An annotation service must provide three functionalites: annotate data, update catalogues and update records
Annotation service functions
|
Annotation service correspondences
|
catalogue service
A basic engineering object that supports the ability to publish and search collections of metadata (descriptive information) for assets such as data, services, and related information objects managed by a research infrastructure. A catalogue service must provide at least four functionalities: query catalogues, update catalogues, export metadata, and query resource.
Catalogue service functions
|
Catalogue service correspondences
|
coordination service
A basic engineering object that that supports the ability to coordinate data processing tasks on infrastructure execution resources. A coordination service should provide at least three functions: process request, coordinate process, create process controller, and prepare data transfer
Coordination service functions
|
Catalogue service correspondences
|
data exporter
A basic engineering object for exporting assets from the data stores. A data exporter should provide five functions: retrieve asset, update records, export metadata, export asset, deliver asset.
data exporter functions
|
data exporter correspondences
|
data importer
A basic engineering object for importing assets into the data stores. A data importer should provide six functions: retrieve asset, update records, export metadata, export asset, deliver asset.
data importer functions
|
data importer correspondences
|
- ↑ ENVRIplus. (2016) Deliverable 5.1 A consistent characterisation of existing and planned RIs, ENVRI plus, 24/05/2016, Horizon 2020 Grant Agreement No 654182 http://www.envriplus.eu/wp-content/uploads/2016/06/A-consistent-characterisation-of-RIs.pdf
- ↑ ENVRIplus. (2017) Deliverable 8.3 Interoperable cataloging and harmonization for environmental RI projects: system design. ENVRI plus, 30/01/2017, Horizon 2020 Grant Agreement No 654182 http://www.envriplus.eu/wp-content/uploads/2015/08/D8.3-Interoperable-cataloging-and-harmonization-for-environmental-RI-projects-system-design.pdf