Page History

...

• The job description is substantially complete. Will be circulated to Steering Group for one more additional review.
• A search committee for the tech lead will be formed with representation fro Leadership Group, Steering Group, Duraspace, and Community.  Mike will chair.  As people are asked and agree to serve, names will be shared.

V. Elsevier

• Daniel Calto and Holly Falk-Kryzinski Elsevier contacted Jonathan to discuss the future of VIVO and Elsevier's role in it
• Jonathan took the call and shared his thoughts with
• .  Also spoke directly with Debra.  Their concerns:
  
  • Their
  Debra – spoke with Daniel and Holly directly
  • Holly as manager of community felt their contributions had not been acknowledged or that they
  • They had not been engaged in strategic planning
  • The lack Lack of advancement in the VIVO technical plan
  • Asked them if there was anything they could do – they said no; they would be making other overtures to other groups such as Harvard
    
  • Daniel was in a worse place than Holly; they are interested in staying in touch with the community
• Dean – some of us at least have been seeing Elsevier acting more like a competitor than a collaborator
  • Mike – ditto
  • Dean – seem to be using us to target opportunities to say why their solution is better than VIVO; unless is more synergistic may not be a good fit
• Kristi – I feel like them not being invited to the strategic planning meeting was a terrible slight – while they sometimes drive me crazy and we like the Symplectic people, it is important to treat both the same
  • But we'll be fine – and frees us from tiptoeing around
  • We should engage Thompson and CrossRef a bit more actively who have been showing interest
  • A real movement to openness happening in lots of places that is not
  • Pivot and knock their socks off
• Debra – probably wasn't a good fit, but once we partner with somebody, we need to work with them and give people the seats they have paid for
  • Dean – how were they left out? Not invited
  • Debra – this gives us a clear picture in our membership drive of what we have to do
• Mike – I did talk with Brigitte from Thompson and there are real opportunities there – openness
• • . They will continue to sponsor the conference and continue to have interest in the community.
    
• Lessons learned:
  • Redouble VIVO efforts on inclusion, openness, transparency
  • Address member concerns in a timely manner
  • Stay the course on pursuit of technical lead, development of open source community
  • Pursue additional corporate sponsorship with others

VI. Steering Committee 2.0VI. Steering Committee

• Our charter says we should have 11 members and we have 6We .  We should be rotating 3 a year; we three members per year
• Plan A:
  • We could add 3 this year (to 9) and
  next until we are at the full complement
• Rotate one off next year, add 3 more, and that makes 11
• The following year we would go to the 3-per-year rotation
• • three next year with one rotating off to get to full complement
  • Add 2 nominated and selected by
  all members; 3 from leadership – add 2 from
  • leadership
  and
  • 1 from all members this year and do the same next year
• Dean – is there reason not to do 5 this year? Gets us up to full size and more engagement across the community
  
• Mike – we could, but we'd have to maybe not offer some of those people a three-year term
• Clearly we are in a transition
• Jon – will be rotating off due to retirement
• • (as per charter)
    
• Plan B:
  • We could add five this year. 3 from leadership and two from all members to get to 11
  • Three members would need to be identified as rotating off next year
• Either way, we are in transition and not fully in line with charter
• Jon will be rotating off next year due to retirement
• We will Mike – we should take these two options to the leadership group for feedback soon – their preference – Mike will get a draft to Dean to review and circulate with Steering before sharing with Leadership

VII. Additional Business

• Kristi – need to bring up the The conference
  • I'm supposed to be the conference chair but I don't know what it is I'm supposed to be doing, and I don't want to drop anything
  • Mike – let's have a conversation about this – for the first 4 years the contract was held by UF, and starting last year by DuraSpace
    • DuraSpace is financially responsible for the conference should it fail, with the hotel and the conference planners
    • the conference has residual funds that mitigate that risk
    • that's the framework Debra is speaking to
  • Debra – the logistics, not the programming; has time after this call
    
  • Kristi – wonderful that DuraSpace can facilitate things; Melissa doesn't have time to do the program, and as conference chair I have to worry about sponsorship – and I haven't been in the conference chair role before so I don't know what all needs to be done in that role – I need a Kristi to take care of what Kristi used to do
    
    • Rachel is our Designing Events rep again but doesn't understand the issue
  • Mike – let's have a meeting and go through it and let's have Designing Events on the call
    • go through the roles and responsibilities
  • Kristi – there are some places where DuraSpace could be very helpful – especially some of the follow up on sponsorship
    • Rachel is our direct person and is a challenge
  • Need to discuss roles of conference chair, program chair, conference planners, Duraspace, volunteers; need to discuss contract; need to discuss sponsorship – financial targets and assistance in recruiting sponsors
    
  • Additional issues: Designing event staff support, potential for Duraspace staff support for conference, engagement of VIVO volunteers, support for program chair
  • Dean – did we ever have a conversation with Michelle about Rachel – happy to chime in from my perspective as well
    • Everything came through wrong
    • One sponsor said they would not renew if have to deal with Rachel again
      
  • Mike will coordinate a meeting – Kristi, Debra, Mike, Designing Events
  • Debra – Michelle had logistical issues to review for change from last year
• Kristi – ORCID will soon have an announcement about funding – wants a major announcement

• • We want to reiterate
out
• • our commitment to collaborate with them and align our two organizations well
• Dean – a big chunk of money for marketing
Debra – Laure
• • ORCID is eager to work with all the DuraSpace projects and mentioned VIVO
; they are
• • ORCID is moving to a membership model
  • Kristi
–
• • is taking Laure's position on the AAUDE meeting panel discussion and will talk about ORCID and VIVO
  • Also a webinar coming up in
April – need help from the VIVO team
need to know what the vision is
• • April on VIVO/ORCID.  Will need to clarify vision for VIVO and ORCID to work together
• what have people done
• not bi-directional data exchange yet, but want to work toward that
• and thinking about properly structured information at ORCID
K – opportunities for us to bring funds in, and to partner with them on something; also a Potential for big effort in the CTSAs – CTSAs
• NCATS has a solicitation out for proposals for areas of work they should fund
• Opportunities in platform-agnostic data sharing across the CTSAs
• Thinking also on evaluation/reporting/visualization of data

The meeting adjourned at 1:53