- Koha - lists.katipo.co.nz

Re: [Koha] Questions regarding Holds (Bohdan Šmilauer)
by BOUIS Sonia 06 Oct '15

06 Oct '15

Hi Andreas, When we began to work on holds, we had the same expectations as you but we gave up. We had no transfer between library for check-out so far, but with the holds' implementation we are forced to make it possible. We try to propose new developments but we finally changed our organization : http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11481 http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11482 (I don't think they are compatible with the master version). We use jquery to hide some branches and ask patrons to choose a pickup location when placing holds but it don't really solve problems. I can give you more details if you want. Best Regards, Sonia Message: 7 Date: Mon, 05 Oct 2015 21:23:57 +0200 (CEST) From: Bohdan Šmilauer <b.smilauer(a)post.cz> To: Andreas Hedström Mace <Andreas.Hedstrom.Mace(a)sub.su.se> Cc: 'Koha(a)lists.katipo.co.nz' <Koha(a)lists.katipo.co.nz> Subject: Re: [Koha] Questions regarding Holds Message-ID: <See.g5kQ.2JeUDatTlyE.1M4ivD(a)seznam.cz> Content-Type: text/plain; charset=utf-8 Dear Mr. Mace, I am engaged in the Koha implementation ver. 3.20 see http://koha2. knihovnavsenory.cz . I have to say that holding functionality doesn't work correctly until now. We have only one branch: main library for simplicity . Our case should be, to enable to put hold, only if no item is free on shelf. By other words, if some issue (item) of the book title is available (free), the patron has to go to the checkout desk and to ask this free item. No remote order is allowed in this case . The hold (order) is allowed only if all items are checked out and patron must wait until some item is returned. There are two preferences influencing the Koha holds function: On shelf holds allowed = NO, Item level holds= Don't allow. It is adjustable in Administration › Circulation and fine rules for patron category. Now it works incorrectly in such manner that holds are enabled if one or more item is checked out, but on the shelf remains some free item. It should not to be enabled, until all items are checked out (no free item). This problem was investigated in bug 6837, see http://bugs.koha-community. org/bugzilla3/show_bug.cgi?id=6873, the problem was resolved by Barry Cannon, see Attachment http://bugs.koha-community. org/bugzilla3/attachment.cgi?id=23162&action=diff, but this attachment is without approval (failed QA). My message is, that this problem is not satisfactory solved until now. Regards Bohdan Smilauer Library Vsenory (near Prague) 252 31 Czechia koha2.knihovnavsenory.cz ---------- Původní zpráva ---------- Od: Andreas Hedström Mace <Andreas.Hedstrom.Mace(a)sub.su.se> Komu: 'Koha(a)lists.katipo.co.nz' <Koha(a)lists.katipo.co.nz> Datum: 2. 10. 2015 15:12:13 Předmět: [Koha] Questions regarding Holds "Hi! We are currently investigating how holds behave in Koha, and see if we can set it up according to our needs. We have so far not managed to do so, but the preferences concerning holds are quite complex so there might be ways we haven't tried yet - any feedback is welcome! Our current set-up: · We have nine branches (libraries), where all patrons are able to place holds on any of the branches. (They are not affiliated with any one branch per se, but with Stockholm University Library as a whole.) · Books can be returned at any library and be sent back to the books home library, but we don't send out books between the libraries. · Item level holds are not available (except for staff) We would like holds to work as follows: · Holds should be limited to all items of a specific branch, not all items (of several branches) connected to the bibliographic record. Holds can only be placed when all items are checked out on a branch. · The pick-up location should always be the same as the books home library. · A hold placed in one branch should not affect books on other branches. An example: The book "Narrative analysis" has 5 items, on three branches: · Library A, 2 items (2 checked out) · Library B, 2 items (1 checked out) · Library C, 1 item (not checked out) Patron A places a hold at Library A. The 2 items connected to that library cannot be renewed and the first one returned will fill the placed hold. Items at Library B and C are unaffected and can be checked out normally. If the checked out item on Library B is returned before any books from Library A, it will not fill the placed hold at Library A but instead go back up on the shelf at Library B. Does anyone know if this set-up is possible with Koha today? Is anyone doing this, or anything similar? Or is some development needed? Best regards, Andreas ____________________________________ Andreas Hedström Mace Librarian Stockholm University Library Stockholm University 106 91 Stockholm Tel: +46 (0) 8-16 49 17 www.sub.su.se<http://www.sub.su.se/> ____________________________________ _______________________________________________ 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 120, Issue 7 ************************************

1 0

Luminita Vulcu - please temporarily unsubscribe - thank you
by Vulcu, Luminita 06 Oct '15

06 Oct '15

Luminita Vulcu <luminita(a)salus.edu> Librarian Technology & Library <http://ecampus.salus.edu/library/> Services (TLS) Salus University <http://www.salus.edu> 8360 Old York Road Elkins Park, Pa 19027 (215) 780-1262

2 1

Koha 3.20 and Plack Server
by Craig Butosi 05 Oct '15

05 Oct '15

Hi all, I'm tinkering with Plack on Koha 3.20.04 (Ubuntu x64 14.04 LTS). I followed the (somewhat outdated) instructions here: http://www.generalthreat.com/2013/04/serving-koha-common-with-plack/ and made sure that my pathways were corrected in the scripts. I'm using the port 5000 option rather than the unix socket option. After restarting koha-common, I received the following output: root@vps43351:~# service koha-common restart * Restarting Koha ILS koha-common Stopping Zebra server for library Stopping Plack servers for library Servers stopped SIP server for library not running. Starting Zebra server for library Starting OPAC Plack server for library /usr/share/koha/misc/plack/unlock-opac-plack.sh: 3: /usr/share/koha/misc/plack/unlock-opac-plack.sh: Syntax error: "&" unexpected /usr/share/koha/misc/plack/opac-plack.sh: 5: /usr/share/koha/misc/plack/opac-plack.sh: Syntax error: "&" unexpected The above looks as if Plack is up and running, but the syntax warning for opac-plack.sh is puzzling. I'm not entirely sure whether there is a syntax error in the code; everything looks correct, but I could be missing something here. Does anyone have any suggestions or advice on how to proceed? I'd love to get Plack up and running to see the performance difference. If there's a better way to install Plack or configure it for 3.20, I am all ears too! My opac-plack.sh file is as follows: #!/bin/sh # --max-requests = decreased from 1000 to 50 to keep memory usage sane # --workers = number of cores on machine test ! -z "$1" && site=$1 && shift dir=`dirname $0` export KOHA_CONF=/etc/koha/sites/$site/koha-conf.xml export OPACDIR="$( xmlstarlet sel -t -v 'yazgfs/config/opacdir' $KOHA_CONF | sed 's,/cgi-bin/opac,,' )" export LOGDIR="$( xmlstarlet sel -t -v 'yazgfs/config/logdir' $KOHA_CONF )" export MEMCACHED_SERVERS=localhost:11211 export MEMCACHED_NAMESPACE=$site PIDFILE=/var/run/koha/$site/opac-plack.pid #SOCKET=/var/run/koha/$site/opac-plack.sock PORT=5000 # uncomment to enable logging opt="$opt --access-log $LOGDIR/opac-access.log --error-log $LOGDIR/opac-error.log" opt="$opt -M FindBin --max-requests 50 --workers 2 -E deployment" if [ $SOCKET ]; then opt="$opt --listen $SOCKET -D --pid $PIDFILE" elif [ $PORT ]; then opt="$opt --port $PORT -D --pid $PIDFILE" fi /usr/bin/starman $opt $dir/koha.psgi Many thanks! Craig Butosi, MA, MLIS, B Mus (Hons.) LIBRARY SERVICES MANAGER the royal conservatory TELUS Centre for Performance and Learning 273 Bloor Street West Toronto, ON M5S 1W2 416.408.2824 x338 www.rcmusic.ca<https://webmail.rcmusic.ca/owa/redir.aspx?C=b481823b299d45ee94b0016389bb76e…> Note: This email message and any attachments are intended only for the use of the individual to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the recipient of this email is not the intended recipient (or the employee or agent responsible for delivering the email to the intended recipient), you are hereby notified that any review, dissemination, distribution or copying or other use of this message is strictly prohibited. If you have received this communication in error, please notify the sender immediately by return email and delete this message and attachments from your system, thank you.

3 3

Koha 3.16.15 released
by Mason James 03 Oct '15

03 Oct '15

The Koha release team are proud to announce the release of Koha 3.16.15. Koha 3.16.15 is a bugfix/maintenance release. It includes 1 enhancement and 20 bugfixes. All Koha 3.16.x series users are encouraged to upgrade to this version. Please install from the tarball, as .deb packages are not currently built for the 'oldoldstable' series More installation info... http://www.koha-community.org/download-koha The full release notes are at... http://koha-community.org/koha-3-16-15-released -- Mason

1 0

Top Borrowers for a given period
by Admire Mutsikiwa 03 Oct '15

03 Oct '15

Hi I have a Children's Community Library which is trying to promote a reading culture among its patrons by giving prizes to top borrowers. Given this backdrop, I am interested in an SQL reports that will enable the library to get Top X e.g. Top 10 borrowers for a given period. My first port of call was the report Ex Heavy Borrowers by Chris Hall for Horowhenua Library Trust, Catalyst http://wiki.koha-community.org/wiki/SQL_Reports_Library#Ex_Heavy_Borrowers SELECT first.borrowernumber, first.firstname, first.surname, first.cardnumber, issues_before, issues_after FROM( SELECT borrowernumber, firstname, surname, cardnumber, count(old_issues.itemnumber) AS issues_before FROM borrowers JOIN old_issues USING (borrowernumber) WHERE issuedate > <<Beginning of first range (yyyy-mm-dd)|date>> AND issuedate < <<End of first range (yyyy-mm-dd)|date>> GROUP BY old_issues.borrowernumber ) AS first JOIN ( SELECT borrowernumber, count(old_issues.itemnumber) AS issues_after FROM borrowers JOIN old_issues USING (borrowernumber) WHERE issuedate > <<Beginning of second range (yyyy-mm-dd)|date>> AND issuedate < <<End of second range (yyyy-mm-dd)|date>> GROUP BY old_issues.borrowernumber ) AS second WHERE first.borrowernumber = second.borrowernumber AND issues_after < 20 AND issues_before > 60 -- borrowers borrowed fewer than 20 items in the second range, and more than 60 in the first range. By I think , I need some help on customizing it to suit my slightly different requirements Kind Regards, Admire Mutsikiwa (Mr) ICT Manager Libraries University of Zimbabwe Tel:+263-4-303276 Mob:+263782476883 "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> ------ UZ at 60: Celebrating our Past, Inspiring the Future.

2 1

Lowering max reserves/ holds
by Cab Vinton 02 Oct '15

02 Oct '15

Hi, All -- Our maxreserves is currently set for 50 items, that is patrons can have up to 50 holds at a time. Turns out we have a patron who actually comes close to reaching this limit on a regular basis -- almost continuously in fact. Since staff are spending an inordinate amount of time dealing with one patron's holds, we'd like to lower the limit to something more reasonable, perhaps 20 or 25. Before doing so, however, we want to make sure there aren't any hidden potholes waiting for us. These are the questions that have occurred to us, but if you have other thoughts or advice, please feel free to share :-) 1./ Is there a message when patrons attempt to place one more hold than is allowed? If so, it seems that the message is not customizable. 2./ Can the the hold limit be overridden by staff? Thanks for any tips you can provide. Even if you don't have any thoughts to share, here's a super-quick 4-question survey on your max reserves policy: http://goo.gl/forms/XhBsajq2j0. We'll share the results on the list! Thank you, Cab Vinton, Director Plaistow Public Library Plaistow, NH

2 1

A governing body for Koha?
by Christopher Davis 01 Oct '15

01 Oct '15

Dear Colleagues, I do not know if this topic has already been discussed before, so please forgive my ignorance if it has. When I was at the Koha North America conference in August, I asked if there was a software development road map for Koha and I was told that the development of Koha primarily follows the needs of its users instead of following such a road map. Is there (or should there be) a governing body or foundation which guides and supports the development of Koha. I know that a few other open source projects have governing bodies (e.g., Mozilla). There are pros and cons to having a governing body at the head (or foundation, depending on your perspective) of a software project. I have organized some research on governing bodies into the document linked to below. I wanted to bring this topic up at the next Koha general IRC meeting, but I thought that I would get your input before I did that. Please share your thoughts. https://atlas.mindmup.com/2015/10/7bd620904a98013345a353e2e87dfd31/foss_gov… Thank you, Christopher Davis, MLS Systems & E-Services Librarian Uintah County Library cgdavis(a)uintah.utah.gov (435) 789-6261 uintahlibrary.org basinlibraries.org facebook.com/uintahcountylibrary

1 0

SIRSI / Koha Differences
by Shell, Lezlie 01 Oct '15

01 Oct '15

Hello! We just installed Koha for testing and I'm having trouble orienting myself. I'm the cataloger for Questia, an online library. After a brief, frustrating flirtation with the Green one, I am really enjoying how neatly Koha fits with my current workflow. We will be using Koha to store MARC records that I catalog. None of it is customer facing. Our Koha will feed some data into the Questia system (subject headings and publisher info), so I need to be able to point the data guys to the right tables. I've been using SIRSI a long time (the clients had to be installed on OS/2 machines). Since then, wherever I went, there it was. After importing some records I fired up Brio to see where all the data lived, expecting to find some variation of the SIRSI catalog/marc0/item/callnum structure. After fleeing Brio I looked at the tables in SchemaSpy. Does the MARC data really live in the marc field of the biblioitem table? I tried to look at this in Brio, but it said I couldn't request a binary datatype. I currently do a lot of data checking in the marc0 table. I was hoping to find an equivalent table in Koha. Can anyone help a recovering SIRSI user? I need to wrap my head around how the MARC data is stored. Thanks, Lezlie

2 1

Re: [Koha] Holds on items waiting to be pick-up or in transit
by BOUIS Sonia 01 Oct '15

01 Oct '15

Hi, Thank you Katrin for your advice. I have just created a new bz ticket : http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14935 I have had to the CC list people who are previously on the BZ4319. Cheers, Sonia Date: Mon, 28 Sep 2015 21:44:22 +0200 From: Katrin Fischer <Katrin.Fischer.83(a)web.de> To: koha(a)lists.katipo.co.nz Subject: Re: [Koha] Holds on items waiting to be pick-up or in transit Message-ID: <56099896.8020504(a)web.de> Content-Type: text/plain; charset=windows-1252 Hi Sonia, we had a library reporting this as a problem in the past and I agree - it should be possible to place holds on items waiting for pick-up with AllowOnShelfHolds turned off. There is some discussion on bug 4319, but putting a patch on a new bug report might be a little cleaner. Katrin Am 28.09.2015 um 16:31 schrieb BOUIS Sonia: > Hello, > I think there's an issue with the possibility to place a hold on items waiting to be pick-up or in transit when you choose that on shelf holds are not allowed. > In this case, items are not checked-out so there are considered to be available. But, they aren't, they are not on a shelf ready to be chosen by a patron but stored aside. > So, other patrons should place a hold on it as they couldn't go on shelves to take it. > I have been testing it on a master and it's the same behaviour. > > So, I have 2 questions : > 1. Does everybody share the same logic than me? > > 2. There's a bug describing this problem (http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4319) but the status is reopened and the patch had been pushed in 2011. Should we open a new bug? > > Thanks, > > Best regards > > Sonia BOUIS > > Responsable du SystÃ¨me intÃ©grÃ© de gestion des bibliothÃ¨ques > > bIBLIOTHÃˆQUES UNIVERSITAIRES > UniversitÃ© Jean Moulin Lyon 3 > 6 Cours Albert Thomas - B.P. 8242 - 69355 Lyon Cedex 08 > ligne directe : +33 (0)4 78 78 79 03 | http://bu.univ-lyon3.fr<http://bu.univ-lyon3.fr/> > > L'UniversitÃ© Jean Moulin est membre fondateur de l'UniversitÃ© de Lyon > > _______________________________________________ > Koha mailing list http://koha-community.org > Koha(a)lists.katipo.co.nz > https://lists.katipo.co.nz/mailman/listinfo/koha >

1 0

Koha 3.18.11 Released
by Liz Rea 01 Oct '15

01 Oct '15

The Koha release team is pleased to announce the release of Koha 3.18.11. This is a maintenance release, but does contain one security fix. All users are recommended to upgrade. You can read the full release notes at http://koha-community.org/koha-3-18-11-released/ As usual, you can download the tarball from http://koha-community.org/downloads or wait for the debian packages, which should be forthcoming in the next day or two. Cheers, Liz

1 0