...

• Membership news
  • Sigma, the research consortium from Spain, has joined as a gold member. They are a national consortium similar to Cineca (based in Italy). We have U. of Grenada and [a Madrid university] are adoption sites, and are so listed in the Registry 
• Developer meeting on the 11th
  • 2018-01-11 - VIVO Developer MeetingDevelopment IG
    
  • We put together a Slack channel - vivo-project. Here's how you register: https://goo.gl/forms/oKpGQkHBOi8RYf992
  • Maybe it's worth having a private channel for Steering.
  • We've discussed how we can move forward in Graham's absence.
  • Next call will be Tuesday at 11am.
  • Seems like there's a lot of interest in development processes, specifically not having there be a single person whose job is to weigh in on code contributions.
  • I want to see that the priorities which Mike defined (based on feedback from the community) are aligned with the developers'.
  • There is a strong interest in getting the 1.10 / 2.0 release out sooner rather than latter.
  • Mike: the Project almost destroyed itself in 2013, because there were a lot of changes to the ontology but no benefits to the user. My preference would be to get some more feature upgrades in there. I think calling it 2.0 without new features is fatal.
• ResearchGraph collaboration (Erin Tripp)
  • Mike and I have been working on ResearchGraph. Goal: develop a repeatable process that significantly reduces the effort of mapping and loading data into VIVO.
  • Wants to provide seed data to produce a fully populated VIVO.
  • Proposing a Feb-April pilot. No memoranda of understanding signed yet. Wants to have something to present at March Berlin conference.
  • Goals, among others: 
    • set up a turnkey VIVO, reducing effort of new implementers
    • augment existing VIVO
  • Outcomes
    • A formal service definition
    • Technical pipeline and deployment model
    • Cost model for people would like to use this service
    • A recommendation re: go to market decision
  • Full proposal
  • Executive summary (for publication/sharing) 
  • Slides (for publication/sharing) 
  • Abbreviated Proposal (for publication/sharing) 
  • Eric: I think there is a market for sites that want a simple profile system, because they're coming to us at UCSF.
  • Alex: Is it okay to share beyond this group? Erin: I have a special verison that leaves off the FTEs.
  • Does ResearchGraph have a roadmap? Erin: I can follow up on this.
• Harvester
  • Tom Cramer has talked with Mellon Foundation about a planning grant.
  • Mike: goal have a plug-in modules for PubMed or licensed resources that allows for putting in a license. Tom has also talked about producing RDF and other formats including JSON. They're thinking quite broadly about collecting data from a variety of sources depending on the plugin library. For example, Dimensions is very interested in getting data from their system into VIVO. This thing would also have to have some sort of disambiguation capability. 
  • Two key functions: retrieval and parsing.
  • Some people already met: Sandy, Rob, Tom, Mike.
  • Julia: is this problem a task force? Mike: Tom asked if this should even be done under the VIVO auspices. We encouraged him to do this. Some of this stuff we will discuss in North Carolina.
• North Carolina meeting
  • Julia: we need to plan this meeting. We should try to plan the objectives for this meeting.
  • Mike: This is very much a leadership group meeting. We should announce this meeting and collect input from the community ahead of time. And, we should try to circulate info so people are "in the know" ahead of time.
  • Julia to create Slack channel and Google Doc.
• Budget planning
  • Early Draft
  • Dean: how is common good divided amongst the projects at Duraspace? Debra: we're transitioning to a new model for charging expenses. It's a tax on direct expenses. 
  • Dean: I would like to follow up on this more later. Val could join us at the next meeting too.

 Action Items