-
Notifications
You must be signed in to change notification settings - Fork 16
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
Managing invalid PMID used in non-pubmed sources #31
Comments
it looks not in the PMID source file:
|
but present in the ISTEX ids file
So it might be present in the ISTEX metadata as provided by the publishers, but not in the mapping file DOI/PMID. It is actually not a valid PMID -> https://www.ncbi.nlm.nih.gov/pubmed/16262981 This DOI does not correspond to a real article but to an index of a Cambridge journal. I think it's fine not to map it to anything indeed with the lookup service, as it's not a valid PMID anymore. But I am not so sure how to deal with it in the full record. |
right... one thing I notice is that we do not use the pmid information from the istex mapping but only from the pmid file (which should be the authority here, isn't it?). |
Yes I think it makes sense to complement like that the pmid lookup. The main issue is then that the publisher metadata are not well maintained. When a PMID becomes invalid at PubMed (which is the reference), apparently they are not removed from the publisher metadata and we would have invalid mapping via the istex data file. The submodule So I would suggest to wait until I review the |
http://localhost:8080/service/lookup?pmid=16262981 results in 404
However it is the PMID indicated by this record, so it exists !
http://localhost:8080/service/lookup?pii=S0266462305050762
The text was updated successfully, but these errors were encountered: