Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a duplicate barcode warning in the lims RC steps #476

Open
FayKanellidou opened this issue Mar 5, 2024 · 3 comments
Open

Add a duplicate barcode warning in the lims RC steps #476

FayKanellidou opened this issue Mar 5, 2024 · 3 comments
Assignees
Labels
enhancement New feature or request Urgency: Medium

Comments

@FayKanellidou
Copy link

Lims Issue

For definitions of headings below see Basic Concepts.

Workflow: Microbial WGS v7, TWIST v8, WGS PCR free v6
Protocol: Pre Processing Microbial v1, Initial QC wgs v4, Pre Processing TWIST v3
Step: Reception Control, Reception Control v3, Reception Control TWIST

Description:
It would be very useful to add a warning message when we assign barcodes to plates and two different plates have been assigned the same barcode. This is an easy mistake to make in the lab and it has happened already a few times.
having a warning message in this case would save us the need to reprep.

@FayKanellidou
Copy link
Author

Hi, AZ and I were wondering if a lims warning like this could be possible to be implemented in lims.
What do you think about it?

@idalindegaard
Copy link
Contributor

Hi Fay. I understand this can be a problem sometimes... We are wondering if the check should be within the step or if it should check all barcodes ever recorded in the "Output container barcode" udf? The workload for this issue differs a bit depending on which of these alternatives are needed

@FayKanellidou
Copy link
Author

Hi Fay. I understand this can be a problem sometimes... We are wondering if the check should be within the step or if it should check all barcodes ever recorded in the "Output container barcode" udf? The workload for this issue differs a bit depending on which of these alternatives are needed

I guess the second suggestion is the most appropriate one but since so far the issue we had was scanning and the barcode is also placed in the udfs of other plates by mistake let's go with the easier solution.

If in the future we still have an issue then we could scale it up.

@amandaraud amandaraud removed their assignment May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Urgency: Medium
Projects
None yet
Development

No branches or pull requests

4 participants