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.
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 available here.
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
- Organizations
- 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
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 emplyment records, grant records, teaching records, mentoring and other activities.
Leadership Follow-up Text of story 3
Story 4 Text of story 4
Call this Thursday Text of story 5
Go VIVO!
Mike
Mike Conlon
VIVO Project Director
Duraspace
