You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Release 1.9 is expected to be a features release, aligned with VIVO Roadmap Process, and addressing its four major themes: 1) getting data out of VIVO using APIs, 2) getting data in to VIVO using best practices, 3) improved VIVO performance, 4) improved VIVO visualizations

Draft

The suggestions below have not yet been aligned with the roadmap process nor with interests to contribute effort to features on the roadmap.

Suggestions for the next release

  • Modularization: Continue modularization: abox reasoner.
    • Break out the ABox reasoner, with options to:
      • Disable the SimpleReasoner
      • Use the SimpleReasoner only to find most specific type
      • Use the SimpleReasoner as we currently do
      • Use an alternate reasoner
  • Performance: alternative triple-stores
    • TDB becomes the default, SDB is deprecated.
    • Distributed with adapters for Virtuoso and others.
    • Test performance with different triple stores:
      • Rendering large profiles
      • Inferencing
      • Indexing
  • Performance: Search indexer
    • Restructure the indexer for:
      • Better multi-threaded performance
      • Fewer unnecessary SPARQL queries
      • More configuration options
  • Ease of use: move the theme to the home directory
    • New themes or modifications won't require re-building VIVO
    • Enables wider usage of the Binary release (below)
  • Ease of use: Binary release
    • Installation instructions:
      • unpack the Zip,
      • set configuration options,
      • run.
    • Based on TDB and Jetty (instead of Tomcat)
    • Requires: Java Runtime Environment
    • Does not require:
      • Ant,
      • MySQL
      • Tomcat
      • Java Development Kit
      • Vagrant
  • Ease of use: Installation recommendations
    • For testing and experimenting, the binary release
      • Allows theme changes (see above), configuration changes, RDF changes
      • Anything that doesn't require changes to the code.
    • For enterprise installations or Java changes, the three-tier build.
    • Don't recommend the two-tier build.
  • No labels