Versions Compared

Key

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

...

  1. Modernize the presentation layer of VIVO.
    This includes the product evolution work on presentation, as well as work on internationalization, simple localization, responsive and accessible interfaces.  The new interface will capitalize on new architectural work to support widgets and visualizations. Development efforts will be aligned with the goal of creating a modern new interface for VIVO.


  2. Decouple the architecture.  
    This occurs on two levels -- VIVO as an ecosystem of applications (combine, search, data store, presentation, analytics) and within the core, separating indexes, presentation, and inferencing, as well as additional components such as the data distribution api, user tracking, access control, and workflow.  Decoupling includes new maven build processes supporting the decoupling. Decoupling also includes architectural work to support widgets and visualizations.


  3. VIVO Combine.
    The VIVO ecosystem needs an open source tool for collecting, identifying, and transforming institutional data such as employment, teaching, and repository entries, with external data such as records from indexing services, into data that can be used by the VIVO ecosystem.  This major effort requires planning. Planning such a development effort could possibly be financially supported by a grant to the VIVO Project. VIVO will pursue planning grant funding for the VIVO Combine.


  4. VIVO Search.
    LG believes cross-site search is of less importance for 2019, and that more conceptual work is needed to determine how search might be used in a VIVO ecosystem, how it might relate to cross-site linking, and how search might be facilitated by new distributed web technologies in VIVO, such as TPF.  A symposium for the conference in Podgorica is suggested as a mechanism for idea generation around se

...