Old Release

This documentation relates to an old version of VIVO, version 1.9.x. Looking for another version? See all documentation.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Linking via concept services

Many people have requested support for associating terms from established controlled vocabularies with people, publications, grants, organizations, and other types of data in VIVO. While small taxonomies or vocabularies may most easily be imported in their entirety into VIVO, a number of the more popular controlled vocabularies are very large in proportion to the number of terms likely to be referenced within a single VIVO instance. Incorporating terms by reference helps keep terms in sync as these vocabularies continue to evolve and is more consistent with linked data principles.

Stony Brook University's Department of Medical Bioinformatics, led by Dr. Moisés Eisenberg, hosts an RDF version of the National Library of Medicine's Unified Medical Language System or UMLS (http://www.nlm.nih.gov/research/umls/). Through a 2011 VIVO mini-grant, Stony Brook has developed a web service that accepts incoming term requests from VIVO and returns one or more matching UMLS concepts with stable URIs. VIVO displays the label associated with the UMLS concept but the concept's URI ensures that references remain unambiguous, even across multiple VIVO instances at different institutions.

The interface from VIVO to the UMLS service has been implemented to allow linking to additional vocabulary services such as GEMET (http://www.eionet.europa.eu/gemet), and we will offer additional choices in upcoming releases.

VIVO RDF statements referencing external concepts

When external concepts are added to VIVO, they retain their original URI from the external vocabulary.  Since we have no way of knowing whether these URIs represent OWL classes or RDF instance data, VIVO does not assert a type for the concepts, which will therefore only be interpreted as being of type owl:Thing.

subjectpredicateobject
http://vivo.cornell.edu/individual/individual22972http://vivoweb.org/ontology/core#hasResearchAreahttp://link.informatics.stonybrook.edu/umls/CUI/C1518584
http://link.informatics.stonybrook.edu/umls/CUI/C1518584rdfs:labelontology
http://vivo.cornell.edu/individual/individual22972http://vivoweb.org/ontology/core#hasResearchAreahttp://link.informatics.stonybrook.edu/umls/CUI/C0036612
http://link.informatics.stonybrook.edu/umls/CUI/C0036612  rdfs:labelsemantic
http://vivo.cornell.edu/individual/individual22972http://vivoweb.org/ontology/core#hasResearchAreahttp://www.eionet.europa.eu/gemet/concept/3645
http://www.eionet.europa.eu/gemet/concept/3645  rdfs:labelgeographic information system
http://vivo.cornell.edu/individual/individual22972http://vivoweb.org/ontology/core#hasResearchAreahttp://link.informatics.stonybrook.edu/umls/CUI/C0599807
http://link.informatics.stonybrook.edu/umls/CUI/C0599807rdfs:labelinformatics
http://vivo.cornell.edu/individual/individual22972http://vivoweb.org/ontology/core#hasResearchAreahttp://link.informatics.stonybrook.edu/umls/CUI/C0872261
http://link.informatics.stonybrook.edu/umls/CUI/C0872261  rdfs:labelrepositor
  • No labels