- Product: Aleph
- Product Version: 20, 21, 22, 23
- Relevant for Installation Type: Dedicated-Direct,Direct,Local,Total Care
There is a problem with publishing to Primo using the reshelving option such that an item remains indefinitely at a status of unavailable.
When an item gets returned in Circulation it is triggered for republishing to Primo. If the library is configured for reshelving in tab14, when the record gets published again it has a status of unavailable in the AVA due to the reshelving status. The problem is that once the reshelving period expires, the record never gets triggered for republishing to Primo. This results in a record that is not checked out but is faceted in Primo as if it were unavailable, because it was never republished with a status of available.
This is a large issue for users who use facets to limit to items that are available. These items will incorrectly be missing from that facet indefinitely.
Remove the RESHELVING=Y parameter from the expand_doc_bib_avail (and/or expand_doc_bib_avail_hol) line, but leave it for the x-server ("X-AVAIL") line.
Thus, a returned item will get published as Available and Primo will create the facets as if the item is available.
But RTA will present the item as unavailable for the length of time configured in tab14. After that time has passed, the facet and real-time will be back in sync.