- Koha - lists.katipo.co.nz

Re: [Koha-devel] Re: [Koha] 3rd pre 2.0 meeting (fwd)
by COURYHOUSE＠aol.com 19 Jun '03

19 Jun '03

To put things in perspective, even before Pate joined this endeavor I had mentioned both LC and MARC with the folks at Katipo Communications. As well as Steve T. When Pate came on board I discussed LC as well as MARC with him as well. I was told this evening by someone from the project I should have submitted it as a bug report. It is just a little weird I feel I am being put in a position of defending myself? The request for LC was not a new one. it may seem so to some of the folk now as many of you were not even here when it was being made! Thanks Ed Sharpe, Archivist for SMECC See the Museum's Web Site at www.smecc.org We are always looking for items to add to the museum's display and ref. library please advise if you have anything we can use. mail: Coury House / SMECC 5802 W. Palmaire Ave. Glendale Az 85301 USA 623-435-1522 > Subj:Re: [Koha-devel] Re: [Koha] 3rd pre 2.0 meeting (fwd) > Date:6/18/2003 6:04:34 PM US Mountain Standard Time > From:<A HREF="mailto:pate@eylerfamily.org">pate(a)eylerfamily.org</A> > To:<A HREF="mailto:koha@lists.katipo.co.nz">koha(a)lists.katipo.co.nz</A>, <A HREF="mailto:koha-devel@lists.sourceforge.net">koha-devel(a)lists.sourceforge.net</A> > Sent from the Internet > > > > hmm, this was really meant for the list at large, not just Ed. > > sorry, > -pate > > ---------- Forwarded message ---------- > Date: Wed, 18 Jun 2003 20:21:56 -0400 (EDT)

2 1

Re: [Koha-devel] Re: [Koha] 3rd pre 2.0 meeting (fwd)
by Pat Eyler 19 Jun '03

19 Jun '03

hmm, this was really meant for the list at large, not just Ed. sorry, -pate ---------- Forwarded message ---------- Date: Wed, 18 Jun 2003 20:21:56 -0400 (EDT) From: Pat Eyler <pate(a)eylerfamily.org> To: COURYHOUSE(a)aol.com Subject: Re: [Koha-devel] Re: [Koha] 3rd pre 2.0 meeting On Wed, 18 Jun 2003 COURYHOUSE(a)aol.com wrote: > Unfortunately my compatriots do not� invest time in futures. We need to make > sure they do not wander off to another system\ having them onboard will add > even more Fame to KOHA. I'm sorry that they're not willing to work toward the solution that they want. Making a bit of an elbow grease investment in 2.0.0 would likely pay back in terms of a better 2.0.1 (with the things they want in it) sooner rather than later. > > they are looking� for something that is complete,� in the following areas.. > > marc import > > marc export > > LC call numbers. > > I assume the other items are all done, but the third one is a necessity too. Yes, the first to are done (subject at this point only to finding and eliminating bugs). > > No one even wants to play with Dewey screens� and start loading the catalog > when what they need is LC. > > It is my belief that the LC item needs to be expedited� so those in the > university and scientific community can start to work. > Ed, we're probably less than 2 months from 2.0.0, the more people who can find and report bugs (and fix them) the faster we can get 2.0.0 out the door. Once 2.0.0 has been put to bed, we can start on 2.0.1. I'm guessing that 2.0.1 will be a much shorter cycle than 2.0.0 (on the order 3 months or less -- no promises though). If you absolutely, positively can't wait until then, you have a couple of choices. The code is freely available and the changes you're looking for aren't too big, you could write them yourself or hire someone to write them. I'm sure that Paul will be happy to accept a big block of changes for 2.0.1 once development starts. I hate to sound negative about this, but it's an important point. Koha exists because people who have wanted specific things have stepped up and done them (sometimes by hiring developers). We're working very hard to get a rock-solid 2.0.0 done in a timely fashion so that we can get back to work on new development. That's the sandbox we all want to be playing in. thanks, -pate > thanks Ed Sharpe archivist for SMECC > ed sharpe archivist for smecc > > Subj: Re: [Koha-devel] Re: [Koha] 3rd pre 2.0 meeting� > > Date: 6/18/2003 3:28:54 PM US Mountain Standard Time > > From: <A HREF="mailto:chicks@chicks.net">chicks(a)chicks.net</A> > > To: <A HREF="mailto:COURYHOUSE@aol.com">COURYHOUSE(a)aol.com</A> > > CC: <A HREF="mailto:koha@lists.katipo.co.nz">koha(a)lists.katipo.co.nz</A>, <A HREF="mailto:koha-devel@lists.sourceforge.net">koha-devel(a)lists.sourceforge.net</A> > > Sent from the Internet > > > > > > > > On Wed, 18 Jun 2003 COURYHOUSE(a)aol.com wrote: > > >OK so it is still not going to be useable� by our community for a while > > then. > > >Ultra bummer. now I have 30 sad news emails to send out. > > > > It doesn't have to be sad news emails!� It's just a matter of timing.� > > You can play with 2.0 koha while waiting for 2.0.1 to get familiar with > > Koha and discover any other issues you may need fixed.� By the time 2.0.1 > > comes out you'll be ready to consider a beta schedule and projected > > production date.� Plus actively testing 2.0 until the next minor release > > comes will almost certainly help 2.0.1 arrive sooner.� What sadness? > > >

1 0

Re: [Koha-devel] Re: [Koha] Re: DDC and LC classification - 2 cents more
by COURYHOUSE＠aol.com 19 Jun '03

19 Jun '03

that is a BIG problem! > > No, that's not correct. The problem isn't putting in the LC number, it's > getting Koha to accept it and display it in the catalogue record!! > > ___________________________________________ > Bernadette Cassidy > Library &Learning Coordinator > Allan Bean Centre > Burwood Hospital > Christchurch

1 0

Re: [Koha] 3rd pre 2.0 meeting
by COURYHOUSE＠aol.com 19 Jun '03

19 Jun '03

any news on the lc vrs dewey?

2 1

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