The aim of the home project is to simplify the end-user experience and minimize their access to content that they should not access directly.
Published content in the form of markers, DivePlans, and DiveBooks from other projects on the DiveLine server are aliased into the home project. These files are normally stored in a client-files directory or in the diver directory. These end-user files point to the content of the cbases and models directories, but the users do not have direct access to the directories. This avoids confusion for the end users and provides protection to the data.
NOTE: Using aliases is not true security on the cbases and models directories because the users must have read access to these directories. Using aliases to the client-files or diver directories gives the users indirect access to the cBases or models that these end-user files reference. A curious user can find their way to see the directories in ProDiver, but it does take effort.
To set aliases in the home project:
Open the home project.
Click Tools > Project Settings.
The Project Settings tab opens.
Click Aliases, and create aliases to the published content folders from each project that you want users to interact with. Normally these are the client-files or diver directories in the projects. Name these aliases so that the end users understand what content to expect.
Save the tab.
The aliases are created and now appear as blue folders in the home project in Workbench Explorer as shown in the example here.
In ProDiver, the end users are pointed to their home directory, but if they choose to navigate to the home project root in the Open or Save dialog boxes, they only see the aliases and the Users folder as shown here.
- Ensure that users have access to the projects that are aliased. See Managing Project Access.
- Set appropriate access control rules to the aliased project directories directly in the originating project. Usually this is read access to the client-files or diver directories, and read access to directories that these files reference, such as the cbases and models directories. See About Access Control.
- Any development on the markers and DivePlans must occur in the project that they are actually located in. The home project is not used for development.
- Ad hoc reports and markers that are created by end users must be stored in real folders in the home project.