October 9, 2015, 1 PM EST

Attendees

Steering Group Members

Paul Albert (star),  Dean B. Krafft, Eric Meeks, Andi Ogier, Bart Ragon, Julia Trimmer, Alex Viggio

(star)= note taker

Ex officio

 debra hanken kurtz, Graham Triggs

Regrets

Jon Corson-Rikert, Robert H. McDonald, Melissa Haendel, Jonathan Markow, Mike Conlon, Kristi Holmes,

Dial-In Number:  641-715-3650, Participant code: 117433#

Agenda

 
Item
Time
Facilitator
Notes
1Updates5 minAllSee below.
2Review agenda2 minAllRevise, reorder if needed
3Email recommendation

20
min

GrahamFirst discussion/ approval. See https://gist.github.com/mconlon17/ad8e7d577b85a7267434
4Semantic Versioning recommendation10 minAllAdditional discussion/approval. See https://goo.gl/OiqCyr
5Use of Maven recommendation

10
min

AllAdditional discussion/ approval. Use of Maven as a build tool in future releases of VIVO. See https://goo.gl/PvihXQ
6Repository Fields and Values recommendation10
min		AllVIVO site info to drive site listings on the new VIVO web site. See https://goo.gl/c7xISd
7Future topics3 minAll

attribution/contribution efforts (10/16); Harvard Profiles (10/23?); In-Kind contributions (Oct 30?) how does VIVO get bigger?; webinar series; training program; rotation of Steering Group members

Notes

Attendees: Dean, Paul, Graham, Alex, Bart, Julia, Eric

  1. Updates
    1. Alex attended CO-LABS 2015 Governor's Award for High-Impact Research – several Boulder-based researchers with VIVO profiles (or hopefully soon) were honored. Good opportunity for networking and sharing VIVO project story with CO-LABS board members and award winners from LASP, CIRES, NOAA, and NIST.
    2. Version 1.8.1 is nearing completion.  Performance improvements.  A patch release.
      1. Meeting with Roadmap task force being scheduled.  Confirm 1.8.1, plan 1.9 for 4th quarter 2015.
      2. Meeting with Cornell team being scheduled
    3. Duraspace is launching DuraSpace Informe, a monthly e-newsletter in Spanish.  Will include VIVO content as well as content for other Duraspace projects.
  2. Email recommendation
    1. As per this Gist file, goal is to consolidate the sprawling number of email listservs. In particular, all the tech emails
    2. Also move from SourceForge to Google Groups.
    3. Benefit: being able to view archives of historical email - which always be through groups.google.com
    4. Steering group and Leadership group currently go through vivoweb.org which is a Google group. It would seem to improve the branding more to use vivoweb.org name.
    5. We should probably get additional feedback from others Steering Group members
    6. Migrating messages shouldn't be a problem, so we shouldn't have that big a problem.
    7. However, we need to get people to re-subscribe to the new list.
    8. We should market the new lists to the broader list we use for conferences.
  3. Semantic versioning for VIVO
    1. Ontology versioning is important but it's not critical to this proposal. This policy, if adopted, wouldn't have an impact until next year.
    2. Perhaps Mike should do an email of the Steering Group to see if there needs to be discussion at a future meeting.
    3. Does this mean we wouldn't call a version 2.0 absent an ontology change? Not necessarily, but I don't think this is accounted for in this document. If we had significant enough changes but no ontology changes, then we might want to seriously consider a 2.0 version number.
    4. The language doesn't state that major ontology changes aren't the only reason.
    5. We may have cause to confer a major release number to software in order to better market it
  4. Maven
    1. Not a ton of feedback about this. Ted did suggest generating technical documentation within the codebase itself. But this is not a key goal of Maven initially.
    2. Having the documentation close to the source makes using an API up to date.
    3. In the absence of contrary feedback over the past two weeks, I suggest we bless this.
    4. Decision: Maven has been blessed.
    5. Close to suggesting we release 1.8.1. There are a number of performance improvements.... With the contributions I've done overnight, I think we're faster than the 1.7 release.... Remaining opportunity: unnecessary conversion of RDF into serialized form. That's taking about 10-20% of execution time per page. Other than that, we're running up against the limits of querying a result set.... The only other possible opportunity is displaying data via AJAX requests.
  5. Repository fields and values recommendation
    1. This is the Duraspace repository to track VIVO sites. Mike had some feelings about adding different types of universities.
    2. It would really help me to know how this information is being used before I could say how this makes sense.
    3. Perhaps we should delay discussion until Mike returns.
  6. In-kind contributions group met
    1. Jonathan M. will write up a proposal. This should be ready the week after.
  7. Update about the SURA group
    1. We had a call with Dave Eichmann and the SURA group. Dave is putting together a search tool specifically for the five pilot schools in SURA. What he gets out of the deal is he can harvest additional data. 
    2. Dave now has a web service where, given a URI for a person, you can get a co-author list, but in addition to names, it will have their URI, if they have a linked data URI. The benefit for us, is that you have a linked open data link to go off to different institutions.

Action Items

  • Jonathan Markow will lead future discussion of on-kind contributions to membership
  • Graham Triggs will document Maven usage and promote via the development list

 

 

 

 

 

 

 

 





All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.