Implementation and Development Call 20150409

Shortcut to temporal Google doc for meeting notes: http://goo.gl/gvN5ZS

Announcements

• Apps & Tools Working Group: next call April 21 at 1pm ET

• Link to presentation sign up sheet

• Link to presentation template

• Ontology Working Group: next call May 5 at 1pm ET

  • When there’s no Apps & Tools or Ontology call, there’s usually an “office hours” call for informal, unscripted questions about the ontology
• 2015 VIVO Conference Call for Papers now open!

  • All submissions through EasyChair due by Friday, April 24th 5:00 PM PST

  • More info and links online: http://vivoweb.org/blog/2015/04/2015-call-papers-now-open

• ORCID/VIVO webinar "Enhancing Early Career Researcher Profiles: VIVO & ORCID Integration" on Thursday, April 16th 11:00 AM EST

  • Additional info and registration link here: http://www.duraspace.org/node/2498

• Site updates on next week's call

Theme: VIVO on Virtuoso Open-Source Edition

• As reported on last week's call, the Weill Cornell VIVO is now running on Virtuoso Open-Source Edition.

  • "Virtuoso is a scalable cross-platform server that combines Relational, Graph, and Document Data Management with Web Application Server and Web Services Platform functionality."
  • Virtuoso Open-Source Edition Wiki
  • Virtuoso Open-Source Edition GitHub repo
• Eliza and Paul from Weill Cornell will join us to discuss how their VIVO 1.7 has been modified to replace Apache Jena with Virtuoso. This will be an open discussion, and we've invited others who have explored replacing Jena with other triple store technologies. Congrats to Eliza!

• Some preliminary stats reported last Thursday:

  • Even the largest profiles (2+ MB) load in 6 seconds

  • Compiling and processing a (???) query takes less than one second

  • Most of the load time is in network lag between the database and the app

  • Still slower for a logged-in user, but Eliza is optimistic that she can get some further gains for logged in users

  • Tried an inference on their staging site and wasn’t especially snappy -- looking forward to how things perform with VIVO 1.8

• Possible questions:
  • How did they acceptance or load test this integration?
  • What kinds of performance gains are they seeing in production?
  • Does Virtuoso increase the server resource (CPU, disk space, memory) requirements?
  • Did they have to disable any VIVO 1.7 functionality to accomplish this integration?
  • Why not use the commercial Virtuoso offering? Is commercial support available for their open source version?
  • How might their custom code be contributed to add out-of-the-box Virtuoso support to a future VIVO release?

• Date: Every Thursday, no end date
• Time: 1:00 pm, Eastern Daylight Time (New York, GMT-04:00)
• Meeting Number: 641 825 891

To join the online meeting

• Go to https://cornell.webex.com/cornell/e.php?AT=WMI&EventID=167096322&RT=MiM2
• If requested, enter your name and email address.
• Click "Join".

1. Call in to the meeting:

   1-855-244-8681 (Call-in toll-free number (US/Canada))

   1-650-479-3207 (Call-in toll number (US/Canada))

2. Enter the access code:

   641 825 891 #

3. Enter your Attendee ID:

   8173 #