Graham Triggs starts Monday, September 21.  Graham Triggs is joining the VIVO project as technical lead this week.  Graham has been an open source developer and a contributor to VIVO.  Recently Head of Repository Systems development at Symplectic, Graham developed the VIVO harvesters for Symplectic.  Please join me in welcoming Graham to the VIVO project!

Graham will be on the Implementation and Development call October 1.  Graham will be joining the Implementation and Development call on October 1 for a question and answer session.  Please plan to attend the call to meet Graham, and share your thoughts about the future of VIVO development.  For more information, see Implementation Calls.

Implementation documentation available.  One of the most common questions we get regarding VIVO has to do with the effort required to implement VIVO at a university – how long does it take, what kind of people are needed, how much does it cost, where do I start, is there a sample plan for implementing VIVO?  The VIVO software has no cost, but the effort required to implement VIVO will depend significantly on the complexity of your institution and your plans for VIVO.  A recent task force, led by Violeta Ilik from Northwestern, did a spectacular job of addressing these questions, and in doing so, provided an entirely new section of the VIVO wiki under the heading Planning a VIVO Implementation.  This section of the wiki describes the planning required to implement VIVO and puts all the various aspects of an implementation – project management, outreach and community engagement, data management, and technical development in perspective, with sections devoted to analysis, design, implementation, launch and maintenance for each.  If you are considering implementing VIVO, you should certainly review this area of the wiki for ideas about what it will take to be successful.  If you are in the middle of an implementation, you will want to take a look to compare your approach to the outline you will find in the wiki.  If you have a production VIVO, you will want to review the material and possibly contribute to refining the material for others.  A hearty thanks to all the task force members and all who contributed along the way.

Publishing VIVO data.  One of the "big ideas" of VIVO is sharing data.  The VIVO-ISF provides a common means for representing scholarly work and each VIVO represents its information using the common format.  This makes sharing data much simpler than when using typical local data dictionaries and tabular data representations.  Sharing data can take many forms.  One form is publishing data.  Thanks to Chris Barnes, and the team at the University of Florida, UF has begun to publish its VIVO data in datasets available for download.  See Dataset, all University of Florida papers published in journals for a given year.  These datasets are for the years 2010 to 2014.  



Mike Conlon
VIVO Project Director