Issue with Protégé 3.5 individuals tab in server-client mode

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue with Protégé 3.5 individuals tab in server-client mode

oyvindg

Hi,


We are running a test of the Protégé Client-server application at the University of Bergen Library and  have met one issue we aren’t sure how to resolve:


During workflow and registering metadata in the individuals tab, the active slot changes to the “for individual” URL line. It seems to occur on “refresh” of the window (Sometimes when pressing enter in a literal slot). This makes registering hard, since the client feels unpredictable and the URL is often  overwritten by accident.


We are running the project with one ontology importing three different ontologies, where two are read only, and all are loaded as in-memory sets on server. The projects are saved as language rdf/xml. We save the ontology hourly to disk.


We tried unchecking allow knowledge-base changes (which greys out the “for individual” slot) but this introduced other issues with other slots being unwritable ( In particular Boolean values). We were also unable to delete instances.


Best regards,

Øyvind Gjesdal,

University of Bergen Library


_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user
Reply | Threaded
Open this post in threaded view
|

Re: Issue with Protégé 3.5 individuals tab in server-client mode

Tania Tudorache
Please see inline the comments.

On 03/03/2014 03:11 AM, Øyvind Gjesdal wrote:

Hi,


We are running a test of the Protégé Client-server application at the University of Bergen Library and  have met one issue we aren’t sure how to resolve:


During workflow and registering metadata in the individuals tab, the active slot changes to the “for individual” URL line. It seems to occur on “refresh” of the window (Sometimes when pressing enter in a literal slot). This makes registering hard, since the client feels unpredictable and the URL is often  overwritten by accident.


I am not sure what you are referring to. There is a feature in Protege 3 desktop that will automatically select the text in the URL of an individual (what you refer to as "For Individual"), if the URL contains a pattern having an underscore followed by a number, which occurs with the automatically generate names for the individuals. For example, if your individual is called "Book_2", whenever the individual is selected, the URL is also automatically selected (so that a user can easily change its name), and if you start typing, it will change the selected text of the URL. Probably, this is the behavior you see, and there is not much you can do to change this behavior. You can let your users know about it, so that they can avoid overwriting the URL.


We are running the project with one ontology importing three different ontologies, where two are read only, and all are loaded as in-memory sets on server. The projects are saved as language rdf/xml. We save the ontology hourly to disk.



If you will be running this project in production mode, I strongly suggest that you use the database backend.

We tried unchecking allow knowledge-base changes (which greys out the “for individual” slot) but this introduced other issues with other slots being unwritable ( In particular Boolean values). We were also unable to delete instances.



This is not a good idea. Please see my first comment.

Rather than using the Protege 3 client-server, which is not under active development anymore, I suggest using WebProtege, which has a much better collaboration infrastructure, it is much easier to install, and all the users' work is done in the browser. Your users will not have to install anything. You can also download your ontology at any time, and load it into Protege 4.x, if you would like to use features that are not yet available in the Web client.

Read more about WebProtege here:
http://protegewiki.stanford.edu/wiki/WebProtege

Try it out on our Stanford server:
http://webprotege.stanford.edu

Tania

Best regards,

Øyvind Gjesdal,

University of Bergen Library



_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user


_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user