[Koha-bugs] [Bug 7720] Ambiguity in OPAC Details location.

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Fri Mar 16 15:39:18 CET 2012


http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7720

Nora Blake <nblake at masslibsystem.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nblake at masslibsystem.org

--- Comment #15 from Nora Blake <nblake at masslibsystem.org> ---
Hi All,

We're the ones that raised this issue and Kyle kindly created a first shot at a
fix.

We would rather just have the owning library listed in the OPAC and then list
it's availability status as the system does now.  So if the item is loaned from
Library A to Library B, it is still showing as owned by Library A, but "checked
out" or "in transit" or whatever stage of the hold fulfillment process it is
in.

It doesn't seem necessary to us to muddy the waters in the OPAC with the level
of detail of "this is owned by Library A but being used by Library B right
now."  We can get that level of information from the staff side with the
"Current Location" and "Home Library" columns.  That seems like enough.

What we're finding is that patrons at our member libraries are getting confused
with the current display.  They're thinking that their library doesn't own an
item because it displays as having a 'current location' of another library when
it has been loaned to another library in the consortium.  So the patrons are
thinking that the library doesn't own the title and the libraries can come off
as looking bad, "why don't we own a copy of 'The Help?' "

I have no idea if this is helpful, but we'd rather see the owning library as
the only library information listed in the OPAC.  We think providing the
current location information in the OPAC only makes for misinformation and
confusion with patrons.

Thanks,

Nora Blake
MassCat

-- 
You are receiving this mail because:
You are watching all bug changes.


More information about the Koha-bugs mailing list