...
Projects in the VIVO / Hercules Ontology?...
- Ontology improvement priorities, and release planning
- Issues: https://docs.google.com/document/d/10Y5j8K_LKa-lAU-Z_p4q1ZnpuuKXEqqTTUb9F-4cFBE/edit#heading=h.zhzo0gde3z5i
- Update:
- Release Management
- we have an org for ontologies
- we have a repo for the VIVO ontology
- next step would be to set up the ontology repo to publish a jar object of an VIVO ontology release that can be included in the VIVO build process
- part of the process is set up sonotype?
CERIF2VIVOKDSFUpdate:
- Application-specific ontologies
- Vitro search - where to put the ontology?
- Options:
- https://github.com/vivo-ontologies
- Should me mix software-oriented ontologies with domain-oriented ontologies in https://github.com/vivo-ontologies?
- not preferred situation, reusability does not seem high
- https://github.com/vivo-community/
- only for additions, not things that VIVO relies upon
- https://github.com/vivo-project/
- should contain essential pieces for VIVO.
- if it stored outside vivo-project it would have consequences for the build process, it should be copied into vivo-project.
- Vitro search ontology and ABAC ontology and any application oriented ontology will be put into the VIVO code-base for now. This decision will be re-assessed later. At the moment it's built for the needs for the VIVO project