VIVO Updates for October 23 -- UCSF joins as a member, opportunities to help

Welcome UCSF as a new member!  The University of San Francisco (UCSF) has joined Duraspace as a bronze member supporting VIVO!  UCSF is one of the leading biomedical research universities in the world.  UCSF contributes expertise in many ways to the VIVO project: Eric Meeks from UCSF serves on the VIVO Steering Group, and UCSF collaborators regularly present at the VIVO Conference regarding search engine optimization, and engagement of faculty in using research networking systems.

Interested in supporting VIVO?  Become a member.  See Becoming a Member of Duraspace.

Want to help?  Here are some opportunities:

  • The Data Loader Task Force is looking for developers interested in working on a new utility for simple loading of VIVO data
  • The VIVO 2017 Conference Planning Task Force is looking for additional task force members to help with planning next year's conference at Weill Cornell Medical College in New York City, August 2-4, 2017.  No experience?  No problem – the conference is always looking for new people.
  • The VIVO Camp Task Force is looking for people interested in helping plan VIVO camps.  The camps will provide people new to the community with a multi-day training experience in all things VIVO.  
  • The Membership Task Force is always looking for people who want to help VIVO with its membership drive.  Membership is critically important to VIVO.  If you are interested in helping VIVO with its membership drive, please consider joining the task force.
  • VIVO 1.10 Release Planning is on-going.  If you would like to help with development, testing or documentation, please contact Graham Triggs.

Want to help with something else?  Have an idea for creating something new?  See How to Form a Task Force.

Apps and Tools call  This Thursday at 1 PM, the Apps and Tools Interest Group will have its monthly call.  Apps and Tools is a great place to share ideas about software you may be working on that uses VIVO data, or produces VIVO data.  The VIVO APIs document how data can be accessed by apps and tools and how apps and tools can be used to provide data to VIVO.  If you are interested in apps and tools for VIVO, please join the call on Thursday.



Mike Conlon  VIVO Project Director Duraspace 

VIVO Updates for Oct 16 -- Save the date for VIVO 2017, Ontology diagrams updated

Save the Date! VIVO 2017 August 2-5, New York City.  The 2017 VIVO Conference will be held at Weill Cornell Medical College, August 2-4, 2017.  Alex Viggio is Conference Chair.  Violeta Ilik is Program Chair.

Would you like to help plan the conference?  The VIVO 2017 Conference Planning Task Force is looking for you.  Please contact any of the task force members if you would like to help.

Ontology Diagrams Updated  The VIVO 1.9.x Documentation has been updated with new ontology diagrams.  See Ontology Diagrams. The new diagrams focus on implementation, with entity models for each of the kinds of things VIVO sites typically want to add.  Diagrams use a consistent style and attempt to show the location of literal values that sites want to add to their VIVOs.  

The VIVO Classes diagram has been updated, showing the classes that exist in VIVO, and how they are related. Missing classes have been added.  Classes not in VIVO have been removed. Numeric predicates have been labeled throughout to ease implementation and SPARQL query.

Numerous additional minor changes have been made throughout the documentation.  See VIVO 1.9.x Documentation and  VIVO 1.9.x Documentation as PDF

Implementation call this Thursday  Implementing VIVO?  That's great!  Have questions?  Of course you do.  The Implementation Interest Group is here to help.  The group has a call on the second Thursday of each month at 1 PM US eastern time.  See the link for call information.  Bring your questions!



Mike Conlon  VIVO Project Director Duraspace 

VIVO Updates for October 9 -- v1.9.1, v1.10, membership, development

VIVO 1.9.1 is available!  VIVO 1.9.1 has been released and is available here.  Release notes are available here.  VIVO 1.9.1 is a minor maintenance release that addresses several issues:

  • Responsiveness of the Capability Map has been improved
  • Turtle support has been added to the filegraph loader
  • errors on profile pages have been fixed
  • Maven character set issues on Windows have been fixed
  • Maven now correctly sets Java 1.7 version
  • VIVO now uses the background RDFService correctly in the visualization cache

If you are implementing VIVO for the first time, we recommend you start with 1.9.1.  If you are upgrading to the current version, we recommend you upgrade to 1.9.1.

VIVO 1.10  We continue to gather feedback and contributions of effort for version 1.10, expected in the summer of 2017.  Thanks to all who have participated in discussions regarding the next version of VIVO.  We continue to look for additional help, particularly in the areas of user interface, internationalization, and technical documentation.  See VIVO 1.10 Release Planning.

Membership in VIVO  October will mark the formal end of the annual VIVO membership drive.  You may receive one additional solicitation this week.  VIVO had a good year.  We'd like to have a better year.  If your institution is not a member, please consider becoming a member.  Membership supports the work of VIVO, insuring the software, and community move forward.  We can do more with more members.  A current list of the members is here.  Becoming a member is easy – just visit this site, and return the form.  We'll take care of invoicing your institution.  We deeply appreciate the support of our members and we look forward to having your institution join as a member.

Development Meeting this Thursday  The Development Interest Group will meet this Thursday at 1 PM.  The Webex link is here.  All interested in working on VIVO and Vitro code are welcome to attend.  The group organizes sprints to add new features to VIVO, using GitHub pull requests.  If you have Java programming skills, or interest in contributing to the technical documentation of VIVO, please consider joining the call and contributing to the improvement of VIVO and Vitro.  We look forward to meeting you and working with you.



Mike Conlon  VIVO Project Director Duraspace 

VIVO Updates for October 2 -- new task forces, technical specs, data packages, and roadmap

New task forces forming. Three new task forces are forming.  If you are interested in helping with any of these efforts, please contact the task force members.

  1. VIVO 2017 Conference Planning Task Force.  Please join Alex Viggio, 2017 VIVO Conference Chair, and Violeta Ilik, 2017 VIVO Conference Program Chair, in planning and preparing for the next VIVO conference.  The conference planning task force "does everything" needed to put on the conference.  The work promises to be fun and interesting!
  2. Data Loader Task Force.  A group is forming to design and build a simple data loader for VIVO.  Given a spreadsheet of people, the loader will create or update the people in VIVO, as well as collect their PubMed and/or Web of Science publications and add or update the publications in VIVO.  Using a single spreadsheet as input, the data loader will create and maintain a VIVO site of people and their publications.  Sound interesting?  Please plan on joining the task force.
  3. VIVO Camp Task Force.  The VIVO community is growing and maturing.  New sites, and sites considering VIVO, need an opportunity for an introduction to the world of VIVO.  We would like to have a two or three day event with 4-5 VIVO instructors where sites could get an immersive experience, and share thoughts and questions with other sites considering VIVO.  Through a camp experience, we hope to grow the community of sites.  The VIVO Camp Task Force will create a business model, and curriculum, as well as identify a location, instructors and materials for a potential camp in the spring of 2017.  If you are interested in helping sites considering VIVO, please join the task force.

VIVO Technical Specs.  VIVO has a new technical specifications document.  The two-sided PDF handout summarizes VIVO from a technical point of view – what it consists of, what is required to run it, what does it do.  We hope the document will be useful in discussions regarding the suitability of VIVO as software at your institution.  You can find the technical specs on the VIVO web site, and links to the specs in the VIVO wiki on the homepage.

Introducing data packages.  VIVO is about data – data about the scholarship at an institution.  VIVO data is linked, and these links refer to other data that may be about the world of scholarship, rather than the scholarship of the institution.  For example, your data may refer to other research institutions around the world – perhaps your faculty members obtained degrees at other institutions, received grants from other institutions, had positions at other institutions.  To date, each VIVO site has been recreating data about the research institutions of the world in order to link data about their scholarship to these data about research organizations.  This approach has several issues. First, there is tremendous duplication of effort.  Each VIVO site is creating similar data regarding the research institutions of the world.  Second, the data each VIVO site creates has local URLs for each of the research institutions it creates and curates.  When VIVO data is combined, the same research institution will have many different URLs and will need to be reconciled.  Third, the data that is being created is secondary to the goal of the institution's VIVO – to represent the institution's scholarship.  The secondary nature of the work is unnecessary effort – why can't the data be provided so that we can all use it?  Provided data might be better than what we could create locally.  As the primary work of the provider, the data might contain persistent identifiers, and other attributes, and be curated at a level higher than what might be done locally.

OpenVIVO explored these ideas, identifying useful sets of data that might be offered as "packages" – simple one file collections of RDF represented using VIVO-ISF that can be loaded into a local VIVO, and refreshed when the provider provides updates.  OpenVIVO worked with Digital Science to create a data package from their data of the research institutions of the world.  You can find their data at  You can find an RDF data package of their data at

Data packages can be loaded into VIVO using the existing "filegraph" mechanism.  The process is described in the documentation here.

We hope to identify other providers of data that can be made into data packages and offered to the VIVO community for use in their VIVOs.  If you would like to be a data provider, or know of sets of data that would be useful to the VIVO community, please let us know.  Use of data packages should provide a simple way to share data, avoid duplication of effort, align data across VIVOs and improve the data quality in each VIVO.

Community input for VIVO 1.10.  The Outreach and Engagement Interest Group will have a call this Thursday to discuss VIVO 1.10 Release Planning.  We are often asked "how does the VIVO project decide what will be in future versions of the software?"  As a member supported, open source, community developed software project, we have a governance process by which decisions are made.  The community expresses its interests through the interest groups and via the email lists,  the governance groups approve directions, various supporters commit to participating in various development activities, the committers group approves changes to the software.  The process is described in the VIVO Roadmap Process.  You can always find the VIVO Roadmap Process in the upper left hand corner of the VIVOwiki, along with the VIVO Project Charter v 1.1 and VIVO Strategic Plan 2015-2016.  The strategic plan will soon be updated.  Expect to see more about that in the weeks ahead.

Please join us this Thursday at 1 PM eastern via Webex to participate in community input to VIVO 1.10 Release Planning.



Mike Conlon  VIVO Project Director Duraspace 

VIVO Update for September 25 -- ECU, Java 7, Roadmap

East Carolina VIVO!  Congratulations to the team at East Carolina University on the launch of their VIVO site VIVO Research and Expertise Across East Carolina University.  Based on version 1.9, the site showcases more than 1,000 faculty, 10,000 academic articles and other works, 850 organizations, campus buildings, and much more.  What a great site!

Deprecating Java 7  In an effort to keep VIVO current, the next version of VIVO is planned to require Java 8.  Java 7 will no longer be supported.  Java 7 has passed out of support by Oracle as of April 2015.  Oracle no longer provides updates, including security patches, for it.  An FAQ from Oracle is available.  The current version of Jena requires version 8 of Java.  Requiring Java 8 for VIVO will allow us to upgrade Jena to the most current version.  Besides keeping current with this critical component of VIVO, the new version of Jena offers support for RDF 1.1 and SPARQL 1.1.  You can read more about the current version of Jena here.

If requiring Java 8 in the next release of VIVO will create a hardship or barrier for your VIVO site, or you have questions about this, please let us know.  We hope to hear from you.

Roadmap call this Thursday  This Thursday, at 1 PM US Eastern time, we will have a meeting of the VIVO Roadmap Task Force to discuss potential features and architecture for the next release, and features and architecture for releases beyond the next release.  Please see VIVO 1.10 Release Planning as background.  All are welcome to attend.  We look forward to hearing your thoughts about what is needed as VIVO moves forward.  The meeting will be held via WebEx.



Mike Conlon  VIVO Project Director Duraspace 

VIVO Updates for Sept 18 -- Documentation, Bootstrap VIVO, Help Wanted

148. 375  Those are the number of wiki pages and the number of PDF pages in the VIVO 1.9.x Documentation and VIVO 1.9 documentation PDF respectively.  We have finished moving the documentation to the documentation wiki.  The documentation wiki has documentation about the software and ontology – what it does and how it is used.  The VIVO wiki continues to be the place for all meetings, interest groups, task forces, planning, and community support.   The documentation wiki is organized by topics familiar to those supporting software.  The project wiki is organized by the needs of the community.

The documentation wiki has an outline, content in most areas of the outline, a style guide, and a first pass over all pages to move toward the style guide.  There is still quite a bit to do.  Some pages are missing or incomplete.  Other pages need to be updated with current content and screen shots.  Other areas need to be improved to address common questions.

In moving and editing content to the documentation wiki, the wiki's indications of "authorship" are often disrupted. The note on the VIVO Technical Documentation page in the project wiki should be emphasized:

These pages contain contributions from many members of the VIVO community. Confluence may state that a certain person has "created" a page, when in fact they have merely split, copied, or merged two existing pages. In this way, the pages may appear to be the work of a single person. Everyone who has worked on VIVO deserves recognition and thanks.

We will continue to improve the documentation.  If you would like to help, please contact Graham Triggs

Bootstrap VIVO  Symplectic has produced a new interface for VIVO.  Based on the popular Twitter Bootstrap (hence "Bootstrap VIVO") look and feel, the new interface is "responsive," meaning that it works well on mobile devices such as phones and tablets, as well as on computer screens of all sizes.  The interface provides new features, emphasizing expert finding.  The new interface is described in a talk given at the VIVO conference, and in a poster.  You can try the new interface here.  As you will see, it looks quite a bit like the new CU experts site and the new UOW Scholars site.  Both these sites use design principles in common with the Bootstrap VIVO work.  We have an opportunity to provide this interface as a selectable option in a future release of VIVO.  Let us know what you think.  If you are willing to help with providing this interface in a future version of VIVO, please contact Graham Triggs

Help Wanted  Speaking of help, VIVO is always looking for additional help.  If you would like to help VIVO, we have many opportunities:

  • Technical writing.  We need help with the documentation wiki.
  • Development.  Are you a developer?  Interested in fixing something that has been bugging you about VIVO?  Adding something that is missing?  There's quite a bit that can be done for the next release of VIVO (tentatively called VIVO 1.10)  See VIVO 1.10 Release Planning and consider working on pull requests, open JIRA requests or otherwise contributing.
  • Ontology.  We need help improving the ontologies used in VIVO.  Interested?  Please join The OpenRIF development group.
  • Community building.  Interested in helping build the VIVO community?  Communications?  Outreach?  
  • Conference planning.  The 2017 VIVO Conference planning is underway.  If you'd like to help, please contact the conference chair, Alex Viggio
  • VIVO Camps.  We'd like to create training opportunities for people to learn more about VIVO.  Interested in welcoming people to the community?  Helping them evaluate VIVO?  Helping them learn more about VIVO?
  • Membership.  We are always looking for new members.  Are you a member (check here).  If so, great!  We appreciate your support.  If not, please considering becoming a member.
  • Steering.  Interested in helping set the course of the project?  In the spring we will have openings on the VIVO Steering Group.  Please consider joining.
  • Web design.  The VIVO web site is always looking for new ideas, new design.
  • And more.  Just want to help?  Not sure where?  Please contact Mike Conlon.  Let's talk about your interests.

Please contact Mike Conlon if you are interested in helping the project in any way.

Apps and Tools  The Apps and Tools Interest Group will have its call this Thursday at 1 PM eastern.  The group discusses software that uses the VIVO APIs, and Linked Open Data - requests and responses to reuse VIVO data, as well as tools that produce VIVO data.  Interested in software development using VIVO data?  Please plan on joining the call.



Mike Conlon  VIVO Project Director Duraspace 

VIVO Updates for Sept 11 -- new members, conference keynote videos available

Welcome two new members – University of Idaho and University Corporation for Atmospheric Research!  VIVO has two new members this week!

The University of Idaho is the U.S. state of Idaho's oldest public university, located in the city of Moscow in Latah County in the northern portion of the state. It is the state's land-grant and primary research university. Wikipedia  See their VIVO here:

The University Corporation for Atmospheric Research is a nonprofit consortium of more than 100 colleges and universities providing research and training in atmospheric and related sciences. UCAR manages the National Center for Atmospheric Research (NCAR) and provides additional services to strengthen and support research and education through its community programs.  Wikipedia  See their Earth Observing Laboratory Artic Data Connects VIVO here:

We thank UCAR and the University of Idaho for joining the project as members.  Their support and the support of all our members, help insure VIVO's ability to continue to develop software, ontology, and community in service to the representation of scholarship across the world.

Becoming a member  If you are considering becoming a member of Duraspace supporting VIVO, you may wish to review our list of members, and Duraspace's Becoming a Member page.  If you haven't considered becoming a member, please take a few minutes to review these pages.  We appreciate everyone's support.

VIVO Conference keynote talks available  New this year, the VIVO Conference recorded and is making available video of the keynote talks.  You can find the talks on Youtube here:

Thanks to Sören and Dario for these amazing talks, and for allowing their talks to be made available openly, and to the conference organizers for creating the video!

More from the conference  It's last call for conference materials to be posted to figshare!  If you presented at the VIVO Conference and have not yet posted your materials to figshare, please do so this week.  We have over 90% of the materials presented already posted. Thanks to all the presenters who have uploaded their materials, the response has been fantastic.  If you haven't posted your materials yet, it's very easy to do.  Log on to figshare (create an account if you do not have one), upload your poster or presentation, and tag your material vivo16.  Your material will become part of the figshare VIVO 2016 collection and will be available on the VIVO 2016 Conference page inOpenVIVO.

Implementation Interest Group this Thursday  The Implementation Interest Group will meet this Thursday at 1 PM US eastern time.  The group is a great forum for sharing ideas about creating and managing a VIVO for your institution.  The group has updates from sites around the world, takes questions regarding VIVO and VIVO data, and helps sites get their VIVOs going.  New to the VIVO calls?  You will find the Implementation call a great place to get started.  It's always great to meet new people and help keep projects moving forward.



Mike Conlon  VIVO Project Director Duraspace

VIVO Updates Sept 4 -- Woods Hole, Tech Docs, Wiki, Fellowships

Woods Hole VIVO launched  The Marine Biology Laboratory Woods Hole Oceanographic Institution in Woods Hole, Massachusetts, has a new VIVO, and its beautiful!  See  Congratulations to the Library at MBLWHOI for creating this wonderful new site!

Technical documentation  We continue to make progress on creating the VIVO 1.9.x Documentation wiki from technical materials that previously were found in the VIVO wiki.  The VIVO wiki will continue to be the primary source for community, news, work in progress, task forces, governance, events, interest groups, planning, and historical material.  Outdated materials have been archived.  Background materials have been gathered into a new heading, Background Resources.  Planning materials have been moved to the appropriate task force areas.  The documentation wiki will focus on describing the VIVO software, and how to do things with it (DevOps, Data Management, and End User usage).  The documentation wiki is version specific.  If you find something missing, out of place, out-dated, confusing, or otherwise in need of improvement, please let us know, and please consider improving the material by editing, writing, or rearranging.  Please contact Graham Triggs if you'd like to help.

Speaking of the wiki  We recently reviewed the Considering VIVO section of the wiki, updating materials, removing outdated materials, and in general, refreshing the section.  There is still more that could be done – particularly regarding product evaluation.  If you recently evaluated VIVO, perhaps you have materials that could be shared with the rest of the community and could become a part of the wiki, helping others evaluate VIVO.  Please contact Mike Conlon if you have thoughts or materials regarding product evaluation.

Fellowships  Have you modeled fellowships in your VIVO?  If so, please consider joining the conversation on and share your thoughts.  Fellowships share aspects of positions (the fellowship pays a stipend and is in an academic organization), person types (the person with the fellowship is a fellow), awards (the person holding the fellowship has been recognized for their scholarship, and many fellowships have names of their own), training (fellowships are often considered part of the training of the scholar holding the fellowship), and projects (many fellowships have a specific academic output associated with the fellowship).  VIVO is well suited for showing the connections between these representations.  How are these treated in your VIVO?  How might they best be treated?

Development call  The Development Interest Group will have its call this Thursday at 1 PM.  Discussions center of technical aspects of VIVO and Vitro, including technical documentation.  If you have an interest in developing new features for VIVO or Vitro, please consider joining this call.



Mike Conlon  VIVO Project Director Duraspace 

VIVO Updates August 28 -- new sites, posters, conferences, documentation

New sites!  August was a big month for new VIVO implementations.  Eight new implementations are underway:

  1. Universidad Zamorano, Honduras
  2. Fred Hutchinson Cancer Research Center, Seattle
  3. University of Alabama Birmingham
  4. Vikram Sarabhai Space Centre, Kerala, India
  5. Research Data Canada
  6. Universidade Federal do Rio de Janeiro, Brazil
  7. McMaster University, Canada
  8. Universidad del Rosario, Colombia

Please join me in welcoming these new sites to the VIVO community!

Who is using VIVO?  Duraspace maintains a registry of all known VIVO sites. The registry currently lists 145 VIVO sites in 26 countries.  You can find the list here:  Is your site listed?  If you are working on an implementation, or have a VIVO and you would like to be added to the registry, you can do so here:  Very easy, very fast, and very helpful for us to know who is using VIVO around the world.

Do we have your VIVO 2016 poster?  We are collecting all the amazing VIVO 2016 conference content into a Figshare collection and an OpenVIVO page.  We've got quite a bit already, see  We are looking for more posters.  If you presented a poster and your poster is not yet on the OpenVIVO page, could you please upload your poster to Figshare and tag it vivo16.  That's all you need to do.  We will add it to the OpenVIVO page.  We appreciate you sharing your work with others!

Conferences and presentations.  The VIVO community is very active in presenting work regarding VIVO, data sharing, open access, persistent identifiers, open science, attribution, research impact, and many other topics of interest in the development of an open scholarly ecosystem that works for all.  Attending a conference?  Planning to submit an abstract?  We have a list of Conferences Attended and to Attend listing presentations made by community members and being planned.  Please add your plans to the list, and we hope to see you at an upcoming conference!

New in the docs  We continue to make progress on the technical documentation, filling in the new wiki.  See VIVO 1.9.x Documentation and a new page Create, Assign, and Use an Institutional Internal Class.  The institutional internal class is a feature sites can use to extend the ontology, defining a class representing people that are associated with their institution, and then use that class to limit the default VIVO people displays to only people associated with the institution.  The feature is not new.  The documentation is.  Please post comments, questions to And if you would like to help with editing and improving the documentation, please contact Graham Triggs.

Outreach and engagement  Interested in how your faculty will use VIVO?  In how to engage faculty in keeping profiles current?  In increasing the interest and use of your VIVO site?  Join the Outreach and Engagement Interest Group call this Thursday at 1 PM.  Webex link is here



Mike Conlon  VIVO Project Director Duraspace

VIVO Updates for August 21 -- Conference, Technical Documentation

Oh my, what a conference!  The 2016 VIVO Conference was truly amazing!  Thanks to all who attended, to Designing Events for all their help, and to the Marriott City Center Denver.  Denver was a great place to visit, even if the weather turned a bit on Friday. I hope everyone's travel home went smoothly and safely.  It was so great to see all our VIVO friends and to make new ones.  Super special thanks to Julia Trimmer, Conference Chair, Manuel de la Cruz Gutierrez, Program Chair, Alex Viggio, Conference Co-Chair, and Violeta Ilik, Program Co-chair, and all the members of the VIVO 2016 Conference Planning Task Force.  What a great job!  What a great conference.  We have quite a few follow-ups and you will be hearing more about them in the weeks and months ahead.

Did you present at the conference?  Thank you for presenting!  We had incredible contributed talks and posters.  

If you haven't already done so, please upload your slides to your Figshare collection, and tag them with vivo16.  Full instructions are here.  We will get them into OpenVIVO from there.  You can see the uploaded materials in OpenVIVO here: and click on "Publications".

VIVO 2017.  Alex Viggio will serve as Conference Chair for VIVO 2017.  Violeta Ilik will serve as Program Chair.  We will be starting VIVO 2017 conference planning soon.  Would you like to be involved? Please contact Alex or Violeta.  We are always looking for ways to make a great conference even better!

Technical Documentation  This past Tuesday in Denver we held a "Documentation Work Party" to create a new set of technical documentation for VIVO.  Many members of the VIVO community attended.  Thanks so much!  A new wiki,  VIVO 1.9.x Documentation, has been created to contain technical documentation for VIVO 1.9.  The VIVO wiki now refers to the technical documentation wiki for all versions of technical documentation.  The 1.9 documentation is focused on what VIVO is and does.  Materials regarding strategy, roadmap, background, history, older versions, and other materials have been moved to Background Resources (see below), appropriate task forces, and the Technical Documentation Archive (see below).  We hope the new 1.9 documentation is easier to use, and more approachable by those charged with creating and maintaining VIVO.  The new documentation is driven by an outline.  When no material is present, the outline page will be empty.  If you find an empty page, please feel free to draft content for inclusion.  Over time, we hope to fill out the entire outline.

All pages previously in the VIVO wiki under "Technical Documentation" have been archived in a new space here:  VIVO Technical Documentation Archive Home.

Background Resources  In creating the new technical documentation, we found a number of outstanding resources that deserved their own place in the VIVO wiki.  A new heading in the left hand menu Background Resources has been created as a home for materials that do not describe VIVO, but may be useful for those new to VIVO, describing technologies and approaches used in the VIVO community.  As these materials continue to improve, they could form the basis for training materials related to VIVO.  If you have ideas about background materials you need, or materials you wish you had when you started with VIVO, drop us an email and share your thoughts.

Apps and Tools call  The Apps and Tools Interest Group will have its call this Thursday, August 25, at 1 PM eastern.  The call features presentations and discussion of (you guessed it) VIVO apps and tools.  The group maintains a catalog of Community Projects – open source software for use with VIVO.  Do you have an open source application or tool that works with VIVO?  Please consider adding to the catalog.  Regardless, all are welcome on the call!



Mike Conlon  VIVO Project Director Duraspace