Versions Compared

Key

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

...

VIVO v1.6 incorporates major changes to the ontology that reflect a need dating back to 2009 to bring the VIVO and eagle-i project (https://www.eagle-i.net) ontologies closer together. NIH elected to fund two distinct projects focusing on the networking of researchers (VIVO) and research resources (eagle-i) but recognized the artificiality of the split and has encouraged collaboration, most recently by funding the CTSAconnect project (http://ctsaconnect.org) with Dr. Melissa Haendel of Oregon Health and Science University as principal investigator.

The new ontology is called VIVO-ISF, short for Integrated Semantic Framework.  The full ISF ontology as published by the CTSAconnect project is freely available for download and includes technical documentation and its modules may be browsed online or downloaded.  The VIVO 1.5 scope has informed selection of ISF modules appropriate for VIVO 1.6, with the anticipation that individual adopting sites may wish to include or exclude individual ISF modules based on their intended population of VIVO with data.

Documentation specific to VIVO-ISF lives on this wiki and will continue to evolve as the VIVO-ISF Ontology Working Group, led by Melissa Haendel and Brian Lowe, receives feedback from the rollout.  Communities of interested are forming within the working group and will lead implementation of corrections, improvements, and expansion of the VIVO-ISF ontology for future releases. Please join the biweekly ontology working group calls

To understand the VIVO-ISF changes from previous releases, we call particular attention to the VIVO 1.5 to VIVO-ISF change diagrams.  Upgrading VIVO from version 1.5.x to version 1.6 includes an automated data migration process that should convert all existing VIVO content to the new ontology structure, but any local data ingest processes will almost certainly need to be modified to generate data compatible with the new ontology.  We recommend backing up the VIVO 1.5 database and performing a provisional upgrade on a test server to confirm that

 

to be continued ...