PMA.core 3.0.1

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:

• One root-directory “projects” pointing to d:\projects
• Two other root-directories “project_foo_004” (project 4 for customer foo) and “project_bar_045” (project 45 for customer bar) that offer you quick access to the files in d:\projects\foo\p0004 and d:\projects\bar\p0045.

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:

• Move files to other locations using the image manager
• Capture on-slide annotations
• Capture form-data

Nested root-directories are fine to use, as long as you only use PMA.core to host and view WSI content.