Prepending study IDs when copying/pasting
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by tracing the copy/paste handling for sample and tube identifiers and the existing autocomplete behavior, then compare it with the intended scope of issue #209. Done means identifiers can be matched by prepending a relevant study ID, while ambiguous matches across studies are visibly flagged for manual intervention.
Written by the indexing model from the issue text.
Description
The wet lab is reporting that study IDs are not being prepended when sample or tube identifiers are copied and pasted into cells.
Frequently, when plating, the qiita study ID is not part of the identifier. As a result, the wet lab may modify the sample information to correct the tube ID field and then attempt to replace. Or, they may copy / paste the IDs into labcontrol and then manually go cell to cell, making slight edits in order to trigger the autocomplete mechanism.
What would be pleasant is for labcontrol, if an identifier does not have an exact match to qiita metadata, attempt to determine if an exact 1-1 match can be made by prepending the qiita study ID. It would be great if this were supported when copying and pasting identifiers.
If multiple studies are being plated, it would be reasonable for labcontrol to attempt to determine if an exact match could be performed to any study that pertains to the plate. If there is an ambiguity (i.e., the same tube identifier is used in multiple studies), for the cell to be flagged / colored as to warn the user that human intervention is necessary.
This is remarked as a possible regression of #209 as the intention of that issue was in part to prepend a study ID. However, I believe #209 was scoped to entering values manually cell by cell as opposed to copying and pasting one or many cells.
- 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
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
EleutherAI/lm-evaluation-harness#4207 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ClickHouse/clickhouse-connect#1057 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
open-telemetry/sig-end-user#406 ·
-
bug ci good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100