- Koha - lists.katipo.co.nz

(no subject)
by Nicholas Stephen Rosasco 26 Jun '01

26 Jun '01

http://freshmeat.net/projects/pybliographer/ Is this of use to anyone? Randomly, Nick ...available for odd Koha research questions.

1 0

Re: [Koha] MARC TODO list
by Tonnesen Steve 25 Jun '01

25 Jun '01

On Mon, 25 Jun 2001 COURYHOUSE(a)aol.com wrote: > Remember some of us will use LC rather than Dewey, especially those in the > scientific library field..... The MARC tables that I'm working on can obviously store the 050 field, and it will be trivial to index on that field. This is the kind of thing that needs to be settable as a system preference ("Primary Call Number Search: Dewey or LC"). This is another issue which I'd like to see addressed, but isn't my current focus. Steve.

1 0

Re: [Koha] MARC TODO list
by COURYHOUSE＠aol.com 25 Jun '01

25 Jun '01

keep up the great work! Will this run OK on the redhat distro? ended up with the server package... love the 90 day phone support aspect. Ed Sharpe archivist for SMECC > Subj: [Koha] MARC TODO list > Date: 6/25/01 1:18:42 PM US Mountain Standard Time > From: tonnesen(a)cmsd.bc.ca (Tonnesen Steve) > Sender: koha-admin(a)lists.katipo.co.nz > To: koha(a)lists.katipo.co.nz (Koha Open Source Library System) > > > > > > I've generated a short TODO list for adding MARC support to Koha below. > I've also checked most of my files into CVS now. I've placed most of them > in the koha/marc/ subdirectory, but the koha/C4/Catalogue.pm file is also > required to convert existing koha records to marc format. > > Please do not use any of this on production systems yet! > > > > TODO list > > 1. Finish cataloguing api (Catalogue.pm) > > 2. Modify existing code to use the new cataloguing api > a. start with all write routines > b. then all read routines > > 3. Polish up MARC editor. Must include some sanity checks to prevent > modifications with the MARC editor rendering the data unusable by > Koha. > a. don't delete the barcode, warning before modifying barcode > b. don't mess up linkages between 852 and 876 tags > c. Home branch and holding branch info should require warnings before > updating. > d. others? > > 4. Need to create some indexes of the MARC data to aid in searches. > Soundex searches would be nice. > a. subject index > b. title index > c. author index > d. dewey index > e. itemtype index > f. soundex indexes would require an index with 1 word in each record. > For example, a book with the title "The Habitat and Lifestyle of the > Elephant" would have entries for "Habitat", "Lifestyle" and > "Elephant" all pointing to the book's record. An sql query like > "select Record_ID from soundex_index where soundex(word) like > soundex('elefant')" would return a point to "The Habitat and > Lifestyle of the Elephant". (Personally, I think this is pretty > silly, but I had some librarians ask for it, and it isn't overly > difficult to implement). Soundex searches should be configurable as > an option somewhere. For example, have a special interface for young > children where they just type in a word and hit enter and soundex > searches are used, but normal searches do not use soundex. It would > be annoying for titles with the words 'Rode' and 'Road' to show up > when you search for 'Rhode', for example. > > 5. A million other things, probably... > > > _______________________________________________ > Koha mailing list > Koha(a)lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha > > >

1 0

Re: [Koha] MARC TODO list
by Tonnesen Steve 25 Jun '01

25 Jun '01

On Mon, 25 Jun 2001 COURYHOUSE(a)aol.com wrote: > Will this run OK on the redhat distro? > ended up with the server package... love the 90 day phone support aspect. I'm a debian user myself, but I don't see why any of this wouldn't work under RedHat. None of my changes are in any way distribution specific, so if you have Koha working, my changes should work just fine. Steve.

1 0

Re: [Koha] MARC TODO list
by COURYHOUSE＠aol.com 25 Jun '01

25 Jun '01

Remember some of us will use LC rather than Dewey, especially those in the scientific library field..... Ed > Subj: [Koha] MARC TODO list > Date: 6/25/01 1:18:42 PM US Mountain Standard Time > From: tonnesen(a)cmsd.bc.ca (Tonnesen Steve) > Sender: koha-admin(a)lists.katipo.co.nz > To: koha(a)lists.katipo.co.nz (Koha Open Source Library System) > > > > > > I've generated a short TODO list for adding MARC support to Koha below. > I've also checked most of my files into CVS now. I've placed most of them > in the koha/marc/ subdirectory, but the koha/C4/Catalogue.pm file is also > required to convert existing koha records to marc format. > > Please do not use any of this on production systems yet! > > > > TODO list > > 1. Finish cataloguing api (Catalogue.pm) > > 2. Modify existing code to use the new cataloguing api > a. start with all write routines > b. then all read routines > > 3. Polish up MARC editor. Must include some sanity checks to prevent > modifications with the MARC editor rendering the data unusable by > Koha. > a. don't delete the barcode, warning before modifying barcode > b. don't mess up linkages between 852 and 876 tags > c. Home branch and holding branch info should require warnings before > updating. > d. others? > > 4. Need to create some indexes of the MARC data to aid in searches. > Soundex searches would be nice. > a. subject index > b. title index > c. author index > d. dewey index > e. itemtype index > f. soundex indexes would require an index with 1 word in each record. > For example, a book with the title "The Habitat and Lifestyle of the > Elephant" would have entries for "Habitat", "Lifestyle" and > "Elephant" all pointing to the book's record. An sql query like > "select Record_ID from soundex_index where soundex(word) like > soundex('elefant')" would return a point to "The Habitat and > Lifestyle of the Elephant". (Personally, I think this is pretty > silly, but I had some librarians ask for it, and it isn't overly > difficult to implement). Soundex searches should be configurable as > an option somewhere. For example, have a special interface for young > children where they just type in a word and hit enter and soundex > searches are used, but normal searches do not use soundex. It would > be annoying for titles with the words 'Rode' and 'Road' to show up > when you search for 'Rhode', for example. > > 5. A million other things, probably... > > > _______________________________________________ > Koha mailing list > Koha(a)lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha >

1 0

MARC TODO list
by Tonnesen Steve 25 Jun '01

25 Jun '01

I've generated a short TODO list for adding MARC support to Koha below. I've also checked most of my files into CVS now. I've placed most of them in the koha/marc/ subdirectory, but the koha/C4/Catalogue.pm file is also required to convert existing koha records to marc format. Please do not use any of this on production systems yet! TODO list 1. Finish cataloguing api (Catalogue.pm) 2. Modify existing code to use the new cataloguing api a. start with all write routines b. then all read routines 3. Polish up MARC editor. Must include some sanity checks to prevent modifications with the MARC editor rendering the data unusable by Koha. a. don't delete the barcode, warning before modifying barcode b. don't mess up linkages between 852 and 876 tags c. Home branch and holding branch info should require warnings before updating. d. others? 4. Need to create some indexes of the MARC data to aid in searches. Soundex searches would be nice. a. subject index b. title index c. author index d. dewey index e. itemtype index f. soundex indexes would require an index with 1 word in each record. For example, a book with the title "The Habitat and Lifestyle of the Elephant" would have entries for "Habitat", "Lifestyle" and "Elephant" all pointing to the book's record. An sql query like "select Record_ID from soundex_index where soundex(word) like soundex('elefant')" would return a point to "The Habitat and Lifestyle of the Elephant". (Personally, I think this is pretty silly, but I had some librarians ask for it, and it isn't overly difficult to implement). Soundex searches should be configurable as an option somewhere. For example, have a special interface for young children where they just type in a word and hit enter and soundex searches are used, but normal searches do not use soundex. It would be annoying for titles with the words 'Rode' and 'Road' to show up when you search for 'Rhode', for example. 5. A million other things, probably...

1 0

MARC
by Tonnesen Steve 25 Jun '01

25 Jun '01

I've now got a pretty basic MARC converter built that will take all existing records in the biblio, biblioitems, items tables and convert them to MARC records. I stuck pretty much with the mapping I sent in my previous post, since nobody pointed out any glaring errors. Item holdings information is stored in tags 852 and 876 with a linkage number in subfield 8 to tie the two tags together. http://142.28.224.11/cgi-bin/koha/acqui.simple/viewmarc.pl will now point you to record 221 by default which has 6 items. This converter uses the beginnings of a Catalogue.pm module that I'm working on. The newBiblioItem() and newItem() subroutines are fairly complete for the MARC side. The Koha side should be much easier to write. Steve.

3 5

i18n of koha - progress report
by Benedykt P. Barszcz 23 Jun '01

23 Jun '01

Hi, Actually I should not be writing this. I have convinced a friend of mine to look at koha project and try to internationalize it. What he did was he wrote a simple perl script that makes it possible to switch between languages in koha by simply setting the language preference in your browser. For that to work an "Action" directive is to be set in Apache, like so: Action text/html /cgi-bin/koha/trans.pl Action text/plain /cgi-bin/trans.pl The "trans.pl" script does the whole magic to present the language of your preference of your browser. Requirements: gettext.pm, translated koha.pot file, and compiled with msgfmt. Now I need to convince him to subscribe to this mailing list to contribute:-) It may take some time. But the thing works and I am amazed.... Benedykt PS. Aha, he also did something to the koha perl scripts so perl variables can be correctly interpreted by HTML. -- Chcialbys zarobic lub "dorobic" naprawde dobre pieniadze? Otrzymasz do 300zl za kazda firme ktora wprowadzisz do Centrum e-biznesu Poszukaj wsrod znajomych, znajdz firme i wypelnij z nia prosty formularz Aby rozpoczac wejdz do http://praca.getin.pl i zostan Partnerem Getin

2 1

miniBib
by Benedykt P. Barszcz 23 Jun '01

23 Jun '01

http://minibib.sourceforge.net/ I wonder what they are up to? They say that tomorrow a first stable version might be released.... Here is what the sourceforge description says: miniBib is a graduate project written in Java and object oriented. miniBib aim to help the management of a library Benedict -- Chcialbys zarobic lub "dorobic" naprawde dobre pieniadze? Otrzymasz do 300zl za kazda firme ktora wprowadzisz do Centrum e-biznesu Poszukaj wsrod znajomych, znajdz firme i wypelnij z nia prosty formularz Aby rozpoczac wejdz do http://praca.getin.pl i zostan Partnerem Getin

1 0

MARC info request from librarians
by Tonnesen Steve 21 Jun '01

21 Jun '01

Here's a question for the librarians in the crowd. I'm trying to match up the data in Koha's biblio, biblioitems, and items tables to MARC tags and subfields. Can you go over the list below and comment on my mapping, both things you think I've done wrong, or things that I'm missing entirely? Thanks for the help, Steve. ========================================================================= Koha to MARC field mapping ========================================================================= # From biblio table: title 245 a subtitle 245 b unititle 246 a ??? serial seriestitle 440 a copyrightdate 245 f (or g?) and what is the format? notes 500 a (maybe set $3 to 'biblio'?) author 100 a,b,c,d additional author 700 a,b,c,d (set $e to 'author') subject 650 a # From biblioitems table: volume 440 v number 440 n classification (I'm not sure this is used in Koha anymore?) itemtype 852 k (call number prefix) isbn 020 a issn 022 a dewey 082 a subclass 852 m (call number suffix) place 260 a (Place of publication) publishercode 260 b (Name of publisher, distributor) publicationyear 260 c (Date of Publication) volumedata volumeddesc illus 700 a,b,c,d (set $e to 'illustrator') pages 300 a size 300 c notes 500 a (maybe set $3 to 'biblioitems'?) lccn 010 a # From items table: barcode 852 p dateaccessioned 876 d (date acquired) booksellerid 876 e homebranch 852 holdingbranch 876 l (temporary location) price 876 c (cost) replacementprice 876 c? (cost) replacementpricedate 876 d? (date acquired) datelastborrowed datelastseen multivolume stack notforloan 506 or 876 h itemlost 876 j (item status) wthdrawn 876 j (item status) bulk issues renewals reserves restricted 506 a restrictions on access for all items, or 876 h for item specific restrictions? binding itemnotes 876 z (public note) 876 x (nonpublic note) interim =========================================================================

2 2