Hi Paul,
Interesting discovery. I suspect that what you are in fact encountering is Elasticsearch's default pagination limit, which is set at 10,000. This was introduced in Elasticsearch 2, and as we learned, can also affect large search and browse result sets, per this older issue that describes the problem a bit more:
The consequences of this for AtoM users as described on the issue ticket:
This means that for uses with 10,000+ records in an AtoM installation, trying to navigate to any page above 1,000 in the search/browse results (when the results per page setting is set to the default value of 10) will lead to an Elasticsearch error.
We wanted to avoid increasing this value as the new default, because doing so also increases the amount of memory required for AtoM to run smoothly. Consequently, in AtoM 2.5 and later, the workaround we provided at the time was to add the ability to change the sort direction of results from ascending to descending, and vice versa. That way, if a user was looking for results past the first 1,000 pages of results, they could reverse the sort direction and see the remaining results from the other side (i.e. as the first results in the new sort order, instead of the last). See:
Nevertheless, this was still a workaround, and may not meet the needs of larger institutions. In the upcoming 2.7 release, we've therefore made it easier to change this value via configuration file, as described here:
Previously this value was hardcoded in a few places, making it more difficult to change in earlier versions. If you have a development environment, you could possibly try applying the relevant pull request as a patch, but be sure to back up any data first!
Keep in mind that you should also only make this change if you have a good amount of RAM assigned to your installation - increasing this pagination value will increase the cost of queries!
Regards,
@accesstomemoryhe / him