- Koha - lists.katipo.co.nz

[Koha-devel] Koha-3.0.1 Stable release
by LAURENT Henri-Damien 20 Feb '09

20 Feb '09

Hi, we are very happy to announce Koha3.0.1 Stable has been released on http://download.koha.org/ Its name is koha-3.00.01-stable.tar.gz You can download file and signatures You can check the integrity of the package; either by verifying the provided GPG signature (.sig) or by comparing the MD5 checksum: eb3577596c172fcafd7fe0e63ef3972e koha-3.00.01-stable.tar.gz I have also tagged this in Git as "version 3.00.01 stable" v3.00.01-stable_update You can download. An extract of release notes is pasted below Cheers -- Henri-Damien LAURENT Release Maintainer Koha 3.0.1 Beta Release : This release of Koha 3.0.1 includes the following general improvements over the previous release: * General Bugfixing Authorities : Authorities structure edition Authorities edition with diacritics merging authorities Adding failover when null string searched Cataloguing : When editing an item, clearing a field. OPAC : tags Management improved shelves browsing improved improved COInS Support Improved RSS support Boolean search on Advanced Search page (more options) Added Deletion of private list fix General Output : Improving concistency of strings markup corrections Adding some untranslated strings to translation files. More consistency in dates display UNIMARC Adds the creation date of biblios to frameworks in order to improve Rss support You have to launch the script ./maintenance/UNIMARC_sync_date_created_with_marc_biblio.pl 995$2 as lost items management. If you had a previous installation of Koha without 995$2 linked to items.lost then you have to launch the script ./maintenance/sync_items_in_marc_bib.pl and rebuild indexes with rebuild_zebra.pl (see wiki.koha.org or rebuild_zebra.pl -h for documentation) Fines fixes Some sorting problems on patron names and libraries fixed js and update of strings for better coherence CGI::Session::Serialize::yaml is now required and not only CGI::Session Adding better display of links on conformance with MARC standards Fixing POD for correctness Preparing for debian packaging Adding more SIP2 functions Adding some information on reports UTF8 support improved Failover improved Many performance improvements under the hood * Adding a Subject cloud * better UNIMARC version 5 compliance * Improving diacritics management in zebra * Additional translations * Improving Quality Assurance with test suite * Adding a Renew All button to OPAC * options added to overdue_notices script Subsequent releases will be bugfix releases, and won't include new features which would require some databas changes. Koha 3.0.x Release Schedule : we plan to issue bugfix only releases on a 2 month base from now on. So Next releases should be beginning of April, June, August, October, December. Note that Windows is not supported for this version as there are blockers. Note that this version is still supporting only MySQL. Support for PostgreSQL is still very experimental. New features which have deep impact on code will be available in Koha 3.2 and subsequent releases. ============================================================================== TRANSLATIONS ============================================================================== Koha 3.0 (this release) currently has complete translations for the following languages: OPAC: ar-Arab (Arabic), da-DK (Danish), de-DE (German), el-GR (Greek), es-ES (Spanish), en (English), en-NZ (New Zealand English), fr-FR (French), hu-HU (Hungarian), it-IT (Italian), nn-NO - Norwegian Nynorsk, nb-NO Norwegian (Bokmål), nl-NL (Dutch), pt-PT (Portuguese), tr-TR (Turkish), ru-RU (Russian), uk-UA (Ukranian) Staff Client: de-DE (German), el-EL (Greek), fr-FR (French), en (English), es-ES (Spanish), it-IT (Italian), uk-UA (Ukranian), Additionally, Koha 3 (this release) has partial translations for the following languages: OPAC: am-Ethi (Amharic), bg-Cyrl (Bulgarian), fa-Arab (Persian), fi-FI (Finnish) gl (Galician), he-Hebr (Hebrew), hr-HR (Croatian), hu-HU (Hungarian), id-ID (Indonesian), ja-Japn (Japanese), kn-Knda (kannada), ko-Kore (Korean), lo-Laoo (Laoo), mi-NZ (Maori), pl-PL (Polish), pt-PT (Portuguese), sv-SE (Swedish), tet (Tetum), zh-Hans-CN (Simplified Chinese in China), zh-Hans-TW (Simplified Chinese in Taiwan) Staff Client: ar-Arab (Arabic), es-ES (Spanish), hu-HU (Hungarian), hy-Armn (Armenian), ja-Japn (Japanese), nn-NO - Norwegian Nynorsk, nb-NO Norwegian (Bokmål), ru-RU (Russian), tr-TR (Turkish), zh-Hans-CN (Simplified Chinese in China), zh-Hans-TW (Simplified Chinese in Taiwan) The Koha Team welcomes additional translations; please see http://www.kohadocs.org/usersguide/apb.html for information about translating Koha, and join the koha-translate list to volunteer: http://lists.nongnu.org/mailman/listinfo/koha-translate _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel

4 4

hold queue is empty
by Amandeep Kansal 20 Feb '09

20 Feb '09

Dear All I have a problem related with hold queue, when a user hold a book, the hold request did not display in hold queue in circulation in koha intranet panel, hold queue is always empty. please help me.. Amandeep Kansal

3 3

list problem
by Amandeep Kansal 20 Feb '09

20 Feb '09

Dear All I am having a problem with the virtual lists. I can create a new list but I cannot add items to it when I click on "Save to your lists" (in an individual record). I get this error message: Koha error The following fatal error has occurred: Can't use string ("1") as an ARRAY ref while "strict refs" in use at /usr/share/koha/opac/cgi-bin/opac/opac-addbybiblionumber.pl line 98. Apache Server version: Apache/2.2.8 (Linux/SUSE) Server built: Nov 23 2008 23:31:28 Koha 3.00.00.107 Koha DB 3.0000107 MySQL mysql Ver 14.12 Distrib 5.0.51a, for suse-linux-gnu (x86_64) using readline 5.2 OS Linux koha 2.6.25.5-1.1-default #1 SMP 2008-06-07 01:55:22 +0200 x86_64 x86_64 x86_64 GNU/Linux Perl 5.010000 thanks Amandeep Kansal

1 0

Items marked long overdue one day after due date
by Tim McMahon 19 Feb '09

19 Feb '09

Running Koha 3, we're having all items marked long overdue one day after the due date and patrons are charged the items replacement price. Our LOST status is 1=lost and 2=long overdue. The crontab entry is from crontab.example 10 21 * * 1 $USER $KOHA_CRON_PATH/longoverdue.pl --lost 20=2 --lost 100=1 --charge 1 --confirm What else should I be checking to get long overdues to wait till books ar long ovedue? -- Tim McMahon Technical Services West Liberty Public Library

3 7

Matching rules on record import
by Martin Longo 19 Feb '09

19 Feb '09

Hi there I'm trying tu get my Koha3 up and running, but need some directions setting Matching Rules to import MARC records. First of all ... Matching rules seems to be working ok ... I've used the ISBN rule and got good results.... BUT ... there are some problems when the records don't have ISBN data (or ISSN) ... so I need a way to match those. for example .. I have this record (already imported into Koha) and when I try to import again it has "no match" (of course, because it has no ISBN) LDR 00645nam#a2200253#a#4500 001 CON000008 003 OUN 005 20060601105400 008 901227| xxu |||| ||eng d 040 _aOUN 080 _a3-055.2 080 _a341.16:362.7 092 _sNU _c3-055.2 _lH431u 100 1 _aHazzard, Virginia. 245 10 _aUnicef and women : _bthe long voyage : a historical perspective 260 _aNew York : _bUnicef, _cc1987. 300 _a148 p. ; _c27 cm. 440 _aUnicef history series. _pMonograph ; _v7 650 04 _aUNICEF 650 04 _aMUJERES 866 0 _a1 ej. 907 _aTEXTO 930 _a90476 _dREST _pv 942 _cBK So ... I need advice on how to set up a valid matching rule to handle a situation like this one. The records will come from various libraries (around 13) each one with distinctive control numbers (field 001) so I think maybe comparing this field and title (field 245$a) would give me a good enough matching rule. the problem is ... how to set it up on Koha :) Frist thing I don't understand completely ... when creating a new matching rule I must specify a "search index" value (on ISBN rule it has 'isbn'). Now, for something like what I need, what should be the value, if it has to be one... Thanks in advance -- Ing. J. Martin Longo Depto. Gestion Informatica SID - UNCuyo http://sid.uncu.edu.ar

6 8

Matching Koha to the Apache
by Darla Grediagin 19 Feb '09

19 Feb '09

Good morning, I am have gotten Linux working on the server, I have Koha installed, now the problem is to match the two together. When I go to the server I get a big message that says *'It works'* While this feels great and is steps beyond where I have gotten before, I now need to get Koha to come up on that website. I have edited /etc/apache2/ports.conf and added the line Listen 8080 When I restart apache2ctl, It tells be that it is using 10.3.33.15 for its name because it can't determine the server's fully qualified domain name. This is fine for when I go to 10.3.13.15 that is where i get the above statement. If this makes sense to someone out there, please let me know. It is all Greek to me. Thank you in advance, Darla -- Darla Grediagin District Librarian Bering Strait School District Unalakleet, Alaska Web Address : http://bssdonline.org/course/view.php?id=51 Blog: http://aklibrarian1.edublogs.org/ OPAC: http://opac.bssd.org:8181/cgi-bin/koha/opac-search.pl

2 1

LDAP Replication error.
by Barry Cannon 19 Feb '09

19 Feb '09

Hi All, I am still battling through getting Koha talking to LDAP. I have managed to get so far but the latest problem is shown below in the apache logs. The problem is the cardnumber field is being completely ignored on the replication. Other LDAP attributes come across fine but we can only manage one sync and the rest fail with the error below. This is obviously because the cardnumber has to be unique and the next patron to import is also '' so duplication occurs. Also, when a user logs into OPAC all the Parton Details attributes are blank. [Thu Feb 19 12:55:15 2009] opac-user.pl: DBD::mysql::st execute failed: Duplicate entry ' ' for key 2 at /usr/share/koha/lib/C4/Members.pm line 769, <DATA> line 466. AUTH_3: no results for userid='mmg', cardnumber=''. [Thu Feb 19 12:55:15 2009] opac-user.pl: PARAM:LOOP:next_loop:hash pointer was expected but not found at /usr/local/lib/perl/5.8.8/HTML/Template/Pro.pm line 191, <DATA> line 466. [Thu Feb 19 12:59:19 2009] opac-user.pl: DBD::mysql::st execute failed: Duplicate entry ' ' for key 2 at /usr/share/koha/lib/C4/Members.pm line 769, <DATA> line 466. AUTH_3: no results for userid='mmg', cardnumber=''. Can anyone help? Regards Barry Cannon

2 1

Re: [Koha] How to connect koha2.2.8 to my website
by thandu venkat narayana 19 Feb '09

19 Feb '09

Dear all I am working with koha 2.2.8 on windows-xp, now it is avialable in my office only. But I want to use this koha through my website from any location. How can I do this process? Please give your valuable guidelines. With Regards Venkata Narayana T. Check out the all-new Messenger 9.0! Go to http://in.messenger.yahoo.com/

2 1

Re: [Koha] Matching rules on record import
by Cab Vinton 19 Feb '09

19 Feb '09

>> It would be nice if during the import process Koha could check a >> sequence of matchpoints when checking for duplicate holdings (e.g., >> first check ISBN, then LCCN, etc.) This is currently not possible, >> however, right? I'm informed by Joshua & Galen that one can check a sequence of match points simply by adding additional match points to a rule set. (Thank you!) So, I've created a new matching rule based on the ISBN rule, adding a match point for the LCCN. I based the match point on the ISBN match point, changing the tag to 010 & entering LCCN as the normalization rule. My expectation was that this new rule would check the ISBN first for matches, & then the LCCN. A test case failed, however. I created a duplicate record of an item in our system & then deleted the 020 ISBN tags before attempting to stage the record. Unfortunately, the system did not pick up on the 010 LCCN match. I thought this might because, at least in our system, the LCCN numbers all seem to be preceded by 3 empty spaces. So I changed the Offset for the LCCN match point to 3. But this didn't work either. Does anyone see anything wrong with following setup for this new rule?: 1. Matching rule code: ISBNLCCN 2. Description: 020_010 3. Match threshold: 1000 Matchpoint 1 1. Search index: isbn 2. Score: 1000 1. Tag: 020 2. Subfields: a 3. Offset: 0 4. Length: 0 5. Normalization rule: ISBN Matchpoint 2 1. Search index: lccn 2. Score: 1000 1. Tag: 010 2. Subfields: a 3. Offset: 0 [or 3] 4. Length: 0 5. Normalization rule: LCCN [No match checks] Perhaps the problem is coming from the normalization rule. Not sure if this field is mandatory, how many normalization rules there are, etc. It would probably too easy to simply enter "OCLC" as a normalization rule when trying to match on the OCLC number ... Many thanks, Cab Vinton, Director Sanbornton Public Library Sanbornton, NH

1 0

Locations and sublocations, again
by Cab Vinton 19 Feb '09

19 Feb '09

Which of these is indexed/ treated as a facet in the OPAC for searching purposes?: 952 $a - Location (home branch) 952 $b - Sublocation or collection (holding branch) I'm assuming it's the latter. Many thanks, Cab Vinton, Director Sanbornton Public Library Sanbornton, NH

1 0