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
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
- Benjamin Gross
- Brian Lowe
- Ralph O'Flinn
- Andrew Woods
- Nicolas Dickner
- Jeff Tyzzer
- Michel Héon
- Huda Khan
- Don Elsborg
Agenda
- Input on Product Direction for 2020
- Goal: agree on the set of near-term project priorities so that we can collaborate on moving the project in a mutually beneficial direction.
- Raw data from above graphic
- 19 - Data ingest
- 11 - Ease of installation
- 8 - Ease of upgrade
- 4 - Project documentation
- 13 - Internationalization (i18n)
- 6 - Modularization / Decoupling triple store
- 4 - Modularization / Decoupling asset store (e.g. image uploads)
- 5 - Modularization / Decoupling frontend
- 8 - RESTful API
- 2 - Notifications / Messaging
- 12 - Advanced role management (more granular permissions in Freemarker UI)
- 6 - More publication claiming options
- Community-provided ideas
- 1 - Analysis of information stored, new graphics
- 1 - Search engine optimization; also core VIVO ontology development to meet user needs outside of traditional universities
- 1 - Evolving the Capability Map . E.g.: improving the graphics, choosing the navigation attribute (e.g.: project)
- 1 - Updated ontology, Cornell Ontology editor, new standard templates for certain entity types (concepts, orgs, events, videos, publications etc.)
- 1 - more ORCID API functionality: importing data from ORCID, writing data to ORCID
- 1 - Ontology editing
- Comments on proposed priorities
Simple data ingest methods is a great way to get up and running fast. Working in a test environment with your own data REALLY make the understanding of the system way easier. Now, I only tinkered with the system a few days so take this for what it is.
Show new graphics and new analysis of the stored information could be interesting for develop.
Decoupling allows easier development, but often means more complicated administration. It's worth to keep this in mind. We were not able to install VIVO 1.11 for example. It's already more complicated then it was.
Data ingest
Data ingest should include better options for concepts, journals, conferences, and other data via VIVO itself, like the publication claim or concept import.
Continue decoupling; establish APIs. This positions for future work.
For i18n - put all linguistic terms in ontological form
Javed had an almost complete new interface for the ontology editor
Future topics
- 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
Actions