- Koha - lists.katipo.co.nz

3rd pre 2.0 meeting
by Pat Eyler 18 Jun '03

18 Jun '03

Well, we had another pre 2.0 bug meeting. Many people showed up and most lurked, but several participated. Some interesting threads came up: NPL is closing in on their migration from Spydus to Koha. Concurrently, there seems to be some interest in Koha building in Australia (currently about 80% of Spydus new business is in Australia). It looks as though interesting things may start happening there once 2.0.0 comes out. Interest in a Z39.50 server cropped up again. It won't happen in 2.0.0, but 2.0.1 is a very real possibility. I (Pat Eyler) will be talking to the developers of Zebra (a free z39.50 server engine) to see about integrating their work into Koha. NPL talked a bit about their work with the bulkimporter. Paul agreed to take on a bug that NPL found. The Spanish language translators from Argentina asked about how to work on translations for 2.0.0. You can look at www.koha.org/irc/ for a full log. If you are interested in getting involved, please feel free to get involved in the next irc meeting -- next Wednesday, same time, same place. -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

1 0

excusme i need you help
by enrique cristian montiel montiel 18 Jun '03

18 Jun '03

hello that so excuses as I can restrict the number of books borrowed at the different existing users, it wanted to establish limits to indicate whatever books as maximo can borrow the users _________________________________________________________________ MSN Fotos: la forma más fácil de compartir e imprimir fotos. http://photos.msn.es/support/worldwide.aspx

1 0

Re: [Koha-devel] 2.0 release meeting
by COURYHOUSE＠aol.com 18 Jun '03

18 Jun '03

JUST BE SURE THE lc CALL NUMBER WITH LINES FOR IT IS DISCUSSED AND IMPLEMENTED PLEASEEEEEEEEEEEEEEE! ED SHARPE > Subj: [Koha-devel] 2.0 release meeting > Date: 6/17/2003 3:44:48 PM US Mountain Standard Time > From: <A HREF="mailto:pate@eylerfamily.org">pate(a)eylerfamily.org</A> > To: <A HREF="mailto:koha-devel@lists.sourceforge.net">koha-devel(a)lists.sourceforge.net</A>, <A HREF="mailto:koha@lists.katipo.co.nz">koha(a)lists.katipo.co.nz</A> > Sent from the Internet > > > > Hello everyone, > With a 2.0.0 release rapidly approaching, and a bunch of bugs needing to > be found, reported, prioritized, and fixed, we're going to institute a > weekly irc meeting to help handle the load. > > We'll meet every Wednesday at 1900 UTC in the #koha channel at > irc.katipo.co.nz -- Anyone is welcome to attend, please bring your bug > reports. If you can't make it this week (short notice, I know), please > drop in to any of the meetings you can make. > > (Here are a couple of conversions follow) > UTC France Seattle New Zealand > Wed 19:00 Wed 21:00 Wed 12:00 Thu 07:00 > > > (Please feel free to translate and/or forward this message to > other mailing lists as appropriate.) > > -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 > >

3 2

remove me from your list
by Daniel Dickinson 18 Jun '03

18 Jun '03

Please remove me from your list. I have been spamming your people for 3 months now and I have had little success getting rid of your group's messages. Thanks --------------------------------- Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month!

1 0

2.0 release meeting
by Pat Eyler 18 Jun '03

18 Jun '03

Hello everyone, With a 2.0.0 release rapidly approaching, and a bunch of bugs needing to be found, reported, prioritized, and fixed, we're going to institute a weekly irc meeting to help handle the load. We'll meet every Wednesday at 1900 UTC in the #koha channel at irc.katipo.co.nz -- Anyone is welcome to attend, please bring your bug reports. If you can't make it this week (short notice, I know), please drop in to any of the meetings you can make. (Here are a couple of conversions follow) UTC France Seattle New Zealand Wed 19:00 Wed 21:00 Wed 12:00 Thu 07:00 (Please feel free to translate and/or forward this message to other mailing lists as appropriate.) -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

Re: DDC and LC classification
by Stephen Hedges 18 Jun '03

18 Jun '03

For starters, here's a good place to learn how Dewey Decimal Classification (DDC) works: http://www.oclc.org/oclc/fp/about/about_the_ddc.htm If you look at this URL and the ones Rob sent, it looks like DDC always fits on one line, while LC can run to as many as five lines. That's true in a theoretical world. In the real world, libraries muck around and add other stuff, to help the people who have to stick the books back on the shelves. Here's an example. The copy of The Chicago Manual of Style I have beside me has the Library of Congress Cataloguing-in-Publication (CIP) data printed inside the fly leaf. It says that the "official" classifications are as follows: LC would be - Z253 U69 1993 DDC would be - 808 or 808.027 or 808.0270973 if I'm really picky. Looks like 3 lines for LC and 1 line for DDC. But in practice, it's hard for humans to keep a long string of numbers straight and in order when re-shelving books, so most libraries that use DDC do what my library does -- add an extra line with the first two letters of the title or the author's name under a _short_ Dewey number. So the spine label on this particular book reads: 808 Ch instead of 808.0270973 Now it gets really fun! Many libraries also add stuff _before_ the Dewey number, like AB for audiobooks or YA for young adult or J for juvenile or junior. (LC libraries sometimes do this, too.) Yeah, they're really categories and shouldn't be part of the call number. But again, they help humans find, retrieve, and replace stuff on library shelves. Practice supercedes theory once again! But to get to the point, five lines should be quite enough for most purposes, for either LC or DDC. I'm sure someone will disagree, but any library that thinks it has to have six lines probably needs some discipline! Stephen Hedges (Nelsonville Public Library) > I've been working on SQL phrasebooks to enable > multiple backend DB support. I would be happy to > help with changing these fields around. > > Since my knowledge of library science is pretty > much limited to what I've learned off of this > list, could someone step up to the plate to do > some research on the type and number of fields > needed? > > ----- Original Message ----- > From: Chris Cormack <chris(a)katipo.co.nz> > Date: Tuesday, June 17, 2003 1:29 pm > Subject: Re: [Koha] More questions - another 2 > cents worth > > > I think there may be some confusion between a > lccn number (library of > > congress control number) and library of > congress call numbers. If I > > understand correctly, a lccn number is single > unique number used > > to identify > > a specific title, kind of like a serial number. > However, > > (librarians, please > > correct me if I'm wrong) lccn numbers are not > used for cataloging and > > shelving books in a library that used the LC > system. Instead there > > are a > > series of four or five lines of call numbers > that are used instead. > > > > Rather than try to explain it, let me refer you > to > > > http://www.lib.ksu.edu/instructional/understanding > lccn/webcall2.html or > > > http://www.hcc.hawaii.edu/education/hcc/library/ca > llno.html for some > > explanation and samples of LC call numbers. > > > > The problem is that koha doesn't currently have > adequate fields of the > > proper type for storing these four or five > lines of information in the > > database (I think there are such fields in the > MARC tables, but > > not in the > > basic koha tables). I agree that accommodating > the different > > catalogingsystems is a template issue, but feel > that the necessary > > fields need to be > > in place in the database tables first. I had > actually emailed the > > development list on this same issue a couple > weeks ago (subject: > > inflexiblefield types for call numbers). > > > > My recommendation would be that we survey as > many knowledgeable > > librariansas possible to find out how many > fields are necessary > > for storing call > > numbers under the various systems, what the > maximum length of each > > needs to > > be, and then add those fields to the database > tables (unless the > > programmerscould suggest existing fields that > can be used). I > > think if there were four > > or five flexible fields for storing call number > information, then > > indeedkoha could be adapted to almost any > cataloging system by > > reworking the > > templates. > > > > Rob > > > > ----- Original Message ----- > > From: "Chris Cormack" <chris(a)katipo.co.nz> > > Sent: Tuesday, June 17, 2003 1:20 AM > > Subject: Re: [Koha] More questions - another 2 > cents worth > > > > > > > We do have an lccn field in the koha > database. And you can load > > data into > > > it, its currently not displaying or > searchable yet though. This > > is a > > > templating issue, im sure we could change it > quite fast. > > > > > _______________________________________________ > > Koha mailing list > > Koha(a)lists.katipo.co.nz > > > http://lists.katipo.co.nz/mailman/listinfo/koha > > > > _______________________________________________ > Koha mailing list > Koha(a)lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha >

3 2

RE: [Koha] RE: perl modules
by Jones, Steven 18 Jun '03

18 Jun '03

nope not really.... I cant run automatically through our proxy server, and tracing modules is proving impossible. The automated script in 1.2.3 is failing on Database.PL, Im beginning to assume koha wont install on rh9 regards Steven -----Original Message----- From: Jerome Vizcaino [mailto:vizcainj@esiee.fr] Sent: Wednesday, 18 June 2003 8:41 PM To: Jones, Steven Cc: koha(a)lists.katipo.co.nz Subject: Re: [Koha] RE: perl modules Hi Mostly all the modules available for Perl are located at http://www.cpan.org Once you get the CPAN module, you can install modules automatically (almost) using the following command (which is printed at the end of the Koha installation if you are missing some modules) perl -MCPAN -e 'install MODULE::EXAMPLE' Hope this helps. Jerome On Wed, 2003-06-18 at 03:58, Jones, Steven wrote: > I seem to be unable to get koha installed due to numerous missing perl > modules, > > Where can I find > > Database.pm and PAN.pm? > > How come when I run the 1.2.3 install script and it says all esential > modules installed, i get a failed install? > > regards > > Steven > _______________________________________________ > Koha mailing list > Koha(a)lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha > >

2 1

koha and annual stocktaking
by Kerstin Henschke 18 Jun '03

18 Jun '03

Hi! The company I am working for would like to use koha but only if it is easily possible to make annual stocktaking. Therefore I would like to know whether it is and how. Unfortunaltely, the test version did not help me with that. Do you provide e.g. scanners for stocktaking? Sincerely, K. Henschke Kerstin Henschke Bibliothek im C-Lab Tel: +49- 52 51- 606070 Fax: +49- 52 51- 606065 Fuerstenallee 11 33102 Paderborn Germany

2 1

1.9.3 bug & question
by Shane Williams 18 Jun '03

18 Jun '03

First off is a minor bug. During the installation process it says to make sure $etcdir/koha-httpd.conf gets included in the standard httpd.conf file. During my installation, the file that actually got created was not $etcdir/koha-httpd.conf, but rather just $etcdir/httpd.conf. Line 1134 of Install.pm confirms this to be the case. Second is more of a question. When I go to koha/acqui.simple/addbooks.pl next to the link that reads "z39.50 Search Tool" is the text "does not work." I've adjusted and run the z3950 proccessing scripts and confirmed that they are actually running. In an email about two weeks ago someone was asking about z3950 searching not working as in 1.2.3, and Paul's response indicates that it ought to be working. Am I missing something? -- Public key #7BBC68D9 at | Shane Williams http://pgp.mit.edu/ | System Admin - UT iSchool =----------------------------------+------------------------------- All syllogisms contain three lines | broot(a)ischool.utexas.edu Therefore this is not a syllogism | www.ischool.utexas.edu/~shanew

2 1

Re: [Koha] More questions - another 2 cents worth
by baljkas＠mb.sympatico.ca 18 Jun '03

18 Jun '03

Monday, June 16, 2003 12:40 CDT Greetings, all! I don't know if it's possible, but perhaps until the developers can create a classification field that uses ANY system/s the users need, it might be useful to have stop-gap 'DDC' and 'LC' versions of Koha. Ed is dead-on in noting that LC is really the standard for scientific libraries. I interviewed on one that insisted in using Dewey a few years ago: most of the call numbers were 20 digits. Not fun to try to use or communicate to users. Anyway, that's just my 2 cents worth, Cheers, Steven F. Baljkas Koha neophyte, Winnipeg MB CANADA P.S. To be honest, I've also thought that it would be good to have MARC21 and UNIMARC versions as well; might simplify some mapping problems interim.

5 6