Skip to main content

Location in storage

Automated storage location entry is supported via barcodes to reduce errors and increase speed. A single scan can populate multiple levels of the storage hierarchy, removing the need to enter each part manually.

How it works​

The system parses a scanned barcode into components based on a defined location separator. For more information on storage location structure and how genebanks should use it, see Storage location and Storage naming conventions.

For example, if the separator is -, the barcode A-01-02-03 is split into four parts:

  • Part 1: A
  • Part 2: 01
  • Part 3: 02
  • Part 4: 03

These parts are automatically assigned to the corresponding storage location fields.

Barcodes can also be partial. For example, LTS-Rack 7-Shelf 2 is split into three parts:

  • Part 1: LTS
  • Part 2: Rack 7
  • Part 3: Shelf 2

Using the barcode scanner​

Depending on the form, there are two ways to use this functionality:

Dedicated barcode field​

Some forms feature a dedicated barcode input. Scanning into this field populates all relevant storage location parts and usually submits the form automatically.

Storage location fields​

In forms with individual fields (Part 1, Part 2, etc.), scanning a barcode while the first part field is focused, or using its attached scanner button, populates the corresponding storage location parts.

Configuration​

The character used to separate barcode parts is configurable in the application settings.

An administrator must register a barcode setting named Location separator in the barcode settings category. The default value is -.

Category tagVariable nameDescription
BARCODElocationSeparatorThe character used as a separator in location barcodes (default: -)

Label generation​

The application does not print storage location labels. Generate these labels using external tools.

Recommended tools include:

  • Zebra Designer
  • Microsoft Word
  • Other label design or barcode generation software

Ensure that the barcodes on your labels follow the naming convention and use the separator configured in the application.