Background

Let's think ahead.  VIVO will support Semantic Versioning, a core concept in open source software development.  Our major releases 2.0, 3.0 may not be quite a as earth-shaking as we once thought.  Any API change, including any change in ontological representations, will generate a major release.  We will become familiar with the idea of VIVO 2.0, VIVO 3.0 and so on. 

People who sell and market VIVO would prefer if major releases included major customer-facing features, that is new capabilities accessible to end users.  One way to reconcile semantic versioning and the needs of people who sell and market VIVO in the marketplace of ideas is to pro-actively plan a major customer feature for each major release rather than let semantic versioning dictate a major release due to API or ontology changes.

Releases using semantic versioning

  • No more than one major release each year – VIVO 2, VIVO 3 and so on.  Expected to include a major customer-facing feature.
  • Dot releases, one or more, during the year to add features, VIVO 2.1, 2.2, but NOT to change the ontology or APIs.
  • Minor releases as needed to fix bugs.  VIVO 2.2.1, 2.1.2

Desired Features

  • A data analytics dashboard, similar wot Weill's VIVO Dashboard
  • A new front-end, using an optimized index, and modern technologies, producing a clean, modern, fast, functional, internationalized, assisted, responsive UX.
  • A data Combine that can collect data from a wide variety of sources, disambiguate people and works, and provide a curation interface
  • Complete ontological agility – as ontology changes, the ecosystem is capable of supporting the changes immediately.


  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.