实验室数据归档与命名规范
为实验室规划文件目录、命名和备份规则,配套原始数据保护措施与成员操作指南。
完整提示词
<context>
In most labs, the data problem is not a lack of a data management plan but a lack of daily habits: raw files left on instrument PCs, names like "final_v2_new.xlsx", processed files saved over raw ones, and no link from a notebook entry to the files. A structure that works is shallow and predictable (project, then experiment ID, then raw, processed, analysis, figures), uses dates in ISO order and the same experiment ID as the notebook and sample labels, makes raw folders read-only once copied, and has one automatic backup the lab does not have to think about. Institutional storage and retention rules come first.
</context>
<task>
<lab>
{{lab}}
</lab>
{{#problems}}
<problems>
{{problems}}
</problems>
{{/problems}}
1. Principles: three to five rules the whole design follows.
2. Folder structure: a tree with an example, one level per decision (project, experiment, data stage), and where shared resources (protocols, templates, reference data) live.
3. File naming: a convention with date as YYYY-MM-DD or YYYYMMDD, experiment ID, sample or condition, instrument, version only where needed; characters to avoid; examples for each instrument named.
4. Raw data protection: copy off instrument PCs the same day, write-protect raw folders, never edit raw files, processed outputs go elsewhere, and checksums or file counts on transfer for large data.
5. Links to notebooks and samples: the experiment ID ties notebook entry, sample labels and folders together; a short README per experiment folder.
6. Backup and retention: use institutional storage, the 3-2-1 principle in plain words, who checks restores, and retention per institutional or funder policy.
7. One-page guide for lab members.
8. Rollout: start with new experiments, migrate active projects only, and a monthly check.
</task>
<constraints>
- Do not recommend personal cloud accounts for research data; follow institutional storage, and flag personal or sensitive data needing approved storage.
- Do not state retention periods as facts; say they come from the institution or funder.
- Keep the structure shallow enough to remember.
</constraints>
<output_format>
## Principles
## Folder structure
## File naming
## Raw data protection
## Links to notebooks and samples
## Backup and retention
## One-page guide
## Rollout
</output_format>可替换内容
- {{lab}}
- {{#problems}}
- {{problems}}
- {{/problems}}
分类与标签
办公效率、实验数据管理、文件命名、数据备份、团队规范