You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 18
Next »
Dates
October 14 - November 1
Participants
- Andrew Woods
- William Welling
- Jim Wood
- Ralph O'Flinn
- Kristina Heinricy
- Robert Nelson
- Don Elsborg
Meetings
2019-10-14 Sprint Kickoff Meeting
Objectives
- Orientation to VIVO Scholar for community developers (Don Elsborg , Andrew Woods)
- Setting up the environment
- Introducing existing documentation
- Loading test data
- VIVO Scholars community defaults (Don Elsborg , Ralph O'Flinn , Jim Wood)
- Defaults should approximate OpenVIVO
- Document how to customize branding, look and feel
- Document how to extend the ontology
- Externalizing the triplestore (Ralph O'Flinn)
- Potentially followed by externalizing TPF server
- Orcid integration (Kristina Heinricy, Ralph O'Flinn)
- pulling and pushing publications
- Vitro messaging service (William Welling)
- Documentation for RDF Delta Log Server connection configuration
- Documentation for spinning up RDF Delta Log Server
- Dockerfile for RDF Delta Log Server
- Documentation for Message Broker connection configuration
- Documentation for spinning up Message Broker
- Dockerfile for Message Broker
- NEMO Freemarker templates (Ralph O'Flinn)
Other
- Release 1.11.0
- Update Solr documentation
- Extract ontology from codebase
- Extract languages from codebase
Tickets
Scrum Board
- Orientation to VIVO Scholars
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
- VIVO Scholars community defaults
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
- Externalizing triplestore
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
- Orcid integration
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
- other (needs ticket(s))
- Pulling from Orcid
- Pushing to Orcid
- Storing access tokens in config database
- Vitro messaging
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
- NEMO
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Reference
Stand-up Reports