<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://rtfm.tapetrack.com/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://rtfm.tapetrack.com/feed.php">
        <title>TapeTrack Documentation - concepts</title>
        <description>Because there is more to tape management than you ever realized</description>
        <link>https://rtfm.tapetrack.com/</link>
        <image rdf:resource="https://rtfm.tapetrack.com/_media/logo.png" />
       <dc:date>2026-04-06T09:27:56+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://rtfm.tapetrack.com/concepts/barcode_rule?rev=1737497272&amp;do=diff"/>
                <rdf:li rdf:resource="https://rtfm.tapetrack.com/concepts/barcode?rev=1737497272&amp;do=diff"/>
                <rdf:li rdf:resource="https://rtfm.tapetrack.com/concepts/definition_file?rev=1737497272&amp;do=diff"/>
                <rdf:li rdf:resource="https://rtfm.tapetrack.com/concepts/extended_attribute?rev=1737497272&amp;do=diff"/>
                <rdf:li rdf:resource="https://rtfm.tapetrack.com/concepts/move_status?rev=1737497272&amp;do=diff"/>
                <rdf:li rdf:resource="https://rtfm.tapetrack.com/concepts/physical_slot?rev=1737497272&amp;do=diff"/>
                <rdf:li rdf:resource="https://rtfm.tapetrack.com/concepts/qualified_barcode?rev=1737497272&amp;do=diff"/>
                <rdf:li rdf:resource="https://rtfm.tapetrack.com/concepts/scan-file?rev=1737497272&amp;do=diff"/>
                <rdf:li rdf:resource="https://rtfm.tapetrack.com/concepts/scan-map?rev=1737497272&amp;do=diff"/>
                <rdf:li rdf:resource="https://rtfm.tapetrack.com/concepts/slot?rev=1737497272&amp;do=diff"/>
                <rdf:li rdf:resource="https://rtfm.tapetrack.com/concepts/target_repository?rev=1737497272&amp;do=diff"/>
                <rdf:li rdf:resource="https://rtfm.tapetrack.com/concepts/virtual_slot?rev=1737497272&amp;do=diff"/>
                <rdf:li rdf:resource="https://rtfm.tapetrack.com/concepts/zones_repositories?rev=1737497272&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://rtfm.tapetrack.com/_media/logo.png">
        <title>TapeTrack Documentation</title>
        <link>https://rtfm.tapetrack.com/</link>
        <url>https://rtfm.tapetrack.com/_media/logo.png</url>
    </image>
    <item rdf:about="https://rtfm.tapetrack.com/concepts/barcode_rule?rev=1737497272&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-01-21T22:07:52+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>barcode_rule</title>
        <link>https://rtfm.tapetrack.com/concepts/barcode_rule?rev=1737497272&amp;do=diff</link>
        <description>Barcode Rule

Barcode rules use a set of defined patterns to parse Scanned Barcodes, enabling TapeTrack to identify Volumes for processing.

Examples

Barcode Rule Generic ????.???.*

WIll parse a barcode, matching the pattern 4 characters, period, 3 characters, period and then any characters, into Customer-ID (first 4 characters), Media-ID (characters 6 to 8 inclusive) and Volume-ID (characters 10 onwards).</description>
    </item>
    <item rdf:about="https://rtfm.tapetrack.com/concepts/barcode?rev=1737497272&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-01-21T22:07:52+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>barcode</title>
        <link>https://rtfm.tapetrack.com/concepts/barcode?rev=1737497272&amp;do=diff</link>
        <description>Barcode

A Volume Barcode is a machine-readable code in the form of numbers and a pattern of parallel lines of varying widths.



Or in the case of a QR code format, a machine-readable code consisting of an array of black and white squares.



Volume Barcodes can be either</description>
    </item>
    <item rdf:about="https://rtfm.tapetrack.com/concepts/definition_file?rev=1737497272&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-01-21T22:07:52+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>definition_file</title>
        <link>https://rtfm.tapetrack.com/concepts/definition_file?rev=1737497272&amp;do=diff</link>
        <description>Definition File

A Definition file is used by TapeTrack to define the format of imported data from files.

Definition files use a .ttidef prefix

Command Line programs that use a definition file will look for a file named default.ttidef in the running directory if no file name is specified in the program call.</description>
    </item>
    <item rdf:about="https://rtfm.tapetrack.com/concepts/extended_attribute?rev=1737497272&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-01-21T22:07:52+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>extended_attribute</title>
        <link>https://rtfm.tapetrack.com/concepts/extended_attribute?rev=1737497272&amp;do=diff</link>
        <description>Extended Attributes

Extended Attributes are variables, excluding Volume-ID and description, that can be applied to specific volumes.  These Attributes can be in the format of dates, strings or Integers.



Extended Attributes can be added, enforced and searched through TapeMaster.</description>
    </item>
    <item rdf:about="https://rtfm.tapetrack.com/concepts/move_status?rev=1737497272&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-01-21T22:07:52+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>move_status</title>
        <link>https://rtfm.tapetrack.com/concepts/move_status?rev=1737497272&amp;do=diff</link>
        <description>Move Status

Volumes have three Attributes based on location, Current, Target and Confirmed, which are used to determine and describe its&#039; status.

If the Current location and Target location are different, the Volume is considered to be in a Move Status from the Current location to the Target Location and a Move</description>
    </item>
    <item rdf:about="https://rtfm.tapetrack.com/concepts/physical_slot?rev=1737497272&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-01-21T22:07:52+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>physical_slot</title>
        <link>https://rtfm.tapetrack.com/concepts/physical_slot?rev=1737497272&amp;do=diff</link>
        <description>Physical Slot

A physical slot is a location for a volume within a storage location that remains static, unaltered regardless of which repository or customer it is allocated to.

e.g. Cabinet A, shelf 1, slot 4 will be the fourth slot in cabinet A on the first shelf.</description>
    </item>
    <item rdf:about="https://rtfm.tapetrack.com/concepts/qualified_barcode?rev=1737497272&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-01-21T22:07:52+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>qualified_barcode</title>
        <link>https://rtfm.tapetrack.com/concepts/qualified_barcode?rev=1737497272&amp;do=diff</link>
        <description>Fully Qualified Barcode

A fully qualified barcode includes the Customer-ID, Media-ID and Volume-ID in a format that can be parsed into those separate values according to the barcode translation table.





For example a fully qualified volume barcode US04.LTO.123456L6, using the Barcode translation ????.???.??????L6 will parse the values:</description>
    </item>
    <item rdf:about="https://rtfm.tapetrack.com/concepts/scan-file?rev=1737497272&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-01-21T22:07:52+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>scan-file</title>
        <link>https://rtfm.tapetrack.com/concepts/scan-file?rev=1737497272&amp;do=diff</link>
        <description>Scan-File

A Scan-File is a listing of Volume-ID&#039;s that, through TapeTrack parsing, is converted in to a Scan-map of Fully Qualified Barcodes for input into Command Line processes. 

The TapeTrack Scan-File Format allows you to specify lists of TapeTrack compatible Barcodes, along with comments and Barcode defaults.</description>
    </item>
    <item rdf:about="https://rtfm.tapetrack.com/concepts/scan-map?rev=1737497272&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-01-21T22:07:52+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>scan-map</title>
        <link>https://rtfm.tapetrack.com/concepts/scan-map?rev=1737497272&amp;do=diff</link>
        <description>Scan-Map

A TapeTrack Scan-Map is a list of fully qualified volumes, usually loaded from a Scan-File, that can be looked up each time that a volume is scanned.

The Scan-Map records how many time each tape has been scanned and also whether the volume was a duplicate when loaded from the Scan-File.</description>
    </item>
    <item rdf:about="https://rtfm.tapetrack.com/concepts/slot?rev=1737497272&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-01-21T22:07:52+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>slot</title>
        <link>https://rtfm.tapetrack.com/concepts/slot?rev=1737497272&amp;do=diff</link>
        <description>Slot

A Slot is a specific physical location designed to accept one (or multiple) Volume.

A Slot may be a position in a rack, library or shelf.

Slots are referred to in TapeTrack as either Virtual or Physical locations.</description>
    </item>
    <item rdf:about="https://rtfm.tapetrack.com/concepts/target_repository?rev=1737497272&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-01-21T22:07:52+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>target_repository</title>
        <link>https://rtfm.tapetrack.com/concepts/target_repository?rev=1737497272&amp;do=diff</link>
        <description>Target Repository

A Volume&#039;s Target Repository is its intended location or the Repository the Volume should be moved to.

For example, a Volume that is currently in a Library and is full needs to be moved to the offsite storage for data preservation.  The Library would be it&#039;s Current Repository and the offsite storage location becomes its Target location.</description>
    </item>
    <item rdf:about="https://rtfm.tapetrack.com/concepts/virtual_slot?rev=1737497272&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-01-21T22:07:52+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>virtual_slot</title>
        <link>https://rtfm.tapetrack.com/concepts/virtual_slot?rev=1737497272&amp;do=diff</link>
        <description>Virtual Slot

The Virtual Slot allocation is a number assigned to a slot based on sequential numbering of all slots from the zones allocated to a repository.

See Also

	*  Physical Slots
	*  Virtual and Physical Slots</description>
    </item>
    <item rdf:about="https://rtfm.tapetrack.com/concepts/zones_repositories?rev=1737497272&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-01-21T22:07:52+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>zones_repositories</title>
        <link>https://rtfm.tapetrack.com/concepts/zones_repositories?rev=1737497272&amp;do=diff</link>
        <description>Zones and Repositories

The purpose of this section is to explain the concept of Zones and Repositories and how these objects interact to facilitate a flexible storage solution in TapeTrack. 

For illustration purposes, rather than discussing a vault we will use the analogy of a restaurant.</description>
    </item>
</rdf:RDF>
