...
- 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 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.
What happens next?
Planning for VIVO 1.8 will start even before the release of 1.7 and can be tracked in Jira. Identification of features, requirements gathering, time estimation, and priority ranking will happen via the VIVO working groups under the overall coordination of Layne Johnson, the new VIVO Project Director. The biggest variable will be the amount of development time that can be allocated to the project by the community, either in the context of membership or by direct participation.