Katalyst: Cannot Attach Data Due to Missing or Incorrect Sample Names

Katalyst uses sample names contained in analytical data files to automatically associate uploaded data with the correct experiments, containers, and wells. Some instrument vendor and acquisition software packages (for example, LC/MS workstations) use proprietary sample naming conventions that may not include the required KAT identifiers or may generate inconsistent, truncated, or invalid well identifiers.

As a result, Katalyst may be unable to match the incoming analytical data to the appropriate records, causing data upload, attachment, or processing to fail.

In addition, analytical data file names must contain only a single occurrence of the KAT ID-Container ID-Well ID identifier. File names that contain duplicate KAT IDs or remnants of KAT IDs from previous upload attempts can prevent successful data upload and processing.

To ensure successful data attachment and processing in Katalyst:

1. Configure the instrument software to use a standardized sample naming format that includes the KAT ID, Container ID, and Well ID.
2. Use the same naming template consistently for all Katalyst experiments.
3. Generate a sequence file in Katalyst and import it into the instrument software.
4. Verify that the sample names in the acquisition sequence match the expected Katalyst naming convention before data acquisition begins.
5. Ensure that analytical data file names contain only one instance of the KAT ID-Container ID-Well ID identifier.

For data that has already been acquired with incorrect sample names:

1. Obtain the correct KAT ID, Container ID, and Well ID values from the Katalyst-generated sequence file.
2. Rename the analytical data files to match the required naming convention.
3. Re-upload the corrected files to Katalyst for processing.

Note: Missing, truncated, incorrect, or duplicated identifiers in sample names can prevent Katalyst from automatically associating analytical data with the correct wells and experiments. Using a consistent Katalyst-generated naming convention is the recommended approach to avoid these issues.