The VIVO Scholar Task Force will be creating a new user interface for VIVO, called VIVO Scholar. VIVO Scholar will work with VIVO implementations at version 1.10 and above. The VIVO Scholar Task Force will begin began on April 15, 2019.

The VIVO Scholar Task Force will address one of the goals in the Product Direction for 2019, "Modernize the Presentation Layer," which is a priority for many existing and prospective VIVO implementers. VIVO Scholar will build on the work of the Product Evolution Task Force, employing many of the ideas and technologies explored by that group. VIVO Scholar is also informed by the work of participants in the Architectural Fly-in Meeting held in January 2019.

...

VIVO Scholar is being designed to be:

• Fast–when Fast–-when loading pages and when retrieving VIVO data in near real-time
• Developer-friendly so it's easy to implement and customize
• Attractive and modern
• Responsive to many devices and accessible for users with disabilities
• Fully supportive of multiple languages

...

• The VIVO Scholar Task Force will consist of members from three or more institutions, but the majority will come from Duke University.
  • Most of the members will have been involved with the Product Evolution Task Force in some way. 
  • We aim to keep the development team small, with 8 members or fewer if possible, and will include developers with applicable skills.
  • Some developers may contribute for specific tasks or for specific sprints.
• The task force will operate with continuous, two-week sprints. Work will be deliverable-based rather than exploratory.
• Weekly meetings will be closed to keep discussions focused.
• We intend to streamline development processes and meetings as much as we can.
• We'll create milestones with deliverables that we can share with the community and get feedback.

Facilitators

Damaris Murry, Duke University

...

For Product Evolution milestones, see here.

More Information

Yep, we'll have meeting notes and all kinds of stuff here . . . soon.VIVO Scholar Task Force meeting notes can be found in the Google Doc, (be warned: they are detailed!)