VIVO Documentation
Old Release
This documentation relates to an old version of VIVO, version 1.9.x. Looking for another version? See all documentation.
Incomplete
This page is being written. Please contact Mike Conlon if you have suggestions for this page.
Overview
VIVO can be used to mange the hierarchical structure, or organizational chart, of any organization. We describe how VIVO represents organizational structure, and how to create data that can be loaded into VIVO to represent the structure of an organization. The Sample Data has a sample university, with sample colleges and departments, illustrating the techniques described here.
"hasPart, partOf"
VIVO uses the Basic Formal Ontology "hasPart" to indicate that organization A "hasPart" organization B. Sample University has a College of Science. We say College of Science "partOf" Sample University. VIVO will automatically assert Sample University "hasPart" College of Science.
The Basic Formal Ontology has been implemented as part of the Open Biomedical Ontologies (OBO). They have coded "hasPart" as "BFO_0000051" and "partOf" is "BFO_0000050" VIVO uses the OBO representation which can be found here: http://purl.obolibrary.org/obo/
Your Organizational Data
To manage organizations in VIVO, you will need to create data representing your organizations and your organizational structure. This is easy to do using a spreadsheet. Simply create one row for each organization in your institution. For example, the table below shows two colleges as part of Sample University, and each college has one or more departments. The Department of Chemistry has a division – Organic Chemistry.
Your URI will contain your domain name. In this example we have structured the URI. VIVO URI always start with the domain, followed by "/individual/" followed by a URI of your choice. Here we have used a tag "org" to indicate URIs for organizations. This will make the URI easier to find. We then use the name of the organization, with each word capitalized. URI must be unique. If two organizations within your institution have the same name, you will need to make unique URI for each – you might add a "1" to the end of one of the URI, for example.
Add as many rows as it takes to represent the organizations within your institution. You can start with some, load them to VIVO (see below), and create more rows and reload, eventually building up a complete set of organizations.
OrgURI | Name | Type | PartOfURI |
---|---|---|---|
http://vivo.mydomain.edu/individual/orgSampleUniversity | Sample University | university | |
http://vivo.mydomain.edu/individual/orgCollegeOfScience | College of Science | college | http://vivo.mydomain.edu/individual/orgSampleUniversity |
http://vivo.mydomain.edu/individual/orgPhysics | Physics | department | http://vivo.mydomain.edu/individual/orgCollegeOfScience |
http://vivo.mydomain.edu/individual/orgChemistry | Chemistry | department | http://vivo.mydomain.edu/individual/orgCollegeOfScience |
http://vivo.mydomain.edu/individual/orgOrganicChemistry | Organic Chemistry | division | http://vivo.mydomain.edu/individual/orgChemistry |
http://vivo.mydomain.edu/individual/orgCollegeOfTheArts | College of the Arts | college | http://vivo.mydomain.edu/individual/orgSampleUniversity |
http://vivo.mydomain.edu/individual/orgTheaterAndDance | Theater and Dance | department | http://vivo.mydomain.edu/individual/orgCollegeOfTheArt |
Making Triples
To load data into VIVO, you will make triples out of your organizational data. You can use Karma, SAS, python, XSLT, or your own scripts, or a text editor.
To load your organizational data into VIVO, you will transform your spreadsheet into triples. Each row of the spreadsheet will result in three triples: 1) a triple that asserts that the OrgURI is an organization of a particular type; 2) a triple that asserts that the organization has a particular name; and 3) a triple that asserts that the organization is part of another organization.