1. A description of the scope of VIVO and its ontologies in content & quality.  In order to ensure that the scope is well-defined, it might help to collect local ontology extensions from individual implementations and see if there is a common need that VIVO doesn't address.  Completed.  See
  2. Develop a process for reporting ontology needs.  Currently there are several places this might be done.  We should have a place that is sufficient for the work and can be shared broadly.  In progress.  See
  3. Make two ontology changes (one relatively easy, and one that would require a change in the software) and then deliver a technical plan and a communication plan to support these changes.  To do.


  1. Plans for meeting at the conference
  2. Update on action items.  See below.
  3. Creating a base ontology file.  See
  4. Dave Eichmann's data on ontology usage across sites.  See vivo_ csv files in the task force Google Drive folder here:


Notes will be available here:

Action items

  1. Create a viable VIVO-ISF master containing VIVO ontologies (in progress)

    1. See summary of ontology sources here:

  2. Create a group of committers and reviewers (in  progress)

  3. Create a folder of exported VIVO ontology files.  Mike Conlon Done.  See

  4. Triage and move issues from community repository to the master repository. Done

    1. Issues moved from community to vivo-isf-ontology.  Tagged VIVO as appropriate.

    2. Additional issues opened in community

    3. Issues from VIVO JIRA added to community of vivo-isf-ontology as appropriate

    4. VIVO JIRA ontology issues opened to stay in synch (2 pending close were not added)

    5. 18 issues in community,  37 vivo issues in vivo-isf, 45 ontology issues in VIVO JIRA
  5. Javed to present his ontology for tracking ontology changes at a future meeting

  6. Explore track changes in Web protege

  7. Explore Robot tool (actively supported) for VIVO extraction -- clone their repo and run their tests (in progress)

  8. Define roles and responsibilities of participants -- analyst, editor, committer, tester.

  9. Create workflows and documentation (“instruction manuals”) for each of those roles