Date

31 Jul 2017

Webex link is here.

Attendees

• Christian Hauschke

• Dong Joon (DJ) Lee
• Muhammad Javed
• Juliane Schneider
• Marijane White
• Brian Lowe
• Mike Conlon
• Damaris Murry
• Anna Kasprzik

Deliverables

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.
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.
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.

Agenda

1. Plans for meeting at the conference
2. Update on action items
3. Process for making changes – see Ontology Change Process (draft) https://goo.gl/3ZMSwC

Notes

Notes available here: https://goo.gl/N7eN6f

Action items

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

   1. See summary of ontology sources here:  https://goo.gl/Wztgon

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

3. Create a folder of exported VIVO ontology files.  Mike Conlon Done.  See https://goo.gl/kUjT1Q

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