- Koha - lists.katipo.co.nz

brach return
by Luis Moises Rojas 13 Jun '17

13 Jun '17

Hello everybody, We got this: Several branches. If you take a book in brach xx and return the book in branch yy. How the return branch code? -- *Luis Moisés Rojas P.*

2 3

Separate hold queues?
by BOUIS Sonia 13 Jun '17

13 Jun '17

Hello, I'm rising from the dead this email because we have a similar problem. We would like to use Koha for asking books in stacks not freely available for public and we have thought that we could use holds for this. For one biblio, we have items directly borrowable and items that are in specific stacks non directly reachable. For items directly borrowable, patrons can put a hold only if the item is on loan but it's not the same for the item in stacks that could be asked for even if they are available. We could manage that with different item types. If someone asks for an item in stacks but if there's already an hold on the other item, when we will return the stack's item, it will be the patron who asked for the item on loan that will be served (as he's on priority 1) So, if we could manage different hold queues, regarding the item type, it would be better. Do you have the same problem in your libraries ? Andreas, did manage to solve your problem ? Cheers Sonia Message: 1 Date: Wed, 22 Mar 2017 21:11:28 +0000 From: Andreas Hedström Mace <Andreas.Hedstrom.Mace(a)sub.su.se> To: "koha(a)lists.katipo.co.nz" <koha(a)lists.katipo.co.nz> Subject: [Koha] Separate hold queues? Message-ID: <AC7E35B5-1CAA-4303-A5D2-4AC6F23AA779(a)sub.su.se> Content-Type: text/plain; charset="utf-8" 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> ________________________________ *******************************

2 1

Koha 17.05.00 and 16.05.14 packages; repository reorganized
by Mirko Tietgen 13 Jun '17

13 Jun '17

1. Koha 17.05.00 Debian package released 2. Koha 16.05.14 CRITICAL bugfix Debian package released 3. Koha community repository reorganized Hi everybody, 1. Koha 17.05.00 Debian package released The Debian package for Koha 17.05.00 is now available from the Koha community repository. The package is available via the 17.05/stable pocket of the repository, more information below. 2. Koha 16.05.14 Debian package released The Debian package for Koha 16.05.14 is now available from the Koha community repository. The package is available via the 16.05/oldoldstable pocket of the repository, more information below. 3. Koha community repository reorganized The repository has been completely reorganized for the 17.05 release. A lot of obsolete dependency packages have been removed, additional configuration options are available. You have two apt configuration options now: a. Follow by codename (version number) We do not have codenames for Koha versions yet, so we use the version number instead 17.05 16.11 16.05 When a new major version is released, you will stay on the version you have chosen until you change your apt configuration. Example: Release of 17.11 If you have set "17.05" in your apt configuration, you will stay on 17.05 until you change your apt configuration to follow 17.11. To use this option, choose one of the following in your apt configuration: (for 17.05) deb https://debian.koha-community.org/koha 17.05 main (for 16.11) deb https://debian.koha-community.org/koha 16.11 main (for 16.05) deb https://debian.koha-community.org/koha 16.05 main b. Follow by suite This has been the standard way so far: follow Koha stable or oldstable, which change every release cycle. At the moment we have stable 17.05 oldstable 16.11 There is also oldoldstable this release cycle. This suite may not be available in every release cycle. oldoldstable 16.05 When a new major version is released, suite names will change and you will upgrade to a newer branch of Koha with your next update. Example: Release of 17.11 17.11 becomes "stable", 17.05 becomes "oldstable". If you have set "stable" in your apt configuration, you will automatically upgrade from 17.05 to 17.11. To use this option, choose one of the following in your apt configuration: (for 17.05) deb https://debian.koha-community.org/koha stable main (for 16.11) deb https://debian.koha-community.org/koha oldstable main (for 16.05) deb https://debian.koha-community.org/koha oldoldstable main Cheers, Mirko -- Mirko Tietgen mirko(a)abunchofthings.net http://koha.abunchofthings.net http://meinkoha.de

1 0

Koha 16.05.14 release
by Mason James 13 Jun '17

13 Jun '17

The Koha community is proud to announce the release of Koha 16.05.14. This is a maintenance release and includes an important CRITICAL bugfix. [18740] Cannot modify patron password https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18740 All users of Koha 16.05.12 to 16.05.13 are recommended to upgrade. The full release notes are available at https://koha-community.org/koha-16.05.14-release/ Packages for 16.05.14 will be available soon. Mason.

1 0

Manually freezing fines
by Mr. Ian McNaught 13 Jun '17

13 Jun '17

Hi At our university, at a certain point in the semester we transfer any outstanding fines from Koha onto the students account on the student information system so it blocks their re-registration or collection of results until paid. At this moment, the books are not returned, so fines continue to increment on Koha leaving us with two systems with out of sync fine amounts. Is there a way to manually freeze fines without the book being returned? I know there's the fine cap value, but that's a fixed amount - we want to freeze the fine at whatever value it's at on the day we transfer the fines. Ian *Ian McNaught* *Head of Library & Computing Services* *Tel: (+968) 24730404* -- Majan College (University College) P.O. Box 710, Postal Code 112, Ruwi Sultanate of Oman Switchboard: +968 24730400 Fax: +968 24730490 Find us: Website <http://www.majancollege.edu.om/> | Linkedin <http://www.linkedin.com/company/majan-college-university-college-?trk=hb_ta…> | Facebook <https://www.facebook.com/majan.college> | Twitter <http://twitter.com/Majan_College> *Ranked No.2 in Oman Economic Review's survey of Most Trusted Brands 2015 (Higher Education sector)* -- This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. Majan College (University College) therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission

2 1

Main page of Koha Community and Koha 17.05
by Michael Kuhn 12 Jun '17

12 Jun '17

Hi 1. As I've just seen on the main page of the Koha Community ( https://koha-community.org/ ) there is a link saying "Introducing Koha 17.05" - but clicking on it will lead to nowhere since the URL looks like: https://koha-community.org/koha-17-05-released/%22 The " character (%22) at the end of this URL should be removed. Maybe the people maintaining the Koha Community page can correct the URL so it will actually lead to the release notes of Koha 17.05 as intended. 2. Just below this link "Introducing Koha 17.05" there is a button saying "Try it now" - it leads to some demo pages, but none of them works with Koha 17.05 but with everything between Koha 3.22 and Koha 16.11. So this is somewhat misleading. Maybe it would be a good idea to give the actual Koha version that these demos use (as shown in the older list https://wiki.koha-community.org/wiki/Koha_Demo_Installations ). 3. Which leads to a question: Usually the (always recommended) Debian packages followed a few day after the initial release of the new Koha version. But this time Koha 17.05 was released two weeks ago and as far as I can see there are still no Debian packages. Did I miss something or does anyone know what happened to the Debian package? When will it be released? 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

1 0

Invitation to Koha-US mtg, June 14, 2017
by Christopher Davis 12 Jun '17

12 Jun '17

Dear Colleagues, I invite you to attend the June 14th, 2017 web-meeting of Koha-US, where participants will discuss issues relevant to U.S. Koha users. The meeting will begin at 10:30 am Central Time and will be held at https://kslib.zoom.us/j/450230564 (I suggest that you use a microphone and webcam for this meeting). To read the agenda for this meeting, please visit http://koha-us.net/index.php/Minutes2017-06-14. As always, if you would like to add an item to the agenda for this meeting, then please email me at the address provided below. All the best, Christopher Davis Secretary, Koha-US cgdavis(a)uintah.utah.gov

1 0

Koha 16.11.08 Patrons Page
by TSO_Lydell 12 Jun '17

12 Jun '17

Hi, we just migrated Koha from 16.05.05 to 16.11.08 and there seems to be an issue on the patrons page. As soon as it loads, a box pops up that says "Processing...". There is also another box that shows "Added patrons to .". These go away after you do a search. Has anyone else run into this? If you did, how did you fix the issue? Alternatively, is there a way to update Koha? I am guessing updating it would also take care of the issue but I am not sure how. We are running a GUI-less Debian server so if someone would have the correct terminal commands, that would be awesome. System Info: OS = Debian 8 Koha Version = 16.11.08 Perl Version = 5.020002 MySQL Version = Ver 14.14 Distrib 5.5.55 Apache Version = 2.4.10 Zebra Version = 2.0.59 Please let me know if you need anything from me. I can get screenshots if necessary. Thanks! -- View this message in context: http://koha.1045719.n5.nabble.com/Koha-16-11-08-Patrons-Page-tp5936648.html Sent from the Koha-general mailing list archive at Nabble.com.

2 2

Koha generating error messages when try to send email
by Admire Mutsikiwa 12 Jun '17

12 Jun '17

Hi I have configured my Koha instance to send emails as per http://kohageek.blogspot.com/2012/09/configure-gmail-with-postfix-to-send.ht ml. However, when I check my root emails, there are some errors that shows why the system cannot send emails. Below are the error messages: Can't locate Authen/CAS/Client/Response/Failure.pm: ./Authen/CAS/Client/Response/Failure.pm: Permission denied at /usr/share/perl/5.22/base.pm line 97. n ...propagated at /usr/share/perl/5.22/base.pm line 106. BEGIN failed--compilation aborted at /usr/share/perl5/Authen/CAS/Client/Response.pm line 68. Compilation failed in require at /usr/share/perl5/Authen/CAS/Client.pm line 8. BEGIN failed--compilation aborted at /usr/share/perl5/Authen/CAS/Client.pm line 8. Compilation failed in require at /usr/share/koha/lib/C4/Auth_with_cas.pm line 26. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Auth_with_cas.pm line 26. Compilation failed in require at /usr/share/koha/lib/C4/Auth.pm line 65. Kind Regards, Admire Mutsikiwa (Mr) ICT Manager Libraries University of Zimbabwe Tel:+263-4-303276 Mob:+263771117777 "It is easy to dodge our responsibilities, but we cannot dodge the consequences of dodging our responsibilities." Josiah Charles Stamp <http://www.goodreads.com/author/show/4867406.Josiah_Charles_Stamp>

2 1

Limit borrow books
by Luis Moises Rojas 11 Jun '17

11 Jun '17

Hello everybody. We have an user called INSTITUCION. This user can borrow 15 books at the same time, but when we just type 2 books, we got the message: User has 2 books, not more book allow. In fact we do not have any rule with 2 books. Any helps? -- *Luis Moisés Rojas P.*

2 1