...
Attendees
LG and SG members:
...
Ann Beynon, Robert Cartolano, Mike Conlon, Tom Cramer, Federico Ferrario, Anna Guillaumet
...
, Doug Hahn, Violeta Ilik, Dong Joon (DJ) Lee, Mark Newton, Virginia (Ginny) Pannabecker, Jean Rainwater, hannah sommers, Julia Trimmer, Terrie Wheeler, Alex Viggio, Joe Zucca
Duraspace:
Erin Tripp, Andrew Andrew Woods
Regrets:
Christian Hauschke, Erin Tripp
Note taker
Connection Information
...
- Membership year starts on June 1 (Julia, 5 minutes)
- Summit on April 10: who’s attending? (Julia, 5 minutes)
- April 12 Steering Group meeting about VIVO Combine (see the Product Direction for 2019) (Mike, 5 minutes)
- Product Evolution Task Force wrap up and VIVO Scholar Task Force plans (Paul/Julia, 10 minutes)
- 2019 VIVO Conference needs sponsors, registrants, and submissions (Violeta, 5 minutes)
- 2019 sprints resources and VIVO Committers (Andrew/Julia/round table discussion, 25 minutes)
- Can you contribute sprint resources?
- Are there potential VIVO committers at your institution?
Notes
- 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 Trimmer
- 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 UAB, 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.
- TAMU is all for aligning with the effort
- Draft a one-pager, have a consistent message
- Timeline? hopefully next year, it could be sooner, but we need to answer some questions first
- 2019 VIVO Conference - Violeta Ilik
- Open call for proposals - 2019 VIVO Conference
- Registration is now open, send people to conference
- Thank you to platinum and gold sponsors
- Presentations are welcome, just like every year
- Vacation discussions... 8-)
- 2019 Sprints and VIVO Committers - Andrew Woods
- fly-in meeting - came up with plan, how to move VIVO implementing product direction
- established sprint schedule, 4 sprints this year - 2019 sprints
- sprints tie back to the statement of direction
- call for developers to participate on the sprints
- how can your development staff work towards becoming a committer
- how can institutions encourage/support staff to participate more regularly on sprints
- build a deeper bench for the VIVO development team
- June 2019 - aligning VIVO and TAMU Scholar, read-only front end, and make VIVO Core supports them
- Julia - encourage your developers to become committers