- Koha - lists.katipo.co.nz

issuing credit on lost item
by Scott Owen 19 Jun '17

19 Jun '17

Hi all, One of my users is reporting : *************************************************** I noticed that a book that was marked lost, charged to a patrons account with the replacement cost, was not credited when the book was found. Steps: Marked book as lost, currently checked out to a patron. Patron paid the fine for the lost book Lost book was checked in, and was then supposed to credit the patron's account. ************************************************** it seems that the proper credit is not being issues back to the patrons account. any ideas on this ??? Koha version: 16.11.08.000 Thanks -S

2 3

Password and Port Change in koha-conf.xml file
by Nasiru Yakubu 19 Jun '17

19 Jun '17

Hi all, We are experiencing the following error whenever we restart our koha (3.18.06.000) server which runs on Ubuntu 14.04: *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/intranet/cgi-bin/mainpage.pl <http://mainpage.pl> line 25. BEGIN failed--compilation aborted at /usr/share/koha/intranet/cgi-bin/mainpage.pl <http://mainpage.pl> line 25. * *For help, please send mail to the webmaster ([no address given] <[no address given]>), giving this error message and the time and date of the error.* When we look at the koha-conf.xml file we notice that the root password and port number for mysql have changed. To resolve this we change the password in mysql and ensure it matches with the value in the koha-conf.xml file. We also change the port number to its original value. Once this is the done the server is now accessible. Has anyone experienced this before and is there a permanent fix for this? -- M Nasiru Yakubu mobile: +234 818 747 4227 and +234 806 601 8785 Skype: nasyak

2 2

Auditory
by Luis Moises Rojas 17 Jun '17

17 Jun '17

Hello, Can we know you catalogued a book? I mean, Does Koha has log where we can see how user catalogued a book or any other thing? Thanks -- *Luis Moisés Rojas P.*

3 3

fuzz
by Arayik Manukyan 16 Jun '17

16 Jun '17

Hi list. How can I prevent_*fuzzily link process*_ in |sudo perl -I /usr/share/koha/lib /usr/share/koha/bin/link_bibs_to_authorities.pl| || |command. Best regards Arayik. |

1 0

Re: [Koha] Separate hold queues?
by BOUIS Sonia 16 Jun '17

16 Jun '17

Hi, Thank you for your advices. I've missed the bug 15533, I'll test it to see it solves our problem. For the moment, we still have a 3.22 koha version but I hope that we are going to install a 16.11 before the end of the year. Cheers, Sonia 1. Re: Separate hold queues? (Coehoorn, Joel) 7. Re: Separate hold queues? (Andreas Hedström Mace) ---------------------------------------------------------------------- Message: 1 Date: Tue, 13 Jun 2017 12:08:44 -0500 From: "Coehoorn, Joel" <jcoehoorn(a)york.edu> Cc: "koha(a)lists.katipo.co.nz" <koha(a)lists.katipo.co.nz> Subject: Re: [Koha] Separate hold queues? Message-ID: <CAMSeE4bygxaQx-fWKjysna8kWHHK8XjHs6D=6QqFX4uzLk4vXg(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" Most libraries I'm familiar with use different shelving locations for these books. It could even be in the same area in the stacks, just one section of a shelf that's labeled differently. This helps you, because you can set borrowing rules for this to more easily accomplish your goal. More importantly it helps your patrons, because now they know right away what they can do with the book; they won't be suddenly surprised that the book can't be checked out when they reach the circulation desk. Joel Coehoorn Director of Information Technology 402.363.5603 *jcoehoorn(a)york.edu <jcoehoorn(a)york.edu>* Message: 7 Date: Tue, 13 Jun 2017 21:07:03 +0000 From: Andreas Hedström Mace <Andreas.Hedstrom.Mace(a)sub.su.se> To: BOUIS Sonia <sonia.bouis(a)univ-lyon3.fr>, "koha(a)lists.katipo.co.nz" <koha(a)lists.katipo.co.nz> Subject: Re: [Koha] Separate hold queues? Message-ID: <E092A488-D8F1-4223-A4C7-504B8805520A(a)sub.su.se> Content-Type: text/plain; charset="utf-8" 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> >________________________________ > > >******************************* ------------------------------ 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 140, Issue 23 *************************************

1 0

Call for News: June 2017 Newsletter
by kohanews 16 Jun '17

16 Jun '17

I'm collecting news for the June newsletter. Send anything noteworthy to: k o h a news AT gmail dot com News criteria: --------------------------- ** For events **: - Please include dates for past events. If I can't find dates I may not add it. - Announcements for future events with dates T.B.A. are fine ...Eg., Kohacon - For past events , **** one month back is the cut-off ****. * News items can be of any length. * Images are fine * Anything and everything Koha. * Submit by the 26th of the month. If you are working on an interesting project or development related to Koha, please let me know and I'll include it in the development section. Thank you! -- Chad Roseburg Editor, Koha Community Newsletter

1 0

17.05 Edit Challenge
by Bruce A. Metcalf 16 Jun '17

16 Jun '17

Greetings, Package install on Jessie, was current16.11, just upgraded to 17.05. Now when I click on a title to edit an item, instead of an editing window, I get one named "Exporting to Dublin Core..." What's that and how do I edit? No joy from docs. Regards, / Bruce / Augustan Society Library

3 2

mobile app
by Castro Alves 16 Jun '17

16 Jun '17

How do I get the koha mobile app with our collection?

2 1

Koha 17.05
by Hugo Agud 15 Jun '17

15 Jun '17

Hi I am testing koha 17.05 and I wish to test Patrons Club, but when I try to launch 'Patrons club' I get one error message 'not found' As this is the demo server, it is not a fresh install, anybody has tested in a fresh install, or it can figure out what is happening There's no errors on log .. On Kohadevbox it is working fine.. just in a 17.05 upgrade -- *Hugo Agud - Orex Digital * *www.orex.es <http://www.orex.es>* <http://www.orex.es/> [image: www.orex.es/koha] <http://www.orex.es/koha> [image: www.orex.es/vufind] <http://www.orex.es/vufind> <http://www.orex.es/omeka> Director Calle Sant Joaquin,117, 2º-3ª · 08922 Santa Coloma de Gramanet - Tel: 933 856 138 hagud(a)orex.es · http://www.orex.es/ No imprima este mensaje a no ser que sea necesario. Una tonelada de papel implica la tala de 15 árboles y el consumo de 250.000 litros de agua. Aviso de confidencialidad Este mensaje contiene información que puede ser CONFIDENCIAL y/o de USO RESTRINGIDO. Si usted no es el receptor deseado del mensaje (ni está autorizado a recibirlo por el remitente), no está autorizado a copiar, reenviar o divulgar el mensaje o su contenido. Si ha recibido este mensaje por error, por favor, notifíquenoslo inmediatamente y bórrelo de su sistema.

2 1

Re: [Koha] Not able to close the leave a message box in Koha 17.05
by Vimal Kumar V. 15 Jun '17

15 Jun '17

Dear Friends, The problem solved after clean the cache of the web browser. Regards, -- Vimal Kumar V. Librarian School of Indian Legal Thought Mahatma Gandhi University Kottayam, Kerala Web: http://www.vimalkumar.info Blogs: http://linuxhalwa.blogspot.com http://kohageek.blogspot.in http://dspacegeek.blogspot.in http://moovandan.blogspot.in <http://moovandan.blogspot.in> --------------------------------------------------------------------------- "I forget what I was taught. I only remember what I have learnt" -Patrick White

1 0