- Koha - lists.katipo.co.nz

Fwd: Re: slow check out/check in
by Liz Rea 23 Sep '15

23 Sep '15

I failed at email addressing. This should have gone to the list. Hi Scott, Is that really Koha 3.01? The solution to this is probably "upgrade Koha," as this version is no longer supported. Cheers, Liz On 23/09/15 06:21, Scott Owen wrote: > Patrons seem to pull up fine, but, there seems to be a 30 second delay in > any part of the circulation module. > > Mass checking in a stack of books is taking huge amounts of time due to the > 30 second delay between scanning and the ability to do the next scan. > > Anything I can try for a quick fix on this ?? > > Using Firefox as the web browser, > > > > Server informationKoha version:3.01.00.145OS version ('uname -a'):Linux > koha3 2.6.26-2-686 #1 SMP Thu Aug 19 03:44:10 UTC 2010 i686 GNU/LinuxPerl > interpreter:/usr/bin/perlPerl version:5.010001Perl @INC:/usr/share/koha/lib > /etc/perl > /usr/local/lib/perl/5.10.1 > /usr/local/share/perl/5.10.1 > /usr/lib/perl5 > /usr/share/perl5 > /usr/lib/perl/5.10 > /usr/share/perl/5.10 > /usr/local/lib/site_perl > /usr/local/lib/perl/5.10.0 > /usr/local/share/perl/5.10.0 > . > MySQL version:mysql Ver 14.12 Distrib 5.0.51a, for debian-linux-gnu (i486) > using readline 5.2Apache version:Server version: Apache/2.2.16 (Debian)Zebra > version:Zebra 2.0.44 (C) 1994-2010, Index Data ApS Zebra is free software, > covered by the GNU General Public License, and you are welcome to change it > and/or distribute copies of it under certain conditions. SHA1 ID: > 419ad759807269fdfa379799a051ed3a551c6541 Using ICU > _______________________________________________ > Koha mailing list http://koha-community.org > Koha(a)lists.katipo.co.nz > https://lists.katipo.co.nz/mailman/listinfo/koha -- -- Liz Rea Catalyst.Net Limited Level 6, Catalyst House, 150 Willis Street, Wellington. P.O Box 11053, Manners Street, Wellington 6142 GPG: B149 A443 6B01 7386 C2C7 F481 B6c2 A49D 3726 38B7

1 0

Re: [Koha] Newly catalogued Items not searchable on OPAC and on Staff
by www retive 22 Sep '15

22 Sep '15

hi, i had the same problem (3.18.9 version); in the About Koha > System information i had warnings about the fact that i didn't choose between grs1 and dom indexing; switching from grs1 to dom indexing and doing a full reindex solved the problem. hope this helps. > I have recently entered more than three hundred item records in to Koha > 3.18.07.000. they are not searchable on both the opac and the Staff > interface, but can be circulated(checked out/ Checkin) using their barcode.

1 0

Marc21 uniform-title and koha
by Gaetan Boisson 22 Sep '15

22 Sep '15

Dear all, as a non specialist in marc21 i am being asked how to fill field 240 properly. What i understood from what was explained to me today, is that when 240 refers to a uniform title that doesn't have a clearly defined and unique author, a uniform-title authority will be used, with the header in 130. But if the title has one unique and unambiguous author, a person for instance, a personal name authority should be used, with the title in 100$t. Seeing how authorities work in Koha this doesn't seem feasible, as the subfields will be copied from the specified header to the bibliographic record, and this would involve copying a 100$t to a 240$a while the 100$a of the authority is copied to the 100$a of the bibliographic record. Can anyone confirm this understanding of the marc21 standard and give me a better clue of how it is supposed to be implemented in Koha? Thanks, -- Gaetan Boisson Chef de projet bibliothécaire BibLibre 06 52 42 51 29 108 avenue Breteuil 13006 Marseille gaetan.boisson(a)biblibre.com

3 4

System generated field 001 control number
by Pablo Bianchi 22 Sep '15

22 Sep '15

Hi! As MARC manual say about control number <http://www.loc.gov/marc/bibliographic/bd001.html> *"Field 001 may be system generated"* we wish Koha generate this number (lastUsed++), to avoid creating manually and periodically having to run a report to remove duplicates (from wiki <http://wiki.koha-community.org/wiki/Multipart_Bibliographics> *"There is currently no way to enforce uniqueness in the 001, or rather uniqueness in 001 + 003."*). We have *autoMemberNum* syspref for "next available card number", *autoBarcode* for 952$p, barcode. but nothing for 001, no marc21_field_001.pl vuilder plugin, only bug 9921 <http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9921> about *"Make it possible to force 001 = biblionumber"*, but that is not exactly what we are looking for. Being this something basic (but asked before <https://lists.katipo.co.nz/public/koha/2010-December/026618.html>) I wonder If I'm getting all wrong... Regards, Pablo BTW on current manual Cataloging Guides say that 001 is "accession number <http://manual.koha-community.org/current/en/catguides.html>", which is usually name to barcode.

6 7

Koha 3.20.4 released
by Chris Cormack 22 Sep '15

22 Sep '15

The Koha team are proud to announce the release of Koha 3.20.4. As always you are recommended to wait for the packages to be updated, but if you can’t wait you can download the release at download.koha-community.org Please go to http://koha-community.org/koha-3-20-4-released/ to read the full release notes Chris

1 0

slow check out/check in
by Scott Owen 22 Sep '15

22 Sep '15

Patrons seem to pull up fine, but, there seems to be a 30 second delay in any part of the circulation module. Mass checking in a stack of books is taking huge amounts of time due to the 30 second delay between scanning and the ability to do the next scan. Anything I can try for a quick fix on this ?? Using Firefox as the web browser, Server informationKoha version:3.01.00.145OS version ('uname -a'):Linux koha3 2.6.26-2-686 #1 SMP Thu Aug 19 03:44:10 UTC 2010 i686 GNU/LinuxPerl interpreter:/usr/bin/perlPerl version:5.010001Perl @INC:/usr/share/koha/lib /etc/perl /usr/local/lib/perl/5.10.1 /usr/local/share/perl/5.10.1 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10 /usr/local/lib/site_perl /usr/local/lib/perl/5.10.0 /usr/local/share/perl/5.10.0 . MySQL version:mysql Ver 14.12 Distrib 5.0.51a, for debian-linux-gnu (i486) using readline 5.2Apache version:Server version: Apache/2.2.16 (Debian)Zebra version:Zebra 2.0.44 (C) 1994-2010, Index Data ApS Zebra is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. SHA1 ID: 419ad759807269fdfa379799a051ed3a551c6541 Using ICU

1 0

Question about Koha Item types.
by Jesse Lambertson 21 Sep '15

21 Sep '15

Hello everyone. I am doing a bunch of record editing right now and I have a question about the Koha item-types as defined in 942 Vs. 952. I know we can edit items and define holdings according to defined item types in what is the 952 via the edit function. But if I have a bunch of records that were imported with $ y already coded in 952 as a BOOK, for instance, or a VISUAL MATERIAL, it seems those are NOT being listed and able to be added to search restrictions at the outset (because I had not defined item-types before I started importing). But all the ones I imported AFTER I defined item-types are (I think). My question is, if I edit the 942 in the cataloging module by choosing to attach an item-type to records, will those then become part of an item-type search capability? Or do I then need to ALSO edit the attached 952 holding fields too? In my mind, this seems redundant, but I do want to know. Curious. No rush, but I want to make sure I am layering as much usability and nuance into our catalogue as I am able. Thank you much. Jesse -- Jesse A Lambertson Librarian Sultan Qaboos Cultural Center 1100 16th St, NW Washington, DC 20036 Ph: (202)-677-3967 Ext. 104 jlambertson(a)sqcc.org

2 2

Newly imported users all get booked the enrollment fee
by Michael Kuhn 21 Sep '15

21 Sep '15

I had an empty Koha database with a user type "Adults" where enrollment period is set to 12 months, enrollment fee set to 10 Euro. Using menu "Tools > Import patrons" I loaded a number of users with user type "Adults" into the database, which went OK. Only the next day when the script "fines.pl" had run I saw that all these users had a fee of 10 Euro booked on their account. It seems like Koha thought all these users were newly enrolled so it booked the fee. All these users were migrated from another system and had already paid their fees, so there is no reason to book these 10 Euro. How can I prevent this behaviour? Or, if I can't prevent it - will it be enough to delete the respective lines in Koha table "accountlines"? I did not find much information about how the process of enrolling and the booking of the fee works. Basing on what date will the next fee get due etc. I appreciate any help! Kind regards, Michael

1 0

koha authority plugin adding choose aside from related headings
by schnydszch 21 Sep '15

21 Sep '15

In current iteration of Koha ILS, when authority plug-in is switch on in Cataloging and catalogers can only choose from controlled vocabularies/authorities/lists, the cataloger has to go through adding authorities/subjects through this plug-in. The cataloger is shown the authority plug-in search interface. When a user search for a particular term through the authority plug-in search interface, he/she is presented with the Topical term and all other related headings (Broader and Narrower heading and used/for see from) with clickable links for the Broader and narrower headings if only these headings were properly linked in the authorites. A user has the option to choose the topical term or heading searched and can also scroll down further for related headings (those in 15x) (see screenshots) but can not choose outright the broader or narrower headings referred to by the Main heading (55x) (see screenshot 1). authorities_choose.png <http://koha.1045719.n5.nabble.com/file/n5854045/authorities_choose.png> <http://koha.1045719.n5.nabble.com/file/n5854045/authorities_plugin2.png> If the topical term (Main heading) is chosen or click by clicking the 'choose' link, the term is added in the cataloging (Add biblio) module. While in order for the user to add the other narrower and broader headings, the user must search again for the previous search query in the authority plug-in and have to go to through the process of scrolling further for these terms and choosing them again in the authority plug-in. This task of adding authorities is tedious for the catalogers. I feel that this is not yet doable in Koha default installation, but I'm posting here to confirm if this really is the case. The ideal case here is to put a clickable 'choose' beside the linked terms (55x $wg or $wh) and when these clickables are clicked, these terms are put in a temporary table. A clickable 'Move to Record' then will add these terms in the Cataloging - Add Biblio module. I don't if this even doable in jquery, or if not it should be an enhancement to Koha ILS. go through the process of searching it again in the authority plug -- View this message in context: http://koha.1045719.n5.nabble.com/koha-authority-plugin-adding-choose-aside… Sent from the Koha-general mailing list archive at Nabble.com.

1 0

Kohacon 2016 location
by Mirko Tietgen 21 Sep '15

21 Sep '15

Hello everyone, the voting period is over and the preliminary results are in. Kohacon 2016 will be hosted by Aristotle University of Thessaloniki, Greece. Congratulations! The survey has been completed 1074 times. In some cases, people were overly enthusiastic and had to vote more than once, which lead to disqualification. The results are 80,35% Thessaloniki, Greece 08,10% Manila, Philippines [11,55% invalid] I'd like to thank the people behind both proposals for offering to host Kohacon 2016! See you all in Thessaloniki next May or June, Mirko -- Mirko Tietgen mirko(a)abunchofthings.net http://koha.abunchofthings.net http://meinkoha.de

3 2