Hopefully easy to implement in the software. At present, when searching for member images or tags, Result XX appears in the lower left, where XX is any number up to the single page submission limit of 48. Search results with 1000 submissions will still display Result 48, making it difficult to characterize the searches one performs.
When searching from the web interface, the total number of submissions (though seemingly not the total number of pages of results, if more than 9) appears in the search headings:
Could this number be obtained in the API along with the first results page? This would not only give one a better idea as to the volume of a given download project, but would also:
Allow the easy computation of the number of pages to attempt to download, preventing the run-on process described in issue #25
Allow a progress percentage bar on the download page that would be somewhat indicative of the stage the project is in (though a great many submissions also have an indeterminate number of additional pages, making the %completion approximate without scanning the page value for every submission in the batch).
Hopefully easy to implement in the software. At present, when searching for member images or tags,
Result XX
appears in the lower left, where XX is any number up to the single page submission limit of 48. Search results with 1000 submissions will still displayResult 48
, making it difficult to characterize the searches one performs.When searching from the web interface, the total number of submissions (though seemingly not the total number of pages of results, if more than 9) appears in the search headings:
Could this number be obtained in the API along with the first results page? This would not only give one a better idea as to the volume of a given download project, but would also: