Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


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)

Anchor
RefFootnote01
RefFootnote01
Anchor
RefFootnote02
RefFootnote02
0102.

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 Object.

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.

Table of Contents
maxLevel2
printablefalse

Info
icon false

Engineering object groups

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

FunctionDescriptionType
annotate data Function for requesting the annotation (free text or semantic) of existing assets. This may require the creation of additional records to record qualitative observations, provenance or structured metadata.server
update catalogues

Function for updating of annotation metadata and the associations to existing assets.

client
update records

Function for updating of annotation records associated to assets.

client

Annotation service correspondences

ViewpointCorrespondence
Sciencedata annotation (behaviour)
Information

metadata catalogue (instance of object)

Computational annotation service

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 catalouguescatalogues, update catalogues, export metadata, and query resource.

Catalogue service functions

FunctionDescriptionType
export metadatafunction for gathering metadata to be exported with assets extracted from the data curation store objects (data stores).server
query cataloguesfunction 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 resourcefunction 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

Catalogue service correspondences

ViewpointCorresponding Object
Sciencecatalogue system (role)
Information metadata catalogue(object)
Computational catalogue service

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

FunctionDescriptionType
process request function for scheduling the execution of data processing tasks. This could require executing complex workflows involving many (parallel) sub-tasks.server
coordinate processfunction used to coordinate the execution of data processing tasks on execution resources presented by process controllers.server
create process controllerfunction for creating and configuring the required process controllers required for the different processing tasks internal
prepare data transfer function used to retrieve data (and metadata) from the data stores and to return the processing results.server

Catalogue service correspondences

ViewpointCorresponding Object
Science

data processing subsystem (role)

coordinate service (behaviour)

Information process data (action)
Computational coordination service

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

FunctionDescriptionType
retrieve asset

function provided to enable requesting data from a designated data store (inherited from  data transporter).

client
update records function provided to inform downstream resources about impending asset transfers (inherited from  data transporter).client
export metadatafunction provided for requesting any additional metadata associated with the asset being transferred. client
export assetfunction provided for extracting assets from a designated data storeconsumer
deliver assetfunction provided for delivery of assets to a designated data store.producer

data exporter correspondences

ViewpointCorresponding Object
Science

data publishing subsystem (role)

data use subsystem (role)

Computational data exporter

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

FunctionDescriptionType
retrieve asset

function provided to enable requesting data from a designated data store (inherited from  data transporter).

client
update recordsfunction provided to inform downstream resources about impending asset transfers (inherited from  data transporter).client
acquire identifierfunction 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.

cllient
import assetfunction provided for receiving assets from a designated data storeconsumer
deliver assetfunction provided for delivery of assets to a designated data store.producer

data importer correspondences

ViewpointCorresponding Object
Science

data acquisition subsystem (role)

data curation subsystem (role)

Computational data importer

data store controller

A basic engineering object that encapsulates the functions required to store and maintain data assets managed by the RI. The data store controller also provides access to authorised agents. A data store controller should provide five functions: update records, query resoruce, retrieve data, import data, export data.

data store controller functions

FunctionDescriptionType
update records

function for editing data records within a data store, as well as preparing ingestion of data streams.

server
query resourcefunction for querying the data store.server
retrieve datafunctions to manage the retrieval of assets from a data storeserver
import assetfunction provided for receiving assets into a designated data storeconsumer
export assetfunction provided for extracting assets from a designated data store.producer

data store controller correspondences

ViewpointCorresponding Object
Science

data curation subsystem (role)

Computationaldata store controller

data transfer service

A basic engineering object for managing the transfer of assets into and out-of the data stores. The data transfer service is responsible for setting up data transfers, including any repackaging of assets necessary prior to delivery.

data transfer service functions

FunctionDescriptionType
prepare data transfer

function for managing and scheduling a data transfer either into or out of the data stores

server
create transporterfunction for creating and configuring the required data transporters ( raw data collector, data importer, or data exporter)internal

data transfer service correspondences

ViewpointCorresponding Object
Science

data curation subsystem(role)

Computationaldata transfer service

pid manager

A basic engineering object for managing the acquisition, registration, and maintenance of persistent identifiers for data assets. Persistent identifiers can be generated internally or externally. For assigning resolvable global unique identifiers, the pid manager commonly depends of an external PID service. A pid manager should provide three functionalities: acquire identifier, manage identifier, and resolve identifier.

pid manager functions

FunctionDescriptionType
acquire identifier

function for providing new persistent identifiers for assets

server
manage identifierfunction for retrieving, updating and deleting identifiersserver
resolve identifierfunction for providing the physical location of an asset to authorised requesterserver

data transfer service correspondences

ViewpointCorresponding Object
Science

PID Manager (role)

Informationassign unique identifier (action)
Computational PID manager (object)

process controller

A basic engineering object providing the functions required for using an execution resource (generically, any computing platform that can host some process) as part of a predefined workflow. A process controller should provide five functions:

process controller functions

FunctionDescriptionType
coordinate process

function for controlling the execution resource associated with a given process

server
retrieve resultsfunctions for retrieving results from an execution resourceserver
update recordsprovides functions for modifying data on an execution resource, including preparing the resource for the ingestion of bulk data streamsserver
stage dataused to acquire streams of data from data store objects as part of some process.consumer
export assetfunction provided for retrieving the assets produced by some processproducer

Catalogue service correspondences

Viewpoint

Corresponding Object

Science

data processing subsystem (role)

compose service(behaviour)

Informationprocess data (action)
Computational process controller

provenance service

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 catalouguescatalogues, update catalogues, export metadata, and query resource.

Provenance service functions

FunctionDescriptionType
export metadatafunction for gathering metadata to be exported with assets extracted from the data store objects.server
query cataloguesfunction 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 resourcefunction 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

Catalogue service correspondences

Viewpoint

Corresponding Object

Science

catalogue system (role)

Information

track provenance (action)

metadata catalogue (instance of object)

Computationalcatalogue_service (instance of object)

raw data collector

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.

raw data collector functions

FunctionDescriptionType
retrieve asset

function provided to enable requesting data from a designated data store (inherited from  data transporter).

client
update recordsfunction provided to inform downstream resources about impending asset transfers (inherited from  data transporter).client
acquire identifierfunction 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.

cllient
import assetfunction provided for retrieving raw data from data acquisition objectsconsumer
deliver assetfunction provided for delivery of assets to a designated data store.producer

raw data collector correspondences

ViewpointCorresponding Object
Science

data acquisition subsystem (role)

data curation subsystem (role)

Computational raw data collector

01

Anchor
Footnote01
Footnote01
 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

02

Anchor
Footnote02
Footnote02
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