Page History

...

There are a number of possible routes to performance improvement for VIVO, and we seek input from the community on what the primary pain points are. Some performance issues are related to installation and configuration of VIVO and we are working on improving documentation, notably on MySQL configuration, tuning, and troubleshooting, but page caching has emerged as the primary performance-related improvement for 1.6.

Anchor
Caching Caching

Page caching

...

• Make the About page HTML content editable through admin interface – this relates to display model changes
  
  •  

    Jira
    server DuraSpace JIRA key VIVO-105

  • Note that the home page cannot be made editable through the admin interface as it is too complex
•  Offering improved options for content on the home page, including a set of SPARQL queries to highlight research areas, international focus, or most recent publications
  

  • Jira
    server DuraSpace JIRA key VIVO-106

•  Offering additional individual page template options
  

  • Jira
    server DuraSpace JIRA key VIVO-107

  • Document the screen capture configuration as part of this
    
    • could put the service-specific aspects in a sub-template that gets imported and could be default not attempt to capture and cache images at all
    • are free services out there, but they may not be there in 6 months
•  Offering the ability to embed SPARQL query results in individual pages on a per-class basis – for example, to show all research areas represented in an academic department
  

  • Jira
    server DuraSpace JIRA key VIVO-108

...