Comment 1 for bug 1218403

Having experienced this "workflow" many, MANY times (sad, I know), I'd love to see this as a bucket function. As far as use cases go, when separating out specific collections from another, we often need to change a large number of call numbers in the system to reflect the new collection. We've also had some inconsistent labeling over the years throughout the collections which makes collection report output nearly unusable without a lot of intervention. Fixing all these call numbers in EG has taken hundreds of hours because of the volume of variants. Our library did experience a pretty large amount of database neglect over the years, but I can't imagine that we're particularly unique from other small libraries (maybe even some larger libraries).