Add precursor mass/charge range columns to DDA template

[jonasscheid]

Summary

• Adds two new optional columns to the DDA acquisition template as suggested in Suggestions to SDRF v1.1.0 #774:
  • comment[precursor mass range] — precursor mass range for database search (e.g., 800:2500)
  • comment[precursor charge range] — precursor charge range for database search (e.g., 1:3)
• Columns added to both sdrf-terms.tsv and the DDA template README.adoc (HTML and AsciiDoc table sections)

These values are commonly defined in MS acquisition methods and parsed directly into search engines. Adding them as optional DDA columns improves reproducibility and enables automated reanalysis workflows.

Closes #774 (point 3)

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[jonasscheid]

The link-check CI failure is pre-existing and unrelated to this PR. The three broken links are in files not touched by this PR:

• README.md: https://github.com/bigbio/proteomics-metadata-standard/blob/master/llms.txt → 404
• README.md: https://eubic-ms.org/ → timeout
• VERSIONING.adoc: https://github.com/bigbio/.../CHANGELOG.md → 404

[ypriverol]

@jonasscheid we don't have terms for that, but we do have them in PRIDE in this way:

MS max charge: https://www.ebi.ac.uk/ols4/ontologies/pride/classes/http%253A%252F%252Fpurl.obolibrary.org%252Fobo%252FPRIDE_0000473?lang=en
MS min charge: https://www.ebi.ac.uk/ols4/ontologies/pride/classes/http%253A%252F%252Fpurl.obolibrary.org%252Fobo%252FPRIDE_0000472?lang=en

Under file properties we do have also intervals for RT and others: https://www.ebi.ac.uk/ols4/ontologies/pride/classes/http%253A%252F%252Fpurl.obolibrary.org%252Fobo%252FPRIDE_0000471?lang=en

[jonasscheid]

Ah! That is good to know! Is MS scan range == MS min MZ : MS max MZ?

Would be good to extend this ontology also with MS min IM and MS max IM or MS IM range for ion mobility experiments if we are using them here

I would include them all as Optional, since you definitely need to define this in you MS device method