search

jonatasgrosman / findpapers

Findpapers: A tool for helping researchers who are looking for related works
MIT License
220 stars 32 forks source link

Query to IEEE database query returns zero results #1

Closed mistune closed 2 years ago

mistune commented 2 years ago

Issue description

Queries to IEEE return zero results

Steps to reproduce the issue

  1. Install using pip install findpapers inside conda environment, python version 3.9.12
  2. Install MSVC Build Tools 2022. See screenshot below
  3. Downgrade click to 8.0.4
  4. Enable python environment, execute findpapers search search.json -q "([artificial intelligence])" --databases "ieee" --token-ieee "mytoken" --token-scopus "mytoken" --limit 30

What's the expected result?

I should see papers from IEEE

What's the actual result?

Please see screenshot below

Additional details / screenshot

image

image

mistune commented 2 years ago

Please ignore item 3 above. This is because of a conflict with dependencies with having Spyder installed on the same environment.

jonatasgrosman commented 2 years ago

Hi @ZeroCommits, I couldn't reproduce your error. I think that maybe your IEEE token is invalid. Could you use the --verbose argument and post the output log here?

mistune commented 2 years ago

Hello @jonatasgrosman, please see the attached text files. Another issue happens (see debug-noscopustoken.txt) when I do not put my scopus token even though I am just using IEEE. debug.txt debug-noscopustoken.txt

jonatasgrosman commented 2 years ago

Hi @ZeroCommits! In your logs, I could see a lot of HTTP 403 errors happening. This HTTP code error is related to authorization issues. Try to generate new authorization tokens for Scopus and IEEE. For some reason, the ones you're using are probably invalid :(

mistune commented 2 years ago

Thanks for looking into this. I tried using the Dynamic Query Tool from the IEEE developer website with new API keys and also getting the HTTP 403 errors there. Registered for a new account and also getting the same error. Already asked support to look into this issue and will update this thread once I get a response.

mistune commented 2 years ago

Fixed after renewing API keys.