Versions Compared

Key

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

Date

Temporary NotesPermanent Wiki Pagehttps://goo.gl/FlvbTFPermanent Wiki Page: y3kOJD

Attendees

  • Graham Triggs, Duraspace

  • Mike Conlon (Duraspace)

  • Ted Lawless (Thomson Reuters)

  • CU Boulder (Don & Alex)

  • Greg Burton (Duke)

  • Javed (Cornell)

  • Marijane White (OHSU)

  • Paul Friedman (Northwestern)

  • Benjamin Gross (UNAVCO)

  • Rob Nelson (Duke)

 

Announcements

Discussion items

TimeItemWhoNotes
5m10mIntroGraham Triggs

Introduction and general announcements

20m15mVIVO 1.9Graham TriggsVIVO 1.9 - Your questions answered
30mVIVO 1.10 / 2.0Graham TriggsPotential developments for the next release

VIVO 1.9.0

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

Define requirements of a JSON interface

Notes

  • Ted has updated Vagrant for VIVO 1.9, but he’s only done some testing

  • Mike has installed 1.9 on his Mac -- was easier with Maven


JSON - Don would like to be involved, concern over differences between RDF and display views.

Ted - can we use Huda’s work?

Don - can we address the content negotiation? Can we change the redirects?

Create a javascript vivo-isf library

Vivo lod server only delivers the content -- doesn’t have logic to translate/transform data -- that belongs in the app layer


Mike - modularisation of ontology.

Published, routable, versioned ontology files -- they need to be accessable

This will enable smart applications that can render our complex data

Modularization will decouple the domain specific ontologies from vivo

Issues with content (vcard) vs continuent (person) entities as authors

Domains and ranges in general need review 


Recent JIRA Tickets

 

GitHub Pull Requests

...