Using Vivo to keep track of and find Dataverses

Preamble

There is a need to be able to easily find Dataverse implementations with specific installations models, versions, and configurations. Whether to check how a particular feature behaves or to consult policies related to various deposit models a listing of Dataverses would be useful.

Here is the Vivo site:
https://duraspace.org/vivo/

Here is a list of Vivo sites:
https://duraspace.org/registry/?filter_10=VIVO

Here is the introduction to Vivo from the documentation:
https://wiki.duraspace.org/display/VIVODOC110x/Introduction

What is VIVO?

VIVO [ Pronunciation: /viːvəʊ/ or vee-voh ] is member-supported, open source software and an ontology for representing scholarship. VIVO supports recording, editing, searching, browsing, and visualizing scholarly activity. VIVO encourages showcasing the scholarly record, research discovery, expert finding, network analysis, and assessment of research impact. VIVO is easily extended to support additional domains of scholarly activity.

When installed and populated with researcher interests, activities, and accomplishments by an institution, VIVO enables the discovery of research and scholarship across disciplines at that institution and beyond. VIVO supports browsing and a search function which returns faceted results for rapid retrieval of desired information. Content in a VIVO installation may be maintained manually, brought into VIVO in automated ways from local systems of record, such as HR, grants, course, and faculty activity databases, or from database providers such as publication aggregators and funding agencies.

The proposal is to use Vivo to harvest metadata about Dataverses and to include information about institutions, people, and events related to the Dataverse project.

Vivo has two components: 'people' and 'capability map'. 'People' can be any entity: a person, scholar, institution, event. 'Capability map' is the network of expertises, usually subject specialities. In this case with Dataverse, 'capabilities' would be the constellation of installation personas, configurations, and versions of Dataverses.

See the documentation about Vivo and the capability map here:
https://wiki.duraspace.org/display/VIVODOC19x/Using+the+Capability+Map

At UQAM we have implemented the capability map and linked it to our directory of professors, https://professeurs.uqam.ca/. The two sites are separate but linked to each other. The intention is to eventually deploy a complete Vivo to host all the information about people and their research and activities at UQAM.

Here are some screen captures of how the capability map works.
You can try it for yourself here :
https://expertises.uqam.ca/vis/capabilitymap

Start by reviewing the linked VIVO introduction and Capability Map documentation, along with the existing Dataverse installations project. The issue does not name files, tests, or an implementation entry point; done would require an agreed scope and a working way to harvest and find Dataverse installation metadata.