Old Release

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


VIVO provides the ability to use external vocabularies to represent the research areas of scholars, and the concepts pertaining to scholarly works.  External vocabularies that provide RDF can be used with VIVO.  Using an external service, a curator, or page owner may query the external vocabulary for terms, and select terms representing the work or scholar.  The terms are fetched from the external service and added to the VIVO triple store.  Links from the work or person and added to connect the person or work to the selected term or terms.

See below

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.

http://link.informatics.stonybrook.edu/umls/CUI/C0036612  rdfs:labelsemantic
http://www.eionet.europa.eu/gemet/concept/3645  rdfs:labelgeographic information system
http://link.informatics.stonybrook.edu/umls/CUI/C0872261  rdfs:labelrepositor

Adding a new external vocabulary service to VIVO

External vocabulary services are defined in the graph http://vitro.mannlib.cornell.edu/filegraph/abox/vocabularySource.n3.  You can explore the contents of this graph by navigating to System Admin / Ingest tools / Manage Jena models.  Find vocabularySource.n3 in the list of models.  Click Output Model.  You will get a file containing the assertions made to define external vocabulary services in your VIVO.

  • No labels