This is an old revision of the document!
Each root directory is given an alias by which it is referred. The alias must be unique, irrespective of its casing. This means that if you have a root directory with an alias “RoOt”, you cannot also have another root directory with a alias “rOoT”.
Apart from its alias, the root directory needs at least one mounting point.
All other configuration options described in this page are optional.
Two root-directories are nested if one is contained within another one. There are very good reasons to have this kind of setup: you can have a folder d:\projects\ with over 100 different subdirectories, but only two or three of those are actually of importance to you at any given time. Nevertheless you may still need to consult occasionally some of the other projects as well, so you really need the following setup:
It is clear that d:\projects\qcor\p0004
is a subdirectory of d:\projects
and as such qualifies as a nested directory.
Whether you want to actually allow this is up to you. In PMA.core, the files will be mapped to different locations and therefore will be accessible through different routes. Therefore, we recommend disabling nested root-directories if you plan to do any of the following:
Nested root-directories are fine to use, as long as you only use PMA.core to host and view WSI content.
The following operations should only be performed by experienced users. If you don't know where or how to find a file called App_Data\Data\PMACore.config
, you should stop reading and contact somebody more knowledgeable in this area.
Assuming that you know what you're doing; you can control whether nested root-directories are allowed by modifying the AllowNestedRootDirectories switch in PMACore.config
:
Appropriate error handling is provided. Say that you have the following situation:
cases
exists and points to c:\wsi\worklist\
c:\wsi\worklist\case04\
When trying to map c:\wsi\worklist\case04
to a separate root directory, an error message shows: