Goals

• Integration of DSpace and VIVO platforms

  • Streamline process for academics
    • Avoid duplicated bibliographic data management
  • Adding semantic web aspect to existing DSpace repositories
  • Adding depositing files and monitoring of Open-access policy compliance to existing VIVO instances. VIVO instance might be used as a front-end for researchers where they can be motivated to create their own profile page including a list of research results (publications, datasets, etc.). For any single research results researchers might provide DOI/URL in the metadata and/or initiate depositing files to DSpace through VIVO user interface, while the rest of the files processing will take place in Dspace by librarian/officers. 

Description

Depositing of open-access publications in a repository such as DSpace can be a source for monitoring an open-access policy compliance at an institution. On the other side, research information systems such as VIVO enable reporting and monitoring on research activities and achievements. Integration of those two types of systems can lead to an integrated all-in-one platform for unique and comprehensive monitoring of the research domain at one institution. Also, this integration avoids duplicated efforts for cataloguing information about publications and researchers (authors) in those two types of platforms. 

Only the first phase of the project has been implemented so far. It enables the following usage scenario: A new fresh and empty instance of VIVO is installed. There is a running instance of DSpace. Configure and run the migration process by using bash scripts as it is described at https://wiki.lyrasis.org/display/VIVO/Migrate+DSpace-Metadata+from+DSpace+to+VIVO. After initial migration of data from DSpace, VIVO UI for editing and adding new items has been turned off (VIVO is used in read only mode). Weekly or daily, there is the update of information in VIVO during the night by dropping triplestore, and running migration with a fresh copy of DSpace data. The update is defined as a bash script run as a scheduled job (for instance a cron job).  

Next Steps

If there is interest in further integration work, some potential phases include: 

• Phase 2: Completion of exchange information task
• Phase 3: Establishing stable links between DSpace and VIVO items and terms
• Phase 4: Description of crosswalks/mapping informal language
• Phase 5: Sending notifications to DSpace from VIVO
• Phase 6: Sending notifications to DSpace from VIVO; Receiving notifications from DSpace; Communication Between VIVO and DSpace should be based on COAR notify and CSRF tokens)

You can see more phase details here.

Getting Involved

Interested in participating in future phases? We welcome financial support, technical donations and ideas. Please reach out to us at: VIVO@lyrasis.org

Documentation & Presentations

User documentation

Technical documentation

Slides