Return to ENVRI Community Home
CV service objects offer programmatic access to distributed systems and resources (internal and external). This allows building RIs using both internal and external sourced components. The service layer includes the main services that enable data access, processing and transformation used in different phases of the research data lifecycle.
Oversight service for integrated data acquisition.
An acquisition service object encapsulates the computational functions required to monitor and manage a network of instruments. An acquisition service can translate acquisition requests into sets of individual instrument configuration operations as appropriate.
An acquisition service should provide at least three operational interfaces:
Oversight service for adding and updating records attached to curated datasets.
An annotation service object collects the functions required to annotate datasets and collect observations that can be associated with the various types of data managed within a research infrastructure.
An annotation service should provide three operational interfaces:
Oversight service for authentication, authorisation, and accounting of user requests to the infrastructure.
An AAAI service object encapsulates the functions required to authenticate agents, authorise any requests they make to services within a research infrastructure, and track their actions. Generally, any interaction occurring via a science gateway object or a virtual laboratory object will only proceed after a suitable transaction with an AAAI service object has been made.
An AAAI service should provide at least one operational interface:
Oversight service for cataloguing curated datasets.
A catalogue service object collects the functions required to manage the construction and maintenance of catalogues of metadata or other characteristic data associated with datasets (including provenance and persistent identifiers) stored within data stores registered.
A catalogue service should provide four operational interfaces:
Oversight service for data processing tasks deployed on infrastructure execution resources.
A coordination service should provide at least three operational interfaces:
Oversight service for the transfer of data into and out of the data store objects.
A data transfer service object encapsulates the functions required to integrate new data into the RI and export that integrated data on demand. The data transfer service is responsible for setting up data transfers, including any repackaging of datasets necessary prior to delivery.
A data transfer object can create any number of new data transporter objects.
A data transfer service should provide one operational interface:
The actual coordination of data transfers is handled by data transporter objects; the data transfer service is responsible for specifying the behaviour of a given transporter.
External service for persistent identifier assignment and resolution.
Persistent identifiers are generated by a global service generally provided by an outside entity supported by the research community. A PID (persistent identifier) service object encapsulates this service and is responsible for providing identifiers for all entities that require them.
A PID service should provide at least two operational interfaces: