-
Notifications
You must be signed in to change notification settings - Fork 2
editing properties
-
The Property tabs (all the non-NCI Edit Tab) don't save changes in the same manner as the NCI Edit Tab. There is no Save button so for the changes to take, an Update/Commit needs to be done from the Server menu.
-
Related to the above, there is a requirement that a commit message be entered and this should be taken out as it's unnecessary for vocabulary development. Or perhaps make this configurable to allow different types of user communities to set it as they desire.
-
There is currently an interaction between these tabs and the NCI tab. When e.g. properties are edited and committed, switching to the NCI tab results in a previously highlighted class flagged as "(editing)", which prevents the user from doing much until a Save or Clear. In some linux environments there is a rendering issue where these buttons are not displayed. The workaround for now is that the admin user needs to exit & restart Protege after doing property edits.
-
Switching to these tabs, not normally utilized, when editing properties often results in an increased memory usage by Protege. Thus when editing properties, a secondary reason for exiting and restarting Protege is to "reset" the memory usage for the class editing session that follows.