VIVO Updates June 25 -- become an ontology reviewer, committer

Ontology improvements.  Interested in ontology?  We need volunteers to become VIVO ontology reviewers and committers. Sign up at

VIVO in New York City.  Save $100 on VIVO conference registration.  Register by June 30!

VIVO in Brisbane.  See VIVO at Open Repositories:  Tuesday night poster session at QUT (Conlon & Triggs) and Thursday afternoon 24x7 presentation (Conlon & Aryani):

Conlon, Michael; Triggs, Graham (2017): VIVO/Vitro system architecture for creating linked open data regarding scholarship. figshare. Retrieved: 22:38, Jun 25, 2017 (GMT)

Conlon, Michael; Aryani, Amir (2017): Creating an open linked data model for Research Graph using VIVO Ontology. figshare. Retrieved: 22:39, Jun 25, 2017 (GMT)

VIVO in Bozeman, MT.  Next year, Open Repositories will be in Bozeman, Montana, June 4-7, 2018.  See  Consider a VIVO presentation, or workshop for Open Repositories 2018.

Fifth Thursday of the month  No interest group call this Thursday.  VIVO has four interest groups, groups that meet on the first, second, third and fourth Thursday of each month to discuss common interests.  The interest groups are Apps and Tools Interest GroupOutreach and Engagement Interest GroupImplementation Interest Group, and the Development Interest Group. June has five Thursdays, so no call on the fifth Thursday.  Interest calls resume next week. 



Mike Conlon VIVO Project DirectorDuraspace 

VIVO Updates June 18 -- Conference, VIVO 1.10 beta, JIRA

The VIVO Conference  The VIVO Conference is the VIVO event of the year.  Keynotes, invited speakers, contributed presentations, posters, round tables, vendors, and your VIVO colleagues.  Plan to join us at Weill Cornell Medical College, 1300 York Street, New York, New York.  More information is on-line at the conference web site with its easy-to-remember web address New York is easy to get to by air and there are lots of places to stay and more things to do and see.  Conference registration is a bargain, and flights to New York are inexpensive.  We have a great deal with the Bentley Hotel, just down the street.  Check it out.

VIVO 1.10 Beta available.  VIVO 1.10 Beta is available for download and testing.  There are many new features, fixes, and improvements.  See VIVO 1.10 Release Planning for a list of what's in 1.10.  Some highlights:

  • Linked Data Fragments server.  VIVO will serve data via a new open API, via linked data fragments.  We hope this will make it much easier to use VIVO data across sites.  See Linked Data Fragments
  • Support for Jena 3 and RDF 1.1.  As standards evolve, VIVO evolves.  See What's New in RDF 1.1  The upgrade to VIVO 1.10 includes an upgrade to Jena 3, which supports RDF 1.1
  • A beta release of a new responsive theme, tenderfoot, based on Twitter Bootstrap.  Not ready for prime-time yet, but shows a direction for a responsive new interface, and for generating additional new themes.

Please download the beta and give a try.  And please report your findings on

JIRA.  VIVO and Vitro track their issues in JIRA.  We have issues grouped by "components" – ontology, interface, documentation, architecture, and lots more.  Using JIRA, you can see a list of known bugs in VIVO, see what is tagged as an issue for version 1.10.  JIRA is available to all members of the VIVO and Vitro communities.  If you have a Duraspace account, you can visit If you don't have a Duraspace account, contact Graham Triggs to get one.  New to JIRA? Search for JIRA intros – there are many, and one should suit your style.

VIVO at Open Repositories.  Graham Triggs and I will be at Open Repositories June 26-29.  We're on the program twice – a poster, and a 24x7 presentation.  If you plan to be in Brisbane, please contact us.  Let's get together!

Presenting about VIVO? Are you planning to present about VIVO or Vitro at upcoming conferences?  We'd love to hear from you.  We have a running list of conferences that people in the VIVO community are planning to attend.  You can find it here:  Conferences Attended and to Attend.  Add your conference, or presentation!  

No apps and tools call this Thursday.  Due to travel, there will be no Apps and Tools call this Thursday.  



Mike Conlon VIVO Project DirectorDuraspace 

VIVO Updates -- June 11 -- Vitro, and Why Ontology?

Vitro  Vitro is the engine that makes VIVO work.  We don't talk about it much.  That's a shame.  Everyone should know about Vitro.  One could even say that VIVO is a customized Vitro.

Vitro is a general purpose, semantic web ontology and data management tool.  Vitro is "domain neutral," that is, it manages data based on ontologies loaded into it.  Or said another way, it can manage any data for which an ontology has been loaded into it.  Vitro has been used to manage collections of clinical trials, spaceships, library catalogues, and data sets.  You can install Vitro, add ontologies describing your domain, and start managing data.  Almost all of what we have in VIVO comes from Vitro.

VIVO is an ontology and customizations to Vitro for representing scholarship.  Visualizations specific to scholarship, such as the capability map are in VIVO.  For a simple comparison of VIVO and Vitro see VIVO and Vitro.  For technical material regarding the organization of the VIVO and Vitro software, see the documentation wiki article Architecture.

You'll hear more about Vitro in the coming months, along with examples of Vitro being used in research settings.  Vitro is a completely general, and very powerful, tool for working with semantic data.

Why Ontology?  Ontology is a new word for many.  Turns out it is the key to data sharing in our world of information.  Systems without ontological foundations find data sharing difficult and costly, and as a result, rare.  Systems built on ontologies, such as Vitro and VIVO, find data sharing natural, and therefore common.  This month's column explores the question Why ontology? What do we get?  What must we do?  What problems will we encounter?

Conference  We're having a conference.  You knew that.  It's in New York, August 2-4.  The deadline for submitting a poster or demo is Monday, June 12.  You can submit here:  And by the way, have you registered?  It's never too early.  You can register here:

Internationalization  The Internationalization Task Force will meet this Wednesday, June 14 at 9 AM US Eastern Time.  Time zone conversion is available here:  Meeting Times Around the World.  Meeting notes are available on the Internationalization Task Force page.  The upcoming meeting will focus on process for translations and organization of file repositories.  Here's the Webex link:  Interested in VIVO in languages other than English?  Hop you can join the call.  If not, share your thoughts on

Implementation  Do you have questions about implementing VIVO?  About data? Policy? Technology?  Tools?  When you will sleep?  Join the Implementation Interest Group calls every month.  This month's call is this Thursday at 1 PM US Eastern time.  Here's the webex link:  



Mike Conlon  VIVO Project Director Duraspace 

Why ontology?

June 2017
Institutions need to collect, organize, preserve, and share the scholarly work produced by their people.  When people consider VIVO, they discover the VIVO ontology, and its associated ontologies.  And then people have questions.
Why don’t we organize information as in almost all other systems, storing data and using it to make pages or answer questions?  Why must we learn about ontologies?  Why must we map our data to ontologies? What do we get from using ontologies?
The first thing we get by using ontologies is meaning.  That's what ontologies do -- they provide meaning.  In VIVO, all data is represented using elements of ontologies.  These elements define the meaning of a recorded data value.  Elements provide meaning for the kinds of things in VIVO.  Other elements provide meaning for the relationships between things.  All elements are defined and the definitions are in the ontology.  The ontology is machine readable and available on-line.  Contrast this to traditional systems.  Data elements are stored in "columns."  Columns have names.  The names may convey meaning.  The meaning may be written down in documentation.  The documentation may be available.  In VIVO, the documentation is the ontology and is part of the system.  The system can not function without its definitions, that is, without its meaning.
We get precision.  In VIVO, we don't put meaning in text, or labels, or data structures, or software.  We put meaning in ontological elements.  We have types of things — types of organizations (university, company, and so on), types of people (faculty member, staff member, librarian) and types of many other things.  We have precision in relationships between things.  And when one VIVO site expresses its data with the ontology, other sites know precisely what is meant by the data.
We get consistency.  In VIVO, a date is an individual defined in the ontology.  It behaves in a way defined by the ontology.  And all things defined as dates behave the same way.  In traditional systems, columns containing dates may be processed as dates.  And in large traditional systems, it may be difficult to identify all the columns that contain dates.  In VIVO, dates are defined as dates in the ontology and can easily be found.  They must be processed as dates.  This same consistency applies to web addresses and every other kind of thing in VIVO.  VIVO treats the thing as it is defined, and can find things based on how they are defined.
As a result of the use of ontologies to insure meaning, and the consistency that results, we achieve commonality -- the ability to share and use each other's data.  We do not need to convert from one set of columns to another another.  We do not need to introduce additional specificity.  We can simply share, the work to share is already done.  Tools built by one VIVO site can be used by another because they share common ontologies, they share common meaning, and common representation.
We get multi-language capability.  Because the meaning is in the ontological elements, we can label these elements using any language we choose, and as many languages as we choose.  We do not express meaning in the labels of things, but in the ontological elements and structures of things.  The label for one’s position might say “Associate Professor” and this may be translated in many ways.  But the position itself has a type, and that type is FacultyPosition.  The FacultyPosition may have many labels, each in another language.
We get extensibility.  Vitro provides an ontology editor that can be used in Vitro and VIVO to add ontological elements, and thereby extend what Vitro and VIVO can represent, that is what VIVO and Vitro an “talk about.”  Additional precision can be added when that is desirable.  New types of things can be added.    New relationships between things can be added.  Entire ontologies developed by others can be added.  And unlike many systems, these changes can be made at any time, without having to bring the system down, or otherwise interrupt users of the system.  And while VIVO is focused on scholarship, the underlying general nature of Vitro supports talking about anything that has an ontology, and that could be anything.
We get inference.  Inference is the ability of Vitro and VIVO to  know something because we have said something precise in the context of an ontology.  For example, we might say “Mike is a faculty member”.  The ontology says “All faculty members are people”.  Therefore, Vitro and VIVO treat Mike as a person.  We don’t need to say that Mike is a person. Inference is a very powerful reasoning capability unique to ontology based systems.  In VIVO, inference is used to avoid having to enter additional data.  In the future, inference can be used to simplify queries, improve visualizations, and reduce the size of data collections.
And finally, we get a world community of practitioners describing scholarship and other domains.
We also get difficulties.  Ontologies are a new idea for most people.  There will need to be time for learning.  Training may be hard to find.  Tools are not as common as for other types of systems.  Tools are not as mature.  But support and use of ontologies is growing.  Progress is being made on all these concerns.
We welcome everyone to work together to refine and extend the VIVO ontologies, and to align ontology work in the VIVO community with others interested in representing scholarship.
Why ontology? Ontologies are the key to our ability to collect, use, and share data about scholarly activities across the world.

VIVO Updates — Conference breaks its glass ceiling, survey, outreach, internationalization

VIVO Conference breaks its glass ceiling!  Where are the women speakers leading our thinking in VIVO, linked open data, research, identifiers, and scholarly profiles?  Well, at the VIVO Conference, of course.  For the first time, both our keynotes are women – Christina Patuelli, School of Information at Pratt Institute, and Jodi Schneider, School of Information Science at the University of Illinois, Champaign-Urbana, will give keynotes to begin our days Thursday and Friday.  We have five invited speakers and three of them are women – Rebecca Bryant, OCLC Research, Katie Frey, Harvard-Smithsonian Center for Astrophysics, and Ying Ding, School of Information Sciences and Computing, Indiana University will be joined by David Eichmann, University of Iowa, and Jim Hendler, Cognitive Science Department, Rensselaer Polytechnic Institute.  What a line-up!  You can see all the speakers at

Have ideas regarding speakers for next year's conference?  Share your ideas with any of the VIVO 2017 Conference Planning Task Force members.

But wait, there's more:

  • Late breaking submissions for posters and demos (new this year) can be submitted here through June 12.  There are some many people doing excellent work all over the VIVO Community.  This is an opportunity to share.  Details here
  • The program is now available on-line.  We won't have a program book this year.  We are saving a few dollars, and quite a few trees.  Everything is on-line here  Hope you like the new approach and the ease of on-line access for the program.
  • Would your organization like to sponsor the conference?  See:
  • Registration is open.  All are welcome.  Register here:

How did you deploy VIVO?  A short survey is being conducted to help us learn about your deployment of VIVO.  Specifically, we're interested in understanding about your use of the interface.  Did you customize it?  Replace it?  Add significant elements?  Your response will take about 10 minutes and will us tremendously.  You can find the survey here:

Outreach and Engagement call this Thursday, June 1 The Outreach and Engagement Interest Group will have its call this Thursday at 1 PM US Eastern time.  The interest group brings together people sharing ideas about faculty and institutional engagement, marketing, and training.  It's a great group for non-technical discussion.  It's also a great group for people considering VIVO and planning messaging and support for VIVO.  We hope you can join us.  Here's the Webex link:

Internationalization call June 8  The Internationalization Task Force will have a call on Thursday, June 8, at 10 AM US Eastern Time.  Check Meeting Times Around the World for the time of the meeting in your time zone.  The group will consider what to tackle first, second and after that, and how work will be organized.  If you are interested in Multi-Language Support (that is, any language other than English) please join the call.  Here's the Webex link:



Mike Conlon  VIVO Project Director Duraspace 



VIVO Updates for May 21 -- Conference News, Ontology Explorer

Conference news.  Did you know we are having the 8th annual VIVO Conference at Weill Cornell Medicine in NYC, August 2-4?  I'm sure you did.  There is lots of news about the conference:

  • Early bird registration ends this Friday, May 26.  After that the rates go up.  Early bird is your best conference registration rate, and includes registration for VIVO workshops and all other conference events.  No add ons.  You get keynotes, invited speakers, workshops, posters, demos, receptions, and conversation with the people creating and implementing VIVO and VIVO related tools across the world.  Just one simple low registration rate.  And its in New York City!  Register today at
  • Speaking of workshops, the line-up is set and available on the conference web site here:  Please register and join us on Wednesday for a full day of workshops.
  • Late breaking call for posters and demos.  Its not too late to submit your poster abstract or abstract for a demo.  You can use a poster to tell the community about your work – we are always looking for stories of implementation, software you are working on, lessons you have learned. Demos are new this year.  Show us your work!  Submit an abstract to demo your software or web site.  We'll set you up in the poster session with a table and power – you bring your laptop and show others your work.  The deadline for late breaking posters and demos is June 12.
  • And if that wasn't enough, we are thrilled to announce Jim Hendler will be a fifth invited speaker at the conference.  Jim is one of the originators of the Semantic web, and was a keynote at the first VIVO Conference.  We are so pleased that Jim will be able to join us this year.  You can read more about Jim and his role in creating the Semantic Web here:  You can find all our invited speakers on the conference web site here:

VIVO ontology explorer. Muhammad Javed of Cornell has created an ontology explorer for VIVO.  The explorer now contains descriptions for each domain model.  And now its in a VIVO Project repo on GitHub ( and available for use from the repo here: Give it a try.  Let us know what you think.

Apps and Tools call this Thursday.  This Thursday, May 25 at 1 PM US Eastern Time, the Apps and Tools Interest Group will have a call. Web Ex connection link is here:  Apps and Tools is the place to share ideas about work you are doing, ask questions of others doing work to create tools and apps creating and using VIVO data.  Have an idea for a visualization?  For using the TPF API?  Or anything else, we will see you Thursday at 1.

Early bird conference deadline is this Friday, May 26.



Mike Conlon  VIVO Project Director Duraspace 

VIVO Updates for May 14, 2017 -- TIB is a member, how you can help VIVO

German National Library of Science and Technology joins Duraspace as a member.  VIVO has a new member!  The German National Library of Science and Technology, has joined Duraspace as member supporting VIVO.  From Wikipedia:

The German National Library of Science and Technology (GermanTechnische Informationsbibliothek), abbreviated TIB, is the national library of the Federal Republic of Germany for all fields of engineeringtechnology, and the natural sciences. It is jointly funded by the Federal Ministry of Education and Research (BMBF) and the 16 German states. Founded in 1959, the library operates in conjunction with the Leibniz Universität Hannover. In addition to acquiring scientific literature, it also conducts applied research in such areas as the archiving of non-textual materials, data visualization and the future Internet. The library is also involved in a number of open access initiatives. With a collection of over 9 million items in 2017,[1] the TIB is the largest science and technology library in the world.

TIB has been very active in the VIVO community, presenting at the VIVO conference, organizing a VIVO workshop in Hannover, conducting VIVO webinars, participating in interest groups, and developing a German-language version of VIVO, along with ontology extensions for German scholars.

We are thrilled to welcome TIB as a member of Duraspace supporting VIVO!

Membership in Duraspace.  It's easy to become a Duraspace member.  Members support the on-going work of Duraspace, including VIVO.  Membership is available at various levels with various member benefits.  All members receive discounts on registration to the VIVO Conference and VIVO Camps. In addition, members participate in the governance of the project, and are invited to the annual Duraspace Summit, held each year in April.  The most recent Summit was held in Albuquerque – it was great to see everyone who attended and have a chance to personally discuss VIVO strategy and next steps with the members.  For more information on membership, see

How you can help.  We are often asked "how can I help VIVO?" There are many ways!  Here are some ideas:

  • Become a member.  Well, I guess that was obvious.  Membership is critically important to the success of the project.  The more members, the faster we go.
  • Attend Interest group calls.  This is a good place to start.  You'll meet other members of the VIVO community and get up to speed with the current community efforts.  Interest group calls are announced in VIVO Updates every week – this week's call is the Implementation Interest Group.  See Interest Groups, and below regarding this week's call.
  • Ask a question or answer a question on the mailing lists,  (non-technical) and  (technical)
  • Contribute code.  Are you a developer?  We have many VIVO sites that have produced wonderful extensions to VIVO.  We'd like to make these new features available to the entire community be making your work available in future releases of VIVO.  See VIVO 1.10 Release Planning and contact Graham Triggs
  • Participate in a task force.  Task forces get work done.  The calls and documents are open to everyone.  Check the VIVO wiki for current task forces. See Task Forces
  • Present about VIVO at a conference.  Get the word out.  Share your experiences.  Build community understanding of the need for VIVO.
  • Contribute documentation.  Are you a writer?  VIVO needs additional material for its technical documentation.  See something missing?  Perhaps you are the person to write the missing piece!  See VIVO 1.9.x Documentation and contact Mike Conlon or Graham Triggs.
  • Hold a VIVO meeting.  Gather the people in your area for a local users group – discuss issues of local interest.  Share your discussions with the VIVO community. If you are planning a meeting, please contact Mike Conlon.  We may be able to help.
  • Sponsor the conference.  The conference is always looking for additional sponsors to improve the conference and the VIVO project.
  • Attend a VIVO Camp.  Perhaps you would like to learn more about VIVO in a training environment.  We expect to hold a VIVO Camp in the fall at a location to be determined.  See VIVO Camp Task Force
  • Share your ideas!  The mailing lists are a great place to share your thoughts about VIVO.  And you can always write directly to me at and to Graham at We'd love to hear from you!

Implementation Interest Group call This Thursday at 1 PM.  Here's the WebEx link The call is open to everyone.  The group discusses implementation issues.  People ask questions, share experience, get advice, and in general, help each other.  If you have any questions, thoughts, concerns, regarding implementing VIVO, this call is a great place to share.

For those who are keeping track, there are seven exclamation points used in this edition of VIVO Updates. No comment.



Mike Conlon  VIVO Project Director Duraspace 

VIVO Updates May 7

VIVO 2017, NYC, Aug 2-4.  The VIVO Conference has some changes this year, changes we think you will like.  First, workshops are included in the registration price.  You should come for Wednesday, the workshop day, and stay for Thursday and Friday.  The workshops have no extra registration fees.  This is a big savings and one we hope will encourage additional participants in the workshops.  Second, registration prices have been lowered.  The conference has the same benefits as always, but at lower registration fees.  How did we do that?  Well, that's the third thing – the conference will be not be held at a hotel.  Weill Cornell Medicine is hosting the conference and they have done a spectacular job lining up space and support for the conference.  So plan now to attend what promises to be a different, yet familiar VIVO conference.  Register now before the early bird rates end.

Ontology domain definition.  Last week we described the work of the Ontology Improvement Task Force and their interest in creating a "domain definition" for VIVO.  The domain definition answers the question "what does the VIVO ontology describe?" You can find a draft of the domain definition here:  The draft is completely open to all for comments and editing.  We've received quite a few very good comments and suggestions and the document is much better as a result.  Please help!

Who should have a profile?  We are often asked this question.  Our answer is that the institutions doing VIVO projects decide for themselves.  That said, many institutions explore the question and many come to similar conclusions.  The question is the topic of a first column in what I expect to be a monthly series, exploring topics of common interest to those engaged in creating profiles.  Please see the inaugural column "Who should have a profile?" available here.  The piece is about 800 words long and non-technical.  Let me know what you think.  And what you think might be good topics for future columns.



Mike Conlon  VIVO Project Director Duraspace 



Who should have a profile?

May 2017
The VIVO community is creating profiles for people engaged in the creation, transmission, and preservation of knowledge and creative works.  These works take many, many forms.  In some cases, the works may be stored in an institutional repository.  In other cases, the works may be ephemeral, as in the case of performances of music or theater.  Some works are openly accessible.  Many are not.  The works may be well identified by a DOI or other persistent global identifier.  Many are not.  And regardless of the nature of the work, its archiving, and its identification, the relationship of people engaged in the work varies considerably.  Some people are “authors.”  The cultural norms for authorship vary significantly across disciplines, domains and activities.  Other people may have contributed in a wide variety of other ways.
And this leads to a fundamental question for the VIVO community and for all those across the world creating and supporting profiles for people — who should have a profile?
For social networking sites, the answer is simple — whoever wants one.  And there is significant pressure from the purveyors of the sites to increase the number of people using their services.  The services are supported largely by two mechanisms — selling the data of the people using the service, and advertising to the people using the service.  In both cases, the more people using the service, the more valuable such sales will be.
The situation is different for systems such as VIVO.  VIVO is not supported by advertising or by selling data.  VIVO data is generally available (we will elaborate on this in a future column), and advertising is not part of the business plan for VIVO.  VIVO is member and institutionally supported.  Through the generous support of members, the VIVO project is able to organize community efforts to advance the software, and support and grow the community.  Through institutional efforts, VIVO infrastructure and data are created in support of the members of the institution.  To date, about 150 institutions have VIVO infrastructure, and about 25 are supporting the VIVO project through membership.
For VIVO, institutions answer the question “who should have a profile?”  They answer this question in a variety of ways.
Most institutions include only faculty.  This provides a simple, bounded definition of who is in the profiling system and who is not.  Of course, there are some edges here — are temporary faculty included?  Clinical faculty?  Are librarians faculty?  Do you include non-tenured faculty?  Instructors?  These institutions typically include all faculty that meet the local definition.  Many do not support “opt out” — removal or hiding of a profile, and very few support “opt in” — faculty get a profile only if they approve the creation of the profile.  The most common case is that the institution defines who is a faculty member for the purpose of creating profiles, and then creates a profile for everyone meeting the local definition.  But take a look at the first sentence of this essay.  VIVO is about “people engaged in the creation, transmission, and preservation of knowledge and creative works.”  Are the faculty the only people such engaged?
Some institutions have more inclusive answers to the question.  Some include post doctoral associates, visiting and other temporary faculty, and graduate students.  These people are often engaged in appropriate activities.  And many times, their participation in these activities goes unrecorded and unrecognized.  There are numerous current difficulties in including these people in profile systems.  Their contributions may not be “authorship” and our ability to track non-authorship contributions is generally poor.  We need better vocabularies, shared understanding, improved reporting and other policy and practice changes to recognize the work of all the participants in the work.  Some sites have objected to the notion of inclusion on the grounds of “density” — some of these people may have contributed little.  Multiplying the number of people in the profile system by five or ten times to include these people may not be seen as cost effective for the institution. And there may be privacy concerns for including students who may not be employees of the institution. 
Some institutions go even further and include professional staff such as lab technicians, software developers, data managers, writers, crafts people, project managers, administrators, and many others.  Think of the last time you saw a list of movie credits.  What kinds of people are included?  Each of the people in the credits had a role in creating the movie you watched.  Is the situation somehow different in the creation, transmission, and preservation of knowledge and creative works?  Should we have the means to recognize everyone’s contribution?
I hope the VIVO community can serve as a forum for the discussion of the question raised here — who should have a profile?  Let’s discuss!

VIVO Updates, April 30, 2017 -- Conference, Camp, Ontology, Outreach

New York State of Mind.  Summer is coming and with summer come thoughts of New York and the VIVO Conference.  The conference will be held at Weill Cornell Medicine, August 2-4, 2017.  Conference registration includes half-day workshops, invited speakers, keynotes, posters, and presentations by your colleagues in the VIVO community. Join us for the premier VIVO event of the year.  Registration is open!

VIVO Camp.  The first VIVO Camp was held in Albuquerque New Mexico, April 6-8.  We had a great group of attendees from del Rosario University, Stanford, the University of New Mexico, MIT, Fred Hutchinson Cancer Center, the University of Auckland, McMaster University, and UNAVCO. Lots of learning and sharing about VIVO and VIVO projects! Thanks to the instructors Julia TrimmerVioleta IlikPaul Albert, and Graham Triggs who joined me in presenting material and leading discussions.  

When and where should we hold the next camp?  Drop us a note a let us know what you think.

Ontology Domain.  We all know what VIVO is about, right?  Kinda sorta?  But sometimes we are surprised by what we find and don't find in the VIVO ontology.  There might be things we want to say about our faculty and our experts that are difficult to say, or are missing.  And conversely, people who study the ontology (you know who you are) find things in the ontology that might not be relevant to the work of VIVO.  Nothing is perfect.  That's why we have an Ontology Improvement Task Force.  The task force is working on a draft "domain definition" describing the domain of the VIVO ontology.  Domain definitions are often accompanied by "competency questions"  – questions that should be answerable using the ontology.  The draft domain definitio, competency questions and some observations are available here: and is open for comments and review.  

Please take a look.

Outreach call this Thursday.  This Thursday, May 4 at 1 PM US Eastern time, the Outreach and Engagement Interest Group will have its monthly call.  everyone is invited to share thoughts about engaging people with VIVO.  This is a non-technical call.  All are welcome!  Here's the  WebEx Link

Can't make the call?  Share your thoughts, questions, comments, and concerns on the VIVO Community Google Group (web) (email)



Mike Conlon  VIVO Project Director Duraspace