...
- Don Elsborg
- Andrew Woods
- Huda Khan
- Benjamin Gross
- Ralph O'Flinn
- Brian Lowe
- Michel Héon
- Alexander (Sacha) Jerabek
- William Welling
- Mike Conlon
- Steven McCauley
- Nicolas Dickner
...
Agenda
- Announcements
- VIVO conference proposals?
- Sheila Rabun has offered to co-present on an Orcid topic
- Facilitator for next week's dev meeting?
- VIVO conference proposals?
- The i18n effort continues
- Please review these softballs
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1782 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1785 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1777
- Discussion of:
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1836 - Incremental evolutionary approach to VIVO-languages and Vitro-languages
- Update and goals of vivo-regression-tests
- Please review these softballs
- VIVO installation: the vision and requirements
- VIVO should be able to be deployed by dropping vivo.war into a servlet container (e.g. Tomcat)
- On startup, VIVO should create ${VIVO_HOME}, if it does not exist <-- start here
- On startup, VIVO should
download, start, andconfigure Solr, if it does has not existbeen configured - System administrators should be able to enable i18n languages via runtime configuration files
- VIVO should only load i18n triples that are associated with enabled i18n languages
- Developers should be able to use a three-tier build to create a vivo.war for advanced customization
- Vitro JMS messaging approaches - redux
- Which architectural pattern should we take?
- What should the body of the messages be?
- Moving tickets forward
- back on your plate, Mike ConlonJira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1658
- Who is working on what? - Are there active tickets in-progress?
Expand Jira server DuraSpace JIRA jqlQuery filter=15500 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
- Incremental development initiatives
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1688 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1751 - Integration test opportunities with the switch to TDB - requires startup/shutdown of external Solr ..via Maven
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1752
...
- Announcements
- VIVO conference proposals?
- Potential proposal: Web of Science
- Potential proposal: CU Boulder - vocabs/MESH
- Potential proposal: Andrew and UQAM - i18n
- Potential proposal: UQAM - Linked open data
- Facilitator for next week's dev meeting?
- Ralph O'Flinn to facilitate!
- The i18n effort continues
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1836 - Main concerns are:
- slow to compile
- will number of rdf/ftl/properties files become an issue as number of languages increase
- Main concerns are:
- Example: https://github.com/vivo-project/VIVO-languages/pull/42
- Issues with concats between the languages.
- Currently still a work in progress... stay tuned