Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gracefully handle situation when a class or property is removed from an ontology #376

Open
szeke opened this issue Mar 15, 2018 · 0 comments
Assignees
Labels

Comments

@szeke
Copy link
Member

szeke commented Mar 15, 2018

Currently this causes an exception and the model is left in a bad state.

One suggestion is that before executing a set semantic type or set link command, Karma checks whether the URIs for the properties are in the ontology. If they are not, then Karma should report an error to the user and skip executing the command. This can cascade an result on many commands being skipped, but that is OK.

In addition, it would be good if such bad commands got a marking in the command history (a red bug icon). Then the user can select them and delete them, or the user can add the missing classes and reload the model.

@szeke szeke added the bug label Mar 15, 2018
@rutujarane rutujarane added this to To do in Web-Karma Maintenance via automation Nov 30, 2020
@Bidisha010496 Bidisha010496 added feature and removed bug labels Nov 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

No branches or pull requests

3 participants