CV Brokered Data Import

Importing data from sources other than the acquisition network requires that the import be brokered by the publishing subsystem before data can be delivered into the data curation subsystem.

A CV Presentation Objects#virtual_laboratory can be used by researchers to upload new data into a research infrastructure. All requests are validated by the  CV Service Objects#aaai_service via its authorise action interface. The laboratory provides an interface to an external resource (this might take the form of a URI and a preferred data transfer protocol) and submits a request to a  CV Broker Objects#data_broker in the data publishing subsystem via its data request interface. The data broker will translate any valid requests into actions; in this scenario, a data transfer request is sent to the  CV Service Objects#data_transfer_service within the data curation subsystem.

The data transfer service will configure and deploy a  CV Component Objects#data_importer, the importer will open a data-flow from an external resource to one or more suitable data stores within the infrastructure and update records within those stores as appropriate. The importer is responsible for the annotation and registration of imported datasets – this generally entails obtaining a global persistent identifier for any new datasets and updating the catalogues used by the research infrastructure to identify and sort its data inventory. As such, the importer can invoke the  CV Service Objects#catalogue_service to update catalogues and invoke any community-used CV Service Objects#pid_service to acquire identifiers.