I remember this feature from 3.12 (bugzilla 7919). We've had libraries
that have run into the same issue you have Sonia. Generally we suggest
that they add their branch (MAIN branch) to the branch limitations for all
authorised values so that they can then see those values when cataloging.
Conversely, we've had larger consortiums that set up a Technical Services
branch that the catalogers are assigned to and that branch is then added to
the list of the authorised values branch limitations.
While both of those are 'free' workarounds for the library, I can see room
for improvement in this area. I talked to our educators and developers and
thought these might make two great options to enhance this functionaliy.
1. Paul's idea to make the authorised value dropdowns change dynamically is
nice. Kyle mentioned this could be done with some javascript and an API
2. Our educators thought perhaps we should add a permission to the
cataloging area that is something like "view and choose all authorized
values". So catalogers would have this particular option selected and all
values would appear in the list for selection when creating items.
-joy
On Wed, Dec 19, 2018 at 9:24 AM Paul Poulain <paul.poul...@biblibre.com>
wrote:
> IMHO, that's a bug (or a mistake in behavior)
>
> When you create an item, if you create it for homebranch X, you must be
> able to see location defined for branch X. It does not depends on the
> branch you're connected to, it depends on the branch of the item you're
> cataloging. So we should change the behavior.
>
> Additional cases:
>
> * libraries having a cataloger in every branch ("I catalogate for my
> branch") will see no difference,
> * I can't see a use case where the librarian want to enter "homebranch
> = X" and "location = a location that is not supposed to exist in
> branch X" !
>
> Le 18/12/2018 à 18:35, BOUIS Sonia a écrit :
> > Hello,
> > It is possible in Koha to limit the locations to specific branches. This
> limitation is active when adding items and in item search.
> > Currently, this limitation is linked to the branch where you are logged.
> But this behavior doesn't fit with our organization because with have a
> centralized service to add items for all branches.
> > I wonder if we could change this behavior to limit the location to the
> branch selected in the home branch or the holding branch (I presume the
> holding branch is more logical?)
> > Actually, I don't think it would be a big change for people that already
> use this functionality because, if I am not mistaken, when you add a new
> item, you're by default on the branch where you are logged.
> > For item search, it could be disturbing to be able to choose any
> branches for home branch or holding branch, but only the location from the
> branch where you are logged. We could perhaps change to limit the location
> the branch that are selected in the search form?
> >
> > Any opinion?
> >
> > Cheers,
>
> --
> Paul Poulain, Associé-gérant / co-owner
> BibLibre, Services en logiciels libres pour les bibliothèques
> BibLibre, Open Source software and services for libraries
>
> _______________________________________________
> Koha mailing list http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
--
Joy Nelson
Vice President of Implementations
ByWater Solutions <http://bywatersolutions.com>
Support and Consulting for Open Source Software
Phone/Fax (888)900-8944
What is Koha? <http://bywatersolutions.com/what-is-koha/>
_______________________________________________
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha
