...

1. Input on Product Direction for 2020
   1. Image Added
   2. Comments on proposed priorities

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

      2. Show new graphics and new analysis of the stored information could be interesting for develop.

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

      4. Data ingest

      5. Data ingest should include better options for concepts, journals, conferences, and other data via VIVO itself, like the publication claim or concept import.

      6. Continue decoupling; establish APIs. This positions for future work.

      7. For i18n - put all linguistic terms in ontological form

      8. Javed had an almost complete new interface for the ontology editor

      Other community priorities?

Future topics

1. Vitro JMS messaging approaches - redux
   1. Which architectural pattern should we take?
   2. What should the body of the messages be?
2. Incremental development initiatives

   1. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1688

   2. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1751

   3. Integration test opportunities with the switch to TDB - requires startup/shutdown of external Solr ..via Maven

      1. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1752

...