March 4, 2016, 1 PM EST

Attendees

Steering Group Members

Paul Albert (star),   Melissa Haendel Dean B. KrafftRobert H. McDonaldEric MeeksJulia Trimmer,   Kristi Holmes

(star)= note taker

Ex officio

Graham TriggsMike ConlonJonathan Markowdebra hanken kurtz

Working group chairs

Ted Lawless,

Regrets

Alex ViggioBart RagonChris BarnesAndi Ogier

 

Location

Webex Meeting Link

Agenda

 
Item
Time
Facilitator
Notes
1Updates5 minAllSee below
2Review agenda2 minAllRevise, reorder if needed
3Conference update5 minJuliaKeynotes accepted.
4Spring User Group Meeting15 minMike, Julia, AlexInterest in a spring meeting? Not an Implementation Fest. Small (15-20 might attend?) focused on issues that could benefit from face to face discussion – Open VIVO, ontology, v1.9, networked VIVO, other. Graham Triggs will be in the US for a Duraspace meeting May 9-12 – we might consider tagging a user group meeting in front or in back. Possible cities: Atlanta (Graham and I will be there, and easy to get to), Orlando (cheap), Austin (Alex and Julia and possibly others will be there for several events), Chicago (also easy to get to, not cheap), others.
5Summit Planning15 minAllVIVO/Fedora discussion, VIVO presentation (Dean), Membership discussion, futures discussion, Breakout summary (Mike)
6VIVO CRM improvement15 minMikeVIVO Data in Zoho. See VIVO Membership Prospects
7Future topics3 minAllWebinars, VIVO Days, training, upcoming conferences

Notes

  1. Updates
    1. Open VIVO progress.  See OpenVIVO Task Force.  Figshare will produce VIVO RDF via its API.
  2. Conference update
    1. Keynotes for the VIVO conference to be announced.
    2. This is a very nice gender-balanced speaker group.
    3. We have no submissions yet. We still have 10 days though.
    4. You might reach out to people via social web. I would suggest reaching out to people and asking them to share these notifications with their community.
    5. Looking for volunteers for the Intro to VIVO workshop.
    6. Suggest reaching out to people who are new VIVO adoptees and asking them if they want to participate.
  3. Possibility of a Spring user group meeting
    1. This would be in lieu of an Implementation Fest. 
    2. Goal: bring people together to talk about hot topics that require in person conversations. This would be a kind of reprisal of some of the discussions we had at the previous i-Fest. Take us to another level of participation with respect to development.
    3. The opportunity is that Graham will be in the US May 9-12 for the Duraspace meeting. There is an opportunity in Austin where Alex and Julia will be attending a community leadership conference there. Other possibilities: Atlanta where Mike and Graham will be.
    4. Attendance of 20?
    5. Another suggestion would be the Big Ten Center. It's in Chicago. It's inexpensive by most standards. There's an A-Loft which is within walking distance.
    6. Suggest sending out a message to the Leadership Group.
  4. Summit planning
    1. The Fedora discussion will start at 8 am. At 8:30, everyone else will be able to join.
      1. Sandy might be able to do this. I will ask her if she wants to do this. 
      2. Mike to send Dean a couple sentences on what this request means.
      3. FYI - this would be just one of many opportunities to participate in this discussion.
    2. There will also be a series of presentations by steering group chairs. 
      1. These are supposed to be forward looking talks.
      2. Suggest you present as a group rather than switching off between
      3. Agenda early next week.
    3. VIVO will have two breakouts
      1. Conversation #1 - VIVO's role in the academy. 
        1. Dean will lead this discussion.
      2. Conversation #2 - Membership. 
        1. Jonathan will lead this.
        2. Jonathan is putting together a membership task force. 
        3. Jonathan will be asking for feedback on the task force charter.
        4. Goal of the meeting: get people to join the working group.
        5. We're also going to have a visit from Rob Cartolano from Fedora Steering. Rob and Fedora has been particularly good at recruiting members, so maybe we can take advantage of what they have learned.
        6. Is growing the community relevant to this discussion?
        7. One key element is helping make people aware of VIVO. Another element is the why. As in, why do we need a linked data system. What is this actually going to do for us. Sharpening this up would be critical.
  5. CRM improvement
    1. One of these things is to get to know our members. We can't just assume a VIVO will be in the library. We have 130-140 VIVO related organizations. In those organizations, we have about 500 people we know. The gap is this: we need to know who at the organization carries the VIVO message forward about membership. Who talks to the people who can decide about a membership.
    2. Duraspace has fleshed out the roles in the CRM, really try to find out who these people are, so we can do better messaging to people. We want to have a better notion of who we're talking to.
    3. The people who step up with sponsorship are often people different than doing the implementation.
    4. At big universities it's challenging to know what the landscape is. Knowing who to talk to can be very difficult.
    5. Mike will be sending out slices of data asking for help in improving our understanding of each VIVO organization.

 

Action Items