-
Notifications
You must be signed in to change notification settings - Fork 773
Allow paging #43
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
Comments
* Since numer of results is limited to MAX_PAGE_RESULTS (20), the 'start' parameter allows offsetting the search for paging. fixes ckreibich#43
I thought after this patch iteration should be as easy as continuously calling querier.send_query(query) and updating query.start if len(querier.articles) == query.num_results and break otherwise. But that somehow lists results repeatedly up to a certain seemingly number... Is there still a plan to implement iteration? |
👍 |
I'd also like this feature |
how should start parameter set? I am not familiar with python. I would be appreciated If you could help. |
In the PR #44 it is not possible via the command line, just in your own code. After initializing your Query you have to use the method set_start.
|
thanks. this is apart of my code:
but it has this error:
|
Yes, that is because this Pull Request is not merged yet and so it is not included in the main branch. You have to get the code from #44 |
Concerning the usage, @eknoes is right,
and then, if paging is due:
|
I change to code according to commit and then add this number: but it find only 20 articles again. |
It will always find a maximum of 20 articles per page. You got article 100 to 120! |
No, i find only 20 articles at all. |
Allow paging to receive results >20. Can be done with Google Scholar's search parameter 'start'.
The text was updated successfully, but these errors were encountered: