I'd like to request adding a coverage field as an optional input column in the Sample Site Updater section of WALDO.
Motivation:
We would like to record coverage values reported in publications and supplementary materials at the time of sample annotation. Having coverage available as an uploadable field would enable future sanity checks comparing recorded coverage values against coverage calculated from our pulldown and downstream processing pipelines.
This would help identify potential metadata inconsistencies, sample mix-ups, transcription errors, or other discrepancies between published metadata and internally generated metrics.
Proposed Change
Add a new optional column: coverage
Allow coverage to be uploaded through the Sample Site Updater workflow alongside other sample metadata fields.
Store the value as sample-level metadata.
Use Case
When annotating a publication, we could enter the coverage reported by the authors. Later, we could compare those values against the calculated coverage generated on our end from pulldown data.
Benefits
Enables automated sanity checks between published and internally calculated coverage values.
Improves metadata validation and quality control.
Helps identify potential discrepancies early.
Reduces the need for external spreadsheets or manual tracking of coverage metadata.
Priority
Not urgently required for current workflows, but would be valuable infrastructure for future QC and metadata validation efforts.
I'd like to request adding a coverage field as an optional input column in the Sample Site Updater section of WALDO.
Motivation:
We would like to record coverage values reported in publications and supplementary materials at the time of sample annotation. Having coverage available as an uploadable field would enable future sanity checks comparing recorded coverage values against coverage calculated from our pulldown and downstream processing pipelines.
This would help identify potential metadata inconsistencies, sample mix-ups, transcription errors, or other discrepancies between published metadata and internally generated metrics.
Proposed Change
Add a new optional column: coverage
Allow coverage to be uploaded through the Sample Site Updater workflow alongside other sample metadata fields.
Store the value as sample-level metadata.
Use Case
When annotating a publication, we could enter the coverage reported by the authors. Later, we could compare those values against the calculated coverage generated on our end from pulldown data.
Benefits
Enables automated sanity checks between published and internally calculated coverage values.
Improves metadata validation and quality control.
Helps identify potential discrepancies early.
Reduces the need for external spreadsheets or manual tracking of coverage metadata.
Priority
Not urgently required for current workflows, but would be valuable infrastructure for future QC and metadata validation efforts.