options:repository:internal
| Both sides previous revisionPrevious revision | |||
| options:repository:internal [2025/01/21 22:07] – external edit 127.0.0.1 | options:repository:internal [2026/08/27 07:31] (current) – [Internal Options] Scott Cunliffe | ||
|---|---|---|---|
| Line 9: | Line 9: | ||
| * '' | * '' | ||
| + | The Internal repository option identifies a repository as being used internally by TapeTrack or for an administrative workflow. | ||
| + | |||
| + | When set to True: | ||
| + | * The repository may be hidden from applications or screens that only show normal operational repositories. | ||
| + | * It remains a valid repository in the TapeTrack database. | ||
| + | * Tapes can still be moved into and out of it where the application or process supports it. | ||
| + | * It does not automatically change movement, confirmation, | ||
| + | |||
| + | Typical uses include temporary holding locations, processing queues or system-managed repositories that ordinary TapeTrack Lite or Checkpoint users should not select. | ||
| + | |||
| + | ^Setting ^Effect^ | ||
| + | |False |Normal operational repository displayed by applications| | ||
| + | |True |Internal-purpose repository that may be omitted from some applications| | ||
| + | |||
| + | For example, a temporary processing repository such as TEMP could be marked Internal so administrators can use it in TapeMaster without presenting it as a normal tape location in every client application. | ||
| + | |||
| + | The precise documented behaviour is that an internal repository “should not be displayed in all applications”; | ||
| {{tag> | {{tag> | ||
options/repository/internal.txt · Last modified: 2026/08/27 07:31 by Scott Cunliffe
