Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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.

Task Force Objectives

  • 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.

This is all preliminary and subject to change . .

Deliverables

VIVO Scholar will consist of three components:

...

  • Install VIVO and VIVO Scholar, using VIVO to edit data and permissions OR
  • Install VIVO and develop their own user interface using the GraphQL endpoint

Image Added

Task Force Objectives

  • 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.

This is all preliminary and subject to change . .

Facilitators

Damaris Murry, Duke University

...

Sarbajit Dutta Weill Cornell Medicine

 . . . and more!

Institutional Benefits of VIVO Scholar

...