February 2011 - Koha-devel - lists.koha-community.org

Call for Articles: February Newsletter
by Nicole Engard 21 Feb '11

21 Feb '11

Hi all, It's that time again - please get me your newsletter articles by the 23rd (your time zone) of February so that I can include them in the newsletter. Thanks a bunch, Nicole C. Engard

1 1

Re: [Koha-devel] Solr and Z3950 server some news.
by Thomas Dukleth 21 Feb '11

21 Feb '11

When briefly testing the BibLibre test configuration of SimpleServer Z39.50 server I have found same problem as BibLibre are reporting when using yaz-client. I have also noted some other issues. 1. BAD MARC ERROR. When setting format to UNIMARC in yaz-client, the following error message is returned along with the record when displaying a record with the show command. "[]Record type: Unimarc bad MARC. Dumping as it is:" When setting format to XML in yaz-client, no error message is returned when displaying a record with the show command. "[]Record type: XML" The issue seems to be consistent for all records in the result set. YAZ is converting between ISO 2709 and MARCXML on the client side. yaz-client does not report a "bad MARC" error when displaying UNIMARC MARCXML records returned from Zebra in ISO 2709 form. Whatever the MARC error may be, it prevents YAZ from parsing the records properly in ISO 2709. Consequently, unlike yaz-client, my very well tested PHP YAZ based Z39.50 client obtains the result set but cannot even attempt to display the records because it relies upon YAZ for parsing them. 2. INVARIANT RESULT SET. In the configuration which I tested, any query would return exactly the same 1011 record result set whether or not there would be any legitimate matches. 3. MISSING EXPLAIN RECORD. Lack of an Explain record should not be fatal but might be helpful for obtaining more debugging information from YAZ. 4. DEBUGGING. I do not have time to try intensive tests myself. First, fix the issue where the result set is an invariant 1011 records. I suggest having yaz-client save the ISO 2709 records, then attempt to validate them with MARC::Lint keeping in mind that most errors would be from the MARC 21 checks in MARC::Lint. I have not verified that MARCXML is working with SimpleServer using Solr/Lucene but I would be happy to test that if some SimpleServer target would be configured to return only MARCXML. If all else fails, Index Data can help solve the problems for a very significant fee. Thomas Dukleth Agogme 109 E 9th Street, 3D New York, NY 10003 USA http://www.agogme.com +1 212-674-3783

2 3

Who are the various Koha vendors in the USA?
by Joann Ransom 21 Feb '11

21 Feb '11

ByWater have an excellent reputation in the States - check out Marshall Breeding's Perception guide: http://www.librarytechnology.org/perceptions2010.pl I wouldn't go near PTFS if you are looking for open source Koha. Cheers Jo. 2011/2/21 Buster <storypage(a)gmail.com> > And which one do you use, if any? > > > I know about LibLime and Bay Water. Anybody else? > > --JimMaroon > > -- > > ================================================== > "The man, who, by his own and his family's labour, can provide a > sufficiency of food and raiment and a comfortable dwelling place, is not a > poor man." --William Cobbett, *Cottage Economy*, 1826. > > > > _______________________________________________ > Koha mailing list http://koha-community.org > Koha(a)lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha > > -- Joann Ransom RLIANZA Head of Libraries, Horowhenua Library Trust. *Q: Why is this email three sentences or less? A: http://three.sentenc.es* -- Joann Ransom RLIANZA Head of Libraries, Horowhenua Library Trust. *Q: Why is this email three sentences or less? A: http://three.sentenc.es*

1 0

Re: [Koha-devel] [Koha] KohaCon 2011 : The Votes Are In
by Koustubha Kale 19 Feb '11

19 Feb '11

Hi All, I am just back from a Koha training trip in Konkan. And this is great news to come back to. :) Thanks to all who voted for VPM, Thane, India. And also special thanks to Nicole for conducting the vote. I will start preparations and discussions immediately as soon as I reach office. Looking forward to participation, help and advise from all the Koha community in making KohaCon11 a success.. Regards, Koustubha Kale Anant Corporation Contact Details : Address : 103, Armaan Residency, R. W Sawant Road, Nr. Golden Dyes Naka, Thane (w), Maharashtra, India, Pin : 400601. TeleFax : +91-22-21720108, +91-22-21720109 Mobile : +919820715876 Website : http://www.anantcorp.com Blog : http://www.anantcorp.com/blog/?author=2 On Fri, Feb 18, 2011 at 5:26 PM, Nicole Engard <nengard(a)gmail.com> wrote: > On Fri, Feb 18, 2011 at 6:27 AM, MJ Ray <mjr(a)phonecoop.coop> wrote: >> So... how can we win next time? In particular, should we bid with >> Weston-super-Mare or Edinburgh and are there any other pointers or >> tips that people would like to pass on, on-list or privately? > > MJ, I think it was pure numbers! With India off the table next year > (based on talks on #koha) I think we're gonna see a European location > next year :) I liked your location choice - all I wanted was for it to > be in the spring instead of the fall (but that's just me). > > Nicole > _______________________________________________ > Koha mailing list http://koha-community.org > Koha(a)lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha >

1 0

Add authorities add/del/mod logging
by Tomas Cohen Arazi 18 Feb '11

18 Feb '11

Hi, I'm planning to add logging to the authorities management. In the 'action_logs' table we have, for biblios: module : CATALOGUING action : ADD/DELETE/MODIFY for biblios, and other actions for issuing, object : a biblionumber or itemnumber info : string: 'biblio' or 'item' or previous 'marc' field (when MODIFYing) My first thought was that we could use 'CATALOGUING' too, and that instead of 'biblio' in the info field we could use 'authority'. Something like module : CATALOGUING action : ADD/DELETE/MODIFY object : a authid info : string: 'authority' or previous 'marc' field (when MODIFYing) But I realized that it is impossible to differentiate, from tools/viewlog.pl point of view, if we're talking about a biblionumber or an itemnumber (and now an authid) when the operation is MODIFY. Check this from Items.pm: logaction("CATALOGUING", "MODIFY", $itemnumber, $new_item_marc->as_formatted) if C4::Context->preference("CataloguingLog"); In the results in fact, they are all shown as biblios (bug?)! So, adding 'authid' to the mix will make it worse. Should I add AUTHCAT module? Should we split CATALOGUING module into BIBLIOCAT and ITEMCAT? Also: should we avoid logging when calling ModItem from Issues::AddIssue? It looks too much overhead as there is a call to $new_item_marc->as_formatted. Have a nice weekend! To+

1 0

Seeking opinions on Koha's calendar widget
by Owen Leonard 18 Feb '11

18 Feb '11

I would like to propose that we stop using the calendar widget which is currently included with Koha and start using the jQuery UI version at the same time that we incorporate jQuery UI into other areas of Koha (see bug 5481 - Replace YUI JS libraries with Jquery UI http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5481) Some reasons: - It's simpler to manage a single group of jQuery UI widgets than to continue to maintain a separate set of files just for the calendar. - jQueryUI is actively developed and packaged with Debian - Our current calendar widget is not longer being developed under GPL. The author asks $80 per domain for the current version. - The current calendar widget uses now-deprecated CSS properties which are causing problems in some browsers. The jQueryUI calendar widget can be tested here: http://jqueryui.com/demos/datepicker/ The configuration which most closely approaches the version we use is this one: http://jqueryui.com/demos/datepicker/#dropdown-month-year Note that when we implement jQuery UI we will be creating a "theme" for all jQuery UI widgets which will be consistent with Koha's colors. In other words, it doesn't have to be orange :) Can anyone suggest any reasons why we should not switch? -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org

8 9

KohaCon 2011 : The Votes Are In
by Nicole Engard 18 Feb '11

18 Feb '11

Hello all, The KohaCon 2011 Location Survey is closed. We had a total of 877 responses. If you voted for a location as your first choice it got 4 points, your second choice 3 points, and so on. Below is the break down in points. ** Thane, India [ End October - Beginning November ] 2640+150+62+33= 2885 ** Kathmandu, Nepal [ November / December 2011 ] 432+96+186+24= 738 Kolkata, India [ November / December 2011 ] 156+339+104+33= 632 Somerset or Bristol, UK [ September / October 2011 ] 160+141+72+108 = 481 The raw results will be posted to the wiki (I can't upload a CSV file - I need some admin help). I do want to know what your opinions are about posting the full CSV file to the wiki - it does have all our email addresses. I might remove that column before posting if enough people express a concern about that or just email the CSV to those who want to see the raw results and not worry about posting it publicly at all. Even if we ignore votes from those who didn't fill in all the information I'm pretty sure we have a winner. Thanks Nicole C. Engard PS. I recommend that we soon move on to voting for the location for 2012 so that we can get on top of things and conference planners have more time to prepare.

4 4

FW: zebra / Heading-Main
by Marcel de Rooy 18 Feb '11

18 Feb '11

Only in authorities.. Van: koha-devel-bounces(a)lists.koha-community.org [mailto:koha-devel-bounces@lists.koha-community.org] Namens Marcel de Rooy Verzonden: donderdag 17 februari 2011 15:25 Aan: koha-devel(a)lists.koha-community.org Onderwerp: [Koha-devel] zebra / Heading-Main Hi, Some time ago Heading-Main was introduced in both authorities and biblios record.abs in marc_defs/marc21 and marc_defs/unimarc. Apparently, it was added to extend authority search with the option to search only in 100a, 110a, .. fields. But Heading-Main is not listed in one the attsets (bib1,..) This gives the warning: zebraidx(18056) [warn] Index 'Heading-Main' not found in attset(s) This bug was reported March 2009 (!) under: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3072 Related reports are: 3052, 3386 and 3429. We still have the following temporary fix in AuthoritiesMarc.pm : ##If mainentry search $a tag if (@$tags[$i] eq "mainmainentry") { # FIXME: 'Heading-Main' index not yet defined in zebra # $attr =" \@attr 1=Heading-Main "; $attr =" \@attr 1=Heading "; Would anyone of you object against defining a new 8XXX field in authorities bib1.att to activate Heading-Main and at the same time fixing AuthoritiesMarc.pm ? We now have there: att 8001 Heading att 8002 See-from att 8003 See-also-from att 8804 Match-heading att 8805 Match-subdivision att 8806 Subdivision att 8807 Subdivision-see-also-from att 8808 Subdivision-see-from att 8809 Match-heading-see-from att 8810 Match-subdivision-see-from BTW, an interesting way of incrementing from 8001 to 8810? We could add 8004 for Heading-Main ? Better idea? Regards, Marcel

4 3

zebra / Heading-Main
by Marcel de Rooy 17 Feb '11

17 Feb '11

Hi, Some time ago Heading-Main was introduced in both authorities and biblios record.abs in marc_defs/marc21 and marc_defs/unimarc. Apparently, it was added to extend authority search with the option to search only in 100a, 110a, .. fields. But Heading-Main is not listed in one the attsets (bib1,..) This gives the warning: zebraidx(18056) [warn] Index 'Heading-Main' not found in attset(s) This bug was reported March 2009 (!) under: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3072 Related reports are: 3052, 3386 and 3429. We still have the following temporary fix in AuthoritiesMarc.pm : ##If mainentry search $a tag if (@$tags[$i] eq "mainmainentry") { # FIXME: 'Heading-Main' index not yet defined in zebra # $attr =" \@attr 1=Heading-Main "; $attr =" \@attr 1=Heading "; Would anyone of you object against defining a new 8XXX field in authorities bib1.att to activate Heading-Main and at the same time fixing AuthoritiesMarc.pm ? We now have there: att 8001 Heading att 8002 See-from att 8003 See-also-from att 8804 Match-heading att 8805 Match-subdivision att 8806 Subdivision att 8807 Subdivision-see-also-from att 8808 Subdivision-see-from att 8809 Match-heading-see-from att 8810 Match-subdivision-see-from BTW, an interesting way of incrementing from 8001 to 8810? We could add 8004 for Heading-Main ? Better idea? Regards, Marcel

1 0

Install hurdle, OpenSUSE on virtualbox
by Nelson Fredsell 15 Feb '11

15 Feb '11

Dear all, I've been repeatedly working through install steps at http://wiki.koha-community.org/wiki/Koha_3.0.0_on_openSUSE_11.3, and keep getting stuck. Currently, my Windows 7 laptop can't see the apache LAMP server on the OpenSUSE 11.3 virtualbox. With ifconfig I can see eth0 inet addr 192.168.1.16 Bcast 192.168.1.255 Mask 255.255.255.0. When I ping from the Windows side, I get request timed out. As indicated in the steps, I have a minimum install with no gui. Using yast to configure network. As an added step I changed from NAT to Bridged adapter in the VirtualBox config, but this didn't help. Any suggestions would be much appreciated. My current goal w/ Koha is to "simply" install the software, including Zebra. Nelson (nfred - irc)

4 5