...
Temporary Notes: https://goo.gl/FlvbTF
Permanent Wiki Page: https:// goo.gl/6HQ14S
Attendees
Graham Triggs, Duraspace
Announcements
...
...
Discussion items
| Time | Item | Who | Notes | |
|---|---|---|---|---|
| 10m | Intro | Graham Triggs | Introduction and general announcements | |
| 15m5m | VIVO 1.9.1 | Graham Triggs | VIVO 1.9 - Your questions answered | Minor pom corrections and SEO improvements |
| 10m30m | VIVO 1.10 / 2.0 | Graham Triggs | Initial progress report and issues | |
| 35m | "Perfect" VIVO | Graham Triggs | What would the perfect VIVO be?Potential developments for the next release |
VIVO 1.9.
...
1
A couple of minor issues have been reported with the pom.xml Released on 8th August, this is the first release to use Maven. This will make it easier for new adopters to implement, and to get started with a development environment (e.g. for encouraging contributions), however existing sites will need to rework their local projects slightly in order to upgrade.
Additionally, in order to take full advantage of the new features in the release - linking to the Capability Map, enhanced AltMetric support, sitemap for better indexing - upgrading sites will need to make some small adjustments to their configuration.
If you have any questions about the new release, this is your opportunity to ask them!
Potential Developments
Upgrade dependencies (e.g. Jena)
New theme
Faceted browse/search (switch to ElasticSearch or implement with Solr?)
VIZ-VIVO contributions
Not building correctly on Windows due to character set encoding issues).
After adding OpenVIVO to Google Webmaster Tools and reviewing the results, there are some minor changes that can be made to the templates so that Google can parse the structured data correctly.
As a result, the intention is to release 1.9.1 soon to address these issues.
VIVO 1.10 / 2.0
New branches with Jena 3.1.0 - these libraries operate as RDF 1.1 by default.
Jena now also incorporates the json-ld libraries, and updates them. The default serialisation is not directly comparable to the existing serialisation.
"Perfect" VIVO
In the last 10 years, a lot has changed in the way web applications are built, and the expectations people have of them. RESTful APIs and JSON for integration and automation, responsive web pages, dynamic loading of web page content, etc.
At the same time, we've learnt a lot of lessons about the current architecture, areas that might not work, have scalability challenges, etc.
So, if we were starting from a completely blank slate, what should VIVO do? What architecture should we implement, what things should not be reimplemented?Define requirements of a JSON interface
Notes
Recent JIRA Tickets
...