`scholarly.search_pubs` runs forever about scholarly HOT 6 CLOSED

Google Scholar actively tries to block programmatic queries that search its publication database but allows queries that search authors database. If you especially want to get info about a specific publication many times over a time period (say regularly track its citation count), I'd recommend going the author's profile page way.

from scholarly.

This is likely a transient issue due to unavailability of reliable proxies. If you tried it again with no proxies (not recommended to do regularly), it should work or try running the code as it is after some time.

from scholarly.

And whenever possible, try fetching a paper via any of the author's profile. In this instance, you could use search_author_id routine to look for papers by 9TqkClQAAAAJ and iterate through the publication list.

from scholarly.

This is likely a transient issue due to unavailability of reliable proxies. If you tried it again with no proxies (not recommended to do regularly), it should work or try running the code as it is after some time.

Yes, running the code without the proxies works.

And whenever possible, try fetching a paper via any of the author's profile. In this instance, you could use search_author_id routine to look for papers by 9TqkClQAAAAJ and iterate through the publication list.

Why is that? I am looking for a specific paper, which has a uniquely identified by its DOI. Performing a search query for the author instead of the unique DOI and then filtering the results seems like a very circuitous way.

from scholarly.

Google Scholar actively tries to block programmatic queries that search its publication database but allows queries that search authors database. If you especially want to get info about a specific publication many times over a time period (say regularly track its citation count), I'd recommend going the author's profile page way.

Thanks for pointing this out!

from scholarly.

I tried running your snippet again with FreeProxies and after a few attempts, it did successfully print the paper details. This was likely due to #465 which has now been fixed. Closing this issue as completed.

from scholarly.