Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Bibliographic metadata on researcher publications remains a big challenge in part because journals and authors are not well identified or disambiguated in many current information systems or on CVs. While national-level systems such as PubMed are improving in that regard by assigning identifiers and including affiliation information on more authors,  

 

...

and large commercial vendors offer value-added disambiguation within the scope of their disciplinary coverage, it may be helpful to manage publication data in a purpose-built system designed to support disambiguation and author claiming (or disclaiming) of publications, such as Symplectic Elements.

As the ORCID movement continues to gain traction and more journal publishers request ORCIDs through their article submission interfaces and/or national-level funding agencies require or at least track researcher ORCIDs, this problem should diminish but will likely never go away, especially in the humanities where there are many smaller publishers and new types of publications.

VIVO beyond one institution

While some VIVO adopters have had a network model in mind from the start, such as the University of Colorado with its multiple geographically distributed campuses and many nearby federal labs, VIVO often starts out with a focus on the home institution.

The vivosearch.org site is intended to awaken more people to the potential of using VIVO data for discovery and networking across institutions, as originally envisioned by the 2009 National Institutes of Health request for applications. By harvesting data from several VIVOs and other software systems using the VIVO ontology into a common search index, users can discover expertise and activities across all the participating universities.  This is just a first step toward developing services targeted by region, by discipline, by consortium, or for the full research networking community.

For more information

...

on to part 5: VIVO as data