Date
Call-in Information
Time: 11:00 am, Eastern Time (New York, GMT-04:00)
To join the online meeting:
- Go to: https://lyrasis.zoom.us/my/vivo1?pwd=a2Q3RUVKVkN2dkNHV3FUaFRtLzhGdz09
- Passcode: 351860
One tap mobile:
US: +16699006833,,9358074182# or +19292056099,,9358074182#
Or Telephone:
US: +1 669 900 6833 or +1 929 205 6099 or 877 853 5257
Meeting ID: 935 807 4182
International numbers available: https://zoom.us/u/aeANHanzED
Slack
- https://vivo-project.slack.com
- Self-register at: http://bit.ly/vivo-slack
- Self-register at: http://bit.ly/vivo-slack
Attendees
Indicating note-taker
Agenda
- Announcements / updates
- RC1 is out!
- Mailing list / Slack discussion
- Internal testing efforts: Release Testing - 1.12.0
- Prioritizing and planning post-1.12 development
4. Other topics?
Future topics
- Forward-looking topics:
- frameworks: Spring / Spring Boot / alternatives
- Horizontal scalability
- Deployment
- Configuration : files / environment variables / GUI settings
- Editing / form handling
- Adding custom theming without customizing build
- Post-release priorities
- Ingest / Kafka
- Advanced Role Management
- Moving Scholars closer to core - next steps
- Vitro JMS messaging approaches - redux
- Which architectural pattern should we take?
- What should the body of the messages be
- Incremental development initiatives
- 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.
- Michel notes that the RC test forms are long and there is no option to save and resume.
- 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.