| Info | ||
|---|---|---|
| ||
This task force is forming. To join, just edit this page and add your nameending. See Ontology Interest Group for more info on VIVO ontology work. To edit this page, get a Duraspace username and password. To get a Duraspace username and password, contact Graham Triggs |
...
Context
Provide a brief description of why the Task Force is being proposed. Include sufficient background information to allow the reader to understand how the work fits into the current context of the current activities of the VIVO project. Only 2-3 bullet points or sentences are necessary.
Objectives
Provide a bulleted list of the Task Force objectives.
Deliverables
Provide a bulleted list of deliverables.
Suggested schedule
...
Develop charter
...
1.5 weeks
...
2015-XX-XX
...
Solicit members and schedule first meeting
...
1 week
...
2015-XX-XX
...
Develop action items, assign to team members
...
2 weeks
...
2015-XX-XX
...
Accomplish deliverables, preliminary review
...
3 weeks
...
2015-XX-XX
...
Revise deliverables, final review
...
2 weeks
...
2015-XX-XX
Following the convergence of the eagle-i and VIVO ontologies into a combined VIVO-ISF ontology in 2013, a manual extraction from VIVO-ISF to produce the “VIVO Core” ontology has been used for VIVO 1.6 through 1.10.0. Changing the VIVO Core ontology between VIVO 1.5 to VIVO 1.6 had significant impact on the VIVO community. Some sites never upgraded. As a result, no ontology changes have been made since 2013. In 2015, OpenRIF, an open source organization, was created to maintain and develop the VIVO-ISF. Several commits have been made to the OpenRIF repository, but none involving the VIVO Core.
What is the purpose of any ontology improvement? What kinds of improvements are there? Why would any improvements be needed? What impacts would ontology changes have on the community? How can we know the impact of any particular ontology change?
If we were great at ontology improvement, what form would that greatness take? What would be included? Can you picture a world in which we were great at ontological improvement? What would that world look like?
How would we get from where we are now to what we want? What would we do first?
Deliverables
- 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.
Suggested schedule
We plan to meet every other week. We will determine deliverables and a timeline for producing the deliverables.
Members
Mike Conlon, Marijane White, Brian Lowe, Christian Hauschke, Matt Mayernik, Tatiana Walther, Tenille Johnson, Juliane Schneider, Muhammad Javed, Benjamin Gross, Dong Joon (DJ) Lee, Damaris Murry, Linda Rowan, Huda Khan, Violeta Ilik, Anna Kasprzik, Ralph O'Flinn.
Meeting Times and Webex link
Every other Tuesday at 10 AM US Eastern Time. Zoom link is here. See Meeting Times Around the World for conversion to your local time.
Task Force Resources
Children Display
Task Force Work Products
Members
Name and Affiliation - task force lead
Name and Affiliation - facilitator
Name and Affiliation - member
Name and Affiliation - member
others to be solicited from the VIVO Community
Meeting Times
TBD
Communication Channels
Distribute proposed charter and solicit participation from community via appropriate mailing list
Announce task force creation and progress on relevant Working Group calls.
Create a page in the VIVO wiki (wiki.duraspace.org), with child pages for agenda, notes, and additional information
Agendas and Notes
Solicit agenda items from task force members 3 days before meeting
Prepare agenda and distribute no less than 24 hours before meeting
...