Choose the OpenLab evidence that answers the receiving question
A selected result table, a chromatogram and a reviewed report support different work. Seal can connect them to the same sample and analysis while preserving their separate roles. Choose the export before choosing the receiving fields.
Choose the source route
Selected reported results
OpenLab CDS reporting supports outputs including TXT, CSV, PDF, Word and Excel. Agilent: OpenLab CDS reporting.
In Seal: Use an agreed structured table for the values to compare in Seal; keep the corresponding report as evidence of the source presentation and calculation context.
Chromatogram signals
Agilent documents AIA exports as CDF files, with a separate file for each injection signal. The 2.8+ export settings control naming, destination and overwriting. Agilent: AIA export in OpenLab CDS 2.8+.
In Seal: Retain channel identity, axis and unit with the trace. Count expected signals before calling the collection complete; a curve does not supply every selected report result.
A Sample Scheduler LIMS handoff
The 2.7 documentation describes a sign-off route that copies CDS-stored result reports into a LIMS result folder after submission. Reports exported only to the Windows file system are not included in that copy step. Agilent: Sample Scheduler 2.7 LIMS configuration.
In Seal: Identify whether collection follows the Scheduler submission or another agreed export event. The configured Seal collection and receiving mapping must follow that chosen handoff.
Produce a results export whose columns you can explain
Start with one processed injection in OpenLab CDS 2.8 and a selected compound. Create a table you can reconcile to the source before automating collection. Record the processing method and result context alongside the file so Seal can link the reported value to the sample, injection and supporting traces.
Download the first-run procedure and receiving checks
Select the injection and expose the relevant columns
In Data Analysis, select the required injection and open Injection Results. Use the Column Chooser at the upper left to select the result columns. For the evaluation, include peak identity, compound name, signal description, retention time, the quantity being transferred and its unit evidence.
Check: Count the selected peak rows and note the source injection/evaluation identity separately if the table does not carry it. Keep unidentified peaks visible in the source comparison rather than assigning a compound name from a neighboring row.
Agilent: choosing result columns · Agilent: Injection Results column meanings
Establish whether the quantity is already corrected
Read the chosen column definition. Amount is the calibration-derived value before subsequent multipliers and factors; Concentration includes those corrections. In the processing method, inspect Compounds → Calibration → General for the concentration calculation setting and Calculate mass %. Record the applicable sample and compound factors.
Check: Write down the reported quantity, unit, factor values and whether the method multiplies or divides by dilution factors. A factor of 10 in a preparation record is not enough to decide what to do to a reported Concentration.
Agilent: Injection Results column meanings · Agilent: concentration and mass% · Agilent: where correction factors apply
Export and inspect the actual file
Right-click the Injection Results table, choose Export to file, then select CSV and a destination. Preserve that original file. Inspect its text as well as the spreadsheet view so the mapping uses the actual headers, delimiters, number representation and blank cells.
Check: Compare the exported row population with the selected source table. Confirm the sample/injection association and quantity unit. Treat this manual export as a mapping specimen; the eventual scheduled report or collection route needs its own equivalent comparison.
Record display precision before comparing numbers
For the quantity column, inspect Numeric precision from its context menu. OpenLab stores double-precision data; changing displayed decimals does not change the saved result. A report template may have a different precision, and injection-result display settings are user-specific.
Check: Compare the numeric text in the delivered file with the intended source value. Document any rounding in the transfer. Do not invent missing decimal places from a rounded report or fail a comparison merely because two displays show different numbers of decimals.
Columns that must not be treated as interchangeable
These source definitions determine the receiving field. Preserve the source heading and unit as well as the value, so a later review can distinguish a peak measurement from a calculated report quantity.
Scroll across to see every column →
| Source column or setting | Meaning to retain | Receiving decision |
|---|---|---|
| Peak# / Name / Signal description | Peak order, compound identity when known, and integrated signal | Scope the peak to its injection, evaluation and signal; peak order alone is not a persistent compound identity. |
| Area / Area% | Integrated area versus a percentage of the signal’s summed peak areas | Use separate fields. An area percentage does not establish a calibrated concentration. |
| Amount / Concentration | Calibration output versus the quantity after configured correction | Record the exact source quantity. Apply no additional preparation factor until its role is resolved. |
| Calculate mass % | The Concentration column can represent a mass percentage | Keep the percent basis. Do not relabel the number as mg/mL or g/L. |
| Missing area-unit header | OpenLab shows the unit only under the documented unit-consistency and source-data conditions | Obtain unit evidence from the source owner before comparing areas from different signals. |
Agilent: Injection Results column meanings · Agilent: concentration and mass%
Worked correction: importing 0.82 as 8.2 would be wrong
Fictional mapping worksheet for a simplified method with all other multipliers equal to one, mass% disabled, a confirmed mg/mL basis and dilution factors configured as multipliers. These are normalized worksheet labels, not default OpenLab CSV headings.
sample,injection,evaluation,source_quantity,source_value,source_unit,method_dilution_factor
S-903,INJ-06,EVAL-02,Amount,0.082,mg/mL,10
S-903,INJ-06,EVAL-02,Concentration,0.82,mg/mL,10The source calculation is 0.082 × 10 = 0.82. If the integration selects Concentration, the proposed Seal record retains 0.82 mg/mL and the correction context. Multiplying that reported result by 10 again would create 8.2 mg/mL. If another method uses dilution as a divisor, the same starting number and factor instead give 0.0082; inspect the method rather than deducing the operation from the factor’s label.
Two signals and one reported result belong to the same injection
Fictional receiving manifest, not an OpenLab export schema. The source system owner supplies the identifiers and confirms how they are represented by the installed report and export settings.
Scroll across to see every column →
| Source information | Example identity or value | Why it stays distinct |
|---|---|---|
| Analysis, injection and evaluation | AN-903 / INJ-06 / EVAL-02 | Carry source identity through the report and signal relationships. Filename tokens help collection but do not replace the identity contract. |
| Reported concentration | 0.82 mg/mL for Protein in S-903 | Retain the source quantity and calculation context; establish whether any preparation factor has already been applied. |
| Signal population | UV214 and UV280 | Track expected and received signals separately from the number of report rows. |
| Export settings | Naming, overwrite setting and processing context | A changed export configuration can affect what arrives even when the underlying acquisition is the same. |
The three files do not become three scientific results. The table supplies the selected concentration, and the two signals remain distinct evidence. If UV280 is missing, retain the received files and mark the evidence population incomplete; do not treat the available signal as the complete chromatogram export.
Inspect the source and proposed destination records
Source example
{
"analysis": "AN-903",
"injection": "INJ-06",
"evaluation": "EVAL-02",
"files": [
{
"role": "reported results",
"name": "AN-903-EVAL-02.csv"
},
{
"role": "UV 214 nm signal",
"name": "AN-903-INJ-06-UV214.cdf"
},
{
"role": "UV 280 nm signal",
"name": "AN-903-INJ-06-UV280.cdf"
}
],
"reportedResult": {
"sample": "S-903",
"analyte": "Protein",
"concentration": 0.82,
"unit": "mg/mL"
}
}Proposed Seal records
{
"sample": "S-903",
"analysis": "AN-903",
"injection": "INJ-06",
"evaluation": "EVAL-02",
"result": {
"analyte": "Protein",
"sourceValue": 0.82,
"sourceUnit": "mg/mL"
},
"evidence": {
"resultTables": 1,
"expectedSignals": 2,
"receivedSignals": 2,
"complete": true
}
}Run these cases against the proposed Seal mapping
These are worked test inputs and expected outcomes to verify in your configured connection.
Import the corrected concentration
Input: Map the Concentration row in the worksheet and retain factor 10 as source context.
Expected: The sample result remains 0.82 mg/mL. A conversion to g/L, if required by the receiving field, remains numerically 0.82. The record can identify which source quantity was selected.
Switch to a mass-percentage result
Input: Use a separate specimen in which Calculate mass % is selected and the reported Concentration is 0.82%.
Expected: The proposed receiving result retains 0.82% with its mass basis. A concentration comparison in mg/mL stays unavailable until the required physical basis and conversion are established.
Deliver a blank quantity
Input: Keep the compound row and unit context but remove the numeric concentration cell from a test copy.
Expected: The receiving record identifies the missing value. It does not import zero, copy a neighboring peak’s value or create an apparently complete result from the attached trace.
Deliver the report before the second signal
Input: Deliver the results table and UV214 file, then deliver UV280 later for the same injection/evaluation.
Expected: The result retains its original identity. Evidence completeness moves from one of two expected signals to two of two when the second file arrives; the later file does not create a duplicate concentration.
What to bring to the implementation review
Provide the unedited results export, the chosen-column list, a source report or saved view, the applicable method/factor settings and the expected signal list. Seal can then map the reported quantity and attach its evidence with enough context for neil to explain where the result came from and which corrections were already made.
Diagnose the failure from the source evidence
Only one CDF remains after several injections
A naming collision with overwriting enabled can replace earlier exports. Agilent: AIA export in OpenLab CDS 2.8+.
Compare the expected injection/signal population with the exported files. Correct the source naming and retention settings, then recover the missing evidence from the source.
A report exists, but the LIMS result folder is empty
In the documented Scheduler sign-off route, the source report must be stored in CDS and submitted through that workflow. Agilent: Sample Scheduler 2.7 LIMS configuration.
Check the report’s storage location, sign-off state and configured result-folder route before changing the receiving parser.
A trace disagrees with the expected source view
Agilent notes that configured smoothing or blank subtraction can affect an AIA export. Agilent: AIA export in OpenLab CDS 2.8+.
Compare processing settings and the matching source view. Preserve the transformation context instead of presenting every exported trace as unmodified acquisition.
Apply this to your records
Use this with the Agilent OpenLab result mapping first-run procedure. Retain the actual configuration and evidence, then record what happened in each receiving exercise. Expected behavior is printed as a prompt; your observed result starts blank.
Download the blank working review
Write your working notes here
Notes stay in this tab and are not submitted. Download them before leaving to keep a copy. Use record references to identify your evidence.
Record the installed CDS version, chosen report/CSV/AIA or other supported route, export configuration, selected result columns and completed-file handoff. Identify the actual source report and any independently collected signal files.
List the analysis, injection, signal/channel and evaluation/result identities. State which source fields establish the relationship, which artifacts are expected and how repeat delivery is distinguished from a later evaluation.
Record the selected Amount or Concentration field, original value and unit, result basis, applicable multiplier/divisor and whether corrections are already included. Compare the report, export precision and receiving value for the same result.
Input: Map the Concentration row in the worksheet and retain factor 10 as source context. Expected: The sample result remains 0.82 mg/mL. A conversion to g/L, if required by the receiving field, remains numerically 0.82. The record can identify which source quantity was selected. Record the actual input/evidence references, observed result, whether it matches the expectation and any unresolved issue.
Input: Use a separate specimen in which Calculate mass % is selected and the reported Concentration is 0.82%. Expected: The proposed receiving result retains 0.82% with its mass basis. A concentration comparison in mg/mL stays unavailable until the required physical basis and conversion are established. Record the actual input/evidence references, observed result, whether it matches the expectation and any unresolved issue.
Input: Keep the compound row and unit context but remove the numeric concentration cell from a test copy. Expected: The receiving record identifies the missing value. It does not import zero, copy a neighboring peak’s value or create an apparently complete result from the attached trace. Record the actual input/evidence references, observed result, whether it matches the expectation and any unresolved issue.
Input: Deliver the results table and UV214 file, then deliver UV280 later for the same injection/evaluation. Expected: The result retains its original identity. Evidence completeness moves from one of two expected signals to two of two when the second file arrives; the later file does not create a duplicate concentration. Record the actual input/evidence references, observed result, whether it matches the expectation and any unresolved issue.
Identify the configuration/mapping revision tested, reviewer, open issues and owner for each next action. Cite the retained source and destination evidence. A filled note is not itself an accepted test; record the review decision through your actual process.
Unanswered sections remain marked ‘Not recorded’ in the download.
Evidence needed to finish
The source report, selected export and receiving value describe the same result and quantity. Expected signals are accounted for separately. The recorded exercise outcomes show that a second factor, a changed evaluation and a missing signal are detected instead of hidden by a successful file import.
Use the connected evidence in a review
Ask neil which source files support the selected S-903 result and whether both expected detector signals are present. A useful answer names AN-903, INJ-06 and EVAL-02, distinguishes the result table from the two traces, and identifies any missing source evidence.
Reconcile repeated and revised exports →