- Koha - lists.katipo.co.nz

serial adding error
by Sunita Barve 09 Jun '09

09 Jun '09

I have upgraded my koha installation from 3.00.01 to 3.00.02 while adding serial in cataloguing through z3950 server i get the following error the same error was there in 3.00.01 as well is this a bug? Is there any solution to this error? Koha error The following fatal error has occurred: All arguments must be MARC::Field objects at /usr/share/koha/intranet/cgi-bin/cataloguing/addbiblio.pl line 146 Apache Server version: Apache/2.2.11 (Ubuntu) Server built: Apr 1 2009 16:03:38 Koha 3.00.02.012 Koha DB 3.0002012 MySQL mysql Ver 14.12 Distrib 5.0.75, for debian-linux-gnu (i486) using readline 5.2 OS Linux lib-pc.ncra.tifr.res.in 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 Perl 5.010000 -- Dr. Sunita Barve SIRC-In-Charge National Centre for Radio Astrophysics Post Bag No. 3, Pune Univ. Campus Pune 411 007, INDIA Phone : Office : 91-20-25719211 Residence : 91-020- 24470022 Mobile: 9922753827 Email : sunitab(a)ncra.tifr.res.in ; sunitabarve(a)gmail.com

1 0

Fwd: Record matching rule for Koha biblio 999c?
by savitra sirohi 09 Jun '09

09 Jun '09

Nelson, you shoud use index "Local-Number". Thanks, Savitra 2009/6/9 Nelson Fredsell -CCE <nelson(a)cfce.org.za> > On batch edits of records and items, I’m using Koha Tools and MarcEdit. > On record matching rules for re-import, we cannot make use of ISBN or ISSN > as neither have been used in legacy catalogue. We’ve been advised to use > Koha biblio number as the unique identifier. > > > > Might anyone be able to share settings for a record matching rule on the > Koha biblio number, 999c? I looked in the manual, but it didn’t seem to > provide enough info for me to actually set up this rule. > > ( > http://koha.org/documentation/manual/3.0/administration/catalog-administrat…) > > > > For testing, I’m exporting a single biblio *.mrc, making edits w/ MarcEdit > *.mrk, re-compiling to *.mrc, then staging w/ Koha Tools. Koha then gives > me a no_match on the record, so I suspect that I’ve used incorrect settings. > > > > Using the ISBN rule as an example, I set up the following: > > -------------------------------------------- > > Matching rule code: KBiblio > > Desc: 999$c > > Match threshold: 1000 > > > > Match points – > > Search index: KBiblio (Do I need an actual Koha index, > or just make something up?) > > Score: 1000 > > Tag: 999 > > Subfields: c > > Offset: 0 > > Length: 0 > > Normalization rule: KBiblio (Do I need an actual Koha rule, or just > make something up?) > > > > If I need actual Koha search index and/or normalization rule, pls cite URL > in manual. > > > > Match checks – N/A > > ---------------------------------------- > > Thanks for any feedback, > > Nelson > > > > Implementing a union catalogue > > in Cape Town, South Africa > > > > > > _______________________________________________ > Koha mailing list > Koha(a)lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha > >

1 0

Indexing problem after importing staged MARC records?
by jthornton 08 Jun '09

08 Jun '09

Our cataloger staged and then imported 13 MARC records. Their status is "imported" and they all were assigned bib numbers. I ran (as root) 'rebuild_zebra.pl -b -a -z' (like the crontab.example file), which finished without an error, but searches for those titles retrieve zero results. Can anyone tell me what I'm doing wrong? Thanks, Joe Thornton IT Consultant Capital District Library Council 28 Essex Street Albany, NY 12206 518-437-9880 x230 Koha version: 3.00.01.005 OS version: Linux koha 2.6.26-1-686 2009 i686 GNU/Linux Perl version: 5.010000 MySQL version: mysql Ver 14.12 Distrib 5.0.51a Apache version: Server version: Apache/2.2.9 (Debian) Zebra version: Zebra 2.0.37 -- View this message in context: http://www.nabble.com/Indexing-problem-after-importing-staged-MARC-records-… Sent from the Koha - Discuss mailing list archive at Nabble.com.

2 1

Re: [Koha] Follett -> KOHA --- 050 field issues
by Doug Dearden 08 Jun '09

08 Jun '09

Robert, Check http://contribs.koha.org/ for a follett to koha conversion script. If you didn't use MarcEdit to break out the record you posted, you need to get that for the script to work. Koha will support multiple 952 records - they are your item records and are repeatable. Best, Doug >>> OLGS <vocations(a)fsspolgs.org> 6/5/2009 8:46:27 AM >>> Hello Everybody, We have decided to change from Follett (2001v) to KOHA. We exported our MARC records from KOHA but there are some things we don't understand. The records all contain the LC number in the Follett 852 field and there are no 050 or 090 LC fields. If we replace the 852 to 952 fields, as noted in the KOHA documentation, what do we do about the missing 050 fields? Follett seems to grab the call numbers from the 852 field. What will KOHA do? Do we have create 050 fields for each record now? By-the-way, I am helping with this migration and just graduated with my MLS. So I don't know anything about how they used this system before me and the librarian isn't that technical. I am stuck in the middle of this migration process trying to determine why 050s were not used and so I don't know if this is a Follett problem, some configuration issue when they set up Follett initially, or something currently being done when they enter records. Here is a sample of a MARC record: =LDR 04790nam 2200793u 4500 =001 B8908AAD60E711D69FD000C0F0520B92 =005 20020506115427.0 =008 020506n\\\\\\\\\\\\\\\\\\\\\\000\0\eng\d =020 \\$a10749 =100 1\$aCopleston, Frederick =245 00$aHistory of Philosophy =260 00$aGarden City, New York$bImage Books$c1962 =300 \\$a9 v. in 17 =500 \\$aImage book ed. 1962 with special arrangement with Newman Press =505 0\$av.1. Greece and Rome.--v.2. Medieval philosophy, Augustine to Scotus.--v.3. Ockham to Suarez.--v.4. Decartes to Leibnitz.--v.5. Hobbes to Hume.--v.6. Wolff to Kant.--v.7. Fitche to Nietzsche. --v.8. Bentham to Russell.--v.9. Maine de Biran to Sartre. =650 \\$aphilosophy$xhistory =852 \\$hB72 .C62 1962 v.1 pt1 c.2$pT0010749$xFSC@aR@c20020506$807/24/1995 =852 \\$hB72 .C62 1962 v.2 pt1 c.2$pT0010806$xFSC@aR@c20020506$807/24/1995 =852 \\$hB72 .C62 1962 v.2 pt2 c.2$pT0010807$xFSC@aR@c20020506$807/24/1995 =852 \\$hB72 .C62 1962 v.3 pt1 c.2$pT0010808$xFSC@aR@c20020506$807/24/1995 =852 \\$hB72 .C62 1962 v.3 pt2 c.2$pT0010809$xFSC@aR@c20020506$807/24/1995 =852 \\$hB72 .C62 1962 v.4 c.2 Set$pT0010810$xFSC@aR@c20020506$807/24/1995 =852 \\$hB72 .C62 1962 v.5 pt1 c.2$pT0010811$xFSC@aR@c20020506$807/24/1995 =852 \\$hB72 .C62 1962 v.5 pt2 c.2$pT0010812$xFSC@aR@c20020506$807/24/1995 =852 \\$hB72 .C62 1962 v.6 pt1 c.2$pT0010813$xFSC@aR@c20020506$807/24/1995 =852 \\$hB72 .C62 1962 v.6 pt2 c.2$pT0010814$xFSC@aR@c20020506$807/24/1995 =852 \\$hB72 .C62 1962 v.7 pt1 c.2$pT0010815$xFSC@aR@c20020506$807/24/1995 =852 \\$hB72 .C62 1962 v.7 pt2 c.2$pT0010816$xFSC@aR@c20020506$807/24/1995 =852 \\$hB72 .C62 1962 v.8 pt1 c.2$pT0010817$xFSC@aR@c20020506$807/24/1995 =852 \\$hB72 .C62 1962 v.8 pt2 c.2$pT0010818$xFSC@aR@c20020506$807/24/1995 =852 \\$hB72 .C62 1962 v.9 pt1 c.2$pT0010819$xFSC@aR@c20020506$807/24/1995 =852 \\$hB72 .C62 1962 v.9 pt2 c.2$pT0010820$xFSC@aR@c20020506$807/24/1995 =852 \\$hB72 .C62 1962 v.1 pt1 c.3$pT0011251$xFSC@aR@c20020506$819950724 =852 \\$hB72 .C62 1962 v.1 pt1$pT0011252$xFSC@aR@c20020506$819950724 =852 \\$hB72 .C62 1962 v.1 pt1 c.3$pT0011253$xFSC@aR@c20020506$819950724 =852 \\$hB72 .C62 1962 v.1 pt2 c.3$pT0011254$xFSC@aR@c20020506$819950724 =852 \\$hB72 .C62 1962 v.2 pt1 c.3$pT0011255$xFSC@aR@c20020506$819950724 =852 \\$hB72 .C62 1962 v.2 pt2$pT0011256$xFSC@aR@c20020506$819950724 =852 \\$hB72 .C62 1962 v.2 pt2$pT0011257$xFSC@aR@c20020506$819950724 =852 \\$hB72 .C62 1962 v.2 pt2 c.3$pT0011258$xFSC@aR@c20020506$819950724 =852 \\$hB72 .C62 1962 v.5 pt2 c.3$pT0011259$xFSC@aR@c20020506$819950724 =852 \\$hB72 .C62 1962 v.3 pt1 c.3$pT0020735$xFSC@aR@c20020506$820001211 =852 \\$hB72 .C62 1962 v.3 pt2 c.3$pT0020736$xFSC@aR@c20020506 =852 \\$hB72 .C62 1962 v.4 c.3$pT0020737$xFSC@aR@c20020506 =852 \\$hB72 .C62 1962 v.5 pt1 c.3$pT0020738$xFSC@aR@c20020506 =852 \\$hB72 .C62 1962 v.6 pt1 c.3$pT0020739$xFSC@aR@c20020506 =852 \\$hB72 .C62 1962 v.6 pt2 c.3$pT0020740$xFSC@aR@c20020506 =852 \\$hB72 .C62 1962 v.7 pt1 c.3$pT0020741$xFSC@aR@c20020506 =852 \\$hB72 .C62 1962 v.7 pt2 c.3$pT0020742$xFSC@aR@c20020506 =852 \\$hB72 .C62 1962 v.8 pt1 c.3$pT0020743$xFSC@aR@c20020506 =852 \\$hB72 .C62 1962 v.8 pt2 c.3$pT0020744$xFSC@aR@c20020506 =852 \\$hB72 .C62 1962 v.9 pt1 c.3$pT0020745$xFSC@aR@c20020506 =852 \\$hB72 .C62 1962 v.9 pt2 c.3$pT0020746$xFSC@aR@c20020506 =852 \\$hB72 .C62 1962 v.1 pt1 c.4$pT0020747$xFSC@aR@c20020506$820001211 =852 \\$hB72 .C62 1962 v.1 pt2 c.4$pT0020748$xFSC@aR@c20020506$820001211 =852 \\$hB72 .C62 1962 v.2 pt1 c.4$pT0020749$xFSC@aR@c20020506$820001211 =852 \\$hB72 .C62 1962 v.2 pt2 c.4$pT0020750$xFSC@aR@c20020506$820001211 =852 \\$hB72 .C62 1962 v.3 pt1 c.4$pT0020751$xFSC@aR@c20020506$820001211 =852 \\$hB72 .C62 1962 v.3 pt1 c.4$pT0020752$xFSC@aR@c20020506$820001211 =852 \\$hB72 .C62 1962 v.4 c.4$pT0020753$xFSC@aR@c20020506$820001211 =852 \\$hB72 .C62 1962 v.5 pt1 c.4$pT0020754$xFSC@aR@c20020506$820001211 =852 \\$hB72 .C62 1962 v.5 pt2 c.4$pT0020755$xFSC@aR@c20020506$820001211 =852 \\$hB72 .C62 1962 v.6 pt1 c.4$pT0020756$xFSC@aR@c20020506$820001211 =852 \\$hB72 .C62 1962 v.6 pt2 c.4$pT0020757$xFSC@aR@c20020506$820001211 =852 \\$hB72 .C62 1962 v.7 pt1 c.4$pT0020758$xFSC@aR@c20020506$820001211 =852 \\$hB72 .C62 1962 v.7 pt2 c.4$pT0020759$xFSC@aR@c20020506$820001211 =852 \\$hB72 .C62 1962 v.9 pt1 c.4$pT0020760$xFSC@aR@c20020506$820001211 =852 \\$hB72 .C62 1962 v.2 pt1 c.5$pT0037852$xFSC@aR@c20060915 =952 \\$iSet2 As you can see, the record has multiple 852 fields. One of the other issues that I can see happening is that for us to export the data into KOHA, the documentation says we need to convert 852 fields to 952s. There only appears to be one 952 field allowed, from what I can see, and so how can KOHA deal with all the 852 fields? It will try to merge them into one? Bomb out completely? Not sure what is going on what that too. Any help anyone can provide would be great. We are spinning our tires on this one trying to figure out how to move forward. Thanks! Robert -- View this message in context: http://www.nabble.com/Follett--%3E-KOHA-----050-field-issues-tp23889646p238… Sent from the Koha - Discuss mailing list archive at Nabble.com. _______________________________________________ Koha mailing list Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha

3 2

Incomplete imports
by Justin Aquadro 08 Jun '09

08 Jun '09

Greetings all, We are looking into using Koha in our school system to replace the aging Winnebago Spectrum. I've installed 3.0.1 on a test server to play with. I've become hung up on the imports however. Taking an export of ~15000 records from Spectrum, I swapped the 852 fields to 952 in MarcEdit according to the wiki instructions, and staged the import without problem. However when I started importing the staged records, it made it through 160 records and just stopped, no error messages or any kind of feedback from the import page. Now I have a partially complete import that I can't resume or roll back. The same thing happened when I tried breaking the import into batches of 1000, the script just stopped processing after an arbitrary number of records. Can anyone offer some insight into what's causing these frozen, incomplete imports? Since there's no errors, I'm at a loss. Also, how can I cleanly remove these frozen batches from the staging area? Many thanks, Justin. P.S. I apologize in advance if this message was accidentally dispatched twice. __________ Information from ESET NOD32 Antivirus, version of virus signature database 4136 (20090606) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com

5 5

Follett -> KOHA --- 050 field issues
by OLGS 08 Jun '09

08 Jun '09

Hello Everybody, We have decided to change from Follett (2001v) to KOHA. We exported our MARC records from KOHA but there are some things we don't understand. The records all contain the LC number in the Follett 852 field and there are no 050 or 090 LC fields. If we replace the 852 to 952 fields, as noted in the KOHA documentation, what do we do about the missing 050 fields? Follett seems to grab the call numbers from the 852 field. What will KOHA do? Do we have create 050 fields for each record now? By-the-way, I am helping with this migration and just graduated with my MLS. So I don't know anything about how they used this system before me and the librarian isn't that technical. I am stuck in the middle of this migration process trying to determine why 050s were not used and so I don't know if this is a Follett problem, some configuration issue when they set up Follett initially, or something currently being done when they enter records. Here is a sample of a MARC record: =LDR 04790nam 2200793u 4500 =001 B8908AAD60E711D69FD000C0F0520B92 =005 20020506115427.0 =008 020506n\\\\\\\\\\\\\\\\\\\\\\000\0\eng\d =020 \\$a10749 =100 1\$aCopleston, Frederick =245 00$aHistory of Philosophy =260 00$aGarden City, New York$bImage Books$c1962 =300 \\$a9 v. in 17 =500 \\$aImage book ed. 1962 with special arrangement with Newman Press =505 0\$av.1. Greece and Rome.--v.2. Medieval philosophy, Augustine to Scotus.--v.3. Ockham to Suarez.--v.4. Decartes to Leibnitz.--v.5. Hobbes to Hume.--v.6. Wolff to Kant.--v.7. Fitche to Nietzsche. --v.8. Bentham to Russell.--v.9. Maine de Biran to Sartre. =650 \\$aphilosophy$xhistory =852 \\$hB72 .C62 1962 v.1 pt1 c.2$pT0010749$xFSC@aR@c20020506$807/24/1995 =852 \\$hB72 .C62 1962 v.2 pt1 c.2$pT0010806$xFSC@aR@c20020506$807/24/1995 =852 \\$hB72 .C62 1962 v.2 pt2 c.2$pT0010807$xFSC@aR@c20020506$807/24/1995 =852 \\$hB72 .C62 1962 v.3 pt1 c.2$pT0010808$xFSC@aR@c20020506$807/24/1995 =852 \\$hB72 .C62 1962 v.3 pt2 c.2$pT0010809$xFSC@aR@c20020506$807/24/1995 =852 \\$hB72 .C62 1962 v.4 c.2 Set$pT0010810$xFSC@aR@c20020506$807/24/1995 =852 \\$hB72 .C62 1962 v.5 pt1 c.2$pT0010811$xFSC@aR@c20020506$807/24/1995 =852 \\$hB72 .C62 1962 v.5 pt2 c.2$pT0010812$xFSC@aR@c20020506$807/24/1995 =852 \\$hB72 .C62 1962 v.6 pt1 c.2$pT0010813$xFSC@aR@c20020506$807/24/1995 =852 \\$hB72 .C62 1962 v.6 pt2 c.2$pT0010814$xFSC@aR@c20020506$807/24/1995 =852 \\$hB72 .C62 1962 v.7 pt1 c.2$pT0010815$xFSC@aR@c20020506$807/24/1995 =852 \\$hB72 .C62 1962 v.7 pt2 c.2$pT0010816$xFSC@aR@c20020506$807/24/1995 =852 \\$hB72 .C62 1962 v.8 pt1 c.2$pT0010817$xFSC@aR@c20020506$807/24/1995 =852 \\$hB72 .C62 1962 v.8 pt2 c.2$pT0010818$xFSC@aR@c20020506$807/24/1995 =852 \\$hB72 .C62 1962 v.9 pt1 c.2$pT0010819$xFSC@aR@c20020506$807/24/1995 =852 \\$hB72 .C62 1962 v.9 pt2 c.2$pT0010820$xFSC@aR@c20020506$807/24/1995 =852 \\$hB72 .C62 1962 v.1 pt1 c.3$pT0011251$xFSC@aR@c20020506$819950724 =852 \\$hB72 .C62 1962 v.1 pt1$pT0011252$xFSC@aR@c20020506$819950724 =852 \\$hB72 .C62 1962 v.1 pt1 c.3$pT0011253$xFSC@aR@c20020506$819950724 =852 \\$hB72 .C62 1962 v.1 pt2 c.3$pT0011254$xFSC@aR@c20020506$819950724 =852 \\$hB72 .C62 1962 v.2 pt1 c.3$pT0011255$xFSC@aR@c20020506$819950724 =852 \\$hB72 .C62 1962 v.2 pt2$pT0011256$xFSC@aR@c20020506$819950724 =852 \\$hB72 .C62 1962 v.2 pt2$pT0011257$xFSC@aR@c20020506$819950724 =852 \\$hB72 .C62 1962 v.2 pt2 c.3$pT0011258$xFSC@aR@c20020506$819950724 =852 \\$hB72 .C62 1962 v.5 pt2 c.3$pT0011259$xFSC@aR@c20020506$819950724 =852 \\$hB72 .C62 1962 v.3 pt1 c.3$pT0020735$xFSC@aR@c20020506$820001211 =852 \\$hB72 .C62 1962 v.3 pt2 c.3$pT0020736$xFSC@aR@c20020506 =852 \\$hB72 .C62 1962 v.4 c.3$pT0020737$xFSC@aR@c20020506 =852 \\$hB72 .C62 1962 v.5 pt1 c.3$pT0020738$xFSC@aR@c20020506 =852 \\$hB72 .C62 1962 v.6 pt1 c.3$pT0020739$xFSC@aR@c20020506 =852 \\$hB72 .C62 1962 v.6 pt2 c.3$pT0020740$xFSC@aR@c20020506 =852 \\$hB72 .C62 1962 v.7 pt1 c.3$pT0020741$xFSC@aR@c20020506 =852 \\$hB72 .C62 1962 v.7 pt2 c.3$pT0020742$xFSC@aR@c20020506 =852 \\$hB72 .C62 1962 v.8 pt1 c.3$pT0020743$xFSC@aR@c20020506 =852 \\$hB72 .C62 1962 v.8 pt2 c.3$pT0020744$xFSC@aR@c20020506 =852 \\$hB72 .C62 1962 v.9 pt1 c.3$pT0020745$xFSC@aR@c20020506 =852 \\$hB72 .C62 1962 v.9 pt2 c.3$pT0020746$xFSC@aR@c20020506 =852 \\$hB72 .C62 1962 v.1 pt1 c.4$pT0020747$xFSC@aR@c20020506$820001211 =852 \\$hB72 .C62 1962 v.1 pt2 c.4$pT0020748$xFSC@aR@c20020506$820001211 =852 \\$hB72 .C62 1962 v.2 pt1 c.4$pT0020749$xFSC@aR@c20020506$820001211 =852 \\$hB72 .C62 1962 v.2 pt2 c.4$pT0020750$xFSC@aR@c20020506$820001211 =852 \\$hB72 .C62 1962 v.3 pt1 c.4$pT0020751$xFSC@aR@c20020506$820001211 =852 \\$hB72 .C62 1962 v.3 pt1 c.4$pT0020752$xFSC@aR@c20020506$820001211 =852 \\$hB72 .C62 1962 v.4 c.4$pT0020753$xFSC@aR@c20020506$820001211 =852 \\$hB72 .C62 1962 v.5 pt1 c.4$pT0020754$xFSC@aR@c20020506$820001211 =852 \\$hB72 .C62 1962 v.5 pt2 c.4$pT0020755$xFSC@aR@c20020506$820001211 =852 \\$hB72 .C62 1962 v.6 pt1 c.4$pT0020756$xFSC@aR@c20020506$820001211 =852 \\$hB72 .C62 1962 v.6 pt2 c.4$pT0020757$xFSC@aR@c20020506$820001211 =852 \\$hB72 .C62 1962 v.7 pt1 c.4$pT0020758$xFSC@aR@c20020506$820001211 =852 \\$hB72 .C62 1962 v.7 pt2 c.4$pT0020759$xFSC@aR@c20020506$820001211 =852 \\$hB72 .C62 1962 v.9 pt1 c.4$pT0020760$xFSC@aR@c20020506$820001211 =852 \\$hB72 .C62 1962 v.2 pt1 c.5$pT0037852$xFSC@aR@c20060915 =952 \\$iSet2 As you can see, the record has multiple 852 fields. One of the other issues that I can see happening is that for us to export the data into KOHA, the documentation says we need to convert 852 fields to 952s. There only appears to be one 952 field allowed, from what I can see, and so how can KOHA deal with all the 852 fields? It will try to merge them into one? Bomb out completely? Not sure what is going on what that too. Any help anyone can provide would be great. We are spinning our tires on this one trying to figure out how to move forward. Thanks! Robert -- View this message in context: http://www.nabble.com/Follett--%3E-KOHA-----050-field-issues-tp23889646p238… Sent from the Koha - Discuss mailing list archive at Nabble.com.

2 2

Z39.50 server problem
by jthornton 08 Jun '09

08 Jun '09

I'm new to Linux and Koha so I apologize if the answer to this is obvious to experts or if it's been answered already -- although I've been looking for an answer for a few days. I installed Koha and imported almost 400,000 bib records and indexed them with zebra. The Koha client looks great -- all the records are there and searchable. I enabled the Z39.50 server and I can search and retrieve records using yaz-client on the koha server. I installed a simple web-based Z39.50 client (written by Mark Jordan, I think) on my desktop. When I query the Koha database through this client it returns the number of search results (the correct number) but no data. This client works fine for other Z39.50 targets. The relevant section of the client's config file: $config_settings = array('title' => 'testZ', 'yaz_connect_string' => '192.168.0.114:9999/biblios', 'yaz_record_syntax' => 'marc21', 'yaz_max_records' => '1000', 'z3950_scan' => 1 ); I also exposed this database to the world and queried it with another Z39.50 client (URSA from SirsiDynix) and got an error (I don't know where the error log for this client is, but I'm looking). The relevant section of the config file for that client looks like this: //Operating parameteres for Partial Union Catalog PUC.PROTO = 'Z3950' PUC.Z3950.DBNAME = 'biblios' PUC.Z3950.TCP.HOST = '66.193.16.555' PUC.Z3950.TCP.PORT = 9999 PUC.Z3950.OPTIONS.RECSYN = 'USMARC' Has anyone had a similar experience? Is it the record syntax? Any help would be greatly appreciated. Thanks, Joe Thornton IT Consultant Capital District Library Council 28 Essex Street Albany, NY 12206 518-437-9880 x230 Koha version: 3.00.01.005 OS version: Linux koha 2.6.26-1-686 #1 SMP Fri Mar 13 18:08:45 UTC 2009 i686 GNU/Linux Perl version: 5.010000 MySQL version: mysql Ver 14.12 Distrib 5.0.51a Apache version: Server version: Apache/2.2.9 (Debian) Zebra version: Zebra 2.0.37 -- View this message in context: http://www.nabble.com/Z39.50-server-problem-tp23874740p23874740.html Sent from the Koha - Discuss mailing list archive at Nabble.com.

3 2

Overdue notices
by Owen Leonard 08 Jun '09

08 Jun '09

We want our Koha-generated emailed overdue notices to come from an address other than our KohaAdminEmailAddress. My first thought is to set our special email address (overdues(a)myacpl.org) as the branch email address for each branch, but I wonder if that's going to affect some other kind of communication. Is the branch email address used for anything else? -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org

2 1

Workshop at NCSI on library automation packages and digital library software
by K.T Anuradha 08 Jun '09

08 Jun '09

WORKSHOP ANNOUNCEMENT NCSI-IDRC Workshop on Library Automation Packages and Digital Library Software: July 27th to 31st and August 3rd to 7th, 2009 (http://dharmaganja.ncsi.iisc.ernet.in/workshop ) Two workshops of one week duration each on Library Automation Packages (LAP) and its integration with Digital Library Software is organised at National Centre for Science Information (NCSI), Indian Institute of Science (IISc), Bangalore from July 27th to 31st and August 3rd to 7th. Topics covered include installation, Staff-Client and OPAC modules of a few LAP and its integration with Digital Library Software on Linux (Ubuntu) platform. The workshop is organised as part of a project on ILAP carried out at NCSI, funded by The International Development Research Centre (IDRC), a Crown Corporation and an agency of the Government of Canada. One of the objectives of the project is to test the available technological tools for the development of union catalogue and to train manpower to implement union catalogue at their respective institutions/libraries. To fulfill this objective a series of workshop is organised. First workshop was organised from 5th to 9th January, 2009 and this is second and third workshop in the series. For registration and more details access the workshop page at: http://dharmaganja.ncsi.iisc.ernet.in/workshop Workshop coordinator: Dr.Anuradha.K.T. E-mail: anu(a)ncsi.iisc.ernet.in Technical Officer Gr III URL:vidya-mapak.ncsi.iisc.ernet.in National Centre for Science Information Indian Institute of Science FAX:(+91-80) 23601426/23600683 Karnataka, Bangalore 560 012 Tel:(+91-80) 23600271/22932511 India ---------------------------------------------------------------------------

1 0

Workshop on KOHA Library Management Software at NCRA, Pune from 13th-15th July 2009
by Sunita Barve 08 Jun '09

08 Jun '09

Dear all, NCRA Pune is organising a workshop on KOHA an open source library management software from 13th July to 15th July 2009. The workshop will cover installation of KOHA on linux operating system, Introduction to Linux Operating System, customization and configuration of KOHA software, demonstration of all modules (Acquisitions, Cataloguing, Serial Control, Circulation & OPAC), Introduction to MARC 21, multilingual support in KOHA, MARC records, Import feature in KOHA etc. The registration fees for the workshop is Rs. 3000/- which includes workshop kit (software installables, installable of Operating System, Training Material), breakfast, tea and working lunch. Accomodation can be provided at NCRA guest house for the outstation candidates at an additional charges. The number of participants is expected to be 30 and the preference will be given to those candidates who have basic knowledge of handling computers. The workshop can be attended by the librarians, information specialists who are working in different types of libraries and wish to automate their library collections. Please find more updates about the workshop at the following URL:- http://www.ncra.tifr.res.in/library/kohaworkshop/index.html For any queries please contact the undersigned. Dr. Sunita Barve SIRC-In-Charge National Centre for Radio Astrophysics Post Bag No. 3, Pune Univ. Campus Pune 411 007, INDIA Phone : 91-20-25719211 (Office) 9922753827(Mobile) FAX : 91-20-25697257 ; 25692149 Email :sunitab@ncra.tifr.res.in

1 0