...
- Membership conversation
- Summit on April 10
- List of attendees
- Project update in the morning
- 1PM and 2PM (St. Louis time) - Two 45-minute sessions - teleconferencing info will be provided
- Suggested topics - general update on development, VIVO project objectives, opportunities under Lyrasis, governance discussion
- April 12 Steering Group Meeting - Mike Conlon
- Open Meeting - ideas around VIVO Combine
- Planning effort around moving 2019 plan forward, at a very early stage
- Share ideas about what we are trying to create
- 11AM on Friday - open meeting, will promote via mailing lists
- Product Evolution and Project VIVO Scholar Task Forces - Paul Albert, Julia
- VIVO Scholar - this is a new development effort
- Build a better interface, one that is appealing to both developers and for key-decision makers. 6 to 12 met on a weekly basis, use React with ElasticSearch back-end, API interface to interface with ElasticSearch back-end, robust search and reporting functionality. At this point, back-end in place, basic data model derived from VIVO data model.
- Product Evolution Task Force will be complete April 15
- - some sample object pages, people, grant, list view, designate as a MVP
- delivery of back-end, sample data, API interface, some sample pages
- fruitful discussion
- VIVO Scholar Task Force
- will start on April 15 - Duke, Weill Cornell, and UAV, continuous sprints - 1-2 FTE from Duke, 2-3 developers at 20%
- Looking for developer contributors - this is our big project for the next year
- Three Main Deliverables - see VIVO Scholar Task Force
- Julia emphasizing importance of GraphQL API - helps to support edit in VIVO, publish everywhere
- Accessibility - Duke accessibility team - what specific accessibility standards to be supported
- Community engagement - share video, share milestones
- Q. Dependency on VIVO 1.10 or 1.11? - VIVO is included to provide a user interface for updating or correcting data, because the new interface is 100% read-only
- Q. What is different between Product Evolution and VIVO Scholar - Evolution was more exploratory, sharing of ideas, hear from a lot of people, then create a different task force for VIVO Scholar with focus on specific development milestones
- Q. Clarify role of VIVO Scholar, relationship to current front-end, also TAMU has been working on something similar - good to reconcile, architecturally if VIVO Scholar and TAMU and VIVO core effort are aligned architecturally. How does get from VIVO to ElasticSearch and what does that data look like? A similar approach recommended.
- 2019 VIVO Conference
- 2019 Sprints
...