We'd like to be able to expand our use of floating at our library, but we're on hold until this functionality is developed to support regulation of both overall limits and limits on # of titles. For a multibranch public library, we need to minimize "pooling" and spread our copies of any given title across our system. Thank you.

It is one thing to have a holiday collection, you want to control how many items you want on the shelves for it but, you also don't want some material types or too many copies of a material type located on those shelves.

Having the functionality to set collection limits and prevent pooling of too many duplicate copies at individual branches would help solve a lot of our float issues.

My library switched to Polaris last August, and we are just running into this. Now that we have floating enabled, we really need to be able to set collections limits and have the ability to set limits to prevent duplicates. We have smaller branches that only have so much space, so we have to be intentional about how many items can float to those locations. We also do not want three copies of a title in one location.

Adding this functionality would be life changing for my library system. As a 9 branch library that floats all youth materials, we spend countless hours each week manually rebalancing and shifting items across branches to alleviate pooled duplicate copies, which takes away from time and energy we could be using to address other collection management issues.

It would be very helpful to us to be able to set both the collection size for a branch and the number of copies! Right now we have to deduplicate and redistribute extra copies manually.

This would be great to have as we are currently looking into and testing using floating via collection but without the ability to then have the material type limit, this will cause issues with our smaller branches having shelves clogged with multiple of the same title.

We've struggled with this limitation for years. Floating by collection is important/necessary for some items, whereas, floating by material type is better for others. Also, we're in a consortium and it is a systemwide setting. Not all member libraries have the same philosophy about floating so it is problematic.

This is very important to reduce the amount of items that go unused because they remain stuck in one location and therefore seen by a fraction of users.

This is extremely important as duplicates reduce the amount of unique material our patrons see and have a choice of while browsing our shelves. Please fix this soon!

Not having this functionality is terrible in a large system with many branches.