我现在在进行APS的prb期刊投稿,现在填到Data Availability Disclosure...

Creado el: 28 de enero de 2026

Respondido usando GPT-5.2 Thinking por Chat01

Pregunta

image.png

我现在在进行APS的prb期刊投稿,现在填到Data Availability Disclosure了,我不太清楚这个界面让我干什么,你能帮我看一下吗?

Pensamiento

Providing guidance on data availability statement

We’ve got style guide lines on data availability and referencing datasets. I need to use citations from reliable web sources for APS policy claims such as data being publicly available at publication and including dataset references in the manuscript. We can refer to the user-provided screenshot, but citations are necessary for policy details. I'll guide them on whether to choose Yes/No, typical examples, and mention that PRB requires a data availability statement at the end of the submission. I’ll also provide a template with a Chinese explanation.

Providing guidance on data availability disclosure

If you choose "No" for open data, you’ll likely need to justify this and still agree to share privately upon request. APS guidelines mention this, and I can reference them. Also, the PRB Info for Authors covers preparing data availability, with details in their citation guidelines. I'll guide step-by-step: first, describe the data and its figure/table, then choose whether the data will be publicly available, including any embargoes.

Clarifying dataset options for submission

If your data is included in the article or supplementary material, it’s considered publicly available with the article, even if not housed in an external repository. The form asks about external datasets, but you can choose options like "All data available within the publication" instead. You might not need "Add Dataset" after all.

Guidance on adding datasets and data statements

If the data is not in an external repository, it’s better to skip the “Add Dataset” option and select a data availability statement, such as “Data in the article.” The “Description” field is still required. If you have a private or embargoed link, you can use it during review and update later post-acceptance.

Providing data availability statement guidance and template examples

The interface is used to create a Data Availability Statement for each dataset, including the DOI/URL. Every PR article will need a DAS, and be sure to cite reference numbers. Common cases include:

  1. If data/code is in a public repository, select "Yes" and fill in DOI/URL.
  2. If data is in the article or supplemental material, select a specific template statement like "All data within the publication.”

Thought for 1m 52s

Respuesta

你这个页面是在 APS 投稿系统里填写“数据可用性(Data Availability)披露” 用的:系统会用你在这里填的内容,自动生成最终文章里会出现的 Data Availability Statement(通常在 Acknowledgments 后面)。APS 目前要求发表的文章都要带这个声明,并且如果你把数据放到仓库里,需要在正式发表前把数据作为一条参考文献引用到文末参考文献列表里(也就是它提示的 “reference number”)。(Cloudinary)

下面按你截图里的每一项解释“它要你干什么”,以及怎么填:

这个 “Add Dataset” 什么时候该用?

  • 当你有一个(或多个)“数据集/代码/材料”要指向某个仓库或链接(例如 Zenodo、Figshare、机构仓库、GitHub+Zenodo 归档 DOI 等),就点 Add Dataset 来登记一条。
  • 如果你的情况是纯理论没产生数据,或数据都已经在正文/补充材料(Supplemental Material)里,通常不需要在这里单独“Add Dataset”,而是去选择系统提供的模板型声明(例如 “No data were created…” / “All data … available within the publication” 这类)。(Cloudinary)

字段逐项怎么填(对应你截图)

1) Description(必填)

这里要你写:这份数据/代码是什么、支持论文哪部分结果
写法建议:一句话即可,尽量具体到图表或结论,例如:

  • “Raw magnetotransport data and analysis scripts supporting Figs. 1–3.”
  • “DFT input/output files and post-processing scripts supporting Figs. 2–5.”
  • “Experimental XRD datasets used in Table I and Fig. 4.”

2) Will this data be publicly available?(必选 Yes/No)

  • 选 Yes:你打算让读者公开获取(通常是放公共仓库;也可以是先 embargo、到某个日期公开)。APS 也鼓励数据在发表时尽量公开。(Cloudinary)
  • 选 No:数据不公开(例如商业/保密/合规限制)。这种情况下,一般需要在声明里说明原因,并且 APS 的表述是:即使不公开,也应在编辑/审稿人需要时私下提供。(journals.aps.org)

3) Reference number (if available)

它说的 reference number 指:你在稿件参考文献列表里给“数据集引用”分配的编号(比如 [34])。

  • 如果你已经在参考文献里加了一条 “Dataset/Software” 引用并且编号确定了,就填这个数字(例如 34)。
  • 如果现在还没法确定编号(投稿阶段经常如此),可以先留空,等接受后/校样阶段再补——APS 也允许在校样阶段对 Data Availability Statement 做合理修改。(Cloudinary)

APS 的写法建议是:数据引用最好包含创建者、年份、仓库名、持久标识符(最好 DOI),并在 Data Availability Statement 里引用这条参考文献。(Cloudinary)

4) DOI or URL

如果你还没有上面的 reference number,就在这里填 DOI 或者审稿可用的链接(有些仓库支持 private link / embargo link)。

  • 最推荐:直接填 DOI(例如 10.5281/zenodo.xxxxxxx)。(Cloudinary)
  • 如果 DOI 还没生成:填仓库给的可访问 URL(能让编辑/审稿人访问即可)。

5) Date Available(如果有 embargo)

如果你选 Yes 但要延迟公开(embargo),这里填预计公开日期(按它提示的格式,例如 01Jan2026)。
如果不 embargo,一般留空。


三种最常见填写路径(你对号入座就行)

  1. 有数据/代码要放公共仓库
    → Add Dataset;Description 写清楚;选 Yes;填 DOI/URL;有编号就填 reference number;有 embargo 就填日期。

  2. 纯理论/没有新数据,或所有数据都在正文/补充材料
    → 通常不要 Add Dataset;去选系统提供的声明模板(类似 “No data were created or analyzed …” / “All data … available within the publication”)。(Cloudinary)

  3. 数据不能公开(保密/商业/安全等)
    → 选 No;后续声明里要说明限制原因,并按要求在合理请求下提供(至少对编辑/审稿流程可提供)。(journals.aps.org)


如果你告诉我你属于上面哪一种(比如:有实验原始数据要放 Zenodo / 纯理论 / 数据在 Supplemental / 受限不能公开),我可以直接帮你把:

  • Description 怎么写(英文一两句)
  • 以及最终 Data Availability Statement 应该长什么样(按 APS 常用措辞) 一起拟好。

Pregunta

我想知道我该怎么把数据放在公共仓库里,我目前使用的所有数据都在几个origin文件下。我能否上传我的origin文件呢?

Pensamiento

Guiding data deposit and citing with Zenodo

To deposit data, I recommend repositories like Zenodo, Figshare, or OSF. While Origin files (.opj) can be uploaded, it’s better to provide raw data in open formats like CSV or ASCII. Include a README, scripts, version, and license. I’ll guide through using Zenodo: upload data, add metadata, reserve DOI, set embargo, and tag as "dataset." Include a Data Availability Statement with a DOI/URL reference. I’ll cite APS guidelines for correct data citation.

Thought for 21s

Respuesta

可以的:你当然可以把 Origin 工程文件(一般是 .opj / .opju)一起上传到公共仓库,但我强烈建议不要只上传 Origin 文件——因为它是专有格式,很多读者/审稿人未必有 Origin 或能顺利打开。更稳妥的做法是:

  • Origin 文件作为“可复现便利包”附带(可选但很有用)
  • 同时导出一份开放格式的数据(CSV / TXT / TSV 等)+ 必要的说明文档(README)
  • 若有数据处理脚本,也一起放上去(Matlab/Python/Origin 的脚本都行)

APS 的 Data Availability Statement 本质上就是要你把“支持结论的数据/代码材料”放到可靠仓库,并在文章里给出可访问的持久链接(最好 DOI),而且如果公开可用,建议把数据集作为参考文献引用,并在声明里引用它。 (APS Journals)


推荐的上手方案:用 Zenodo(最省心、最常见)

Zenodo 的优点是:免费、可设置 embargo、能生成 DOI,适合 APS 这种需要“持久标识符(preferably DOI)”的要求。(Cloudinary)

你可以按这个“打包标准”准备文件

建议你仓库里至少有这些:

  1. 开放格式数据(必做)
    从 Origin 里把每个关键图/表对应的数据导出为:
  • fig1.csv, fig2.csv …(或按样品/温度命名)
  • 原始数据也可以放 raw/ 文件夹,处理后的放 processed/
  1. README(必做)
    写清楚三件事:
  • 每个文件对应论文哪里(Fig. 1 哪条曲线、Table I 哪列)
  • 数据列含义、单位、坐标含义(比如 B(T), R(Ohm)
  • 从 raw → processed 的处理步骤(哪怕只是文字说明)
  1. Origin 工程文件(可选但推荐)
    .opj/.opju 放进 origin_project/,并在 README 里写:用哪个 Origin 版本打开、图层/拟合在哪个 workbook。

  2. (如果有)分析脚本/参数(推荐)
    比如 Python 拟合脚本、Origin 的 LabTalk/脚本、拟合参数表等。

直觉判断:APS/审稿人想要的是“能支撑并复现关键结论的最小数据集”,不一定要把你电脑里所有中间文件都倒上去,但关键图表对应的数据和处理说明最好齐。(APS Journals)

在 Zenodo 上发布的关键点

  • 创建 upload,上传一个 zip(里面按上面结构放文件)也行
  • 填标题、作者、描述、关键词、license(常见:CC BY 4.0 或 CC0;代码用 MIT/BSD 也很常见)
  • 需要保密到发表再公开:Zenodo 可设置 embargo,到某日期自动公开;APS 投稿系统里你就把这个日期填到 “Date Available”。(APS Journals)
  • 发布后拿到 DOI(最理想),回到 APS 投稿系统的 “DOI or URL” 填进去

回到你截图的 APS 表单:该怎么填

等你拿到 DOI/链接后:

  • Description:一句话说明“这些数据支持哪几幅图/结果”
  • Will this data be publicly available?:选 Yes
  • DOI or URL:填 Zenodo DOI(最推荐)或公开 URL
  • Reference number:如果你已经把数据集作为参考文献加进稿件(比如 [45]),这里填 45;没确定就先不填,接受后/校样阶段再补也行。(Cloudinary)

你问的核心问题:我能否只上传 Origin 文件?

能上传,但不建议只上传。
最稳妥是:CSV/TXT(开放格式)+ README(说明)作为主交付,Origin 文件作为补充。这样即使读者没有 Origin,也能直接用任何工具读数据;而想完全复现你出图流程的人还能用 .opj。这也更符合 APS 鼓励“可获取、可验证”的初衷。(APS Journals)


如果你愿意,把你论文里最关键的 2–3 幅图(Fig. 1/2/3)大概是什么数据(比如电阻-磁场、XRD、拟合曲线之类)跟我说一下,我可以直接给你一份:

  • 你在 Zenodo 里该用的文件命名方案
  • README 模板(英文,按 PRB 风格)
  • 以及你在 APS 表单里 Description 应该怎么写(一句话版)

Pregunta

我已经注册了Zenodo,怎么上传数据呢?(我想了想,打算把origin里面的数据copy到txt或者csv里)

Pensamiento

Providing step-by-step Zenodo upload guidance in Chinese

I’ll provide step-by-step instructions in Chinese for uploading to Zenodo, including exporting data to csv/txt, recommending file packaging, and including metadata. I'll cover the upload steps, caution about reserving DOI without deleting drafts, and mention file size limits. Additionally, I’ll include advice for publishing and filling out the APS form.

Thought for 47s

Respuesta

可以的,你的思路(从 Origin 导出成 txt/csv 再上传 Zenodo)是最稳妥、也最符合期刊“可复用/可读取”的习惯做法。下面给你一套从准备文件 → Zenodo 上传 → 拿 DOI 回填 APS的具体步骤。


1) 先把数据包整理好(建议这样放)

必备(强烈建议)

  • README.txtREADME.md:说明每个数据文件对应论文哪张图/哪条曲线、列含义、单位、处理步骤。
  • data/:导出的开放格式数据(CSV/TXT/TSV)

可选但推荐

  • origin_project/xxx.opju(或 .opj):作为复现你出图/拟合流程的补充(但不要只放它)。
  • scripts/:如果你还有拟合脚本/参数表也放上。

小技巧(从 Origin 导出时)

  • 导出时让第一行包含列名(header),并在 README 里写清楚单位。
  • 统一小数点为 .(避免地区设置导致逗号小数点)。
  • 文件命名尽量能看懂:fig1_RvsB_2K.csvfig2_fit_params.txt 这类。

如果文件很多:Zenodo 单条记录最多 100 个文件,总量一般 50GB/record;超过 100 个文件建议打包成 zip。 (Zenodo)


2) 在 Zenodo 上传(网页操作步骤)

  1. 登录 Zenodo → 进入上传页面(一般是页面右上角 Upload / New upload)。
  2. 点击 “New upload / Create new upload”(新建一条记录)。 (Zenodo)
  3. 在“Files/Upload”区域把你的文件 拖拽上传(或点按钮选择文件)。上传完成后你会在列表里看到每个文件。 (Zenodo)
  4. 填元数据(metadata),至少这些别漏:
    • Upload type / Resource type:选 Dataset(数据集)
    • Title:建议类似 “Data for: <你的论文题目简写>”
    • Creators:作者列表(至少通讯作者/数据整理者)
    • Description:一段话说明数据内容 + 对应图号(后面我也可以帮你写)
    • Keywords:PRB 常用关键词
    • License:数据常见用 CC BY 4.0CC0(看你组里习惯)
  5. 设定公开方式(Access right):
    • 想现在就公开:选 Open access
    • 想等论文接收/发表再公开:选 Embargoed access 并填日期(这和你 APS 表单的 “Date Available” 对应)
      Zenodo 的协作/共享功能也支持对受限/embargo 文件用“secret link”等方式分享给审稿人/合作者(如果你需要)。 (Zenodo)

3) 提前拿 DOI(用于投稿阶段非常有用)

如果你现在就想把 DOI 填到 APS 系统里(即使你还没最终发布),可以在草稿里 先 Reserve DOI

  • 在 DOI 相关区域回答 “Do you already have a DOI?” 选 No
  • 然后点 “Get a DOI now!”(Reserve DOI) (Zenodo)

⚠️注意:Zenodo 文档明确提醒:如果你删除这个 draft,会丢失已保留的 DOI。 (Zenodo)


4) 发布(Publish)与后续修改的规则

  • 第一次 Publish 后,Zenodo 会给你 两个 DOI
    • 版本 DOI(对应这一次发布的具体版本)
    • 概念 DOI(concept DOI)(代表所有版本,通常指向最新版本) (Zenodo)
  • 以后如果你要改数据文件(不是仅改描述),走 New version,会生成新的版本 DOI。 (Zenodo)

对论文最严谨的做法:引用“与你这篇 PRB 对应的那个版本 DOI”,这样别人复现时不会被你后续更新影响。


5) 把 DOI 回填到 APS 你截图那个表单

  • DOI or URL:填 Zenodo DOI(例如 10.5281/zenodo.xxxxxxx
  • Date Available:如果 Zenodo 设了 embargo,就填同一个日期
  • Reference number:等你把 Zenodo 数据集作为参考文献加入稿件后,再把它的编号填进去(投稿阶段不确定编号也很常见)

如果你把下面两点告诉我,我可以直接给你一份“可直接粘贴”的 Zenodo Description + README 模板 + APS 表单 Description(英文):

  1. 你的数据主要支撑论文哪些图(Fig. 1–3 之类)
  2. 数据类型大概是什么(比如 R–B 曲线、拟合参数、原始谱图等)

Pregunta

Cover letter.docx

好的,我现在在写prb期刊的cover letter,你能帮我看一下,并润色吗?

Pensamiento

Polishing cover letter and providing citations

I'll craft a polished version of the cover letter in English, without code or email formatting—just plain text. I’ll include citations referencing the uploaded document, such as "你原稿里..." for lines L1-L29. Along with the revised letter, I will provide key editing notes and optional additions like suggested reviewers if needed.

Refining cover letter phrasing

I’ll make the following improvements:

  • Change “Dear Editor(s),” to “Dear Editors,” for consistency.
  • Adjust the phrasing to “to Physical Review B for consideration for publication.”
  • Clean up the author list with "co-authored by."
  • Shorten the summary paragraph for clarity.
  • Reword the sentence about strain-induced magnetic order for precision.

Clarifying and polishing cover letter

I’ll make the following refinements:

  • Replace “not inconsistent with the results” with “consistent with.”
  • Correct “thin film and induce” to “thin films and can induce.”
  • Change “potential SDW state as the ground state” to “a spin-density-wave (SDW) state as a candidate ground state.”
  • Add the significance of the paper and clarify author declarations.
  • Adjust address and institution lines for proper formatting and capitalization.

Finalizing the polished letter

I’ll tidy up a few things:

  • The affiliation looks good as it is: "Key Laboratory of Magnetism and Magnetic Functional Materials, Ministry of Education."
  • I'll keep “Zhenhua Li” as it was written.
  • I'll consider removing "Website" unless the user prefers it included.
  • The letter is in English, with a brief Chinese explanation.

Now to finalize the letter, ensuring all formatting is coherent and professional.

Thought for 1m 27s

Respuesta

我看了你这份 cover letter 的原稿内容(主要在称呼、措辞严谨性、句子过长、以及 PRB/APS 更常见的写法上做了精修)。(Cover letter.docx) 下面给你一版可以直接替换粘贴的英文润色稿(信息保持不变,只是表达更“期刊投稿化”):


润色后版本(可直接用)

Key Laboratory of Magnetism and Magnetic Functional Materials, Ministry of Education
Lanzhou University
Lanzhou 730000, Gansu, China

January 28, 2026

Dear Editors,

I am pleased to submit our manuscript entitled “Strain-induced magnetic order in RuO2 from first-principles calculations” for consideration for publication in Physical Review B. The manuscript was coauthored by Wending Liu, Xiaoyu Feng, Jun Zhao, Dangwei Guo, Desheng Xue, Mingsu Si, Zhenhua Li, and Xiaolong Fan. I, Xiaolong Fan, will serve as the corresponding author (Email: [email protected]; Key Laboratory of Magnetism and Magnetic Functional Materials, Ministry of Education, Lanzhou University, Lanzhou 730000, P. R. China).

In this work, using epitaxial RuO2 thin films grown on TiO2 substrates as a representative system, we systematically investigate the magnetic ordering in RuO2 under epitaxial strain from first-principles calculations. We show that substrate-induced strain can drive RuO2 from a nonmagnetic (NM) state to an antiferromagnetic (AFM) state. Importantly, this strain-induced magnetic order does not rely on introducing a Hubbard U (i.e., it persists in standard DFT), and the AFM state retains a band structure and Fermi surface similar to the NM case, supporting consistency with ARPES and quantum-oscillation observations. Moreover, when the global strain approaches the critical value separating the AFM and NM phases, we find that local lattice distortions can strongly affect the magnetism and stabilize a spin-density-wave (SDW) ground state. We further characterize the SDW state and elucidate why local distortion favors SDW order. These results provide a theoretical framework for the SDW scenario proposed in Phys. Rev. Lett. 132, 086701, and broaden the strain-engineering parameter space for RuO2.

This manuscript has not been published previously and is not under consideration for publication elsewhere. The authors declare no competing interests.

Thank you for your consideration. We look forward to your response.

Sincerely,

Xiaolong Fan (on behalf of all authors)
Email: [email protected]
Address: No. 222 South Tianshui Road, Lanzhou 730000, Gansu, P. R. China
Website: www.lzu.edu.cn


我改动的要点(你也可以对照自行微调)

  • 把 “Dear Editor(s)” 改成更常用的 Dear Editors;把 “for publication Physical Review B” 改成更标准的 for consideration for publication in PRB。(Cover letter.docx)
  • 把你原来那段很长的研究总结拆句,并把 “not inconsistent with …” 改成更正向、更常见的 supporting consistency with …(语气更自信但不过度)。(Cover letter.docx)
  • “independent of DFT+U” 这个说法容易让编辑误解为“与 DFT+U 无关/没用到”,我改成更清晰的:不依赖引入 Hubbard U,也就是说标准 DFT 下就出现(更准确表达你的原意)。(Cover letter.docx)
  • 结尾把 “We hope… And we are looking forward…” 合并成更自然的 closing。(Cover letter.docx)

如果你愿意,我也可以顺手帮你加上 PRB cover letter 里“可选但常见”的两句(不加也完全没问题):稿件类型/栏目适配(例如 Magnetism, correlated oxides 方向)以及一句话强调主要 novelty(编辑更容易秒懂亮点)。

Compartir este Q&A