-
Notifications
You must be signed in to change notification settings - Fork 0
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
Library Batch Information #173
Comments
What types of data go in these fields? |
TipBatch: we need to write something typically like this: Yellow.5.5 qPCR batch: is a date that is the same for a big chunk of plates at a time. I'm thinking it would be nice if theres a way to write into WALDO kinda like a protocol when we make a batch, and then it would show up as a dropdown option? and then when we run out we can close the batch so it doesn't show up anymore? qPCR lib positive value: is the value in the qPCR column for the sample in the lib positive position (typically G12 for regular plates and B1 for U plates). we would just like this to be visible in the header (is there a way for WALDO to just auto read the cell needed and place it in?) |
most of these things are stuff we track in our Plate Tracker and so I'm trying to get the headers in WALDO to have the same information so when we look at having WALDO make our Plate Tracker for us its already there and ready |
qPCR library positive value is already known for control. Query this out and display in library batch header form. Also put on library batches page if performance allows. The batching should be similar to how protocols are created and selected.
|
Considering #154, how should single-stranded batches have the qPCR displayed? |
we don't track the qPCR values for SS in our Plate Tracker. so the value doesn't need to be displayed. we would like to track the date the positive was made but this would be a different date than the DS one |
can we add a section in the header for library batches called Tip Batch. and a section for qPCR lib positive value and batch
The text was updated successfully, but these errors were encountered: