Increase limit of "Export Results" records 10-fold, or 100-fold
Currently, Export Results limits one to a max. of 100 records per export iteration. This is clearly a policy decision, not a technical limitation. But, if a determined user can export 10,000 results simply by iterating through 100 export iterations of 100 apiece, then the policy is not enforceable, now, is it?
A simple use case describes the total inadequacy of a 100-record limit: I am piecing together disparate strands of a VERY common surname. There are tens of thousands of records of that surname in just the state of Maine, and just for vital stats years 1850 and prior.
When one starts with few known data points beyond a surname and a date range, the initial casting of the search "net" yields zillions of hits. Every. Time. No analysis is possible on an exported results set of 10, 20, 50, or 100.
Please change these export limits to permit 100, 200, 500, or 1000 ... or 5000! ... at a time.
I want to get 10,000 or 20,000 Search Results records into one Excel spreadsheet, and then use all the power of Excel to search and filter in ways that your tech team will never ... and SHOULD NEVER ... invest their limited time and resources to replicate. Please allow your fabulous resource to become that much MORE powerful by considering "Export to Excel" a valuable partner technique, not an alien, competing, rival technique.
Comments
-
I completely agree. This would be so incredibly helpful in being able to find the proverbial "needle in a haystack". Sometimes the top search results are not the ones you're looking for and a deeper dive is necessary. Exporting to Excel can make searching through large sets of data for an individual or family so much easier!
1 -
There must be some code-savvy people in this group that can provide a hack to overcome this truly frustrating upper limit. I anxiously await that work around.
0 -
Hello, has there been any progress on this? Having very painfully exported 89,000 Records results into a database (collection by collection, because otherwise the export doesn't identify the collection) I am now reaping the rewards, as others here have described. But I really can't face doing it again for other surnames, some of which have far more entries. Even periodically updating what I have to reflect updated collections is painful. It would be great to hear of any workarounds or plans.
0
