Latest revision |
Your text |
Line 12: |
Line 12: |
| 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. | | 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. |
| | | |
− | * [[Engineering Objects (Draft)#annotation service|annotation service]] | + | * annotation service |
− | * [[Engineering Objects (Draft)#catalogue service|catalogue service]] | + | * catalogue service |
− | * [[Engineering Objects (Draft)#coordination service|coordination service]] | + | * coordination service |
− | * [[Engineering Objects (Draft)#data exporter|data exporter]] | + | * data exporter |
− | * [[Engineering Objects (Draft)#data importer|data importer]] | + | * data importer |
− | * [[Engineering Objects (Draft)#data store controller|data store controller]] | + | * data store controller |
− | * [[Engineering Objects (Draft)#data transfer service|data transfer service]] | + | * data transfer service |
− | * [[Engineering Objects (Draft)#pid manager|pid manager]] | + | * pid manager |
− | * [[Engineering Objects (Draft)#process controller|process controller]] | + | * process controller |
− | * [[Engineering Objects (Draft)#provenance service|provenance service]] | + | * provenance service |
− | * [[Engineering Objects (Draft)#raw data collector|raw data collector]] | + | * raw data collector |
| | | |
| | style="width: 70%; background-color: #fcfcfc; border-radius: 5px; border: 1px solid #ccc; padding: 10px 10px 10px 40px"| | | | style="width: 70%; background-color: #fcfcfc; border-radius: 5px; border: 1px solid #ccc; padding: 10px 10px 10px 40px"| |
Line 28: |
Line 28: |
| <center>Engineering object groups</center> | | <center>Engineering object groups</center> |
| |} | | |} |
− | | + | ----- |
| === <span style="color: #BBCE00">annotation service</span> === | | === <span style="color: #BBCE00">annotation service</span> === |
| | | |
Line 340: |
Line 340: |
| |- | | |- |
| | Computational || [[CV Component Objects#Process controller|'''process controller''']] | | | Computational || [[CV Component Objects#Process controller|'''process controller''']] |
− | |}
| |
− | |}
| |
− |
| |
− | === <span style="color: #BBCE00">provenance service</span> ===
| |
− |
| |
− | A basic engineering object that supports the ability to publish and search collections of provenance metadata for assets such as data, services, and related information objects managed by a research infrastructure. A provenance service is a specialisation of a catalogue service. A provenance service must provide at least four functionalities: query catalogues, update catalogues, export metadata, and query resource.
| |
− |
| |
− | {| style="width: 85%;"
| |
− | |-
| |
− | | style="width: 55%; vertical-align: top; padding: 10px 10px 10px 10px"|
| |
− | Provenance service functions
| |
− | {| class="wikitable sortable"
| |
− | |-
| |
− | ! '''<span style="color: #BBCE00">Function</span>''' !! '''<span style="color: #BBCE00">Description</span>''' !!
| |
− |
| |
− | '''<span style="color: #BBCE00">Type</span>'''
| |
− | |-
| |
− | | export metadata || function for gathering metadata to be exported with assets extracted from the data store objects. || server
| |
− | |-
| |
− | | query catalogues || function for querying assets held by the infrastructure, including the retrieval of assets associated with a given persistent identifier. || server
| |
− | |-
| |
− | | update catalogues || function for updating of catalogues and the associated data assets. || server
| |
− | |-
| |
− | | invoke resource || function for enabling the invocation of other services such as harvesting, exporting data, or automated update. This includes the communication with internal components such as the data store controller for retrieving data. || client
| |
− | |}
| |
− | | style="width: 45%; vertical-align: top; padding: 10px 10px 10px 40px"|
| |
− | Catalogue service 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_curRolesintheDataCurationCommunity '''catalogue system'''] (role)
| |
− | |-
| |
− | | Information || [[IV Information Action Types#trackprovenance|'''track provenance''']] (action) <br>[[IV Information Objects#metadatacatalogue|'''metadata catalogue''']] (instance of object)
| |
− | |-
| |
− | | Computational || [[CV Service Objects#Catalogue service|'''catalogue_service''']] (instance of object)
| |
− | |}
| |
− | |}
| |
− |
| |
− | === <span style="color: #BBCE00">raw data collector</span> ===
| |
− |
| |
− | A basic engineering object to acquire, package, and transfer raw data produced by acquisition objects. A raw data collector 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"|
| |
− | raw data collector 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 retrieving raw data from data acquisition objects || 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"|
| |
− | raw data collector 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#Raw data collector|'''raw data collector''']]
| |
| |} | | |} |
| |} | | |} |
Line 421: |
Line 347: |
| <ref name="Deliverable 8.3">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</ref> | | <ref name="Deliverable 8.3">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</ref> |
| </references> | | </references> |
− | __NOTOC__
| + | |
| [[Category:Engineering Viewpoint (Draft)]] | | [[Category:Engineering Viewpoint (Draft)]] |