Blog

VIVO Updates for June 26 -- Conference deadline, ALA, Persistent identifiers

Conference early bird deadline extended to Tuesday June 28.  And the conference program is available on line!  And we have a new keynote, Dario Taraborelli of Wikidata! Register today at http://vivoconference.org

VIVO 1.9 beta is coming.  VIVO 1.9 introduces Apache Maven to VIVO and uses Maven to simplify VIVO builds, code development, and resolution of dependencies.  Using Maven, dependencies can be declared in the VIVO release, and resolved at build time from the Maven Central Repository, simplifying the build process and code maintenance.  VIVO 1.9 addresses more than 25 reported issues with VIVO and introduces a capability map for expert finding and research discovery.

Call this Thursday.  At 1 PM Eastern US time, VIVO will have a call regarding VIVO 1.9 documentation.  A new documentation wiki is being planned.  The new wiki would focus on documentation for VIVO 1.9.  The existing Wiki would remain to facilitate all community VIVO activities, as it does now.  Only technical documentation would make its way to the new space, to be organized as preserved as a version specific technical manual.  The meeting will be held on WebEx here.  If you are interested in VIVO technical documentation, please join the call!

American Library Association Meeting.  Saturday I had the pleasure of attending my first American Library Association meeting in Orlando.  I gave a presentation on OpenVIVO (see Figshare), saw presentations on the current work in linked data in libraries – with libraries considering how to move from current record-based approaches to the entity-based (person, organization, work) approach of linked data.  I met with friends from Lyrasis and Thomson Reuters.  ALA 2016 had 18,000 registrants and a huge exhibit area.  A full trip report is availablehere.

Persistent Identifiers.  OpenVIVO, as you may know, makes extensive use of persistent identifiers.  Persistent identifiers allow accurate identification of entities – people, organizations, works, journals, concepts and dates.  In each case, OpenVIVO uses an entity URI that contains the persistent identifiers for the entity.  OpenVIVO uses the letter "a' in URI rather than the default "individual" to shorten URI.  Here's a summary of the persistent identifiers in use in OpenVIVO:

  • People – ORCiD.  In OpenVIVO, if a person does not have an ORCiD, they can not be in the system.  This eliminates the disambiguation problem, as well as providing usernames and passwords for OpenVIVO through the ORCiD OAuth service.  Finally, use of the ORCiD public API insures that works in OpenVIVO from ORCiD are publicly available.  Person in OpenVIVO has a URI that includes their ORCiD.  For example: http://openvivo.org/a/orcid0000-0002-1304-8447
  • Journals – ISSN.  OpenVIVO uses a collection of more than 44,000 journals, each with a print ISSN.  The data was created by the OpenVIVO team by matching a list of CrossRef journal titles with ISSN with a list of journal titles with ISSN from PubMed.  The union of the two sets of data was used.  RDF was created for the journals with URIs for each journal that look like http://openvivo.org/a/jou.0028-4793.  Data properties include title, abbreviation, print ISSN and electronic ISSN.
  • Works can be identified by DOI or PubMed ID (PMID).  A work identified by a DOI has  URI that looks like: http://openvivo.org/a/doi10.1101/048744.  A work identified by a PMID has a URI that looks like:  http://openvivo.org/a/pmid11569568.  All works are identified by either DOI or PMID.  Services exist to assign DOI to software (eg,Zenodo), presentations (eg Figshare) and datasets (eg DataCite) with metadata provided by CrossRef.  Many other services exist to provide DOI to content, and many local repositories assign DOI.  Reliance on DOI and PMID simplifies OpenVIVO.  Metadata for DOI comes from CrossRef exclusively, regardless of the type of work or the source of the original DOI.  Metadata for PMID comes from PubMed.
  • Organizations.  OpenVIVO partnered with Digital Science to create RDF from the Grid data, an open license dataset of the world's research organizations available for download at no charge from Digital Science.  The Grid data contains more than 58,000 research organizations and is being updated each month.  Data values include contact information, preferred and alternate labels, latitude and longitude, organizational type and much more.  See http://grid.ac  for a complete description of GRID.  GRID assigns GRID identifers to each research organization.  Software for converting the GRID data to RDF and a set of RDF for the GRID data is available from GitHub at https://github.com/OpenVIVO/grid-rdf
  •  Dates - dates have persistent identifiers based on their values and precisions.  "2006-10-01" indicates a dateTimeValue with a year month day precision, and has the URI http://openvivo.org/a/date2006-10-01.  Similarly, "2006-10" indicates a dateTimeValue with year month precision and the URI http://openvivo.org/a/date2006-10.  Predictably, "2006" indicates a dateTimeValue with year precision and URI http://openvivo.org/a/date2006.  OpenVIVO is preloaded with all dates of these three precisions in the range 1960 to 2030.  You can find a set of date RDF that you can use in your VIVO at GitHub at https://github.com/OpenVIVO/date-rdf, along with software with generating date RDF of this kind.
  • Concepts.  Open VIVO uses the FAST terminology for research areas.  This operates a little different from the previous cases.  When a profile owner wishes to to indicate one of their research areas, they select the card catalogue icon by research areas on their profile.  They are presented with their current research areas from FAST, if any, and a button marked "Add Concept."  Clicking Add Concept provides a search box for the FAST external vocabulary service.  The user can type text, and matching FAST concepts are returned.  The user can select concepts to be added to the user's research.  OpenVIVO supports only the FAST vocabulary.  No concepts are preloaded into VIVO.  Concepts are added as they are selected by users.  To date, over 300 concepts have been selected and added.  Each concept has a URI that looks like http://openvivo.org/a?uri=http%3A%2F%2Fid.worldcat.org%2Ffast%2F1045995, which is referencing the FAST term URI http://id.worldcat.org/fast/1045995

Many VIVO sites extend the ontology to record persistent identifiers in common use at their institution.  Perhaps the most common extension is for the local employee number and/or netid.  Recording this identifier in VIVO simplifies matching of VIVO person entities to data about people provided by the institution, which may include employment records, grant records, teaching records, mentoring and other activities.  Many VIVO sites imbed persistent identifiers in URIs, as OpenVIVO does.

The choices made by the OpenVIVO project to use persistent identifiers and to provide open, reusable RDF for common entities can be used by VIVO sites to simplify and standardize the RDF for VIVO sites.  More work is needed to implement this approach in future releases of VIVO.  Interested in helping?  Contact Graham Triggs or Mike Conlon.

Go VIVO!

Mike

Mike Conlon  VIVO Project Director Duraspace 

 
 

 

VIVO Updates for June 19 -- University of New Mexico, University of Wollongong, Open Repositories

Welcome, University of New Mexico, as a member of Duraspace supporting the VIVO Project!  The University of New Mexico has joined the VIVO Project as a Silver Member.  You can find their VIVO site here:  https://vivo.health.unm.edu/.  The University of New Mexico is the flagship university of the state of New Mexico in the US.  The university is a member of the Clinical and Translational Science Award program of the National Institutes of Health.  The university has coordinated the Mountain West Consortium, a group of schools in the western university states, each providing VIVO data.  See https://search.vivo.ctr-in.org/ for a consortium search capability across the schools of the consortium.  A hearty thanks to the University of new Mexico for their support of Duraspace and VIVO!

New VIVO site at the University of Wollongong.  The University of Wollongong Australia has launched a new VIVO site.  See https://scholars.uow.edu.au/.  This site has an attractive, responsive user interface with data on people, publications, grants, research areas and more.  Check it out!

Open Repositories, 2016.  Graham Triggs and I enjoyed meeting people at Open Repositories in Dublin, learning more about current work in repositories, repository software, open science, and projects  with intersections with VIVO.  The conference of 480 or so attendees from around the world had significant content this year on acquisition and preservation of research data.  We presented OpenVIVO as a poster.  The poster is available at Figshare here.

Apps and Tools Interest Group call this Thursday. The Apps and Tools Interest Group will have its call this Thursday at 1 PM US Eastern time.  Please join the call to discuss tools and applications used with VIVO.  Have an idea for software that might improve the value of VIVO – make VIVO data easier to manage, use VIVO data in a new way?  Share your idea on the call!  Have  question about a tool listed in the Community Projects?  Share your question on the call!

See OpenVIVO at ALA.   I'll be presenting OpenVIVO at ALA this Saturday, June 25 at the Orlando Convention Center in a panel session regarding linked data.  If you are going to ALA, I hope you have a chance to attend the panel.

Go VIVO!

Mike

Mike Conlon  VIVO Project Director Duraspace 

VIVO Updates for June 5 -- Membership, early-bird conference deadline

Showcase the scholarship at your institution!  This week, the VIVO membership drive began in earnest with an email to all VIVO community members.  I hope you received the email and are considering how your institution might financially support VIVO:

  • Corporations can participate as Duraspace corporate sponsors.  See  http://vivoweb.org/sponsorship
  • Academic institutions and research organizations can participate as Duraspace members.  See http://vivoweb.org/membership
  • Existing members and financial supporters may wish to consider increasing their support for 2016.  Cornell University recently tripled its financial support of the VIVO Project.  We thank Cornell for this outstanding support!

The text of the email is available as a blog post.  Please share the link with those in your institution who may wish to support open source software, and the development of VIVO.  We appreciate your help in getting the word out regarding the membership drive and we look forward to your financial support!

Early bird conference registration deadline is June 20.  Register now to get the lowest rate on VIVO Conference registration.  The early bird deadline is Monday, June 20. Register now and join us for a great conference in Denver, August 17-19!

Development Interest Group call this Thursday. The Development Interest Group will have its call this Thursday at 1 PM US Eastern time.  Developers will discuss version 1.9, including JIRA tickets in progress and recently closed.

See OpenVIVO at Open Repositories.   Graham Triggs and I will be at Open Repositories, Trinity College, Dublin, June 13-16.  Stop by the OpenVIVO poster.  We'd love to meet you!

Go VIVO!

Mike

Mike Conlon  VIVO Project Director Duraspace

Showcase the scholarship at your institution!

Have you speculated on what it would take to "move the needle" toward a digital future that effectively showcases all facets of institutional scholarship? I am writing today to tell you that VIVO, the open source software that creates an integrated record of the scholarly work of your organization, needs your help. If you care about showcasing the institutional scholarship at your institution please consider financial support of VIVO to move the needle forward in 2016.

Your financial support is critical at this time. Without it, we will be unable to continue to advance the VIVO Project and meet the community's goals for 2016, including:

  • Release of VIVO 1.9 with simplified build and management tools
  • Release of VIVO 1.10 with improved presentation, data acquisition, and data management tools

To support VIVO, join DuraSpace as a member at  http://duraspace.org/become_a_member

"VIVO is fundamental to representing the work of the faculty at Duke.  Our Scholars@Duke site, based on VIVO, showcases their work to the whole world."

Julia Trimmer,
Manager Faculty Data Systems
Duke University

Three VIVO financial myths:

Myth 1: DuraSpace has financial resources to support ongoing VIVO project development.

Reality: DuraSpace funding comes from its members.  DuraSpace has no other funds to support projects.

Myth 2: The DuraSpace organization, and in turn the VIVO Project, are funded by grants.

Reality: DuraSpace project funding comes from membership.  VIVO was funded by a large NIH grant from 2009-11.  Since then, VIVO has been supported by DuraSpace members.

Myth 3: In-kind code contributions and coordination of community outreach are acceptable substitutes for dollars.

Reality: While volunteer community efforts are at the heart of open source software development and are deeply appreciated, financial contributions in the form of DuraSpace memberships are required for VIVO core salaries, travel and other expenses.

More information

If you have questions please feel free to contact me.

I look forward to your financial support of the VIVO project.

Sincerely,

Mike

Dr. Mike Conlon
VIVO Project Director
DuraSpace
mconlon@duraspace.org

 

VIVO Updates, May 29

Web site update.  Two pages have been added to the VIVO web site, http://vivoweb.org.  The About page describes the VIVO project, software and ontology.  Please refer people to this page who are looking for a short answer to the question "What is VIVO?"  The Corporate Sponsorship page describes the Duraspace corporate sponsorship program and how the program works for VIVO.  Please refer any companies with a potential interest in supporting the VIVO project to this page for a brief overview of the corporate sponsorship program.  Both pages are available from the menus at the top of every page, and from the footer on every page.

Outreach and Engagement call this Thursday. The Outreach and Engagement Interest Group will have its call this Thursday at 1 PM US Eastern time.  All are welcome to join the discussion regarding engaging faculty and staff in the use and support of VIVO.  

See OpenVIVO at Open Repositories.   Graham Triggs and I will be at Open Repositories, Trinity College, Dublin, June 13-16.  Stop by the OpenVIVO poster.  We'd love to meet you!

Go VIVO!

Mike

Mike Conlon

VIVO Project Director

Duraspace

VIVO Updates, May 22. Google Scholar. Membership.

Google Scholar.  Occasionally we are asked about using Google Scholar and Google Scholar data to populate VIVO.  Is there an API?  Are there open source tools for harvesting Google Scholar data?  Are there licensing restrictions?  Google Scholar does a good job  of scanning the web looking for authors' works and uses sophisticated heuristics to assemble collections of works for authors.  Many faculty curate their Google Scholar collection, thereby enriching the data.  Google has a global Terms of Service document that covers all of its services.  In that document it says "Do not misuse our services."  The key questions then are what constitutes a service, and what constitutes misuse?  We asked Google representatives specifically about the use of Google Scholar data in VIVO.  Their answer was very clear.  The Google Scholar service can only be used by an end user using a browser. Google Scholar data can not be harvested by software, or repurposed in VIVO or other systems.  This is unfortunate, but at the present time, Google Scholar is not a source of data for VIVO.

VIVO Financial Support.  We are sometimes asked questions about the VIVO project's finances.  Where does the money come from to support the VIVO project?  The answer is very simple. VIVO is a member-supported project of Duraspace. This means that the financial support for VIVO comes from Duraspace members supporting the VIVO project.  Each year, Duraspace member institutions provide financial support to the VIVO project.  Without Duraspace members, VIVO is unable to operate.  VIVO has a fabulous set of members – they contribute financial resources, and in return participate in VIVO governance, and have the satisfaction of knowing they help support an important open source project for the world of scholarship.  You can find a list of Duraspace members and corporate sponsors supporting the VIVO project here:  http://vivoweb.org/membership  We would not exist without them.  

Last year, 94% of the VIVO project revenue came from its members and corporate sponsors.  6% came from other sources.  The VIVO conference is an independent financial entity – it does not receive funds from the VIVO members and it does not provide funds to the VIVO project.  Duraspace supports the VIVO project through its membership.  It does not have other assets with which to support VIVO or its other projects.  The projects exist in a sustainable way if enough members financially support the project.

The support of Duraspace members drives the success of the project.  Because of the Duraspace members, we are able to have a technical lead, travel to represent VIVO, organize events such as the user group meeting, provide a wiki, a web site, and other project infrastructure.  In the past year, the VIVO project released version 1.8.1, providing a significant improvement in end user performance, and created OpenVIVO, a demonstration of a hosted VIVO, using ORCiD sign on, collecting metadata from multiple sources in real-time, and publishing its data to an open web site every hour.

VIVO needs your institution to become a member.  If you are a member, we are most grateful for your continued support.  If you are not a member, you will be hearing more about membership in the coming months, from additional material to be posted here, from direct mailings, and from personal contacts by members of the VIVO community.  Please consider this information and consider how your institution may be able to financially support VIVO by becoming a Duraspace member.  We need your support.

Becoming a member is very simple.  You can find all the materials you need at http://vivoweb.org/membership.  Membership benefits are described in the VIVO Project Charter v 1.1.

Please give membership some thought.

VIVO meet-up at Symplectic Meeting.  Symplectic will hold its annual conference September 13-14 at Duke.  Interested in having a VIVO meet-up or other activity in conjunction with the Symplectic conference?  Contact Julia Trimmer with any ideas you may have.

Wiki Updates.  The VIVO wiki home page had some updates this week, improving some language, updating entries and fixing links.  Take a look at the VIVO wiki.   Please update anything you find that could be improved.  It's your wiki and its open for editing!

Apps and Tools call this Thursday. The Apps and Tools Interest Group will have its call this Thursday at 1 PM US Eastern time.  All are invited to hear about tools and applications regarding VIVO.

See OpenVIVO at Open Repositories.  Graham Triggs and I will be at Open Repositories, Trinity College, Dublin, June 13-16.  Stop by the OpenVIVO poster.  We'd love to meet you!

Go VIVO!

Mike

Mike Conlon VIVO Project Director

VIVO Updates for May 15 -- conference, merger, Duraspace, email lists

Poster deadline extended.  There's still time for you to submit a poster to VIVO 2016!  This is a great opportunity for you to share your work with the VIVO community. The deadline for poster submissions has been extended to May 23.  See http://vivoconference.org

Conference registration open.  And, by the way, conference registration is open.  Our keynotes this year are Sören Auer and Kaitlyn Thaney.  Should be a fantastic meeting in Denver, August 17-19.  Take advantage of early-bird registration rates.   http://vivoconference.org

LYRASIS and DuraSpace Announce Dissolution of "Intent to Merge".  After several months of due diligence, the boards of Lyrasis and Duraspace have dissolved the intent to merge.  The full text of the press release can be found here:  http://duraspace.org/articles/2879.  As a full participant in the process, I believe the result is a good one for our communities.  I look forward to strong years ahead.

Duraspace Retreat.  Mike Conlon and Graham Triggs attended a bi-annual Duraspace retreat in White Plains Georgia, May 9-12.  We had an opportunity to review the past six months and plan for the next six months with the rest of the Duraspace crew.  Many people help with VIVO.  debra hanken kurtz and Jonathan Markow are heavily involved – attending our meetings, helping with membership, strategy, and governance, and introducing us to people across the community.  Valorie Hollister handles the money.  Kristi Searle manages events and maintains our contacts.  Carol Minton Morris organizes communications and branding strategy.  The other Duraspace projects and services were represented by their managers and technical leads – David Wilcox and Andrew Woods for Fedora,  Tim Donohue for Dspace, Carissa SmithBill Branan and Danny Bernstein for Duraspace services including DuraCloud and Dspace Direct. Together, Duraspace seeks to enable the preservation of digital assets in scholarship and cultural heritage.  It's a great group of people who care about open source, and the missions of our institutions.

Use of the VIVO email lists.  The VIVO email lists – vivo-community@googlegroups.com and vivo-tech@googlegroups.com are for the use of the VIVO community.  "VIVO" is now a common trade name – there are many VIVO's around the world.  Our VIVO, this VIVO, the VIVO we participate in regarding open source, and representation of scholarship, is often confused with telecommunication companies, and nongovernmental organizations.  Our email lists are open – anyone can subscribe, and any subscriber can post.  This seems appropriate for an open source community.  The consequence of this openness is that occasionally someone will join the list and post something that is not appropriate for us.  This happened recently.  In each case, I responded to the poster privately, explaining the purpose of the list and the nature of our community.  I then unsubscribed the poster.  Our lists serve as open forums for the exchange of ideas about VIVO – its software, its ontologies, and its use in scholarship.

Apps and Tools call this Thursday. The Apps and Tools Interest Group will have its call this Thursday at 1 PM US Eastern time.  All are invited to hear about tools and applications regarding VIVO.

See OpenVIVO at Open Repositories.  Graham Triggs and I will be at Open Repositories, Trinity College, Dublin, June 13-16.  Stop by the OpenVIVO poster.  We'd love to meet you!

Go VIVO!

Mike

Mike Conlon VIVO Project Director

VIVO Updates for May 8, 2016 -- VIVO User Group Meeting

VIVO User Group Meeting. We had a great VIVO User Group meeting in Chicago at the Galter Health Science Library.  You can find materials from the meeting on line here. The two day meeting sessions included:

  • Introductions. Logistics. Session Topics. Ground rules. Work Products for the user group

  • Showcasing scholarly work. Design. User experience. Optimizing -- landing, person, org, and work pages. Performance

  • Expert finding. Research Discovery. Search. Cross-site linking and search.
  • Accessing works – linking to works on the web, in repos, use of public APIs. Ingesting data – domains of ingest, tools, data packages.

  • Community change management for ontology changes. Notices, training, documentation, tools, support for changes.

  • How to improve VIVO. Software architecture. Tools. Process. Releases. 1.9. 1.10. VIVO Labs. VIVO Futures
  • Read back, summary, action items. Next meeting. Meeting adjourns

The group discussed action items that will follow from the meeting. Each of these will involve community input on the VIVO calls and email lists, and possible task forces:

  1. Develop an Ontology development process - how is the ontology developed?

  2. Release 1.9 (before conference) – including new technical documentation

  3. Organize VIVO Labs – a method for experimenting with new VIVO capabilities.  See the Contributed Software Task Force Report

  4. Develop a 1.10 roadmap – using the VIVO Roadmap Process, continue the user group discussions to develop a roadmap for version 1.10

  5. Approach to Expert finding – consider how best to move forward with significant new capability in expert finding

  6. Approach to Central Services – consider how best to establish significant, sustainable, central services for cross-site search and disambiguation

  7. Approach to VIVO Futures – consider how best to further discussion regarding technical debt, and architectural issues for future VIVO software.

Thanks to all who attended!  Attendee list is here https://goo.gl/yFmWea   The discussions were incredible!

Special thanks to Kristi Holmes for hosting the meeting and to the staff at Northwestern for their hospitality and assistance.  Chicago is a lovely city, and the Feinberg School of Medicine at Northwestern is close to the lake and close to Michigan Avenue with many top attractions, amazing food, and shopping.

The group considered when to meet again.  VIVO will likely have an in-person meeting sometime in late fall to discuss the strategic plan – more about that in the coming weeks.  A second user group meeting might occur in early 2017 (February?) to assess progress, and discuss direction.  Please share thoughts on vivo-community@googlegroup.com Plans for future meetings will be summarized here in VIVO Updates, along with any specific announcements of meetings.

We will have more regarding the user group meeting in a trip report, and user group meeting report to come.  Stay tuned.

Community Leadership Summit.  VIVO folks Julia TrimmerAlex Viggio, and debra hanken kurtz will be attending the Community Leadership Summit in Austin Texas, May 15-16.

Duraspace Retreat.  Mike Conlon and Graham Triggs will be attending a bi-annual Duraspace retreat in White Plains Georgia, May 9-12.  This is an opportunity to connect to other Duraspace projects, and develop strategy for the next six months.  We will report back here next week.

Duraspace/Lyrasis Board Meeting.  Mike Conlon will be attending a joint Duraspace/Lyrasis board meeting in Atlanta Georgia, May 15.  The intent to merge will be discussed.

Development Call. The Development Interest Group will have its call this Thursday at 1 PM US Eastern time.  Developers interested in VIVO 1.9 should plan to attend.

OpenVIVO. A VIVO anyone can join.  Have you tried OpenVIVO?  162 people in 12 countries have signed on to OpenVIVO, with 975 works entered from ORCiD, PubMed and Figshare.  Give it a try and let us know what you think.

Comments on all things VIVO.  Questions, comments, concerns, ideas for VIVO? Non-technical items are always welcome on vivo-community@googlegroups.com Technical items are best shared on vivo-tech@googlegroups.com. The VIVO community is always looking to help and always interested in questions and comments from all!

Go VIVO!

Mike

Mike Conlon VIVO Project Director

 

 

VIVO Updates for April 24 -- Hackathon, Apps and Tools, OpenVIVO, User Group, Open Repositories

Mozilla Open Science Hackathon.  On June 2 and June 3, Mozilla will host a global open science hackathon.  VIVO participated last year, working on ORCID2VIVO, and generating ideas that led to features in OpenVIVO.  Interested in participating?  Have ideas for the hackathon?  Just curious about what a hackathon is, and how it might help VIVO and open science?  See 2016 Mozilla Science Lab Global Sprint in the wiki and contact Alex Viggio with questions, ideas, interest.

Apps and Tools Call. The Apps and Tools Interest Group will have its call this Thursday at 1 PM US Eastern time.  Apps and Tools features short presentations by VIVO implementors and developers regarding tools they have created for use with VIVO.  Many of these tools are available in the Community Projects catalog.  These tools may help you with your implementation, with improving your VIVO services, or give you ideas about how you might use VIVO.

Force16.  The Force16 conference in Portland was fabulous in no small part due to the incredible leadership and vision of the conference chair, and VIVO Steering Committee member,  Melissa Haendel of Oregon Health and Sciences University.  The "Force" idea grew out of a small meeting at UCSD called "Beyond the PDF" – an eclectic group of people seeking to create new forms of scholarly communication, going beyond the published paper to include all forms of scholarly work, and making room for data, visualizations, software, and other contributions that the current scholarly ecosystem currently finds difficult to support.  Force11 is the name of the organization.  You can find them here:  http://force11.org.  OpenVIVO debuted at Force16, demonstrating a contribution ontology by which people could indicate their non-author roles in scholarly works. It was very well-received.  You can find the poster on Figshare and in OpenVIVO (imagine that).

OpenVIVO. A VIVO anyone can join.  Have you tried OpenVIVO?  It's easy.  Get an ORCiD at http://orcid.org and sign on to OpenVIVO at http://openvivo.org OpenVIVO received many positive comments and tweets at its debut at Force16.  Force16 used OpenVIVO to represent its scholarship – attendees registered with their ORCiD and provided their work to Figshare, tagging the work "force16."  Using the public Figshare API, the OpenVIVO Task Force developed software to identify tagged works in Figshare, gather their metadata, and create RDF for VIVO.  The RDF was then loaded to VIVO.  You can find the Figshare ingest software on GitHub:  https://github.com/openvivo/figshare-rdf  The result is an event page in OpenVIVO that contains a roster of attendees and a roster of works, creating a record of the conference.  See http://openvivo.org/display/eventFORCE2016.  The VIVO Conference (August 17-19, Denver) plans to use the same approach.

VIVO User Group Meeting, May 5-6, Chicago.  It's 10 days or so until the first VIVO User Group meeting in Chicago.  Still time to register and attend.  http://vivousergroup.eventbrite.com  The meeting will provide an important opportunity to discuss directions for the future of VIVO.  Many ideas for VIVO have been generated through the roadmap process, the "I wish I could use VIVO to ..." survey, steering and leadership calls, and community participation on VIVO email lists.  You can find a synthesis of ideas, open for comment here.  The ideas are not presented in any order.

Open Repositories.  Graham Triggs and I will be in Dublin for Open Repositories, June 13-16.  We hope to see you there!

Go VIVO!

Mike

Mike Conlon VIVO Project Director

VIVO Updates for April 18 -- OpenVIVO, Implementation

Did we launch OpenVIVO?  Yes, we did.  See http://openvivo.org  Have an ORCID?  Sign on.  Don't have an ORCID?  Get an ORCID at http://orcid.org and sign on.  It's that easy. If you follow VIVO on Twitter (@vivocollab) you'll see good people saying nice things about OpenVIVO.  It would be great if you did that too!

Dozens of people at Force16 have signed on.  All the Force16 presentations are being posted in Figshare and are available in OpenVIVO here: http://openvivo.org/display/eventFORCE2016.  As of this writing, OpenVIVO has data for 210 people,  560 academic works, and 769 attributions associated with academic works. All the data is published hourly to http://openvivo.org

You may want to promote OpenVIVO.  Here's a flyer that describes it's features.  Feel free to print and share the flyer, or use text from the flyer in your own materials.

OpenVIVO is a VIVO everyone can join.  It is the joint work of the OpenVIVO Task Force, the Force11 Attribution work group and OpenRIF.  What a great job these people did to design and build OpenVIVO.

We hope you try OpenVIVO and share your thoughts about it on one of the VIVO Google Groups. 

Implementation Call. Implementing VIVO?  Join us this Thursday at 1 PM, we will have a Implementation Interest Group call.  It's a friendly group.  New to VIVO, this is a great place to introduce yourself and your project and share your thoughts and questions about implementing VIVO.

Need help with your VIVO implementation? VIVO works with companies that can help you:

"Symplectic is a world-leading software development and service company specialized in the delivery of integrated research information management systems."

"Gunter Media Group Inc. (GMG) is a strategic management-consulting firm that helps libraries, publishers and companies to not only solve their key operational, technical and human assets but address new business opportunities."

You can find contact information on the VIVO web site here: http://vivoweb.org/community/service-providers

Do you represent a company that works with VIVO and could provide services to sites looking to implement VIVO?  Please contact us to become a registered service provider for VIVO.

You can help VIVO.

  1. Plan to attend the User Group Meeting.  The VIVO User Group Meeting will be held in Chicago, May 5-6.  You can register at http://vivousergroup.eventbrite.com
  2. Help build financial support for VIVO.  Join the Membership Task Force.  Contact Jonathan Markow
  3. Help us identify needs for VIVO.  I wish I could use VIVO to ...  Complete the sentence here:  http://goo.gl/forms/u7mqR0OrCv. Click the link.  Will take two minutes or less.  We will use the results to help plan future features.

Sea Change: Challenges and Opportunities in the Publishing Ecosystem.  On April 21, I'll be in Washington DC, presenting on collaboration in science and the role of the scholarly data ecosystem and systems like VIVO to improve collaboration and science.  Perhaps I'll see you there! http://allenpress.com/events/seminar

Go VIVO!

Mike

Mike Conlon VIVO Project Director