Y24-209 - Update the Short Read Team Cross Charging Report with corresponding to NovaSeqX platforms

[SujitDey2022]

User story As a User (Rich R.) responsible for Short Read cross-charging reports, I would like to include the details relevant for NovaSeqX v1.2 sequencing platforms SO THAT accurate billing is possible considering the increased usage of the platform

Who are the primary contacts for this story Tris B. Rich R.

Who is the nominated tester for UAT Rich R.

Acceptance criteria

1. Link to the exiting cross charging report: https://globalreporting.internal.sanger.ac.uk/#/views/NewBilling/SequencingBilling?:iid=1

To be considered successful the solution must allow:

• [ ] Information needed to be included to the cross charging report is extracted for only v1.2 version runs of the NovaSeqX platform runs contained in the “RunParameters.xml” file.
  • “RunParameters.xml” file example here: https://esa-sv-20201215-02.dnapipelines.sanger.ac.uk:12443/export/esa-sv-20201215-02/IL_seq_data/analysis/20240321_LH00275_0020_B222V7HLT1/RunParameters.xml

• [ ] Following sequencing run details are included in the report,

  • Kit Type and Kit Cycle, available under 'ConsumableInfo' Example:

  

  Where, 1.5B is the Kit Type (Flowcell Type) and 100c is the Kit Cylce information

  • Primer details, available under 'RecipeVersion' Example:

OR

• [ ] Fields with no values are left blank with no default values added.

Dependencies This story is blocked by the following dependencies:

• N/a

References This story has a non-blocking relationship with:

• N/a

Additional context Add any other context or screenshots about the feature request here.

[SujitDey2022]

@KatyTaylor adding your comment regarding MLWH,

[SujitDey2022]

[SujitDey2022]

Team Discussion 24 July 2024:

1. The RunParameter.xml file details are contained in the MLWH database field with the parameters.
2. Need to confirm if point 1 here with NPG
3. Need to confirm if PSD needs editing capability for the Tableau Report (Can be referred from the guidelines provided for reporting work linked here https://ssg-confluence.internal.sanger.ac.uk/display/PSDPUB/Automating+Billing+Report)
4. Need to confirm the column labels in the report be called (Need to check with Rich R.)

[KatyTaylor]

Link to Harry's billing docs - https://ssg-confluence.internal.sanger.ac.uk/display/PSDPUB/Automating+Billing+Report

See section

ExtractValue(iseq_run_info.run_parameters_xml, '//SbsCycleKit')

for an example of how to pull info from the XML.

[sabrine33]

I double-checked with Marina and confirmed that the data is being consistently populated. However, some very old run data might not be available. Marina also mentioned that the data should appear at the end of the primary analysis stage.

[sabrine33]

Hi @SujitDey2022 , @khelwood , @KatyTaylor; It is not entirely clear on the specific information that needs to be included in the report, particularly regarding the column names and their corresponding values. From our last meeting, I recall that we agreed to add two columns:

Custom Primer(s) Used: This column should indicate a boolean value. Recipe Name: This column should contain a string value, if applicable.

Could you please confirm if this is correct?

[sabrine33]

From Tris:

I’d suggest just the ‘<RecipeVersion>’ values – an example below:

<RecipeVersion>10B-01.02.00_CustomPrimer_CP1CP2</RecipeVersion>

Rich can then likely just add a filter – which can then translate into a Yes/No depending on the recipe contents.

I’m sure Rich will flag if not at the UAT stages.

I suppose this is quite ready to progress on now.

[sabrine33]

UAT Tableau Dashboard link: https://globalreporting.internal.sanger.ac.uk/#/views/BillingReport/SequencingBillingUAT?:iid=5