We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi, mapping disappear when I change ontology
Open an ontology using Protege and load the dependencies, Move to another ontology, Return to the previous ontology, There is mapping no more.
Expected behavior: I need to work in many ontologies at the same time, when I change I would like to see the appropriate mapping.
Actual behavior: If I change ontology, the mapping disappear.
Reproduces how often: Always
If I save after changing the ontology, the OBDA file is overwritten with an empty one.
http://g.recordit.co/GfO49sa1RF.gif
The text was updated successfully, but these errors were encountered:
Hi, we never worked with multiple ontologies in Protege before, and we will look into the issue your reported.
Btw, I like the way you report the bug via GIF. This communicates the problem immediately,.
Sorry, something went wrong.
I have suffered this issue too. My Ontology has some imports and when I switch to one of those I have lost my work.
Fixed with 478b0a6.
No branches or pull requests
Hi,
mapping disappear when I change ontology
Steps to Reproduce
Open an ontology using Protege and load the dependencies,
Move to another ontology,
Return to the previous ontology,
There is mapping no more.
Expected behavior:
I need to work in many ontologies at the same time, when I change I would like to see the appropriate mapping.
Actual behavior:
If I change ontology, the mapping disappear.
Reproduces how often:
Always
Attached material
If I save after changing the ontology, the OBDA file is overwritten with an empty one.
http://g.recordit.co/GfO49sa1RF.gif
The text was updated successfully, but these errors were encountered: