Auto-Split Record Sets Based on Recommended sizes for bulk changes
Once you create a record set, it's very annoying to try and break it into smaller record sets (ESPECIALLY in Leap). Given that bulk changes are supposed to be limited to 10k items or less (according to my site manager), it would be really helpful if there was a way to break up a record set into smaller ones. Ideally I could pick to split the record set in half or in multiple sets of maximum X records.
Idea Value
Libraries needing to manage their collection can bring their system to a halt if they make too big a change (and then bulk change may not finish and then the staff doesn't know which items were updated and which weren't). But cutting down the record set to a smaller size is a very tedious process in Leap.
-
AdminSamantha Quell (Admin, Innovative) commented
Now that the bulk change process for item and patron record sets in Leap is asynchronous in Polaris 7.6, It would be great if some libraries could try performing larger bulk changes in Leap to help identify if this is still needed for the bulk change scenario.
There are other enhancements covering requests for features like "load all" instead of the "more" action. Record sets will continue to load with only the first 250 rows so that the initial workflow load is fast and then the user can decide if loading all records within the record set is necessary. But in Polaris 7.7 we plan to make the "load all" process easier.