...
- 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.
- 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
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
...