Integration test opportunities with the switch to TDB - requires startup/shutdown of external Solr ..via Maven
Tickets
Status of In-Review tickets
Notes
Bruce Herbert sends his congratulations to the team on achieving the RC1 milestone.
Release testing
Michel notes that the RC test forms are long and there is no option to save and resume.
Does not seem to be a Google feature, or maybe it would only be activated if multiple submissions are disabled
There's no problem in submitting multiple submissions each with only part of the test filled out. Doesn't need to be completed in one sitting.
Should add link to 1.11 test results table for sample API submissions to use in 1.12 API tests
Michel notes that the UI test procedure also serves as a nice demo of the capabilities of VIVO. Would be nice to turn this into a kind of walthrough for new users after testing is done.
Michel's testing of new i18n functionality largely successful, but uncovered a few bugs (especially 'no match to existing data property' errors when trying to edit certain existing values)
The capability map text search does not fall back to other language values: have to enter text in the language in which the interface is currently set. Should be made clear in the instructions.
UQAM's Vivo Studio discussion
ontology is at center of workflow
multiple types of users: librarian works on ontology/vocabulary and pushes to GitHub. Developer can use same environment to develop data ingest pipeline. Sysadmin can develop deployment environment.
Uses Eclipse plugins / update site / Maven approach to everything
Will be presented at the conference
Uses TopBraid Composer free edition
not (at least yet) open source, but could be interesting to explore potential for VIVO community to collaborate with TopBraid developers on maintenance of free ediition.