Dates

October 14 - November 1

Participants

1. Andrew Woods
2. William Welling
3. Jim Wood
4. Ralph O'Flinn
5. Kristina Heinricy
6. Robert Nelson
7. Don Elsborg

Meetings

2019-10-14 Sprint Kickoff Meeting

Objectives

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

Tickets

Scrum Board

1. Orientation to VIVO Scholars
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
2. VIVO Scholars community defaults
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   5. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   6. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   7. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   8. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
3. Externalizing triplestore
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
4. Orcid integration
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   5. other (needs ticket(s))
      1. Pulling from Orcid
      2. Pushing to Orcid
      3. Storing access tokens in config database
5. Vitro messaging
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
6. NEMO
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Reference

• https://github.com/vivo-community/scholars-discovery
• https://github.com/vivo-community/scholars-react
• https://github.com/vivo-community/scholars-angular