- Koha - lists.katipo.co.nz

Error when trying to see some user
by Luis Moises Rojas 14 Jun '17

14 Jun '17

Hello everybody Test::DBIx::Class (0.42) No Installed How can i fix this error. Koha ver. 17.05 Thanks -- *Luis Moisés Rojas P.*

2 1

Koha IRC Developers Meeting Reminder - TODAY, June 14, 21 UTC
by Nick Clemens 14 Jun '17

14 Jun '17

Hi All, My apologies for late reminder, we have a Developers meeting in IRC scheduled for today at 21 UTC Local time/date conversion here: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+I… The agenda is here: https://wiki.koha-community.org/wiki/Development_IRC_meeting_14_June_2017 Please add any topics you wish to discuss to the agenda, or add yourself in to the apologies if you can't make it. Hope to see you all there! -Nick

1 0

Serious problem with Koha issue/return
by vinod mishra 14 Jun '17

14 Jun '17

Dear All, I am facing very serious issue regarding issue/return of books from koha 16.11.07 installed on debian jessie via package. Problems are as below: 1. Some issued books automatically get returned from the member account i.e it does not display in check out screen but it still shows check out status in circulation history 2. Some books return by user does not return from its check out screen but it shows check in under the circulation history of the patron along with date of return. Overdue message also generating to that patron too for that particular book. Please note i was using RFID middle ware for transactions but it has been disabled too even though problem persists i.e. now directly issuing/returning the books from Koha. With Regards, Vinod Kumar Mishra, Assistant Librarian, Biju Patnaik Central Library (BPCL), NIT Rourkela, Sundergadh-769008, Odisha, India. Mob:91+9439420860 Website: http://mishravk.com/ *"Spiritual relationship is far more precious than physical. Physical relationship divorced from spiritual is body without soul" -- Mahatma Gandhi*

2 3

Patron Authentication - 16.05.13
by Bortel, Gary 13 Jun '17

13 Jun '17

Debian package on Ubuntu 16.04 with MySql 5.7.18, multi-tennant installation. Recently upgraded from 16.05.12 to 16.05.13-2 Since the upgrade to 16.05.13-2, one library reports that patrons are no longer able to log on to their accounts through the opac. The error returned is "You entered an incorrect username or password. Please try again! And remember, passwords are case sensitive." The server hosting Koha has been restarted since the upgrade. I am able to log into their instance of Koha through the browser at my location using my "super user" account. The library was asked to clear the browser cache on the affected machine. Their patrons are still receiving the error message. However, I see no entries in the opac-error.log that might be related to this. Thoughts? gcb

5 6

Book with no item Not to be dispaly, but PDF yes
by Luis Moises Rojas 13 Jun '17

13 Jun '17

Hi everybody, We have PDF books, these books HAVE NOT ITEM associated, How can we SAY: BOOKS with no ITEMS could not be display, but PDF YES? Thanks -- *Luis Moisés Rojas P.*

2 1

Software Error
by Nasiru Yakubu 13 Jun '17

13 Jun '17

Hi, We have noticed the error below at our library and we really need assistance to resolve the issue. We are running Koha 3 on Ubuntu on a virtual server. Please let me know if there is any other information required in order to assists us further issue. Software error: Can't call method "do" on unblessed reference at /usr/share/koha/lib/C4/Context.pm line 816. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Auth.pm line 88. Compilation failed in require at /usr/share/koha/opac/cgi-bin/opac/opac-main.pl line 23. BEGIN failed--compilation aborted at /usr/share/koha/opac/cgi-bin/opac/opac-main.pl line 23. For help, please send mail to the webmaster ([no address given]), giving this error message and the time and date of the error. -- M Nasiru Yakubu mobile: +234 818 747 4227 and +234 806 601 8785 Skype: nasyak

2 1

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

13 Jun '17

Hi! The issue we wanted input on was not separating hold queues per se (separate queues = specific hold fulfillment), but rather how the queue(s) are displayed to staff and patrons. If I read your e-mail correctly, you have books in closed stacks and would like to separate these from the books you have in open collections. For one biblio, a book from the closed stacks should not fulfill a hold placed on a book from the open collection. Is this correct? If this is the case, then it is possible to achieve already today. We do it currently, with different itemtypes for items in closed stacks and open collection and the syspref AllowHoldItemTypeSelection set to allow. (For those wainting to look at the original development, look at bu 15533: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15533) I hope this is helpful in any way! Best regards, Andreas Den 2017-06-13 18:42 skrev BOUIS Sonia <sonia.bouis(a)univ-lyon3.fr>: >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> >________________________________ > > >*******************************

1 0

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