Skip to content
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.

Sign up for GitHub

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

Jump to bottom

/pubmed/query returns 400 error #42

Open
paulalbert1 opened this issue Nov 15, 2021 · 0 comments
Open

/pubmed/query returns 400 error #42

paulalbert1 opened this issue Nov 15, 2021 · 0 comments
Assignees
@sarbajitdutta

Comments

@paulalbert1
Copy link
Contributor

paulalbert1 commented Nov 15, 2021 •
edited
Loading

Update: to be more specific, the problem is that the PubMed Retrieval API /pubmed/query is returning a 400 error. This may have to do with the API_KEY being wrong or blocked.

(The count API, which does not rely on the API_KEY I think, does work: /pubmed/query-number-pubmed-articles/.)

Screen Shot 2021-11-16 at 8 34 44 AM

Today is Nov. 15. The last new publication added to ReCiterDB is from Nov. 10.
Screen Shot 2021-11-15 at 8 34 56 AM

An example of a publication that should appear is 34776100 for klk9001.

This record won't but should appear if I run Feature Generator and select the ONLY_NEWLY_ADDED_PUBLICATIONS flag.
@paulalbert1 paulalbert1 transferred this issue from wcmc-its/ReCiter Nov 16, 2021
@paulalbert1 paulalbert1 changed the title Incremental lookup isn't working PubMed API returns 400 error Nov 16, 2021
@paulalbert1 paulalbert1 changed the title PubMed API returns 400 error /pubmed/query returns 400 error Nov 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sarbajitdutta sarbajitdutta

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@paulalbert1 @sarbajitdutta