Differences

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

--- desktop:desktop_purpose:lite [2024/07/08 04:17] – [Scan In] Scott Cunliffe
+++ desktop:desktop_purpose:lite [2025/01/21 22:07] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
-====== Lite ======
+====== Using Lite To Scan In And Out  ======
 Using the following Repositories, or locations, as an example of Volume movement.
 Volumes are placed in the Library to be written to.
-When full, the Volume is placed in a move to either the onsite or offsite storage.
+When full, the Volume is placed in a move to either the onsite or offsite storage.  For this example we will move the Volume to the offsite vault.
 When the Volumes expire, they are moved to the scratch rack to await re-use in the Library.
-{{repository_setup.png}}
+{{datacenter.png}}
 Following the life cycle of Volume LTO123L4 from the Library.
@@ Line 37: / Line 37: @@
       * Software interface used
       * Repository details
-    * Confirmation of the correct Volume/s being sent out as incorrect Volumes will flag as an error, as well as a notification of any Volumes not [[lite:function_scanning_out|scanned out ]].
+    * Confirmation of the correct Volume/s being sent out as incorrect Volumes will flag as an error, as well as a notification of any Volumes not [[lite:function_scanning_out|scanned out]].
+See [[lite:function_scanning_out|Lite Scan Out]] for more detailed information on the Scan out function.
 ===== Scan In =====
@@ Line 85: / Line 87: @@
 Software interface used
 Repository details
-Confirmation of the correct Volume/s being sent out as incorrect Volumes will flag as an error, as well as a notification of any Volumes not scanned out .
+Confirmation of the correct Volume/s being sent out as incorrect Volumes will flag as an error, as well as a notification of any Volumes not scanned out.
+See [[lite:function_scanning_out|Lite Scan Out]] for more detailed information on the Scan out function.
 ===== Scan In =====
@@ Line 91: / Line 96: @@
 Once the Volume arrives back at the data center, it is scanned in to confirm arrival and placed in the relevant spot in the scratch rack.
-{{scaninscratch.png}}
+{{scaninscratch1.png}}
 Scanning the Volume in has two main purposes:
@@ Line 101: / Line 106: @@
   * Confirmation of the correct Volume/s being received as incorrect Volumes will flag as an error, as well as a notification of any Volumes not scanned in.
+See [[lite:function_scanning_in|Lite Scan In]] for more detailed information on the Scan in function.
 ====== Scratch Rack To Library ======
@@ Line 126: / Line 132: @@
       * Repository details
     * Confirmation of the correct Volume/s being sent out as incorrect Volumes will flag as an error, as well as a notification of any Volumes not [[lite:function_scanning_out|scanned out ]].
+    *
+See [[lite:function_scanning_out|Lite Scan Out]] for more detailed information on the Scan out function.
 ===== Scan In =====
@@ Line 145: / Line 153: @@
 Once the Volume is confirmed at the Library, it is updated in TapeTrack from a moving status to currently being at the Library.  The **U** flag is removed
+See [[lite:function_scanning_in|Lite Scan In]] for more detailed information on the Scan in function.
+===== See Also =====
+  * [[desktop:desktop_purpose:lite_move|How to put Volumes into a Move using Lite]]
+  * [[lite:function_scanning_in|Scan-In]]: Receiving Volumes in to your location.
+  * [[lite:function_scanning_Out|Scan-Out]]: Recording Volumes being shipped out from your location.
+  * [[lite:function_send|Send]]: Placing Volumes into a move out of your location.
+  * [[lite:function_recall|Recall]]: Requesting offsite Volumes to be returned from an offsite location.
+{{tag> lite scan_in scan_out }}