PMA.core 3.0.7

User Tools

Site Tools

Trace: • security • audit_trailing
image_manager

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
image_manager [2022/03/28 18:17] – yvesimage_manager [2023/11/21 14:22] (current) – chris
Line 1: Line 1:
 ===== Image management ===== ===== Image management =====
  
-The image manager is accessible from the "Images" option on the left menu. This section allows the user to browse through the available virtual slides, manage the [[caching|cache files]], view, move and rename each image and [[viewport|launch the built in slide viewer]].+The image manager is accessible from the "Images" option on the left menu. This section allows the user to browse through the available virtual slides, [[viewport|launch the built in slide viewer]], manage the [[caching|cache files]], view, move and rename each image.
  
 {{ :man.png?nolink&400 |}} {{ :man.png?nolink&400 |}}
Line 11: Line 11:
 {{::img_man_left.png?400|}} {{::img_man_left.png?400|}}
  
-In this view, only the root directories appear that the administrator has access to according to [[rootdir_security|ACL rules]]. [[rootdir_security#public_vs_private|Public root directories]] (by definition) are always included here.+In this view, only the root directories that the administrator has access to appear (according to [[rootdir_security|ACL rules]]). [[rootdir_security#public_vs_private|Public root directories]] (by definition) are always included here.
  
-It is possible for an administrator to manage mappings to 100s of root-directories and access points, without actually being able to navigate the content in these folders. When an administrator therefore wants to inspect certain content of a [[rootdir_security#public_vs_private|private root directory]], it may be necessary to temporarily change this directory's access properties.+It is possible for an administrator to manage mappings to 100s of root-directories and access points without actually being able to navigate the content in these folders. When an administrator wants to inspect the content of a [[rootdir_security#public_vs_private|private root directory]], it may be necessary to temporarily change this directory's access properties.
  
 Root directories that are NOT available for technical reasons, //are// shown in the folder hierarchy. The reason for this is: PMA.core is an administrative tool, and it must be possible for an administrator to emulate a non-accessible root directory to trigger a particular error that can then be further inspected via the [[elmah|Elmah log]]. Root directories that are NOT available for technical reasons, //are// shown in the folder hierarchy. The reason for this is: PMA.core is an administrative tool, and it must be possible for an administrator to emulate a non-accessible root directory to trigger a particular error that can then be further inspected via the [[elmah|Elmah log]].
Line 19: Line 19:
 {{::img_man_search.png?400|}} {{::img_man_search.png?400|}}
  
-A search bar let's you search for specific files or extensions across the entire spectrum of the PMA.core server (this feature is mainly useful during startup; search a multi-terabyte repository this way in real-time is not very practical, and we've developed [[https://www.pathomation.com/products|other products]] to facilitate this latter use case more efficiently).+A search bar lets you search for specific files or extensions across the entire spectrum of the PMA.core server (this feature is mainly useful during startup; searching a multi-terabyte repository this way in real-time is not very practical, and we've developed [[https://www.pathomation.com/products|other products]] to facilitate this latter use case more efficiently).
  
 There's a [[image_manager_left_menu|dropdown menu]] to provide convenient access to certain managerial tasks related to the image management view. There's a [[image_manager_left_menu|dropdown menu]] to provide convenient access to certain managerial tasks related to the image management view.
Line 29: Line 29:
 {{::img_man_mid.png?600|}} {{::img_man_mid.png?600|}}
  
-Similarly to the Tree view, there's a quick menu access menu to provide convenient access to certain managerial tasks related to the directory content view.+Similarly to the Tree view, there's a quick access menu to provide convenient access to certain managerial tasks related to the directory content view.
  
 [[image_manager_mid_menu|Several operations can be performed on a directory]]. [[image_manager_mid_menu|Several operations can be performed on a directory]].
Line 41: Line 41:
  
   * Dimensions: The width & height of the image in pixels   * Dimensions: The width & height of the image in pixels
-  * File format: Name of the format / vendor as well as the compression type used by the selected slide.+  * File format: Name of the format / vendor as well as the [[compression type]] used by the selected slide.
   * Tile size: The size of the tiles that PMA.core will server for this image.   * Tile size: The size of the tiles that PMA.core will server for this image.
   * Physical size: The total size of all the files that this slide comprises of.   * Physical size: The total size of all the files that this slide comprises of.
Line 57: Line 57:
   * Move image: Moves the image to another directory   * Move image: Moves the image to another directory
   * Rename image: Renames the image   * Rename image: Renames the image
-  * Heatmap: Displays a heatmap which highlights the areas of the image that have been consulted most so far+  * Heatmap: Displays a heatmap which highlights the most consulted areas of the image
   * Event log: Displays a list of events that involve the currently selected image   * Event log: Displays a list of events that involve the currently selected image
image_manager.1648484265.txt.gz · Last modified: by yves
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki