...
- The scenario to be realized by this procedure consists in developing the necessary steps in order to migrate the metadata of two DSpace instances (the DSpace-6 Demo instance and the DSpace-7 Demo instance) to a local VIVO instance
- At the end of this procedure, the experimenter should have a fully operational VIVO instance containing the metadata harvested from DSpace-6-Demo DSpace-7-Demo, both of which are available from the web.
- The experimenter will also have in his possession, the necessary information to harvest in VIVO the metadata of a DSpace instance that he will have chosen and that it is possible to harvest from an OAI-PMH endpoint
General Esquema
The migration process consists of 3 main phases as shown in the image :
Extraction : Harvest the Dspace repository to extract resources metadata
Transformation : The extracted data is mapped to a vocabulary compatible with the VIVO ontological model
Insertion: Insert the data as triples in the VIVO repository through its sparql API
Useful addresses
| Title | URL | Description |
|---|---|---|
| DSpace-6 Demo Home Page | This entry page links to other links concerning the DSpace-6 demo | |
| DSpace-6 Demo UI | https://demo.dspace.org/xmlui/ | This page is the DSpace-6 api allowing to manipulate metadata |
| DSpace-6 OAI Api | https://demo.dspace.org/oai/request | OAI API used to harvest data |
| DSpace-7 Demo Home Page | https://demo7.dspace.org/home | This entry page links to other links concerning the DSpace-7 demo |
| VIVO Project GitHub Home Page | https://github.com/vivo-project | Source code location needed to install VIVO |
| DSpace-VIVO Integration Project (DV-IP) | https://github.com/vivo-community/DSpace-VIVO | Source code location for the migration of DSpace metadata to VIVO |
| DSpace-VIVO ETL Example | https://github.com/vivo-community/DSpace-VIVO/tree/main/test/org.vivoweb.dspacevivo.etlexample | Source code location for extract-transform-load (ETL) metadata processing from DSpace to VIVO |
...