Sample ID to tube ID information
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
Research direction
Start at the sample plating page and trace how selected studies, sample IDs, and tube identifiers are loaded. Check the existing interface entry point and data flow before defining the read-only window; done means a searchable two-column view handles studies with missing or mixed tube identifiers and requires reopening after selection changes.
Written by the indexing model from the issue text.
Description
The wet lab requests an interface to see the association between sample IDs and specimen (tube) IDs, which can be helpful in the event of usual characters, sanity checking, etc. Access to this interface would be from the sample plating page, and open a new window. The new window would present a two column spreadsheet, where the first column is the sample ID and the second column is the specimen ID. The wet lab additionally requests the ability to easily search in these columns.
A mock up of the proposed interface is attached. On the left side in blue is a (very) rough sketch of what the sample plating page looks like. The mockup proposes to add a button (in red color on the left), labeled “Sample ID <-> Tube ID”, or something to that effect, which when clicked opens the window on the right side of the mock up.
The proposal here is for the new window to be read only. It is acceptable that the new window not dynamically update if studies are added or removed from the sample plating page — if studies are added or removed, a user would need to reopen the window.
There are important edge cases here:
- a study may not have a tube identifier set
- a study may not be selected for plating
- multiple studies may be selected for plating. Some, none, or all may have a tube identifier set
The issue was created with @ghsmu414. It is presently remarked as a low priority request; the relative priority can be revisited in upcoming iterations.

- Dominant language
- Python
- Stars
- 2
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from biocore/LabControl
-
bug front-end question
Difficulty 4/5 3-5 days Newbie friendliness 30/100
biocore/LabControl#594 ·
-
front-end question
Difficulty 5/5 Over a week Newbie friendliness 35/100
biocore/LabControl#593 ·
-
front-end
biocore/LabControl#592 · 1 assignee ·
-
code refactor front-end
Difficulty 5/5 Over a week Newbie friendliness 25/100
biocore/LabControl#591 ·
-
priority:low
Difficulty 3/5 1-2 days Newbie friendliness 20/100
biocore/LabControl#590 ·
All issues in biocore/LabControl
Similar issues
-
area: harness bug status: needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Human-Agent-Society/reef#625 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 1/5 Under an hour Newbie friendliness 80/100
learningequality/kolibri#15351 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Name consistency Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
eellak/triplestore#65 · 1 comment ·