...

• Ontology release tooling (SHACL validation, Github Actions, automated release notes etc.) - Philip Strömert 
  
  • see also:
    • https://nfdi4chem.github.io/VibrationalSpectroscopyOntology/odk-workflows/
    • https://oboacademy.github.io/obook/reference/odk/
  • What would need to be done, if VIVO were to be migrated to ODK?
    1. install requirements (ODK Docker container and Make)
    2. seed a new naked repo → https://docs.google.com/presentation/d/1TnLzIg_Y40I6hqbemmFOMHjwOmIOfuz2usKYZDxbgPY/
    3. build import modules for all existing VIVO ontology dependencies → probably the most time-hungry step as this might need some tweaking in the custom Makefile
    4. copy native VIVO terms into vivo-edit.owl, imported terms will be there via the import modules
       1. maybe think about, if you need/want a ROBOT tsv template pipeline as used in VIBSO
    5. activate documentation build pipeline and edit docs to entail what you need for your contributors
    6. make a release using the automated release build pipeline of ODK
    7. publish new release
  • about version history
    • this workflow depends on GitHub, so the better the PR and issue titles the easier it is to automatically let GH create a "what has changed" list from the merged PRs since the last tag, which will then be your release description
• ...

Ideas for future meetings

...