Wednesday, November 25 at 11:00 EDT

LG members:

Paul Albert, Ann Beynon, Mike Conlon, Anna Guillaumet, Doug Hahn, Christian Hauschke,  Anthony Helm, bruce herbert, Damaris Murry (star) Terrie Wheeler

LYRASIS:

Laurie Gemmill Arp, Robert Miller, Michele Mennielli

Regrets:

Federico Ferrario, Tom Cramer Robert Cartolano

(star) = Secretary

Connection Information

Zoom connection information is available in the Outlook invitation.

Agenda

We have three interesting and important topics to discuss and vote upon this meeting that include:

1) the release schedule for the next major release of VIVO

2) do we want to organize a 2021 VIVO Annual Conference

3) VIAB direction, should we pursue growth in the US or Europe or both?

Meeting Minutes

  1. News
  • VIVO presentations have been submitted to Expert Finders (Thanks Ann) and will be highlighted at American Association of Health Sci Libraries (AAHSL) Panel on Research Networking Tools and HSL/institution experiences (Thanks Terrie)
  • Innovation and funding Opportunities (Thanks Mike)

Discussion:  We need to keep innovating.

Laurie: Lyrasis does have a grants officer, but any grant proposal needs to be further along than we are now.  Need a description of the project, the outcome, and the funder to offer an opinion.

Christian:  Received surprise funding from German government, got 11 person months for some product development. This grant is also for integrating knowledge graph and VIVO.  Have only known for a few days.  He is looking for software developer (EU Citizen is best)


  1. Discussion:   Report on Development Activities and Vote on Plan (Andrew Woods)

Andrew:   Has a proposed schedule for us to approve the next major release of VIVO.  University of Quebec at Montreal (UQAM) provided the bulk of the development work. They are Bronze members and ran for community seat on Leadership Group and but didn’t win.  They seem to be not well known yet in the VIVO Community, and ideas were discussed to raise their profile and effort in the VIVO Community. Furthermore, Andrew would like an agreement for the proposed schedule, which is as follows:

The process for moving from where we are now to a next VIVO release will involve:
1. Final review and merge of the i18n work (which is on a feature branch) into the core codebase
  - One week-long sprint during the week of Jan 25th
2. Publication and community testing of a release-candidate (RC-1)
  - Two week-long period of community testing from Feb 1st through Feb 12th
3. Iteration based on community testing and subsequent release candidates (RC-2, RC-3, etc)
  - Each iteration will be another two weeks. We should expect at least an RC-2, maybe more.
4. Final release of VIVO 1.12
  - Optimistically, early March

Timing is in line with resource availability.  

Decision:  The Leadership Group voted to approve this schedule.

Christian: Has a collaboration with Quebec working on two projects for data ingest.  Rather an adhoc meeting to find out if Apache Kafka messaging can be used alongside VIVO.  These two universities will make a short sprint to investigate the possibilities of messaging in VIVO. They are investigating ReCiter as well.  Hope to find a way to contribute something to each other, and eventually to the VIVO Community as well. 

Bruce:  William Weld also wants to move messaging forward. 

Mike: Pontificia Universidad Católica de Chile also presenting a messaging idea at the 2017 VIVO Conference.  They likely have dropped their VIVO membership, however.


2.   Discussion:    Do we Want to Organize A 2021 VIVO Annual Conference?

Bruce:  Kudos to Mike, Mic, Anna and Christian for organizing our 2020 Virtual Annual Conference. 

Mike: Thinks it is incredibly important to continue holding conferences.

Anthony: Important to the organization and to the user body as well.

Bruce:  Is anyone available, and willing to do it again?  Mike, Anna, Christian, agree to take this on again for 2021.  They will look for dates. 

Anna:  We are interested in more interactive session where engage the audience.  We need ideas for sessions that users would want to see. 

Christian: would like a dedicated discussion of ideas and feedback in a future leadership meeting.

Anna: Mic and I are working on a Spanish regional meeting (for Spanish speaking community).

Ann: Are we thinking of June for the annual meeting again?  Various user group meeting dates already set are discussed.

  • Spanish VIVO Regional Group Meeting – March/April (Anna)
  • German VIVO Workshop will be conducted in March (Christian)
  • VIVO 2021 North American User Meeting Announced for Jan. (Julia Trimmer, Benjamin Gross, Sacha Jerabek, Bryan Cooper, and David Wilcox)
    • We should invite UQAM to present on development work for i18N (Christian)

Decision: Leadership Group supports a 2021 VIVO Conference (virtual) and thanks Mike, Mic, Anna and Christian for (again) taking the lead.


3.  Discussion:  VIVO-in-a-Box has raised a fundamental question:  Project Summary

  1. There is reasonable consensus on the need for a system+services that would lower the difficulties or barriers for US institutions to experiment with or implement a VIVO instance. 
  2. VIAB, though, may not serve European institutions because of the different ways VIVO is used across the pond. If true, then serving this growing market may be the opportunity cost of addressing US institution needs.
  3. To meet the needs of institutions new to VIVO will take a coordinated strategy:
    1. VIAB software system – biggest lift is the need for an ingest system
    2. Training – Clarivate could help with this
    3. Community enculturation activities (invite to VIVO meeting, partner with other institution)
    4. Marketing materials to support activities of both Clarivate and VIVO community members
  4. The VIAB requires several development tasks:
    1. VIVO Core and VIVO Scholar (pretty good shape): may allow some 
    2. Separate VIVO from installation
    3. Data harvester based upon Reciter that draws from local sources, PubMed and Web of Science
    4. Profile Editor
  5. Major development teams that have expressed willingness to listen
    1. Development team completes Internationalization and installer work (through end of Feb?)
    2. Data harvester based on Reciter: Benjamin, Paul and Sarbijit
    3. Editor - William at Texas A&M
    4. Data Ingest Team - define data needed
    5. VIVO Membership & Community Engagement- training program
    6. VIVO Marketing Team: marketing materials
    7. New group: define minimal profile  
    8. Clarivate: Ann and her team explore how to market VIAB to Web of Science customers
  6. Lyrasis tasks
    1. Want to develop a hosted solution for VIAB?
    2. Want to build features that allow interoperable solutions for VIAB and DSpace (and maybe Fedora) 

Bruce:  The main question to address in the Leadership meeting is whether we should pursue growth in the US or Europe (or both).  VIAB, though, may not serve European institutions because of the different ways VIVO is used across the pond. If true, then serving this growing market may be the opportunity cost of addressing US institution needs.

VIAB meets our agreed-upon development priorities https://wiki.lyrasis.org/display/VIVO/Product+Direction+for+2020

Mike:  seeks clarification about why these are posed as competing, rather than complementary.

Bruce and Andrew offered clarifying ways to think about it. 

Ann: No one has disagreed with VIAB in the Leadership Group for the last two meetings, so why are we now seeing this as a competing choice.

Anna: VIAB could be helpful to smaller European institutions. 

Christian: Still need to see an institution where a standard VIVO can be used.   VIAB might help some institutions and certainly cannot hurt.

Comments from Leadership Group:

  • VIAB is aligned with development priorities
  • VIAB may be useful for small European institutions.

Decision: Quick discussion but there seemed to be consensus to continue developing the VIAB proposal.  Bruce promised a draft VIAB proposal ASAP.


Bruce:  Adjourned at 12:01 EST








   








  • No labels

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