When adding a 2026 on-order item to a serial record, that volume doesn’t appear as an option for placing a volume-level hold UNLESS there is something in its barcode field. If we add a number in barcode, then the 2026 volume does appear as an option when placing a hold.
This is different behavior than for on-order bib-level or item-level holds, which do not require anything in the barcode field for the hold to be placed. We don’t understand why a volume-level hold should need any barcode, if the item’s volume field is all that’s needed to select the right volume. The problem exists for both serial and multivolume monograph bibs (e.g. the new volume of a graphic novel).
We’ve been adding random numbers in the barcode field when we discover this situation, usually after a user asks why they aren’t able to select the new volume for a hold. We do not add barcodes for any other type of on-order item, and it is not feasible for our acquisitions staff to look for this at ordering, even if they knew what they were looking for.
Our catalogers reported this issue - our ticket is 08008327 - We were told that "by virtue of being part of a serial record, Polaris needs the item to be fully cataloged (with barcodes) so that it can be sure the correct version is being selected. "
Do add this to the ideas and let us know when posted and I’m happy to vote on it. I’ve been frustrated by this issue myself and can only imagine patrons struggle more so. I didn’t discover the barcode trick-- so thanks for sharing that. I’ve relied on item-level holds, but this is never ideal when multiple copies of a volume will be purchased.
Thanks @smcclain, our site manager basically said that too, but of course it doesn’t seem to make sense when the volume field should be enough. My consortium is asking them for clarification. It appears if you attempt an item-level hold in Leap on one of these items (that has volume but no barcode) and select “first available copy” in the pop-up, it WILL place a volume-level hold. We are thinking this should also be possible when attempting a hold in the PAC, or bib-level hold in Leap.
If we add an idea in the exchange, we’ll be sure to follow up here when it’s posted.
Interesting… Are y’all using the PAC? we are using Vega. We’ve found many things that would work in the PAC, that don’t work in Vega. Honestly, we haven’t been using the first available copy thing (which was something we loved in the demo) since we went live 8 months ago. I’ll need to investigate.
