- Koha - lists.katipo.co.nz

18.05.07 Released
by Jesse Maseto 21 Dec '18

21 Dec '18

The Koha community is proud to announce the release of Koha 18.05.07. Please note, this release removes support for using Cache::Memory as your caching strategy due to unresolvable bugs with its implementation which cause issues in plack environments. memcached has been the recommended caching module for some time now, so anyone still relying on Cache::Memory should consider migrating to Memcached. This is a maintenance release that includes 2 enhancements, 28 bugfixes. The full release notes are available at https://koha-community.org/ koha-18-05-07-released/ Debian packages will be updated within a few days. Best Regards, Jesse and Lucas -------------------- Jesse Maseto Dev/Ops Support ByWater Solutions Support & Consulting for OSS Office - Stratford,CT T/F 888.900.8944 http://bywatersolutions.com Jesse(a)bywatersolutions.com

2 1

Koha 18.11.01 release
by Renvoize, Martin 20 Dec '18

20 Dec '18

The Koha community is proud to announce the release of Koha 18.11.01. Please note, this release removes support for using Cache::Memory as your caching strategy due to unresolvable bugs with its implementation which cause issues in plack environments. memcached has been the recommended caching module for some time now, so anyone still relying on Cache::Memory should consider migrating to Memcached. This is a maintenance release containing 35 bugfixes The full release notes are available at *https://koha-community.org/koha-18-11-01-release/ <https://koha-community.org/koha-18-11-01-release/>* Debian packages will be updated within a few days That just leaves me to wish everyone a Happy Christmas and express my thanks to everyone involved in this release, *Martin Renvoize* <https://www.ptfs-europe.com> Development Team Manager *Phone:* +44 (0) 1483 378728 *Mobile:* +44 (0) 7725 985 636 *Email:* martin.renvoize(a)ptfs-europe.com *Fax:* +44 (0) 800 756 6384 www.ptfs-europe.com Registered in the United Kingdom No. 06416372 VAT Reg No. 925 7211 30 The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this email message in error, please email the sender at info(a)ptfs-europe.com

1 0

List of AV items to be exported
by Peter Lau 20 Dec '18

20 Dec '18

I would like to export a list of all AV items including the title, producer, year of publication information etc. to Excel or CSV file, I wonder if there’s a way to export information. Thanks & regards, *Peter Lau* Librarian Tel: (852) 3977 9868 | Email: Peter.Lau(a)yccece.edu.hk | Fax: (852) 23384320 [image: https://docs.google.com/uc?export=download&id=1wiYZQsqhNTJZjyNbLJx-6ODZyoYE…] 2 Tin Wan Hill Road, Tin Wan, Aberdeen *YCCECE, Here We Grow Our Future | *www.yccece.edu.hk

2 2

Re: [Koha] Koha Digest, Vol 158, Issue 18
by Peter Lau 20 Dec '18

20 Dec '18

Tks Caroline, it works for us. Thanks & regards, Peter Lau Librarian Tel: (852) 3977 9868 | Email: Peter.Lau(a)yccece.edu.hk | Fax: (852) 23384320 2 Tin Wan Hill Road, Tin Wan, Aberdeen YCCECE, Here We Grow Our Future | www.yccece.edu.hk -----Original Message----- From: Koha [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of koha-request(a)lists.katipo.co.nz Sent: Thursday, 20 December 2018 7:00 AM To: koha(a)lists.katipo.co.nz Subject: Koha Digest, Vol 158, Issue 18 Send Koha mailing list submissions to koha(a)lists.katipo.co.nz To subscribe or unsubscribe via the World Wide Web, visit https://lists.katipo.co.nz/mailman/listinfo/koha or, via email, send a message with subject or body 'help' to koha-request(a)lists.katipo.co.nz You can reach the person managing the list at koha-owner(a)lists.katipo.co.nz When replying, please edit your Subject line so it is more specific than "Re: Contents of Koha digest..." Today's Topics: 1. Tag Cloud tab (Peter Lau) 2. Re: Tag Cloud tab (Caroline Cyr-La-Rose) 3. Re: Branches limitations for locations (Paul Poulain) 4. Re: Branches limitations for locations (Joy Nelson) 5. Re: Branches limitations for locations (Jonathan Druart) ---------------------------------------------------------------------- Message: 1 Date: Wed, 19 Dec 2018 16:51:06 +0800 From: Peter Lau <peter.lau(a)yccece.edu.hk> To: koha(a)lists.katipo.co.nz Subject: [Koha] Tag Cloud tab Message-ID: <acd36ddff400c126be35a8b0bd16aec2(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" What is the meaning of Tag Cloud tab, which is next to the Authority Search tab in Koha? After clicking the Tag Cloud tab, I can see the following: Tags to show from other users : Thanks & regards, *Peter Lau* Librarian Tel: (852) 3977 9868 | Email: Peter.Lau(a)yccece.edu.hk | Fax: (852) 23384320 [image: https://docs.google.com/uc?export=download&id=1wiYZQsqhNTJZjyNbLJx-6ODZyoYE…] 2 Tin Wan Hill Road, Tin Wan, Aberdeen *YCCECE, Here We Grow Our Future | *www.yccece.edu.hk ------------------------------ Message: 2 Date: Wed, 19 Dec 2018 09:17:35 -0500 From: Caroline Cyr-La-Rose <caroline.cyr-la-rose(a)inlibro.com> To: koha(a)lists.katipo.co.nz Subject: Re: [Koha] Tag Cloud tab Message-ID: <f1c0ea7f-c60f-7709-5f5b-c6abc9dd0d0f(a)inlibro.com> Content-Type: text/plain; charset=utf-8; format=flowed Hello Peter, Koha has a tagging function where patrons are able to add tags (or keywords) to records in the catalog. There are several system preferences that control the behaviour of this functionality (see Administration > Global system preferences > Enhanced content > Tagging) : * TagsEnabled (this is the one you want to disable if you want to remove the "tag cloud" link on the catalog) * TagsExternalDictionary * TagsInputOnDetail * TagsInputOnList * TagsModeration * TagsShowOnDetail * TagsShowOnList Best regards, Caroline Caroline Cyr La Rose, M.L.I.S. Librarian / Head of Training and Support Phone : 1 (833) 465-4276 caroline.cyr-la-rose(a)inLibro.com <mailto:caroline.cyr-la-rose@inLibro.com> inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com> Le 18-12-19 à 03 h 51, Peter Lau a écrit : > What is the meaning of Tag Cloud tab, which is next to the Authority > Search tab in Koha? > > > > After clicking the Tag Cloud tab, I can see the following: > > > > Tags to show from other users : > > > > Thanks & regards, > > *Peter Lau* > > Librarian > > Tel: (852) 3977 9868 | Email: Peter.Lau(a)yccece.edu.hk | Fax: (852) > 23384320 > > [image: > https://docs.google.com/uc?export=download&id=1wiYZQsqhNTJZjyNbLJx-6OD > ZyoYE5NNu&revid=0BzpPRj4UE0XeT1R2WUt2dnhmTFBBeEpVR3dqcU5QbnF6NVg4PQ] > > 2 Tin Wan Hill Road, Tin Wan, Aberdeen > > *YCCECE, Here We Grow Our Future | *www.yccece.edu.hk > _______________________________________________ > Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz > https://lists.katipo.co.nz/mailman/listinfo/koha ------------------------------ Message: 3 Date: Wed, 19 Dec 2018 17:23:45 +0100 From: Paul Poulain <paul.poulain(a)biblibre.com> To: koha(a)lists.katipo.co.nz Subject: Re: [Koha] Branches limitations for locations Message-ID: <99a6dfa8-dd0d-b5b7-8396-35cd691ce644(a)biblibre.com> Content-Type: text/plain; charset=utf-8; format=flowed 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 ------------------------------ Message: 4 Date: Wed, 19 Dec 2018 12:07:16 -0700 From: Joy Nelson <joy(a)bywatersolutions.com> To: Paul Poulain <paul.poulain(a)biblibre.com> Cc: Koha <koha(a)lists.katipo.co.nz> Subject: Re: [Koha] Branches limitations for locations Message-ID: <CAFpshE8YJxp3JtO4WHcm9YV0Me+d5pdpwqydVr0TMhai-MwT5g(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" 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.poulain(a)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(a)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/> ------------------------------ Message: 5 Date: Wed, 19 Dec 2018 17:23:23 -0300 From: Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> To: Joy Nelson <joy(a)bywatersolutions.com> Cc: Koha <koha(a)lists.katipo.co.nz> Subject: Re: [Koha] Branches limitations for locations Message-ID: <CAJzKNY59DAN-k_iCtmVK=4ZryoW3=tTyrAoAQLKpgYtJGqAqQw(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" The problem is bigger I think, as it impacts all AVs (as well as patron's categories - see bug 21255). However this specific problem could indeed be solved quite easily with the dynamic dropdowns. Le mer. 19 déc. 2018 à 16:07, Joy Nelson <joy(a)bywatersolutions.com> a écrit : > > 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.poulain(a)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(a)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(a)lists.katipo.co.nz > https://lists.katipo.co.nz/mailman/listinfo/koha ------------------------------ Subject: Digest Footer _______________________________________________ Koha mailing list Koha(a)lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha ------------------------------ End of Koha Digest, Vol 158, Issue 18 *************************************

1 0

Branches limitations for locations
by BOUIS Sonia 19 Dec '18

19 Dec '18

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, Sonia BOUIS ------------------------------------------------------ Responsable du Service des applications documentaires Bibliothèques universitaires Université Jean Moulin Lyon 3 ADRESSE GÉOGRAPHIQUE > Manufacture des Tabacs | 6 cours Albert Thomas | LYON 8e ADRESSE POSTALE > Bibliothèque de la Manufacture | 1C avenue des Frères Lumière | CS 78242 - 69372 LYON CEDEX 08 Ligne directe : 33 (0)4 78 78 79 03 http://bu.univ-lyon3.fr<http://bu.univ-lyon3.fr/>| Suivez-nous > Facebook<https://www.facebook.com/bulyon3/> | Twitter<https://twitter.com/bulyon3>| Instagram<https://www.instagram.com/bu.lyon3/?hl=fr> --------------------------------------------------- L'Université Jean Moulin est membre de l'Université de Lyon

4 3