Page History

...

1. Orientation to VIVO Scholar for community developers (Don Elsborg , Andrew Woods)
   1. Setting up the environment
   2. Introducing existing documentation
   3. Loading test data
2. VIVO Scholars community defaults (Don Elsborg , Ralph O'Flinn , Jim Wood)
   1. Defaults should approximate OpenVIVO
   2. Document how to customize branding, look and feel
   3. Document how to extend the ontology
3. Externalizing the triplestore (Ralph O'Flinn)
   1. Potentially followed by externalizing TPF server
4. Orcid integration (Kristina Heinricy, Ralph O'Flinn)
   1. pulling and pushing publications
5. Vitro messaging service (William Welling)
   1. Documentation for RDF Delta Log Server connection configuration
   2. Documentation for spinning up RDF Delta Log Server
   3. Dockerfile for RDF Delta Log Server
   4. Documentation for Message Broker connection configuration
   5. Documentation for spinning up Message Broker
   6. Dockerfile for Message Broker
6. NEMO Freemarker templates (Ralph O'Flinn)

Other

1. Release 1.11.0
   1. Update Solr documentation
2. Extract ontology from codebase
3. Extract languages from codebase

...

1. Orientation to VIVO Scholars

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

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

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

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

      Load known test data (need a ticket)
2. VIVO Scholars community defaults

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

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

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

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

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

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

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

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

3. Externalizing triplestore

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

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

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

      TPF ticket(s)?

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

      Verify RDFServiceBasedRequestProcessorForTPFs.java works against external triplestore
4. Orcid integration

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

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

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

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

   5. other (needs ticket(s))
      1. Pulling from Orcid
      2. Pushing to Orcid
      3. Storing access tokens in config database
5. Vitro messaging

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

6. NEMO

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

...