Page History

Release update

Jim: RC3 should go out Monday

Current blocker issues

Join the release test mailing list if you wish to be informed of release candidates, plus the final distribution -- and we’d love to have help testing -- subscribe here: https://lists.sourceforge.net/lists/listinfo/vivo-release-test

Apps and Tools Group

The next call is next Tuesday, November 19 at 1 pm ET

, led by Chris Barnes from the University of Florida.

Upcoming Events

VivoCamp pre-conference at SWIB13 conference, November 25-27 in Hamburg https://sites.google.com/site/vivocamp13/ 

• short presentations and demos on a number of topics by a couple of experienced people, followed by discussion, Q&A, panels etc.
• Organized by Valeria Pesce, Lambert Heller, and Lukas Koster
• John Fereira from the U.S. will be attending

Duke will be hosting the 2014 VIVO Implementation Fest from March 19-21 – reserve your hotel room today and stay tuned for more information in coming weeks

Updates

• Brown (Ted)

• Finalizing data load process from existing profile system for December rollout to faculty, starting with campus availability

• Stephen: please share results of your focus groups

• Working with Provost’s office on displaying organizational structure in VIVO, thus filling a real need on campus.

• Colorado

• (Stephen & Alex)

• Working on testing 1.6 of VIVO starting with our UCCS data.  We’ll send in tickets to Jira later today (and confirm tickets if they already exist)

• Beginning to wireframe visualizations using D3.js and Google’s API and our VIVO data.

• 2013 curation in Elements is finished and our curators are going back in time

• Will be looking at Harvester integration with VIVO 1.6

• Working on getting the Harvester examples translated to 1.6. API integration slated for 1.7.

• Cornell (Jim, Brian, Huda)

• Working on 1.6RC3 for early next week

• Huda continuing to work on DataStar

• Duke (Patrick, Richard & Sheri)

• Continued work on artistic works looking at legacy data from previous systems.

• Looking at the Library of Congress Subject Headings and getting those included into our instance.

• Sheri: will version 1.6 include an LCSH service call? Answer: yes!

• EPA (Zac)

• No updates again today, sorry. 

• Memorial (Max)

• Working on a Drupal application…[sorry didn’t catch the details]

• Correction: Memorial is continuing to work with Stella as a migration analyst.

• Looking for third party VIVO consultant as Stella who was consulting on a project basis with them, but has moved to a full-time job -- also VIVO docs need updating for 1.5/1.6

• Stephen recommended posting this to the VIVO dev list, as some older VIVO NIH project developers might have interest and availability

• Alex to follow up with Max offline about tracking down a possible consultant; it’s important that the project (DuraSpace) maintains and provides a list of consultants, vendors, or interested former VIVO developers

• Paul: what’s the best way to publicize your need and solicit consultants?

• There are a lot of other semantic web developers outside the VIVO community (see LinkedIn Semantic Web groups -- is there a VIVO wiki page for this?) who might be drawn into the VIVO project.

• RPI - Patrick out today, but interested in possible VIVO/CKAN integration demo next week

• Scripps (Michaeleen) - no update today

• Does the Implementation Fest rate apply to Saturday night? Who should I contact?

• Stephen: try calling the hotel

• Alex: still working out a schedule, but considering a hackathon on Tuesday; possible Friday sponsor meeting

• Update: Julia Trimmer at Duke will contact the Hilton to discuss the possibility of extending the VIVO rate to include Monday and Saturday nights

• Stony Brook (Tammy) - loaded data on to VIVO Stony Brook Medicine, converted from VIVO 1.5.2 to VIVO 1.6 rc 2.  I know rc2 is not officially “ready” yet, but… I’m happy to report that it appears to be working very nicely!

• Although, one strange little thing happens - when you log in, a few rogue predicates are visible under “Other” (“bearer of”, “has contact info”, “participates in”, “related by”).  “Related by” shows some good things -- the labels for grant name and position name.  But it also shows only the URI for the authorship(s).

• First look at a VIVO 1.6 instance with data?

• Paul to talk with Tammy about modeling medical expertise data

• Might be a 1.6-specific bug modeling organizations

• UCSF (Eric)

• Would be willing to do an OpenSocial demo at a future implementation call

• Alex: you should try to attend the Implementation Fest -- interest in OpenSocial and ORNG, and Profiles’ VIVO RDF

• Virginia Tech (Julie)

• No major updates; been working on other projects

• Beginning of the search process to find two systems engineers (one for VIVO and Symplectic Elements and another for cloud management)

• Weill Cornell (Paul, Eliza)

• VIVO is in Large Pilot stage

• Struggling to remove/subtract data from graphs using site admin tools

• Stephen: this has been a recurring bug in Harvester; Eliza: but we are using the site admin tool

• Brian: normally this should work; we might have to go offline and see what the problem is

• Eliza to send out message describing the problem to dev-all list

• any others?

Next Thursday’s call

• Alex: what about two demos next week - VIVO/CKA and OpenSocial?

• Stephen: sounds good; we should do the release update, the two demos, and then the updates pending time 

Notable list traffic

See the vivo-dev-all archive and vivo-imp-issues archive for complete email threads

SPARQL Query for paper title

• CAS and VIVO – (John from Memorial) – Is anyone using it, and if so, do you have any good anecdotes or documentation to share? Our institutional single sign-on is built on a stock CAS instalI.

  • Notre Dame may have done so in the past but is not pursuing it.

  • Tammy is using CAS.

  • I hear no

• How are user accounts associated with profile pages?
• JRuby code that performs the equivalent of creating inferences in the process of assembling a Jena resource: https://gist.github.com/patrickmcelwee/7377676 (Patrick)

  • This is awesome. Thanks, Patrick!

Call-in Information

• 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".

To view in other time zones or languages, please click the link:  https://cornell.webex.com/cornell/globalcallin.php?serviceType=MC&ED=167096322&tollFree=1

To join the audio conference only

• • To receive a call back, provide your phone number when you join the meeting, or call the number below and enter the access code.
  • Call-in toll-free number (US/Canada): 1-855-244-8681
  • Call-in toll number (US/Canada): 1-650-479-3207
  • Global call-in numbers:  https://cornell.webex.com/cornelluniversity/globalcallin.php?serviceType=MC&ED=161711167&tollFree=1
  • Toll-free dialing restrictions:  http://www.webex.com/pdf/tollfree_restrictions.pdf
  • Access  code:645  873 290