Summary: | OPAC needs syspref to show homebranch instead of current location on detail page | ||
---|---|---|---|
Product: | Koha | Reporter: | Liz Rea <wizzyrea> |
Component: | OPAC | Assignee: | Galen Charlton <gmcharlt> |
Status: | CLOSED FIXED | QA Contact: | |
Severity: | enhancement | ||
Priority: | PATCH-Sent (DO NOT USE) | CC: | bchurch, chris, gmcharlt, jwagner, mcoalwell, nengard, oleonard, wizzyrea |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Attachments: |
Proposed patch
Revised fix showing branch name instead of code |
Description
Chris Cormack
2010-05-21 01:08:26 UTC
> I'd argue that this doesn't need a system preference but just to be changed. I
> agree that the patrons only want to know what the home library is
This may be true for some libraries, but not mine. Mine doesn't match Liz's example in which call numbers are different at different libraries. In my system call numbers are consistent across the board, and items may travel from branch to branch. An item "owned" by branch A might actually be available on the shelf at branch B, and the catalog needs to reflect that.
This has come up as a question/problem for some of our sites. It's confusing people who see the location as Library B rather than the real owning Library A, because a patron from B has checked it out. On the one hand, some sites want to see where the library physically is (952b current branch -- the current display). On the other hand, some sites want to see who owns the item (952a owning branch). We had some discussion on the IRC today; it sounds like a syspref to control which displays is the best solution. Should one syspref control both staff and OPAC? If it's to be changed in staff and opac there should be two prefs so that the staff can decide what they want - which is often different from what the patrons want. Created attachment 2850 [details] [review] Proposed patch I believe this is a better solution for this than a syspref. the OPAC will still need to be dealt with. LR > I believe this is a better solution for this than a syspref.
This solution works for me. But can we get it to show the library name rather than the code?
As far as I can tell, the full name for homebranch isn't being generated for the templates. That's not one I know how to do (but could conceivably learn). Created attachment 2874 [details] [review] Revised fix showing branch name instead of code This patch takes Liz's and adds the home branch name instead of branch code. Pushed, please test Looks good! (Thanks Owen, for getting the branch name instead of code in there) LR |