Skip to content

Add TR prefix for NTP Technical Reports - #1840

Open
cbizon wants to merge 1 commit into
masterfrom
add-ntp-technical-report-prefix
Open

cbizon wants to merge 1 commit into
masterfrom
add-ntp-technical-report-prefix

Conversation

@cbizon

@cbizon cbizon commented Oct 20, 2026

Copy link
Copy Markdown
Collaborator
  • Add TR to prefixes, as https://cebs.niehs.nih.gov/cebs/publication/.
    • Several ROBOKOP graphs (CEBS-sourced edges, infores:cebs) cite National Toxicology Program Technical Reports in publications as TR:TR-128, TR:TR-576, and so on.
    • Neither Biolink nor Bioregistry had a prefix for these, so the CURIEs didn't expand.
    • CEBS serves each report at this URL with the TR- id exactly as written. For example, TR:TR-128 expands to https://cebs.niehs.nih.gov/cebs/publication/TR-128, the "Bioassay of 3,3'-Dimethoxybenzidine-4,4'-diisocyanate for Possible Carcinogenicity" (NTP's own page: https://ntp.niehs.nih.gov/publications/reports/tr/tr128).
    • TR-576, TR-372 and TR-540 resolve the same way.
  • Add TR to publication's id_prefixes. The ids name publications (the reports), alongside PMID, PMC, doi and NLMID.

On the name: TR is short and generic, but it's what the data already uses. A longer prefix (e.g. NTP.TR) would mean rewriting the ids downstream; happy to change it if that's preferred. The prefix should also be registered with Bioregistry.

Checked locally: yamllint, make lint (no problems) and make test-python (25 passed).

- Add `TR: https://cebs.niehs.nih.gov/cebs/publication/` to prefixes. ROBOKOP's CEBS edges
  cite National Toxicology Program Technical Reports as `TR:TR-128`, `TR:TR-576`, ...; CEBS
  serves each report at that URL with the `TR-` id as written, so the CURIEs expand to working
  pages. Neither Biolink nor Bioregistry had a prefix for these.
- Add `TR` to `publication`'s `id_prefixes`, since these ids name publications (the reports).
@cbizon
cbizon requested a review from sierra-moxon October 20, 2026 19:31

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant