VIVO Updates -- conference time, Scholars@Cornell launches

Conference time!  The VIVO Conference starts this Wednesday with five workshops and a welcome reception.  Thursday continues with a full program and the poster session and reception.  Friday is another full day with a second keynote, contributed presentations and the closing session.  Weill Cornell Medicine has done an outstanding job preparing for all of us.  Alex Viggio, Conference Chair and Violeta Ilik, Program Chair, and the VIVO 2017 Conference Planning Task Force have put together a great conference.  Registration is open on line at  And walk-up registration is welcome in New York.  Student registration is just $99.  It's going to be a great event.  See you there!

Are you presenting at VIVO 2017?  Once again, VIVO is partnering with figshare to demonstrate the value of a connected ecosystem.  Presenters are encouraged to deposit their materials at figshare, register their ORCiD with the their figshare account, and tag their work with the keyword vivo17.  VIVO uses scripts to harvest materials tagged vivo17 and add them to OpenVIVO under the conference page in OpenVIVO.  Works are also linked to author's profiles.  The result is identified, public metadata for the presentations at the conference.  You may also choose to copy your work to a USB provided at the conference – we can take it from there.  Our goal is a complete presentation of the conference on OpenVIVO.

Tweeting the conference?  Following the conference on Twitter?  It's #vivo17.

Scholars@Cornell Cornell University Library announces the beta launch of Scholars@Cornell - a new data and visualization service for exploring Cornell research from the standpoint of the scholarly record. Scholars@Cornell provides a knowledge network with interactive visualizations for exploring faculty, academic units, and scholarly outputs.  It uses data feeds of publications, grants, and academic affiliations, and provides quality control from both automated routines and data curation partners.   It’s easy to explore the data with the new web-based experience provided by Scholars@Cornell.

Check it out now!

No interest group meeting this week  It's conference time!  See you in New York!



Mike Conlon VIVO Project DirectorDuraspace 



VIVO Updates -- membership, conference, ontology improvements, apps and tools

Membership supports VIVO  How can we afford to do the work we do – advance the software, organize meetings, provide documentation, evangelize VIVO, work with partners, and coordinate the work of all the volunteers supporting VIVO?  The answer is membership in Duraspace supporting the VIVO project.  The VIVO Project relies on you – the users of VIVO, to provide financial support through institutional memberships.  Our sincere thanks go out to all the sites that are institutional members.  You can find a list of these fine folks here:  VIVO Members.  I would like to thank each and every member for their critical financial support.  Without members, there is no project.  If you are a member, please consider whether you might be able to increase your support.  If you are using VIVO and you are not a member, please start a discussion at your institution regarding membership.  If you have questions about membership or member benefits, please do not hesitate to contact me.  Becoming a member is easy.  Follow this link: (that's so easy you can remember it, or write it down).  And please tell your friends and share with others in the VIVO community.  We look forward to your continuing support!

The VIVO Conference  This is NOT the last time VIVO Updates will tell you about the VIVO Conference.  Next week is the last VIVO Updates before the conference.  If you haven't made plans, you still have a 10 days!  See Weill Cornell Medicine has done a tremendous job with local arrangements – we have an exciting line-up of workshops on August 3 followed by an opening reception at the Skylight Lounge, fabulous keynotes and invited speakers, tons of contributed work showing VIVO at various institutions, problems being solved, work for the future, Posters, panels, and of course, an opportunity to discuss VIVO with practitioners from around the world.  It's going to be a great time and I hope to meet you and discuss VIVO with you.  I want to take this opportunity to thank our sponsors.  Sponsors provide critical support for the conference.  When you are at the conference, please stop by the sponsor tables, discuss their interests and thank them for their support.  A special thanks to our institutional sponsors providing additional support.  You can find the sponsors listed on the conference home page.

Ontology Improvements  The Ontology Improvement Task Force will have its next meeting Monday July 31, at 10 AM US Eastern.  The group has been defining a new ontology improvement process for tracking issues, working issues, and insuring that ontology improvements are represented in versions of the released VIVO software – we also expect to be able to update the ontology without needing to update the software.

One feature of the ontology improvement process is the concept of impact.  Some changes are cosmetic, internal, or otherwise have no impact on existing VIVO sites.  Other changes will require changes to the data of existing sites.  And still other changes will require changes to the data and software of running sites.  As changes are proposed, we will try our best to be clear about the impact of a proposed change.  We are planning to have proposed changes vetted by the community during an open comment period.

You can find the draft ontology improvement process, available for comment, here:

Apps and Tools  The Apps and Tools Interest Group will have a call this Thursday at 1 PM Eastern time.  Here's the webex link:  We will take a look at the new Triple Pattern Fragments server available in version 1.10 and available now in OpenVIVO here:



Mike Conlon 

VIVO Project Director


VIVO Updates -- inflibnet workshop, implementation support, open repositories, and more

InfLibNet National VIVO Workshop, Gandhinagar, India, Aug 16-18   The Information and Library Network Centre (INFLIBNET), Inter-University Centre of UGC, Gandhinagar is organizing "Three-day National Workshop on VIVO Faculty Profile Management System and Discovery’’ 16- 18th August 2017 at INFLIBNET Centre, Infocity, Gandhinagar, India.  More about the workshop here:  Online registration:

Implementing VIVO?  We have some resources that might help:

  • Planning a VIVO Implementation is a section of the VIVO wiki focused on issues that arise in using VIVO as an enterprise system to represent scholarship.  Written by VIVO experts, the material covers project management, outreach and engagement, data management, and technical development.  A glossary of common VIVO terms is included to get you started.
  • The Implementation Interest Group meets every four weeks, and will meet this Thursday at 1 PM US Eastern time.  The group discusses implementation issues and checks in on the status of implementations currently underway.  Here's a webex link:  All are welcome!
  • VIVO Camp is a 2.5 day ticketed event with hands on training in VIVO implementation.  We are considering a VIVO Camp in the Raleigh Durham area November 9-11.  If this would be of interest to you and your site, please drop me a note.

Managing Organizations  Many VIVO sites use VIVO to maintain the organizational structure of their site using VIVO.  VIVO provides the means to indicate the types of organizations – colleges, departments, divisions, and many others, and the means to indicate that one organization is part of another.  Managing organizations is a good training use case – one can see how data is represented – both data properties (attributes of the organizations such as name) and object properties (connections between objects).  We have a new complete worked example of managing organizations in The VIVO 1.9.x Documentation.  See Managing Organization Hierarchy

Open Repositories followup  Open Repositories is an annual conference bringing together people work on repositories based on open source software such as Dspace, Fedora, and VIVO.  The conference was held in Brisbane Australia June 26-30.  Graham Triggs and Mike Conlon attended along with Andrew Woods, Tim Donohue, Erin Tripp, and Debra Kurtz of Duraspace.  We had a poster and a presentation, both available via OpenVIVO.  The conference is a great opportunity to discuss VIVO with people in the community and those new to VIVO.  In particular, we had very productive conversations with Mark Fallu of the University of Melbourne, Tom Cramer of Stanford, Amir Aryani of the Australian National Data Service, Rick Johnson of Notre Dame and OSF, and many others.

The open repository community is growing in its interest in open data, open access, open science, open metadata, common identifiers, linked data, and interests in institutional representation of scholarship.  Duraspace is a sponsor of the conference and has many roles of the years in fostering the growth and continuance of this community.  Next year's conference will be at Montana State University in Bozeman Montana, June 4-7, 2018.  See

Vitro Page  Want to use Vitro without VIVO?  Vitro is a general purpose semantic web data hosting and ontology editing platform.  VIVO is built on Vitro, but you can use Vitro all by itself to manage any kind of data for which you have an ontology.  See

VIVO Conference, Weill Cornell Medicine, New York City, Aug 2-4  17 days until the VIVO Conference.  See you all there!



Mike Conlon VIVO Project DirectorDuraspace 



VIVO Updates -- conference, workshop, development, monthly column, Research Graph

VIVO Conference Aug 2-4, Weill Cornell Medicine, NYC  Plenty of time to register and plan to attend.  Fabulous keynotes, invited speakers, contributed talks, posters, sponsors, NYC, and your VIVO colleagues!  Questions, answers, discovery, enlightenment.  What could be better than that?  See you in New York!

Second VIVO Workshop September 28,  German National Library of Science and Technology (TIB) in Hannover, Germany  Amongst other, there will be reports on existing or planned VIVO projects. We would be delighted to hear from your experiences, or your own developments, too. Please send me an email with your suggestion, if you would like to hold a talk at our workshop.  More information and registration:  Due to the limited number of participants, an early registration is recommended. The workshop will be held in German language.

Development Meeting  The Development Interest Group will meet this Thursday at 1 PM Eastern.  Plans for 1.10 will be discussed.  Here's the webex link:

VIVO is more than profiles  We often talk of VIVO as a profile system – a system for showcasing the work of scholars.  But it is much more than that.  VIVO create a connected graph of scholarship – one that can be used to discovery connections between all the elements of scholarship – people, grants, works, datasets, resources, and much more.  This month's column explores the idea of VIVO as a connected graph of scholarship, and the opportunities that affords us.

Research Graph and VIVO  Speaking of connected graphs of scholarship, there is Research Graph, an effort of the Australian National Data Service in partnership with the Research Data Alliance.  Research Graph has been mapped to VIVO and Research Graph data hosted in a VIVO.  You can read more here.  Duraspace and Research Graph are exploring possible services related to the mapping of Research Graph and VIVO.  You can express interest in this work here.



Mike Conlon VIVO Project DirectorDuraspace 


July 2017
When I first saw VIVO, I was struck by the simplicity and power of its connective nature.  Anything could be connected to anything through the elegant syntax of the semantic web.  Over the years, there has been a focus on "profiles" -- assemblies of works of individual scholars, in formats that resemble department web pages, or curriculum vitae, or biosketches.  This focus has created a perception that VIVO is a profile system.  That's unfortunate.
VIVO can display profiles, and there is great value in using an open source, semantic web application to display profiles.  But VIVO is much more than a profile system.  VIVO creates an integrated "graph" of the entities it represents.  Graphs are the natural structures for representing connections.  Triples are the natural means of representing graphs in computers.
What connections are of interest?  A simple, but perhaps not very useful answer is "all."  We want to know which people used what resource.  We want to know which grants funded what datasets.  We want to know what events exhibited which presentations.
Suppose we wish to make connections between six kinds of things -- works, people, datasets, grants, organizations, and people.  We can, of course, imagine other kinds of things we might wish to connect -- events, resources, locations, time periods, and so on.  For six kinds of things, there are 15 kinds of pairs of things -- grants and people, works and datasets, plus the six reflexive pairings -- people to people, works to works, etc.  
We can start to think of the kinds of connections there might be between various kinds of things.  Consider people and grants.  We have a person funded by a grant.  A person is the principal investigator of a grant.  A  person might follow a grant, in the way a person might follow another person in social media.  There could be many types of connections between people and grants.  Each can be modeled in VIVO.
We can start to think of a thing and the types of connections that thing might have to other things.  Consider a publication as a thing.  The publication is connected to a journal, to its authors, to a time of publication.  The publication is connected to its publisher through its journal, to various organizations through its authors, to a full text representation in a repository, to metrics regarding its use, possibly to grant funding, to software and datasets, to concepts, and to other publications through references and citations.  In other words, the publication is a node in a connected graph consisting of other elements of scholarship.
Some connections have their own data -- data about the connection itself.  A person has a position in an organization.  The position is a connection between the person and the organization indicating employment.  The employment has a time period, and a title.  The position typically has a type.  Each of these pieces of data are about the connection between the person and the organization.
Each connection is recorded as data in VIVO.  VIVO has data about the connected things, and the nature of the connection between the things, and data about the connection between the things.  Of all of these, the person has a bit of a special place in a VIVO.  There has been more effort put into representing people and their connections, and more effort in displaying people and their connections.  This is the so-called profile, and leads to the characterization of VIVO as a profile system.  But underneath, VIVO is a connected graph, and we can have any amount of detail we wish about any of the elements of the graph.
What if we made profiles of events rather than people?  What would an event "profile" look like?  What information do we want to see? How far into the graph of connections would we reach?  Are there important connections between events?  Between events and other things in the connected graph of scholarship?  What would we be able to know that is difficult to know now?  The same questions can be asked of any of the graph entities.
What are the connections of interest?  What connections are already in VIVO and which should be added?  What is missing in order to make the connections of interest?  If we had the connections we need, how would we use them to better understand and use the scholarship of our organization and of the world?  What tools and capabilities would we create?
In future columns, I'll share some thoughts about these questions.  Please share your thoughts with others.  It is through sharing that we will grow our understanding of the utility of connections, and of what we must build next.

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