Differences

This shows you the differences between two versions of the page.

--- rootdir_config [2022/02/11 16:04] – [Defining your root-directory] yves
+++ rootdir_config [2023/11/21 14:08] (current) – chris
@@ Line 12: / Line 12: @@
 {{ :rootdir_add_00.png?direct&400 |}}
+Next, you fill out the general characteristics for the root-directory. Don't worry about filling out details like C:\slides references yet. We'll take care of that later when we talk about mounting points.
+{{ ::rootdir_add_10.png?direct&400 |}}
+You must enter a unique name ("Alias") for the root directory.
+The following parameters are available for further tweaking:
+^ Parameter                ^ Meaning  ^
+| Alias | The unique name or alias for the root directory |
+| Description | An aribitrary string that can help administrator in the future remember what your root directory actually contains. The Description field of a root directory can also be used to hide additional information about a group of data that you don't want everybody to know about immediately. Do //not// use this field for sensitive information, as it can be seen by everyone with access to PMA.core. If you're an instructor working with students e.g., it's perfectly ok to enter reminders for yourself in this field like "these are all trick-questions"... |
+| Quota   | You can set a limit on the amount of data that you want to allow PMA.core to manage in a particular for. This can be useful when facilitating temporary workers, visiting staff, residents or other students that only will be at your department for a brief period of time. If you //don't// want to restrict the amount of data, you can leave the default value of 0 in place. |
+| Offline | When checked, the folder will not be available to downstream applications like PMA.studio. Maybe you're just creating a placeholder for a future department, or you're not done curating a new collection yet. Instructors can also use this option to prepare a list of exam slides and only expose them to students for a limited amount of time (we don't offer scheduling though; you're still going to have to flick the proverbial switch manually) |
+| Prevent rendering of labels/barcodes | This prevents any slide in this root directory to show any label or barcode image. This is done primarily for anonymization of the slide (see also the [[anonymization|section on anonymization]]) |
+Once you create your root directory, you will see a reminder that you still need to provide a mounting point.
+{{ ::rootdir_add_20.png?direct&400 |}}
+Clicking on the suggestion takes you to the Mounting Points tab, which is empty by default.
+{{ ::rootdir_add_30.png?direct&400 |}}
+Now it's time to tell PMA.core where the content //actually// lives that you want the root directory to refer to.
 ==== Adding mounting points ====
-=== A note about (mapped) network drives ===
+PMA.core [[storage_management|supports different types of storage]] (see also [[https://www.prweb.com/releases/pathomation_announces_support_for_cloud_storage_and_file_transfer_protocol_ftp_servers/prweb18296771.htm|our press release]]):
-In many organizations, it is commmon to map network paths to drive letter. It's easier to remember that all the images are stored on the shared I: drive, rather than in the \\server_emea_48F\content\shared\incoming_slide_data\. PMA.core needs the latter path however to be able to mount content, rather than the I: drive letter. You cannot use the I: drive letter as a reference when attaching a new mounting point to a root directory.
+^ storage type ^ information needed ^
+| local hard disk | a path reference like ''c:\my_slides'' or ''e:\department\pathology\staff\dr_seuss''. Note that you cannot map network drives (drive letters like Y: or Z: are usually network drives) as root directories this way. |
+| network drives | a UNC path reference like ''%%\\server\sharename\our_slides%%'' ([[accessing_data_on_a_network|more about networks]]). |
+| [[rootdir_s3|S3 storage]] | Access and secret key combination, a path to a bucket like /my_bucket. Sub-paths underneath this path are allowed, too. |
+| [[rootdir_azure|Azure storage]] | A connection string, container name. As of [[what_s_new_in_version_2.0.1|PMA.core 2.0.1]], you can also specify a path to traverse directly down a hierarchy within the container |
+| FTP server | FTP server URL, username and password, optionally an initial path |
-The reason for this is that your I: drive letter is a transient designation that only exists when you're logged in. In a server content (PMA.core is a server application running on [[https://www.iis.net|Microsoft IIS server]]), the software runs unattended (i.e. without a human being logged on to the machine). The drive letter therefore is not available (in unattended mode), but the network path is.
+For some of these storage types, you'll also see a field "Chunk size". This has to do with [[caching]] and can almost always be left to its default setting.
+In our [[rootdir_security|section on security]], [[rootdir_security#accessing_secured_content|we elaborate more]] on each storage type.
-Think of root directories then as PMA.core's own alternative to mapped network drive letters on your local computer.
 ==== Nested references ====
@@ Line 38: / Line 69: @@
 Nested root-directories are fine to use, as long as you only use PMA.core to host and view WSI content.
 ==== Control nesting ====