Plan a pilot box
Menu

File naming builder for digitization projects

One naming pattern for every image, agreed before the first capture, so files sort in page order and always find their catalog record.

File name builder

A fictional example is filled in. Change any part; the names update as you type. Nothing leaves your browser.

File names

achs_c003_b03_f012_i004_0001_m.tif

  1. achs_c003_b03_f012_i004_0001_m.tif
  2. achs_c003_b03_f012_i004_0002_m.tif
  3. achs_c003_b03_f012_i004_0003_m.tif

A digitized collection is thousands of files that must stay in order, move between systems and point back to the right box and catalog record. The file name is the one piece of description that goes everywhere the image goes. This builder turns a few codes and numbers into names that follow one pattern, so nobody has to invent a name at the scanner.

The pattern

The builder joins eight parts with underscores:

<institution>_<collection>_b<box>_f<folder>_i<item>_<sequence>_<role>.<ext>

Part Example What to enter
Institution code achs A short code for your organization, letters and digits only
Collection code c003 The collection, record group or accession the item belongs to
Box b03 Box number, padded to two digits
Folder f012 Folder number, padded to three digits
Item i004 Item number within the folder, padded to three digits
Sequence 0001 One number per image, in page order, padded to four digits
Role m or a m for the preservation master, a for the access copy
Extension tif tif, jpg, jp2 or pdf

Enter the number of images in the item and the builder writes one name per image. Download the list as a CSV to hand to whoever is scanning.

Why the rules matter

Lowercase only

Some file systems and most web servers treat capital and small letters as different characters; others treat them as the same. Box3.TIF and box3.tif can be one file on a laptop and two files on a server. Lowercase everywhere removes the question.

No spaces or punctuation

Spaces turn into %20 in web addresses and break command-line scripts. Slashes, colons, ampersands and accented letters are reserved or handled differently from one system to the next. The builder turns spaces into hyphens and drops other characters, so underscores separate the parts and hyphens are only used inside a code.

Fixed-width numbers

Computers sort names character by character, so 10 lands before 2 unless both are padded. With fixed widths, 0002 always sorts before 0010 and pages stay in reading order in any folder view. The builder pads boxes to two digits and folders and items to three. A box numbered 100 or higher would print with three digits and sort out of step, so a collection that large needs a wider box field before capture starts.

Short enough to read

The builder warns when a name passes 64 characters. Long names hit path limits in some systems and are hard to read aloud or check by eye. Keep codes short: achs rather than the full society name.

Identifiers that match the catalog

The name is a location identifier: it says which box, folder and item the image came from. Your catalog record usually has its own identifier, such as an accession number. Decide before capture whether the file name stem is built from that number or recorded next to it. Either way, the exact stem (everything before the sequence number) must appear in your inventory and in the catalog record, so files and records can always be joined again. The metadata mapping worksheet has a row for this.

Masters and access copies

A preservation master is the full-quality capture you keep unchanged. FADGI’s guidelines list TIFF and JPEG 2000 among master formats. Access copies are smaller files, usually JPEG, made from the master for viewing and sharing. Giving both the same stem and changing only the role code (m or a) and the extension keeps each pair together and makes it obvious which file must never be edited or overwritten.

Using the names in a project

  1. Agree the codes first. Fix the institution and collection codes and the number widths before the first image is made. A pilot box is the right moment to test them.
  2. Generate names from the inventory. Each row of the collection inventory worksheet gives you box, folder and item numbers. Build the names item by item and keep the CSV with the inventory.
  3. Check names during quality control. The image QC checklist asks whether names follow the scheme with no gaps or duplicates. A missing 0003 usually means a missing page.
  4. Write the scheme down. Put a one-page description of the pattern in the delivery folder, so the names still make sense in twenty years.

Example (fictional). The Aster County Historical Society uses the institution code achs and the collection code c003. In Box 3, folder 12, item 4 is a letter with three images: two pages and an envelope. The builder writes achs_c003_b03_f012_i004_0001_m.tif, achs_c003_b03_f012_i004_0002_m.tif and achs_c003_b03_f012_i004_0003_m.tif for the masters. Switching the role to access and the format to jpg gives achs_c003_b03_f012_i004_0001_a.jpg and so on, with the same stem. The stem achs_c003_b03_f012_i004 goes into the item’s inventory row and catalog record.

Where this fits

File naming is set in the Assess stage and used at every stage after it. Our document scanning work applies the agreed pattern at capture, and the digital preservation package lists every file by name with its checksum. For more on capture planning, see the Reading Room’s capture and imaging section, or plan a pilot box and test your naming scheme on real material.

Send one box first.

A pilot box shows you the images, the recognized text and the catalog records before you commit a whole collection. Tell us what is in the box and what you want people to find.

Agree file names in a pilot box

Studio and contacts

24 South Weber Street, Suite 225
Colorado Springs, CO 80903
(719) 244-8450sales@dastok.com