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. FIRST RUN 1. 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: https://openlab.help.agilent.com/2.8/en/mergedProjects/DataAnalysis/DA_chooseColumnsForInjectionResults.htm Agilent: Injection Results column meanings: https://openlab.help.agilent.com/2.8/en/mergedProjects/DataAnalysis/iDA_DataAnalysis_InjectionResults.htm 2. 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: https://openlab.help.agilent.com/2.8/en/mergedProjects/DataAnalysis/iDA_DataAnalysis_InjectionResults.htm Agilent: concentration and mass%: https://openlab.help.agilent.com/2.8/en/mergedProjects/DataAnalysis/DA_concentrationMassPercent.htm Agilent: where correction factors apply: https://openlab.help.agilent.com/2.8/en/mergedProjects/DataAnalysis/DA_correctionFactors.htm 3. 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. Agilent: exporting injection results: https://openlab.help.agilent.com/2.8/en/mergedProjects/DataAnalysis/DA_Review_ExportInjectionResults.htm 4. 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. Agilent: display precision versus saved results: https://openlab.help.agilent.com/2.8/en/mergedProjects/DataAnalysis/ChangeNumericPrecisionInjectionResults.htm 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. Source column or setting: Peak# / Name / Signal description Meaning to retain: Peak order, compound identity when known, and integrated signal Receiving decision: Scope the peak to its injection, evaluation and signal; peak order alone is not a persistent compound identity. Source column or setting: Area / Area% Meaning to retain: Integrated area versus a percentage of the signal’s summed peak areas Receiving decision: Use separate fields. An area percentage does not establish a calibrated concentration. Source column or setting: Amount / Concentration Meaning to retain: Calibration output versus the quantity after configured correction Receiving decision: Record the exact source quantity. Apply no additional preparation factor until its role is resolved. Source column or setting: Calculate mass % Meaning to retain: The Concentration column can represent a mass percentage Receiving decision: Keep the percent basis. Do not relabel the number as mg/mL or g/L. Source column or setting: Missing area-unit header Meaning to retain: OpenLab shows the unit only under the documented unit-consistency and source-data conditions Receiving decision: Obtain unit evidence from the source owner before comparing areas from different signals. Agilent: Injection Results column meanings: https://openlab.help.agilent.com/2.8/en/mergedProjects/DataAnalysis/iDA_DataAnalysis_InjectionResults.htm Agilent: concentration and mass%: https://openlab.help.agilent.com/2.8/en/mergedProjects/DataAnalysis/DA_concentrationMassPercent.htm 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,10 The 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. PROPOSED RECEIVING CHECKS — NOT EXECUTED CUSTOMER VALIDATION 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. HANDOFF 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.