Resources
- Ontology Interest Group Google Folder https://drive.google.com/drive/u/0/folders/1RGBh4fDZdzpJdwyiUMO8OPWwkcmVYrI0
- VIVO Ontologies on Github: https://github/vivo-ontolgy
- OBO Slack https://join.slack.com/t/obo-communitygroup/shared_invite/zt-kpkvg7x3-kz7DeGoYKiY~VGWKO0voQg
Attendees
Please add yourself to the list of attendees.
Agenda & Notes
- VIVO Meetup at SWIB 2023 in Berlin
- Ontology improvement priorities, and release planning
- CERIF2VIVO
- Projects in the VIVO / Hercules Ontology
- What areas need work?
- The current ontology extension has to be cleaned up and transfered to the VIVO-DE name space
- A set of competence questions for the ontology need to be expressed to guide the development of the ontology in terms of model domain, axioms, constraints and reasoning
- The current ontology extension has to be cleaned up and transfered to the VIVO-DE name space
- What needs to be evaluated?
- the set of competence questions need to be evaluated for consistency against the prerequisites of the research domain
- the ontology needs to be evaluated in terms of how it fulfills the CQ
- the set of competence questions need to be evaluated for consistency against the prerequisites of the research domain
- What are the challenges in comparison to the current functional state of the VIVO code
- What do we need to find out to start the process?
- survey the research domain to get a detailed and accurate picture of the current state of the research domain, and to what future functionality within the field of linked data based open research could be
- a minimal functional test of the project ontology in the current snapshot version of VIVO to ascertain what will not work out of the box
- survey the research domain to get a detailed and accurate picture of the current state of the research domain, and to what future functionality within the field of linked data based open research could be
- Rolf already created a bua-namespaced ontology which reflects his work that can be built upon.
- Salm: different kinds of fundings, even no funding
- Christian: projects are a subclasss of BFO:0000015 (process), can have subclasses based on their configuration (like: has funding means it is a funded project / third party project comparable to Dr30 (Drittmittelprojekt) in KDSF)
- Differenty types of entities could be considered as projects: e.g. print costs, awards and prizes, events etc.
- What areas need work?
- KDSF
- Rolf will share his fork, create a merge request
- TIB will try to set up a demo VIVO implementation for this without focusing on forms etc.