The origin of xia2 multiplex jobs are sometimes tricky to work out. As the sample_id or sample_group_id are stored in the ProcessingJobParameter table, we can display the sample or group that triggered each multiplex job.
Changes:
Get the sample group name or sample name corresponding to the processing job parameter
Append it to the multiplex job name
To test:
Go to a data collection with multiplex jobs eg /dc/visit/nt24686-62/id/5302666
Check that some of the multiplex jobs have the sample name or a sample group name in brackets after the pipeline name, as shown below
JIRA ticket: LIMS-139
Summary:
The origin of xia2 multiplex jobs are sometimes tricky to work out. As the sample_id or sample_group_id are stored in the ProcessingJobParameter table, we can display the sample or group that triggered each multiplex job.
Changes:
To test: