Discuss development of OpenVIVO demo for Force11, seek potential collaborators
Notes
JIRA Tickets
VIVO-1229 was reported by Benjamin, has a proposed solution which he will commit for the next release.
GitHub Pull Request
Brian has improved the performance of writes to the triple store. Will merge prior to the next release, but currently on hold whilst we ensure there are no existing problems from the Maven changes that may come to light whilst working on OpenVIVO.
EarthCollab potential contributions
Huda demonstrated an extended view of the RDF for a profile, and a JSON serialisation.
The RDF extension seems uncontroversial, and everyone looks forward to seeing contributed.
JSON serialisation is of the Template model used in FreeMarker. Whilst this is functional in the short term, Graham noted that it was not a clear, concise model of the data that could be consumed by non-linked data experts - Justin confirmed that his JSON work had been targeting the use of case of non-linked data users.
Serialising the data model that drives the Freemarker templates is also prone to instability in upgrades - it doesn't just risk a change to the underlying ontology affecting the serialisation, but also any changes that we might make to the Freemarker templates necessitating a different contract between the back and front ends.
There wasn't a significant appetite for a JSON serialisation of the template model on the call, most people would prefer a simpler, clearer JSON model.
OpenVIVO demonstration
Confirmed on the developers call that we are actively pursuing, and have a task force to produce, a demonstration OpenVIVO system by the time of the Force16 conference.
Graham demonstrated the current work to make it possible to enter a DOI and claim an author / editorship against that work.
Sought potential collaborators to fulfil some of the other requirements for branding, etc.