- Koha - lists.katipo.co.nz

Re: [Koha] Separate hold queues?
by Andreas Hedström Mace 11 Apr '17

11 Apr '17

Hi Christopher! Thanks for your reply. Simply not showing the information is of course one way to go, but unfortunately I don’t think this is an option for us since we have previously shown the hold queues for 20 years or so, with our old system. Our patrons are used to having this information available. But things like high demand hold periods (which I interpret as shorter loan periods, for popular books) is one of the reasons we would like to show separate hold queues in Koha - to give the patrons a more accurate view of when they can expect to receive a book. Not showing the information, as we do today with the limits that are currently in Koha, has instead increased the number of questions about the hold queues, and apparently adding a lot of confusion. Best regards, Andreas ________________________________________ Andreas Hedström Mace Librarian Stockholm University Library Stockholm University 106 91 Stockholm Tel: +46 (0) 8-16 49 17 www.su.se/english/library/ ________________________________________ Den 2017-04-01 21:04 skrev Koha på uppdrag av BRANNON, CHRISTOPHER <koha-bounces(a)lists.katipo.co.nz på uppdrag av CBRANNON(a)cdalibrary.org>: >Andreas, > Our consortium simply does not show the patron where they are in the queue. We find it to be misleading, due to the number of items available to be placed on hold, local holds priority, cancellations, and high demand loan periods that kick in. Plus there is the rare occasion a hold is shifted. Showing that information is just inviting patrons to try and manage what the system is doing. We do let them know how many requests are on the record, but that is it. We never let them know where they are in the queue, even if they ask. This has worked very well for us. > >___________________________ >Christopher Brannon >IT Coordinator > > >702 E Front Ave >Coeur d'Alene, ID 83814 >(208)769-2315 Ext. 456 >cbrannon(a)cdalibrary.org >www.cdalibrary.org >Keep tabs on us at: > > > >-----Original Message----- > > >Hi all! > >We are at Stockholm University Library experiencing some difficulties with how Koha is currently handling hold queues, and are considering development in this area. Are there any other libraries who are experiencing similar issues (see below), and would be interested in the development of separate hold queues? Or have an opinion on whether this would be a good/bad idea? > >In Koha today it is possible to limit the fulfilment of holds per branch (same pick-up location as home/holding library) and item type. For us, it makes most sense to view this as several hold queues for one bibliographic record. For example: a person queuing for a book from the textbook collection (item type = ”TC”) isn’t actually queuing for books for the general collection (item type = ”GC”). But Koha handles this as one big queue. This isn’t a problem for the holds per se, as Koha only fetches the book that has the right criteria to fill the hold (i.e. the correct item type or home/holding library) but it has proven to be an issue for our patrons. > >As Koha displays it as one big queue, it might seem that the queue is much bigger that it actually is. This has confused a number of patrons, and have discouraged others from placing holds. Continuing our example: a book has three patrons on hold for item type GC, when a new patron adds a hold for TC. This makes this person number four in the queue in Koha today, making the patrons believe that they will have to wait weeks or months for the book (in our library TC is 7 days, GC 28 days) when in reality it is only one week. > >For us, this would better be described as two queues: >One with 3 patrons on hold (General collection) One with 1 patron of hold (Textbook collection) > >The same is true for hold fulfilment that require pick-up location to be the same as home/holding library (i.e. hold fulfilment per branch). Say a public library also have a school library in it’s organization, that is a special case where books from the other libraries should not be sent to the fulfil holds, or vice versa. As in our example above it would be better to display queues separately so 5 holds at the main library won’t discourage a student from placing a hold on that same book at the school library. > >So my question is basically, is there are other libraries out there who are using any of these hold fulfilment features (or would like to), and would want to see a new feature to separate/split hold queues? Or who could see the benefit of such a feature. > >Please note that separate hold queues would of course only come in effect if any system preference that limits hold fulfilment is set to allow. Also, this would not effect holds to pull. > >I look forwards to hearing people’s opinion about this! > >Best regards, >Andreas > >________________________________ >Andreas Hedström Mace >Librarian >Stockholm University Library >Stockholm University >106 91 Stockholm >Tel: +46 (0) 8 16 49 17 >su.se/english/library<http://su.se/english/library> >_______________________________________________ >Koha mailing list http://koha-community.org >Koha(a)lists.katipo.co.nz >https://lists.katipo.co.nz/mailman/listinfo/koha

2 1

Protocol Z39
by Luis Moises Rojas 07 Apr '17

07 Apr '17

Hi everybody. Take a look at this. Our z39 protocol stopped. Why? We do not know. We can not made it works again. But, see this: We installed a new UBUNTU 16.10 and koha 16.11.06 protocol z39 works, but when do: sudo koha-upgrade-schema library sudo koha-rebuild-zebra -v -f library login in the new koha(remeber the z39 protocol was working), and try to use the protocol: WRONG AGAIN, it does not works. Any idea why? Thanks -- *Luis Moisés Rojas P.* <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Libre de virus. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

1 0

Re: [Koha] How to show description of authorized value in facet? SOLVED
by Marc Véron 07 Apr '17

07 Apr '17

Hi Michael, Thanks for sharing your findings about resolving an authorised value while using MARC field 385 $a (Audience term) as a facet. As you write, such code changes will have to be maintained with every update. Since there are monthly releases, including bug fixes and sometimes security fixes, maintaining such code can be a bit cumbersome. IMO it would be a good idea to open a Bug (enhancement) in https://bugs.koha-community.org That would be a good starting point to have a more generic solution inside the Koha code base. Kind regards Marc www.koha-support.ch Am 07.04.2017 um 00:12 schrieb Michael Kuhn: > Hi > > Today I wrote: > >> Environment: Debian GNU/Linux 8 with Koha 16.11.04 (package installation) >> >> Our Koha catalogue contains MARC field 385 $a with content e. g. "KG", >> linked to category "Lesekategorie" containing authorized values for the >> target audience, e. g. value "KG" (description for staff client and OPAC >> is: "Kindergarten"). Instead of "KG" the OPAC shows "Kindergarten" as >> expected. >> >> Now I have recently added a new facet for MARC field 385 $a and the >> facet does show - only instead of the description ("Kindergarten"), the >> facet shows the authorized value "KG". How can it be achieved to show >> the description in the facet? >> >> As I see it is actually possible to show the description because the >> authorized values for standard category "LOC" are properly showing the >> descriptions. I tried to find out how this works in file >> "opac-facets.inc" but without success. Can anyone please give me a hint? > > For the record: > > Jens Weber found the following code in file "/usr/share/koha/lib/C4/Search.pm": > > # also, if it's a location code, use the name instead of the code > if ( $link_value =~ /location/ ) { > # TODO Retrieve all authorised values at once, instead of 1 query per entry > my $av = Koha::AuthorisedValues->search({ category => 'LOC', authorised_value => $one_facet }); > $facet_label_value = $av->count ? $av->next->opac_description : ''; > } > > I copied this section and adapted it as follows: > > # also, if it's a lesekategorie code, use the name instead of the code > if ( $link_value =~ /lesekategorie/ ) { > my $av = Koha::AuthorisedValues->search({ category => 'Lesekategorie', authorised_value => $one_facet }); > $facet_label_value = $av->count ? $av->next->opac_description : ''; > } > > After a restart of Koha (including Plack) now the created facet actually shows the description ("Kindergarten") instead of the authorized value "KG". Great! > > Of course this change will have to be reconfigured with every update but I guess it makes no sense to include this in the official Koha code... > > Best wishes: Michael > -- > Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis > Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz > T 0041 (0)61 261 55 61 · E mik(a)adminkuhn.ch · W www.adminkuhn.ch

2 1

How disable sending email
by Tim Koop 06 Apr '17

06 Apr '17

Our Koha is sending duplicated emails for checkin notices. Is there an easy way to disable this for everybody until we can upgrade Koha to get it fixed? Thanks. Tim Koop , TimK(a)mysouthland.com<mailto:TimK@mysouthland.com>

7 9

Error : Undefined subroutine CGI
by Rejeesh K.Nair 06 Apr '17

06 Apr '17

Hi All, We were moved KOHA files from our server to new server. When I try to navigate into Search page(/cgi-bin/koha/catalogue/search.pl) got an error Undefined subroutine CGI::multi_param at /usr/share/koha/intranet/cgi-bin/catalogue/search.pl line 215. But it working fine on our existing server. Can anyone help on this issue? Thanks & Regards, Rejeesh K.Nair m: +91 (0) 9495316906 e: rejeeshknair(a)gmail.com <https://www.facebook.com/rejeeshnairk> <https://twitter.com/rejeeshknair> <http://in.linkedin.com/in/rejeeshknair> <https://www.instagram.com/rejeeshknair/>

3 8

A question about the icon reference.gif packed into the Bridge iconset in Koha
by Indranil Das Gupta 06 Apr '17

06 Apr '17

Hi all, I'm curious (and slightly confused) about the reference.gif shipped as part of the Bridge Material type iconset in Koha. Where did it come from? https://apps.carleton.edu/campus/library/bridge_icons/ lists the icons, but there seems to be no reference.gif or psd or ai file in the currently available iconset at https://apps.carleton.edu/campus/library/bridge_icons/bridge_material_icons… cheers -idg -- Indranil Das Gupta L2C2 Technologies Phone : +91-98300-20971 WWW : http://www.l2c2.co.in Blog : http://blog.l2c2.co.in IRC : indradg on irc://irc.freenode.net Twitter : indradg

2 1

Fwd: Error in Koha
by Chris Cormack 06 Apr '17

06 Apr '17

-------- Original Message -------- From: Bharat Chaudhari <openbharat(a)gmail.com> Sent: 29 March 2017 6:21:38 PM NZDT To: Chris Cormack <chrisc(a)catalyst.net.nz> Subject: Fwd: Error in Koha Dear Sir, This error occurs when trying to search any books in koha *Software error:* Can't call method "data" on an undefined value at /usr/share/koha/lib/C4/Search.pm line 1915. For help, please send mail to the webmaster ([no address given]), giving this error message and the time and date of the error. Please do helpful. -- *Thanks & Best Regards,* Think Green... Keep it on the Screen... Save a Tree... Bharat M. Chaudhari, The best way to know where I'm at is to check my Blog shape <http://bharatchaudhari.blogspot.com/>, or one of the many other social networks designed to give us more information than we ever wanted to know about a person. -- *Thanks & Best Regards,* Think Green... Keep it on the Screen... Save a Tree... Bharat M. Chaudhari, DSpace Enthusiasts & ALA-ALCTS Fellow, Faculty of Engineering and Technology, PDPU, Gandhinagar URL: http://library.pdpu.ac.in Office: 07923275091, Mob. 9428415401. The best way to know where I'm at is to check my Blog shape <http://bharatchaudhari.blogspot.com/>, or one of the many other social networks designed to give us more information than we ever wanted to know about a person. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

9 18

Re: [Koha] How disable sending email
by Stefano Bargioni 06 Apr '17

06 Apr '17

Tim, emails are governed by crontabs /etc/cron.daily/koha-common /etc/cron.d/koha-common HTH. Stefano > > Our Koha is sending duplicated emails for checkin notices. > > Is there an easy way to disable this for everybody until we can upgrade Koha to get it fixed? > > Thanks. > > > Tim Koop

1 0

Authority file
by vikram zadgaonkar 06 Apr '17

06 Apr '17

Hi, Can we import authority file for Authors in koha ?

2 2

What's on in koha-devel #11
by Jonathan Druart 05 Apr '17

05 Apr '17

Hello librarians and developers, Not much has happened this month in terms of development. Things are going very slowly at the moment, despite the hackfest in Marseille. We see a lot of new people on the mailing list and the IRC channel asking for questions, but we need more people to be involved in the discussions and the signoff process. There are hundreds of people on this list, you need to know that the Koha community needs you to make the project moving forward. I know that nobody has enough time, but you know one hour per week of even per month can help a lot. It is very easy, fun and interesting :) = How to get involved? = The first action would be to join us on the #koha IRC channel and the koha-devel mailing list. Start by presenting yourself, where do you come from, what do you do? For how long have you been using Koha? How do you think you can help? Attend meetings! We have two kinds of monthly meeting. There is a general one to talk about koha-related stuffs, and the development meeting to talk about technical stuffs. It is important for the community to have a place to be all together and try to make things move. If you are a librarian, we need you to tell developers the directions they need to go. Open bug reports It is important to know that everybody can open new bug reports on our bug tracker (https://bugs.koha-community.org) It is useful for the development team to know the new bugs. And it is also important for you to search for known bugs. A lot of bugs are known from developers but we do not know how to fix them because we are waiting for feedbacks from users. The dashboard (http://dashboard.koha-community.org) is very helpful to know the "hot" bugs that need to be fixed/tested/QAed. The "Overall bug traker health status" section displays the number of new bugs that are important to follow, make moving. If a developer submits a patch for the bug you opened, try and test it! Test bugs Here is how you can really makes things move for the community. You become involved in the development process and make the Koha project better. Sandboxes (https://wiki.koha-community.org/wiki/Sandboxes) are available to test patch easily. You do not need to install anything on your computer and do not need any technical skills. If you are a Koha user, you can test patches! Write patches If you are a developer or have a minimum of technical skills you can write your own patches and fixes bugs or develop new feature. Our dedicated wiki page (wiki.koha-community.org/wiki/Submitting_A_Patch) will guide you over the different steps. It is very easy to get a development environment using KohaDevBox ( https://github.com/digibib/kohadevbox) Start with small patches :) = Refactoring = If you have read my previous "what's on in koha-devel" emails, you may have noticed I talked a lot of "refactoring" bugs. And maybe you do not know what it is and what it brings. The Koha codebase is aged/old, and has grown very quickly since 2006. Since the last few years the development team decided to make the code more robust and slow the integration of patches, getting a stronger integration process. That's why we need to have at least one tester validating the patches, then one QAer to review the patch technically and finally the Release Manager to push it. That's mean 4 independent persons for a single patch. That made our codebase stronger and less regression prone. Some part of the code now needs to be rewritten, and it is why I have focussed on the "refactoring" work over the last year. The goal is to rewrite modules of Koha, step by step. It cleans the code, makes it more readable, reduces the number of lines, centralise the responsibilities, homogenise the code, fixes bugs, adds test coverage, etc. On the mid-long term it means a modern application, easy to maintain, robust, flexible. The bugs will be easier to fix, the enhancements will be quicker to develop and so less expensive. Do you start to understand how it is useful? So yes, it's boring to test because it does not bring anything new to the interface, but the project needs it. If you have been using Koha for months or years, it made you save money, it makes you happy to use it and you love it. If you already got answer from people on the mailing lists or the IRC channel, it's time to say thank you, by getting involved! If you have any specific questions on how to get involved, you can join me on the IRC channel or by email. I can help and guide you if necessary. A developer that loves Koha but needs help, Jonathan

2 1