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

Two Ontology Files Being Updated Inconsistently after Merge #798

Open
giraygi opened this issue Dec 4, 2023 · 0 comments
Open

Two Ontology Files Being Updated Inconsistently after Merge #798

giraygi opened this issue Dec 4, 2023 · 0 comments
Labels
Status: Needs Triage Should be the default status for issues that have been acknowledged, but not yet processed. Type: Bug Indicates that WebProtege is not working as expected

Comments

@giraygi
Copy link

giraygi commented Dec 4, 2023

Describe the bug
There started to appear two ontology files in download after a merge operation in our instance (https://service.tib.eu/wp4tib/). The second file does not have a name and its name is OntologyID(Anonymous-1234).owl. After that point, some changes in our project started to be reflected to both of the files while some changes only being reflected to the anonymous file. Plus, some annotations started to reappear or appear multiple times after removing them. And some annotations started not to appear in the downloaded version.

To Reproduce
Merging a big ontology file into an existing one in a project in WebProtege V5.0 may create the bug. We tried in multiple projects and we could not reproduce it every time.

Expected behavior
We expect only a single download file that is associated to our Ontology in Development. Plus, we expect all our changes in Editing Mode to be reflected to the download file consistently.

Desktop (please complete the following information):

  • OS: Linux/Windows
  • Browser: Chrome
  • Version 5.0
@giraygi giraygi added Status: Needs Triage Should be the default status for issues that have been acknowledged, but not yet processed. Type: Bug Indicates that WebProtege is not working as expected labels Dec 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Needs Triage Should be the default status for issues that have been acknowledged, but not yet processed. Type: Bug Indicates that WebProtege is not working as expected
Projects
None yet
Development

No branches or pull requests

1 participant