- Koha - lists.katipo.co.nz

Re: UK Koha users?
by Andrea Chandler 17 Mar '03

17 Mar '03

I'm sure I'm not the only British librarian lurking on this mailing list. Is there anyone out there in the UK using or considering Koha who would like to share ideas? And is there anyone offering formal support in England? There was nothing up on the website. Email me off-list if you wish. Regards, Andrea Chandler

2 1

MARC scheme for item data
by Larry Currie 17 Mar '03

17 Mar '03

We're getting ready to load item data from a file into our MARC records, and I proposed that the following fields be added to each MARC record: 945 b biblio.biblionumber c biblioitems.biblioitemnumber 946 a biblioitems.biblioitemnumber b biblioitems.itemtype c biblioitems.dewey and for each copy or, in the case of multivolume works, each volume, a 949 field with the following subfields: 949 a items.itemnumber b items.biblionumber c items.multivolumepart d items.biblioitemnumber e items.barcode f items.dateaccessioned g items.homebranch h items.price i items.datelast seen j items.issues k items.itemsnotes l items.holdingbranch .... .... My question is, I came upon this scheme only because it seemed to pass the Check MARC test within the MARC Related section of version 1.9.0, but is this the optimal scheme to use? I noticed that Paul Poulain has proposed that the 995 tag be used for the item data in conjunction with Biblio.pm and I can certainly make this change. Am I correct in assuming that there will be one such field for each volume and copy of a work (i.e., that the 949s or 995s will be repeatable)? What about the information I have chosen to go into 945 and 946 fields? Is this appropriate? We have also tried to get some guidance from the Library of Congress MARC specifications pages as to whether we should either 1) be creating separate MARC holdings records and/or 2) modifying the leaders of our MARC records to indicate that they contain holdings tags. I personally don't think that we have to concern ourselves with either of these specifications, but I just want to be sure. Larry Currie -- Lawrence W. Currie User Services Librarian California Academy of Sciences Golden Gate Park San Francisco, CA 94118 lcurrie(a)calacademy.org (415) 750-7108 (415) 750-7106 fax http://www.calacademy.org/research/library/

2 1

Koha - Failed to set fines
by awie dicu 17 Mar '03

17 Mar '03

Hi.. I'm using koha 1.2.3 and try to set fines for overdue books. I've manually edited table categoryitem but it's not working. I've tried to setup using http://163.128.16.100:12000/cgi-bin/koha/charges.pl but failed with arrors below: [Mon Mar 17 11:53:14 2003] [error] [client 163.128.18.107] script not found or unable to stat: /usr/local/cgi-bin/charges.pl Global symbol "$query" requires explicit package name at /usr/local/koha/intranet/cgi-bin/updatecharges.pl line 22, <KC> line 11. Execution of /usr/local/koha/intranet/cgi-bin/updatecharges.pl aborted due to compilation errors. [Mon Mar 17 11:55:32 2003] [error] [client 163.128.18.107] Premature end of script headers: /usr/local/koha/intranet/cgi-bin/updatecharges.pl What did I go wrong? Can anybody guide me? thanks & regards, -Nawawi- __________________________________________________ Do you Yahoo!? Yahoo! Web Hosting - establish your business online http://webhosting.yahoo.com

1 0

Re: [Koha] anyone using rfid, robot sorter, or self checkout interfaces?
by Stephen Hedges 16 Mar '03

16 Mar '03

Christopher - I think the folks at Ann Arbor District Library have done some work with rfid and Koha. I'm not sure if they watch this list -- you might drop an e-mail to eli(a)aadl.org if you don't hear from them first. As for self-checkout, I think that will require SIP2 support, which is still on the way for Koha. Stephen Hedges Director, Nelsonville Public Library 95 W. Washington St., Nels.,OH 45764 (740) 753-2118 fax (740) 753-3543 > Pardon me if this is a FAQ. A group of us at the > University at Buffalo are > working on a proposal to test various interfaces > between radio frequency > ID self-checkout machines and library software in > our learning lab. Our > vision includes the use of hand held devices by > patrons and staff, as well > as patron self checkout systems and perhaps robot > sorters. I would like > this to be an all Linux (or some sort of *nix) > system, right down to > palmtops like the Sharp Zaurus. However, right > now, I am wondering if > anyone is using any self checkout devices or > sorters with Koha? > > cbs > -- > Christopher Brown-Syed, PhD. Editor, Library & > Archival Security. > School of Informatics, University at Buffalo. > <clb24(a)buffalo.edu> > > > _______________________________________________ > Koha mailing list > Koha(a)lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha >

2 2

Exporting MARC Records from OCLC CatME to Koha
by Larry Currie 14 Mar '03

14 Mar '03

Just about all of our cataloging is done through the OCLC CatME software program. I just now exported 15 MARC records from OCLC CatME into a file called mar142003.dat (see attached) and then ran them through a Perl script called marcmanip.pl (see attached) and MARC::Lint. The marcmanip.pl script should simply extract the control number along with data from about 6 of the MARC tags, if those tags are present. # From marcmanip.pl I got absolutely no results, and from MARC::Lint I only got a few minor warnings (see attached). I'm wondering why this was so: I believe that each record has an 001 field, and that its value in each case is the character string "ocm" followed by the OCLC record number. Since we would somehow need to get our MARC records from OCLC CatME into Koha, I'm wondering about several things: 1. Can anyone detect what is wrong with this set of 15 MARC records? The marcmanip.pl script seems to be bypassing the 001 fields for some reason. 2. Koha presently seems to require a number value for the key field biblionumber in the biblio table, and it seems like this should correspond to the 001 field of the MARC record. Has anyone devised a method of taking a single exported OCLC record or a batch of exported OCLC records, changing the OCLC record number-based 001 field to a value acceptable to Koha, and then loading these MARC records into Koha? Larry Currie -- Lawrence W. Currie User Services Librarian California Academy of Sciences Golden Gate Park San Francisco, CA 94118 lcurrie(a)calacademy.org (415) 750-7108 (415) 750-7106 fax http://www.calacademy.org/research/library/ RECORD 1 246: Indicator 2 must be 0, 1, 2, 3, 4, 5, 6, 7 or 8 but it's " " RECORD 3 022: Indicator 1 must be blank but it's "0" 260: Must have a subfield _c. RECORD 4 700: Subfield _p is not allowed. RECORD 5 246: Field is not repeatable. 246: Indicator 2 must be 0, 1, 2, 3, 4, 5, 6, 7 or 8 but it's " " RECORD 6 246: Field is not repeatable. RECORD 7 490: Subfield _x is not allowed. RECORD 8 040: Subfield _b is not allowed. 440: Subfield _x is not allowed. RECORD 9 040: Subfield _b is not allowed. RECORD 10 110: Subfield _d is not allowed. 110: Subfield _c is not allowed. 440: Subfield _x is not allowed. RECORD 11 110: Subfield _d is not allowed. 110: Subfield _c is not allowed. 246: Field is not repeatable. 440: Subfield _x is not allowed. RECORD 12 440: Subfield _x is not allowed. RECORD 14 440: Subfield _x is not allowed.

1 0

Integrating Koha with a Wiondows application
by Laurent 14 Mar '03

14 Mar '03

Hello everyone on the list. I am new to this list and new to Koha too and have a little question to ask... My client is currently developping an application for the general management of an educational organisation (EO). The application is 2-tiered: Visual Basic front end and MS-SQL back end; it is however supposed to be able to interface wih other applications. On the other hand, the EO is implementing a library under Koha, obviously running on a Linux box. In order to fully integrate both applications, what would be the best way to link them? They will currently be made available on an intranet only but the library should eventually be accessible from the Internet. Thank you all in advance for any input on how to make this possible. -- Laurent Saplairoles Here's my thought: Bagpipes (n): an octopus wearing a kilt.

1 0

Musing on a museum module
by Trevor Jenkins 13 Mar '03

13 Mar '03

A little while ago I enquired whether there was any interest amongst the Koha community in a museum module. A few people responded in the affirmative. :-) Seems to be a rather small and widely scattered group (me: UK, two: US, one?: NZ). My first thought is whether this fits into Koha! Whilst there are some proprietary library systems that have museum bolt-ons the latter modules are just that bolt-ons. The functional provision is therefore limited by the underlying library workflow assumptions. My second thought concerns the design of a museum module. Although the proprietary systems use the same or similar database this might not be the best choice. It is clearly a case of shoe-horning additional requirements. results in various comprises. There are also national standards for museum databases. For example here in the UK it is the Museum Documentation Association's SPECTRUM. Other national museum communities have similar standards. None of these are National Standards from BSI, ANSI, AFNOR, DIN, SiS or even ISO but are "de facto" standards. (I was part of the BSI/ISO cummunity responsible for SGML so am very aware of the different status "standards" have.) SPECTRUM is somewhat unwieldy and its documentaion is targeted at the museum professional not software engineers. Perhaps those interested would comment upon these thougts. First, should a museum module be added to Koha itself or is it better to use Koha as an example of open source achievements. Second, what database model should be adapted for a museum module/system? Personally, I'm not a fan of relational systems; my primarty experience is with text retrieval systems. Though my intent here is to consider the "schema" for a museum system not to make product choices. Regards, Trevor British Sign Language is not inarticulate handwaving; it's a living language. Support the campaign for formal recognition by the British government now! Details at http://www.fdp.org.uk/ -- <>< Re: deemed!

3 3

he panui Koha (Mar 11, 2003)
by Pat Eyler 12 Mar '03

12 Mar '03

he panui Koha 11 March 2003 Hello, it's time again for another of my slightly irregular newsletters. There are a couple of things I'd like to let everyone know about and this seems the best way to do it. First, we've got a couple of changes to the management group: - Ingrid Lacis has agreed to take on the role of QA/Testing for us. She'll be heading up an effort to create tests to help us develop a better, faster, more error-free Koha going forward. Please join me in wishing her welcome and lending your support to this important initiative. - With his new job, Nicholas Rososco (who wears many hats for Koha) is going to be stepping down as the Translation Manager as soon as a suitable replacement is found. Nick will continue on as our Documentation Manager. If you're interested in getting deeply involved in the translation, localization, etc. effort, please drop me an email. - With the 2.0 series just around the corner, we're starting to talk about 2.1/2.2. One of the key pieces of making this work is to have someone in the driver's seat. Steve Tonnesen has graciously accepted this position. Another important piece of the 2.1/2.2 puzzle is building a solid vision for Koha's future. One place I'd like this to happen is on the koha2010 mailing list. This list is intended to be a place where non-technical discussion about features, enhancements, and the like can occur. As ideas take shape on this list, they can be moved over to the koha-devel mailing list for technical discussion about how to implement them. More information about the mailinglist is available from http://www.kohalabs.com/projects/koha2010/mail.html (including subscription info). On a different front, work is moving along on a Win32 Koha installer. At this point you can get a working Koha system set up on a windows system if you can get perl, apache, and mysql there. A new version of the installer may take care of these for you as well. Paul is hard at work on the 2.0 series, and we hope to see a 1.9.1 release quite soon. I've recently posted a request for developers to help clean up the bug database at bugs.koha.org -- if you've noticed a problem with Koha, please submit a bug report at that web page. We'd really like to get all of the bugs squashed. (BTW, one squashed and one that seems to have been squashed already ... and in under 30 minutes) And, as one last request for this newsletter, If you're currently using, migrating to, or testing Koha please add yourself to the koha users list at http://www.saas.nsw.edu.au/wiki/index.php?page=KohaUsers (editing this page is easy to do). Getting the word out about Koha means a wider pool of users and developers ... and a better Koha. thanks, -pate Pat Eyler Kaitiaki/manager migrant Linux sys admin the Koha project ruby, shell, and perl geek http://www.koha.org http://pate.eylerfamily.org

2 1

title search.pl returns no bib number for detail.pl to use
by James Guthrie 12 Mar '03

12 Mar '03

Hi all, Our installation of Koha seems to have gone smoothly, and I've migrated our old library catalogue across, again, successfully it would seem. But... Keywords and Author searches from the opac search page result work ok, but a search by Title spits out the correct results, but omits the bib number from the details page link. I end up with a URL that looks like... detail.pl?type=opac&bib=&title=Meteorology ...so, when I click on a hit, it leads me to a blank detail page -- the problem being, I imagine, that it doesn't have a bib number to run the query off. I've looked at the code, and the title and author searches both seem to be run from this line... ($count, @results)=&CatSearch(\$blah,'loose',\%search,$num,$offset); ...so I'm not sure why the title search is failing to come up with the bib number. So, to summarise ... help! cheers, James Guthrie Information Enthusiast MetService

2 2

Re: [Koha] Musing on a museum module
by Stephen Hedges 11 Mar '03

11 Mar '03

> That's the fundamental requirement. But I > question whether a MARC oriented > schema is appropriate? A very good question. The serious catalogers I know complain that MARC is very weak when it comes to cataloging "realia." Stephen

1 0