...

1. Orientation to VIVO Scholar for community developers
   1. Setting up the environment
   2. Introducing existing documentation
   3. Loading test data
2. VIVO Scholars community defaults
   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
   1. Potentially followed by externalizing TPF server
4. Orcid integration
   1. pulling and pushing publications
5. Vitro messaging service
6. NEMO Freemarker templates

Other

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

Tickets

Scrum Board

1. Orientation to VIVO Scholars

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

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

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

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

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

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

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

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

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

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

   4. TPF ticket(s)?

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

   2. Message on-demand
6. NEMO

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

...