rootdir
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
rootdir [2022/02/11 15:48] yves |
rootdir [2022/09/21 17:36] (current) antreas |
||
|---|---|---|---|
| Line 34: | Line 34: | ||
| ==== Configuration ==== | ==== Configuration ==== | ||
| + | |||
| + | **Root directories management** | ||
| + | |||
| + | Root directories can be managed by selecting the "Root directories" option under the "Settings" section in the left menu. | ||
| + | |||
| + | {{ :roots.png?nolink&400 |}} | ||
| + | |||
| + | The list displays all the configured root directories and provides options to add new, edit and delete entries. | ||
| + | |||
| + | * The "Offline" column indicates whether or not a root directory is enabled. An offline root directory is not advertised by the system and its contents are not available to the end-users. | ||
| + | * The "Path exists" column indicates whether or not the system is able to mount a root directory's path and access it's contents. For example a root directory that points to a local file system folder, that has been deleted, will not have the "Path exists" column checked. | ||
| We have a [[rootdir_config|separate section]] in this wiki that takes you through the different steps that you can take to [[rootdir_config|configure root directories and mounting points]]. | We have a [[rootdir_config|separate section]] in this wiki that takes you through the different steps that you can take to [[rootdir_config|configure root directories and mounting points]]. | ||
| - | We also talk about the security precautions that you can take when configuring these. | + | Root-directories can be labeled public or private, which allow you to [[rootdir_security#public_vs_private|take security precautions when configuring these]]. |
| + | |||
| + | === Edit ==== | ||
| + | You can edit the following properties of a root directory | ||
| + | |||
| + | |||
| + | ^ 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 is actually about. 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 | | ||
| + | |||
| + | {{ ::prevent_rendering_of_labels.jpg?600 |}} | ||
| ==== Security ==== | ==== Security ==== | ||
| Line 52: | Line 76: | ||
| You can monitor logs for several kinds of acivity: | You can monitor logs for several kinds of acivity: | ||
| + | |||
| + | {{ :rootdir_logs.png?direct&400 |}} | ||
| === Audit trail === | === Audit trail === | ||
| Line 67: | Line 93: | ||
| {{ :rootdir_activity.png?direct&400 |}} | {{ :rootdir_activity.png?direct&400 |}} | ||
| - | === Elmah log === | + | ==== Integrity check ==== |
| + | When problems persist over time, a structured and proactive approach is warranted. | ||
| - | ==== Integrity check ==== | + | When you suspect certain slides in a particular root directory are corrupt, you can run an integrity check on a particular folder: |
| + | |||
| + | {{ :rootdir_integrity.png?direct&400 |}} | ||
| - | If you suspect certain slides in a particular root directory are corrupt, you can run an integrity check on a particular folder by going to | + | This attempts to read all slides in a folder and reports on the ones that fail. You should then [[format_troubleshoot|try to find out why such slides cannot be read]]. |
| + | For problems that only occur occasionally and don't appear to be persistent, [[diag_elmah|Elmah logs]] are available to assist in for ad-hoc troubleshooting. | ||
rootdir.1644583680.txt.gz · Last modified: 2022/02/11 15:48 by yves
