VIVO Updates for Jan 7 -- New Year, new initiatives

Happy New Year from VIVO!  I wish everyone in the VIVO community a very Happy New Year.  We have much to be thankful for and much to look forward to.  Here are just a few things we can look forward to in 2018:

  • A new approach to community development. In the coming year we hope to organize sprints – concentrated effort related to the development of specific new features.  Software sprints will develop new capabilities for VIVO and Vitro, and incorporate great work available at VIVO sites into the base VIVO for everyone to use.  We look forward to building on the great work of the community to share that great work with others.  This is the essence of open source software development.  Do you have work to share?  We look forward to creating sprints to incorporate your work in future releases. We are gathering examples of great community work that should be available to others through the VIVO community open source efforts.  Please send any example you have of your work, or work of others that you have seen presented at a VIVO conference, or have heard of through lists or community activity. Let's build a better VIVO and Vitro for everyone!
  • VIVO events throughout the year:
    • The VIVO Conference will be held at the JB Duke Hotel in Durham North Carolina on the campus of Duke University, June 6-8, 2018.  Let's see the new community development process bearing fruit for discussion and further development at the conference.  This year, the conference specifically welcomes all those engaged in the representation and creation of open data regarding scholarship.
    • VIVO Camps.  VIVO is planning two camps – one for the spring (April?) and one for the fall (November?).  If you have comments or questions about dates, location, content, or anything else related to these 2.5 day training opportunities, please contact Mike Conlon.
    • VIVO Meet-ups.  Are you planning to attend a conference where other VIVO folks, or people interested in VIVO, or people who should be interested in VIVO (that's almost everyone!) will be attending?  Perhaps you'd like to organize a VIVO meet-up – an informal meeting of VIVO people to discuss VIVO and introduce others to VIVO.  Here's a list of some of the events that we expect VIVO folks to attend over the coming year.  Conferences Attended and to Attend  Are there others?  Please drop us a note.
  • New engagement with Leadership and Steering. The  VIVO Leadership Group and VIVO Steering Group set direction for the project.  New members are elected each year predominantly from organizations supporting VIVO through membership in Duraspace.  Becoming a member is easy.  See Becoming a Member of Duraspace.  Want to help? Please contact a member of Leadership or Steering.  Leadership and Steering will be having a joint meeting in the new year to establish a new roadmap and new strategies for executing the roadmap.  We will have more news about this shortly.
  • Technical developments New approaches for getting data out of VIVO (see below), new approaches for getting data into VIVO (see below) and more are being developed.  Do you have ideas about community open source development?  Are you a developer and want to help?  Please contact Andrew Woods who will be helping develop VIVO's technical community in 2018.
  • New approaches at Duraspace.  In the past, Duraspace provided services to its projects, while the projects operated quite independently.  Over the coming year, expect to see a more integrated approach from Duraspace, with multiple people participating in the project in various new ways.  Business development, membership, partnering, and development of technical community will engage new people and new efforts across all Duraspace projects, including VIVO.

Graham Triggs.  Graham is leaving the VIVO Project as of December 31, 2017.  After two plus years of developing software, creating new releases, launching OpenVIVO, and helping organize the technical documentation, Graham is moving on. Graham's deep knowledge of software development, the VIVO code base, and system environments for VIVO will be sorely missed.  I greatly enjoyed and appreciated working with Graham.  He is an amazing talent. We wish him well in all his future endeavors and profusely thank him for all he has done for VIVO.

Getting Data out of VIVO.  We have a number of methods for getting data out of VIVO.  We can unload the triple store into a single file for use in data analysis software such as R and Tableau.  We can use the Vitro APIs to issue SPARQL queries, and we have many examples of using SPARQL queries for answering adhoc questions, and providing standard tabular data for other applications. And now, Cornell University has made available their Data Distributor, available as an add-in for VIVO versions 1.8 and above.  The Data Distributor supports adding SPARQL queries to VIVO and having them respond at URls of your choice.  This makes it very convenient to support the use of VIVO data in other web sites and for data analysis.  

Congratulations to Cornell for providing this fundamental new capability to the Vitro and VIVO communities!

You can find the Data Distributor here:  https://cul-it.github.io/vivo-data-distribution-api/

Getting Data into VIVO.  There are many methods for getting data into VIVO.  People use the VIVO Harvester, Karma, the VIVO Pump, XSLT, and locally written scripts to gather data, disambiguate works and people, map to the VIVO ontologies, transform to RDF, load and curate as needed.  Can we standardize parts or all of these processes for publications and other works to leverage the great work of the community and provide supported approaches for all?  Would this help VIVO adoption and implementation?  Let's see what our community can do to help others!

Go VIVO!

Mike

Mike Conlon VIVO Project DirectorDuraspace 

 

 

preserve