[OPEN-ILS-DEV] Details for un-available items
Bill Erickson
erickson at esilibrary.com
Mon Sep 15 11:00:44 EDT 2008
On Wed, 10 Sep 2008 22:33:55 -0400, Bill Ott <bott at grpl.org> wrote:
> I've been digging through rdetail.js trying to figure out a way to do
> this...
>
> If the last item at a location has a status that is not opac visible,
> then the only way to view it is through holdings maintenance, even
> though the staff client reports 0/1 (available/total), there is no call
> number row displayed.
>
> On the other hand, if there are say 4 damaged items, and still one
> available, you can see the details (i.e. barcode, status, location, etc)
> for all 5.
Hi Bill,
There is a disconnect between the copy count summary methods
(open-ils.search.biblio.copy_counts.summary.retrieve, which calls
open-ils.storage.biblio.record_entry.status_copy_count.atomic) and the
copy details display. The summary methods do not return counts for non
opac-visible copies, however, once it's time to render the copy details,
the OPAC fetches /all/ copies associated with a given volume, regardless
of status. If the summary method returns no items, the OPAC does not
attempt to retrieve any copies.
It comes down to how strict we want the definition of "opac visible" for
copies to be. If staff should see all copies, regardless of status, we
should add .staff versions of the summary methods to return counts of
copies of all statuses, regardless of their opac visibility. We'd also
need to make sure the opac renders all statuses in the status columns in
the staff client (though, I'd be concerned about the columns getting
scrunched together).
Additionally (or alternatively), I think a filter on item status should be
applied to the method the OPAC calls to retrieve all copies when not in
the staff client.
-b
--
Bill Erickson
| VP, Software Development & Integration
| Equinox Software, Inc. / The Evergreen Experts
| phone: 877-OPEN-ILS (673-6457)
| email: erickson at esilibrary.com
| web: http://esilibrary.com
More information about the Open-ils-dev
mailing list