...
Page properties | ||||||
---|---|---|---|---|---|---|
| ||||||
|
Agenda & Notes
- Ontology release tooling (SHACL validation, Github Actions, automated release notes etc.) - Philip Strömert
- see also:
- What would need to be done, if VIVO were to be migrated to ODK?
- install requirements (ODK Docker container and Make)
- seed a new naked repo → https://docs.google.com/presentation/d/1TnLzIg_Y40I6hqbemmFOMHjwOmIOfuz2usKYZDxbgPY/
- 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
- copy native VIVO terms into vivo-edit.owl, imported terms will be there via the import modules
- maybe think about, if you need/want a ROBOT tsv template pipeline as used in VIBSO
- activate documentation build pipeline and edit docs to entail what you need for your contributors
- make a release using the automated release build pipeline of ODK
- 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
- Q by Egon Willighagen on Mastodon: https://mastodon.social/@egonw@social.edu.nl/111937329072554484 - Christian Hauschke
- Who is using CiTO in VIVO, in production?
- Could the data be parsed/queried/scraped for export to Wikidata?
Ideas for future meetings
...