-
-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PubMed preferred prefix should be PMID #323
Comments
There are several reservations about this requst:
Assessing the CommunityI think it's very difficult to say if there actually is a consensus on what prefix should be used for PubMed, and if so, what that is. There's lots of different camps for We can take a look at the Bioregistry's page for PubMed to see which registries use which prefix. GO is actually the only external registry Bioregistry aligns on that uses Anyone who standardized on Identifiers.org will therefore be using
Further, anyone who has already started standardizing based on the Bioregistry will be using
Impact of ChangeA big question remains: if we change something so widely used in the Bioregistry, then all of these people would have to update their data too. BlockersNCBI InvovementThe Bioregistry does not list a contact person for PubMed. I think it would be valuable to identify an individual from the NCBI who can participate in this discussion and authoritatively speak on the issue. Alternate SolutionsFor people who want to immediately use
|
Hmm.. Usually your arguments convince me more.. You are trying to pitch personal aesthetic preference against current practice and even turn against PubMed as a whole and their own choice of prefix. I am not swayed (yet). orcid also has the ID in it. I still think PMID should be canonical, but I am happy to change my mind of new arguments arise. |
I also would strongly favor adding PMID as the preferred prefix. It’s just the prefix that has been used in many applications forever and publicized on Pubmed itself. |
People in Zhiyong Lu's group at NCBI should be qualified to comment: https://www.ncbi.nlm.nih.gov/research/bionlp/Team |
@cthoyt - I just want to be clear that while I think we could advocate for |
I chatted in PM with @sierra-moxon and she agreed to take the lead in writing up a more structured set of arguments to support changing from |
@rleaman can you help us identify a responsible individual for PubMed that can join our public discussions on GitHub about how to best reference PubMed identifiers? |
The person at NCBI who could most authoritatively comment on the preferred prefix / CURIE for PubMed would probably be in engineering. I'll figure out who that would be (I am in research) and follow up. My opinion, for what it's worth: this seems like a case of a reasonable standard (e.g. "ID" shouldn't be part of the prefix) conflicting with a case ("PMID") that is probably both (1) better known than the standard and (2) predates the standard (e.g. https://pubmed.ncbi.nlm.nih.gov/15048644/). But I don't think that "pubmed" is unclear, and I don't have a good sense for how many people are using each one overall. While the literature isn't the best use case for CURIEs, we can use it to try to get a sense of what's actually used: my best guess is that "pmid" is over 10x more popular than "pubmed." [Specifically: the number of times that "pmid" appears followed by a colon or a 7- or 8-digit number is 27,372. The number of times that "pubmed" appears followed by a colon or a 7- or 8-digit number is 2,037. Data is for case-insensitive bigram counts of PubMed and the PMC text mining subset, through early 2020.] |
I've made some inquiries here at NCBI. For PubMed, we would prefer pubmed:123456 rather than using the more obscure "PMID". This is consistent with the pmc:PMC5678910 that we already discussed where the resource is the prefix. The difference between pubmed and PMC (and most other ncbi databases) is that the PubMed ID is just an integer. They do not define the Accession ID structure like we have in PMC (PMC999999.9). So pubmed:45678910 would be the best option. |
@jeffbeckncbi thank you for inquiring. As this is an extremely consequential and costly decision I would really like to know who is "we" in "we would prefer" and what steps NCBI is taking to replace their own usage of PMID in all their websites and resources with pubmed:123. Is their a concrete plan to depreciate use of PMID across the organisation? |
@matentzn I answered this question about the prefix for a PubMed CURIE as a followup to my response about PMC CURIEs (#965) There is no intention to change the label on the pubmed identifier on the pubmed site to use CURIEs, but if you are trying to write CURIEs for both the pubmed and pmc resources, identify the resource in the prefix and don't just use the abbreviation for pubmed id. I am the Program Head for Literature at NCBI - the group that runs PubMed and PMC at the US Library of Medicine. And I consulted on the question of CURIE prefix for these resources with NCBI leadership |
Thank you for the clarification, I didn't see that discussion - followed up now. I will come back to you soon! |
@jeffbeckncbi thank you, having an authoritative voice on this is incredibly valuable. @sierra-moxon It's still the Bioregistry Review Team policy to weigh all arguments, even those contrary to the Identifier Space Owner (ISO). If you are still willing to write up a more detailed argument (I mentioned in #323 (comment) that you had already agreed to do this), then the Bioregistry Review Team can consider this. If you're still interested in doing that, do you think you could do it by the end of this week? |
I think @rleaman's simple search for the prefix in the corpus of publications before 2020 in this thread paints a good picture of the usage and I imagine others on this thread to be better than I at justifying. To clarify again, my ask on this ticket was to simply add a Bioregistry Here are several more resources (besides the Gene Ontology) that use
|
As per conventions and pubmed itself, pubmed IDs should be prefixed with PMID:
Example page with a PMID: https://pubmed.ncbi.nlm.nih.gov/35189623/
Blocked By
The text was updated successfully, but these errors were encountered: