Using Vivo to keep track of and find Dataverses

[sachaj]

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

[pdurbin]

@sachaj this is neat. It reminds me of a little visualization I did with d3 years ago at https://github.com/IQSS/dataverse-viz that looks like the screenshot below. I was trying to express who is involved in what project at IQSS.

I guess I have some questions:

• Is https://expertises.uquebec.ca/vis/capabilitymap available in English?
• Is UQAM willing or able to host Vivo for the Dataverse community?

[sachaj]

Hi Phil,

Yes! This is very much what I had in mind.

To answer your questions:

1. there is only one version in French for UQAM, but Vivo itself natively is in English. We at UQAM are working with the Vivo team to finish the i18n-ing of Vivo - I'm not sure exactly where we are or how much is left, I joined the project in mid-stream. We do have a meeting next week on this topic so I'll find out more then. But the default installation is English for now.

2. As for hosting it here, I will bring this up with my Vivo boss and the IT team here. I think it would be fairly easy to clone our existing Vivo, the policy is for all new installations to be mostly dockerized if possible and on VMs. So there should be no problem. If we are to move ahead with this project though, I'd need some help with the setup, I have limited bandwidth right now as we in the process of migrating our library system to a new platform so that is the priority until summer 2020. But I could come up with a detailed plan here and see what it looks like.

I think this project is worthwhile, interesting, and useful. The initial set up might be a bit of a slog, but once it is up and rolling apart from some regular maintenance it should not be too onerous. I'll propose it at our end and see if it gets approved.

Sacha

[TaniaSchlatter]

Vivo looks like it would be an interesting way to explore dataverse installation metadata. Thanks for posting, Sacha!

[sachaj]

Hi,
By the way I made a typo, now fixed:
The UQAM site is :
https://expertises.uqam.ca/vis/capabilitymap

and not
https://expertises.uquebec.ca/vis/capabilitymap

The uquebec site is hosted by UQAM, but groups together all health science departments throughout the University of Quebec system.

Sacha

[sachaj]

Just adding a link to the installations personas document that Tania sent to me and Janet.

https://docs.google.com/document/d/1mTaHuulanL3GIbmvu91uabdy5_cMJ5qiKEEAioWPk_0/edit

Sacha

[janetm]

hi All
Thanks Sacha, Vivo looks to have potential in that it can visualise relationships, and store data for persons, and organisations (installations). Now we just need to decide on the 'Installation Persona' metadata fields. I will upload my original thoughts on the google link above.

[sachaj]

Hi Janet, yes there is work to be done on deciding on metadata fields among other issues. I am still trying to determine the best way to provide a test instance of a Vivo for our purposes, on this I may have more information later this summer as time and vacation absences across departments permit.

[janetm]

Hi Sacha I will put up my notes today, but basing ideas on the notes Tania uploaded can be a start. I recall Amber had some ideas too. This is my first full week in the office since ADA hosted the IASSIST conference in Sydney at the end of May so have a lot of catching up. Still v excited though! I am also setting up an Archivematica instance on a test VM so maybe I will ask about a vivo instance too. Anyway ideas are a start for now considering workloads. Thanks again Janet

…

---------------------------------------------------- Janet McDougall | Senior Data Archivist Australian Data Archive (ADA) ANU Centre for Social Research and Methods The Australian National University T: +61 2 6125 0571<tel:+61%202%206125%200571> E: [email protected]<mailto:[email protected]> W: http://ada.edu.au/<http://ada.edu.au/%3Chttp://assda.anu.edu.au/%3Chttp://ada.edu.au/%3chttp:/assda.anu.edu.au/%3Chttp://ada.edu.au/%3chttp:/assda.anu.edu.au/%3chttp:/ada.edu.au/%3chttp:/assda.anu.edu.au/%3E%3E%3E> ---------------------------------------------------- On 25 Jul 2019, at 04:50, Sacha Jerabek <[email protected]<mailto:[email protected]>> wrote: Hi Janet, yes there is work to be done on deciding on metadata fields among other issues. I am still trying to determine the best way to provide a test instance of a Vivo for our purposes, on this I may have more information later this summer as time and vacation absences across departments permit. — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#2?email_source=notifications&email_token=AAJISVCCJAI6A7Z4TTJ6BZ3QBCP6DA5CNFSM4H3VLOI2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2XISOQ#issuecomment-514754874>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AAJISVBPPDGPR6EXGLAKC7TQBCP6DANCNFSM4H3VLOIQ>.