Hi Karl,
Sorry to take so long to get back to you.
First, I just want to make sure I understand where you are in the setup process. It sounds like you are installing in multi-user mode and have got as far as running the Protege server but when you try to connect to the server and open a project, that's where you're not seeing the Essential Project. Am I right?
I've done some testing and I think the problems lies with the setup of the metaproject. I suspect that the path to the essential project file is not correct.
- Open the metaproject as described in the multi user install guide in section 8.
- Open the Policy Controlled Object class and then select Project
- Select Essential AM Repository (or whatever name you have given the project)
- In the Location field, make sure that this shows the FULL path to where you have saved the essential_project_baseline_v1.1.pprj. Note that in the install guide, the screenshot is an example where this project is located in a folder off the root of the filesystem, called '/EssentialAM Repository/essential_project_baseline_v1.1.pprj'. If this path is not correct, then the project will not show up in the list of available projects on the server. On Windows, this will be something like 'C:/EssentialAM Repository/essential_project_baseline_v1.1.pprj' and it is really important to note the Unix-style directory slashes, even on Windows, as this is a Java system. If you use the '\' Windows slashes, then the file will not be found (this could be the problem)
We can actually ignore the Annotations file for now. The annotations are used to manage the change history but we can switch this on once we've got the server working properly. So, skip that part for now.
I realise that the multi-user install guide needs to be updated to reflect more accurately how this is done in the latest version of Protege. I will sort this out as soon as I can and update the screenshots.
To answer your question about the Annotations, these are created automatically by Protege when you turn on the Collaboration panel. This is done from the Collaboration menu and selecting "Show Collaboration Panel". Protege will then ask how you wish to store the change history (the annotations repository). This has been significantly improved with the latest version of Protege - allowing us to use a database to store the annotations - but is now a little more complex than our documentation. Again, we'll update the documentation to reflect our recommended approach. For now, let's skip the annotations.
Let me know how you get on with this.
Just to explain some background to the current installation process, we don't currently ship things like the metaproject or the annotations so as not to confuse or break existing Protege installations that some users have. However, we realise that this could be made easier and we're working on improving the installation process, which would include automating more of this setup.
Hope this helps - do let me know
Jonathan