Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Sample ID to tube ID information

未关闭
#495 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
38/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
python
领域
frontend

调研方向

从样本铺板页面开始,跟踪选定的研究、样本 ID 和管标识符是如何加载的。在定义只读窗口之前,检查现有的界面入口点和数据流;完成的标准是,可搜索的两列视图能够处理缺少管标识符或管标识符混杂的研究,并且在选择发生变化后需要重新打开。

由索引模型根据 Issue 内容生成。

描述

feature request front-end priority:low

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.

20190503_104452

主要语言
Python
星标
2
派生
15
PR 合并指标
30 天内没有已合并 PR

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

biocore/LabControl 的其他 Issue

查看 biocore/LabControl 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。