Missing or incorrect validation of measurement-level properties for pooled measurements

[Shraddha0903]

What are you missing?

• Clear, blocking validation for measurement-level fields in pooled measurements.
• A sheet structure that prevents mixed values by design.
• Explicit distinction between measurement-level and sample-level fields.

Why do you need a solution?

Pooled measurements require exactly one value per measurement-level field.

Mixed values can be understood by the user as confusing errors, leading to:

• Invalid metadata
• Silent data corruption
• User confusion about where values belong

Ideas

1. Validation error copy (blocking)

A. Conflicting values (specific field)

Title: Conflicting values in pooled measurement

Message:
The field “Read type” must have the same value for all samples in a pooled measurement.
Found multiple values:
• single-end
• paired-end
Please choose one value and apply it to all samples.

(Repeat for: Library kit, Flow cell, Run protocol, Instrument, Facility)

B. Generic (multiple fields)

Title: Invalid pooled measurement configuration

Message:
One or more measurement-level fields contain different values across samples.
Pooled measurements require a single value per field.
Please resolve the conflicts and try again.
(Optionally list affected fields)

2. Sheet structure redesign (preferred long-term fix)

Keep row-based structure
Clearly mark measurement-level columns
Enforce identical values across rows; block save if violated

Field classification (to document)
Measurement-level: Facility, Instrument, Read type, Library kit, Flow cell, Run protocol, Organisation
Sample-level: Sample ID/name, Index i7/i5, comments, biological attributes

Code of Conduct

• I agree to follow this project's Code of Conduct