Versions Compared

Old Version 30

changes.mady.by.user Mike Conlon

Saved on

compared with

New Version 31

changes.mady.by.user Mike Conlon

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

There is great interest in creating a "virtual cycle" of data movement between VIVO and SHARE.  The VIVO existing VIVO Harvester for SHARE will be upgraded by SHARE to their version 2 data model.  VIVO will enable harvesting of OpenVIVO for SHARE.  SHARE2VIVO will be upgraded to allow users of OpenVIVO to update their profiles from SHARE data – this will require additional specificity in the SHARE data.

Tyler Walters – Closing Comments

VIVO is a fundamental part of the university's infrastructure

Some Observations

The SHARE information environment is maturing rapidly.  They have a large staff of talented young developers augmented by a very large group of talented interns from UVA.  They have a sophisticated version control, change set architecture for all their data which allows them to reharvest data to improve the quality of the current version.  The API is easy to use.  ElasticSearch works very well.  They recognize the need to disambiguate their data and are planning heuristics, use of identifiers, and use of curation associations at libraries to merge entities.

Their data model is shallow, and driven by the fields that are commonly available from the providers.  VIVO is very interesting to SHARE as it provides missing semantics and a very deep data model. The two efforts – VIVO and SHARE – are strikingly complimentary.  VIVO would benefit tremendously from "world" metadata collected and curated by SHARE.  SHARE qould benefit tremendously from VIVO's institutional footprint and the potential to feedback metadata improvements to SHARE.

Additional Conversations

Numerous COS staff regarding data specification, semantics, use of identifiers, and the "golden query": "Return all the metadata for institution x"  Given a reasonable result for this query, institutions could contribute to metadata improvement and use SHARE metadata for VIVO.

Next Steps

There is great interest in creating a "virtual cycle" of data movement between VIVO and SHARE.  The VIVO existing VIVO Harvester for SHARE will be upgraded by SHARE to their version 2 data model.  VIVO will enable harvesting of OpenVIVO for SHARE.  SHARE2VIVO will be upgraded to allow users of OpenVIVO to update their profiles from SHARE data – this will require additional specificity in the SHARE data.