Versions Compared

Key

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

...

  • An ElasticSearch index which will contain all data from VIVO
  • A GraphQL endpoint to provide an easy, developer-friendly mechanism for obtaining VIVO data (see video for interacting with GraphQL interface)
  • The VIVO Scholar site, a read-only user interface that displays public profiles, provides a faceted search, and enables users to browse VIVO data
  • The VIVO Scholar interface will conform with the Worldwide Web Consortium Content Accessibility Guidelines version 2.0, Level AA Conformance (WCAG 2.0 Level AA) https://www.w3.org/TR/WCAG20/


Benefits

VIVO Scholar is being designed to be:

...

  • 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

...

Ralph O'Flinn, University of Alabama at Birmingham

Don Elsborg, CU Boulder

Alex Viggio, CU Boulder . . . and more!

Institutional Benefits of VIVO Scholar

...