Linkouts to PubMed from AmiGO and Noctua giving 503 error - wrong URL in dbxrefs

[vanaukenk]

I'm not sure if anyone else has reported this, but I'm finding that linking out from AmiGO or Noctua to PubMed is giving a 503 error because of what looks like a change to the PubMed URL.

In our dbxrefs.yaml we have:

http://www.ncbi.nlm.nih.gov/pubmed/[example_id]

but I think the url should now be:

https://pubmed.ncbi.nlm.nih.gov/[example_id]

Compare:

http://www.ncbi.nlm.nih.gov/pubmed/38936225/

to:

https://pubmed.ncbi.nlm.nih.gov/38936225/

I can make the update to the dbxrefs.yaml, but would like another pair of eyes to confirm this before I do. Thanks.

@kltm @suzialeksander @pgaudet

[pgaudet]

Interesting, because for me that link is redirected

But it does seem like PubMed changed their URL.
I see that P2GO has the same URL as AmiGO.

I would assume we can get the up-to-date info here: https://registry.identifiers.org/registry/pubmed
but I don't find it.

[kltm]

The forward works for me, so no "problem" that I've been able to duplicate; this goes back to whatever the canonical URL/identifier is supposed to be, which can sometimes be hard to pin down. That said, I don't think there is any problem in updating to what they currently forward to in dbxrefs.yaml, as it is the namespace forwarding metadata, rather than direct identifier metadata.