...
Issues are created as the development team is made aware of them – most often through questions raised on the mailing list, or discussions on the weekly development and implementation calls. Anyone is welcome to request an account for creating and/or commenting on issues, and the JIRA issue tracker is open for public viewing without a login.
Four Five factors have affected the priorities for VIVO 1.6:
- Grant obligations – the VIVO-ORCID grant promised to include creation and confirmation of ORCID iDs in the next VIVO release
- Community – we have heard from multiple fronts that as VIVO installations grow in size, performance challenges associated with degrades when editing and with large pages
- Coherence – feedback on new features introduced in 1.6 such as the web services API suggests changes that would make them truly useful
- Bugs – assessed for priority based on likelihood of occurrence and seriousness of impact
- Resources – we will run out of time before we run out of tasks
Will VIVO 1.7 require another data migration?
After the major changes introduced with the VIVO-ISF Ontology in VIVO 1.6, we want to avoid changes that would require another data migration in 1.7. This means that your data ingest processes that have been adjusted for VIVO 1.6 should continue to work for 1.7.