You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 7
Next »
Date
Time: 11:00 am, Eastern Daylight Time (New York, GMT-04:00)
To join the online meeting:
Slack
Attendees
Indicating note-taker
- Don Elsborg
- Brian Lowe
- Benjamin Gross
- Ralph O'Flinn
- Andrew Woods
- Taeber Rapczak
- Mike Conlon
- Steven McCauley
- Alex Viggio
- William Welling
Agenda
- What are folks working on? What are the local priorities?
- Sprint update (June 17th - 28th)
External Search
- Merge 'sprint-search' (vivo, vitro) into 'develop'?
- Ralph is refreshing "devsprint" today that will bring in develop, sprint search, and tickets.
Enable connection of decoupled, read-only "profiles" user interface to VIVO
Define "shapes" of VIVO entities
Dockerize appropriate components
- TAMU Scholars / VIVO Scholars Entities
- Domains related to representing scholarship
- VIVO classes
- TAMU data model
- VIVO UI default expectations?
- New feature: Messaging
- Based on the IndexingChangeListener pattern
- Potentially with RDF-Patch bodies
- Early development
- Working towards the VIVO 1.11.0 release
- Landing Design - External Search
- Other tickets we want to include?
- Docker work:
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
- Don Elsborg to review?
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
- Don Elsborg to review?
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
- Ralph O'Flinn to review? - Now in https://github.com/vivo-community/vivo-docker2
-
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.
- Release manager?
Tickets
- Needing additional review
-
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.
- Benjamin Gross?
type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
Tickets
Status of In-Review tickets
type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
Received
type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
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.
(re-)Raises interest in reconsidering first-time, every-time, tdbconfig design
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
- Should be low-hanging
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Where does this stand? What is needed to add more person identifiers to VIVO?
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
- Mike Conlon : thoughts on where this stands?
Bugs (1.11)
type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
Notes
Draft notes in Google-Doc
Actions
Previous Actions
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
- Mike Conlon, can you give this one a review?