...
- 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.
- 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.
- 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
- Plans for meeting at the conference
- Update on action items
- Recap and updates
- Ontologies to watch, use, collaborate
- Update on state of VIVO-ISF, VIVO ontology elements
- Process for making changes – see Ontology Change Process (draft) https://goo.gl/3ZMSwC
- Plans for meeting at the conference
Notes
Notes will be available here: https://github.com/openrif/vivo-isf-ontology/wiki/
...
Create a viable VIVO-ISF master containing VIVO ontologies (in progress)
Create a group of committers and reviewers (in progress)
Create a folder of exported VIVO ontology files. Mike Conlon Done. See https://goo.gl/kUjT1Q
Triage and move issues from community repository to the master repository. Done
Issues moved from community to vivo-isf-ontology. Tagged VIVO as appropriate.
Additional issues opened in community
Issues from VIVO JIRA added to community of vivo-isf-ontology as appropriate
VIVO JIRA ontology issues opened to stay in synch (
2 pending close were not added)
- 18 issues in community, 37 vivo issues in vivo-isf, 45 ontology issues in VIVO Jira
Javed to present his ontology for tracking ontology changes at a future meeting
Explore track changes in Web protege
Explore Robot tool (actively supported) for VIVO extraction -- clone their repo and run their tests (in progress)