Skip to content

[VIVO 1652] - Add vivo:AdministrativeUnit as a subclass of foaf:Organization

backups requested to merge vivo-1652 into main

Created by: mconlon17

VIVO-1652

What does this pull request do?

Adds a new class to the VIVO ontology -- AdministrativeUnit. Administrative Unit is a part of an organization not otherwise identifiable as a department or school, college, etc.

Example: The UF Health Science Center is an administrative unit (not a center)

AdministrativeUnit is not:

  • a department. We plan to add AdministrativeDepartment in the future. AdministrativeDepartment is the counter part to AcademicDepartment and should clarify organizational representation in VIVO.
  • an administrative unit of a country. Wikipedia uses the term local administrative department to represent administrative divisions in countries not otherwise classified as states, counties, municipalities. Administrative Unit is analogous for organizations. VIVO will likely add LocalAdministrativeUnit as a term for countries in the future.

What's new?

  • Changes to vivo.owl to define AdministrativeUnit in the VIVO ontology.
  • Changes to vitroAnnotations.n3 to support use of AdministrativeUnit in the VIVO application.

How should this be tested?

  1. Build
  2. Empty database (to force reread of vitroAnnotations.n3)
  3. Start Tomcat
  4. Use SysAdmin menu to add a new Administrative Unit (available under the Organizations heading)
  5. Confirm new Administrative Unit in the Index under Organizations

Additional Notes:

  • The ontology file with its annotations serves as documentation. The file can be opened in ontology tools and visualizers to see structure.
  • When a new version of VIVO is released, the version of the ontology corresponding to the ontology is placed at http://vivoweb.org/ontology/core

Interested parties

@VIVO-project/vivo-committers @vivo-project/contributors @vivo-project/vivo-developers @mjaved495 @marijane @brianjlowe @tawahle

Merge request reports