andrecastro0o
commented
3 years ago Hello @RichSimon. Thank your for interest.
You no longer need to use the non-aeon branch. You can use the master branch now. Non-aeon branch has been merged to master in https://github.com/TIBHannover/ontology2smw/commit/c8b54803e26b47ec5c3d1ee4c3587122571f96a7
Now about your question: you want the changes you make on the developing ontology, to also change the wiki property and category definitions, right? I do not see an issue there. If you update a few terms in the ontology, and run the ontology2smw with the updated ontology, only the terms which have changed will be edited. The terms that remain the same, will not be changed, in other words the MW api wont perform the edit.
The only possible issue I see is with ontology terms which get deleted from previous to the current version. ontology2smw does not perform deletion, as it knows nothing about the previous version of the ontology. You must do the deletion yourself. However you can look at the history diff of the MediaWiki:Smw_import_yourontology page to see what terms were removed, between the latest edit, and previous ones.
Hope it helps. But let me know if I am misreading your question.
Great work on this. We've got the no-AEON branch working to import an ontology from Protege into Mediawiki and we're starting to think about how to manage updates as they happen.
Unless there's a better idea, we're thinking about assigning a unique set of [[Category:]] or [[Property::]] to a taxonomy import event (say name, version, title) so we can address the ones that need to be updated. It might be as simple, to start, as mass deleting the old ones before refreshing the new ones.
Is there a better way we're missing to do this? #enhancement