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

barcode NOT mandatory [done]
by paul POULAIN 30 Sep '03

30 Sep '03

I've created the patch that makes barcode NOT mandatory in Koha. It's in CVS, and will be in next public release. PS : for those intereseted : download CVS version somewhere. run updatedatabase script (don't forget to export PERL5LIB=/your/path/to/koha) That's all. No code involved in Koha. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

Re: [Koha] 090 Fields [good news :-)]
by MJ Ray 30 Sep '03

30 Sep '03

These are dev questions, so moved to koha-devel. On 2003-09-19 08:34:10 +0100 paul POULAIN <paul.poulain(a)free.fr> wrote: > To support any MARC flavour, NO MARC TAG/SUBFIELDS ARE HARDCODED into > Koha. The MARC export appears to call as_usmarc(), which needs MARC21 to be used to get valid results, doesn't it? I spoke on Wednesday's IRC with jferraro (excuse misspelling) who was having some trouble with MARC export. Any progress? -- MJR/slef My Opinion Only and possibly not of any group I know. http://mjr.towers.org.uk/ gopher://g.towers.org.uk/ slef(a)jabber.at Creative copyleft computing services via http://www.ttllp.co.uk/

2 6

z3950 queue problems
by Chris Hobbs 29 Sep '03

29 Sep '03

Please disregard my prior note about BUG 622 - I found and posted on bugzilla a workaround that should allow the coders to find and fix the issue, and it now seems to allow me to attempt to query the LOC database. However, the logs now show this type of message when I get a hit: Library_of_Congress ==> at /usr/local/koha/z3950daemon/processz3950queue line 156. Library_of_Congress ==> answered : 3 found at /usr/local/koha/z3950daemon/processz3950queue line 170. Processing title="Count Zero" at Library_of_Congress z3950.loc.gov:7090 Voyager (2 forks) Library_of_Congress SPEED: 3 z3950.loc.gov:7090 done 3 z3950.loc.gov:7090 done. A network dump of what transpires over the wire is at the bottom of this e-mail. The last few packets are probably the most interesting - z3950.loc.gov (140.147.249.38) tells the koha server that it was unable to retrieve record #x. I guess this means either it had some internal problem that there's nothing koha can do to solve, or processz3950queue is sending a request that the loc server can't handle. The record created in the z3950results table claims to have found 3 records, but the results blob field is 0 bytes. While the above example was based on a title search, ISBN searches produce similar results. Any help would be appreciated! 09/29-13:57:34.525163 0:E0:81:23:75:F0 -> 0:A0:CC:39:BA:F type:0x800 len:0x4A 10.168.12.235:40985 -> 140.147.249.38:7090 TCP TTL:64 TOS:0x0 ID:37437 IpLen:20 DgmLen:60 DF ******S* Seq: 0xA747119D Ack: 0x0 Win: 0x16D0 TcpLen: 40 TCP Options (5) => MSS: 1460 SackOK TS: 2041086880 0 NOP WS: 0 =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 09/29-13:57:34.683752 0:A0:CC:39:BA:F -> 0:E0:81:23:75:F0 type:0x800 len:0x4A 140.147.249.38:7090 -> 10.168.12.235:40985 TCP TTL:43 TOS:0x0 ID:1097 IpLen:20 DgmLen:60 ***A**S* Seq: 0xAFE5527C Ack: 0xA747119E Win: 0xFB28 TcpLen: 40 TCP Options (7) => NOP NOP TS: 88217525 2041086880 NOP NOP SackOK MSS: 1380 =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 09/29-13:57:34.683913 0:E0:81:23:75:F0 -> 0:A0:CC:39:BA:F type:0x800 len:0x42 10.168.12.235:40985 -> 140.147.249.38:7090 TCP TTL:64 TOS:0x0 ID:37438 IpLen:20 DgmLen:52 DF ***A**** Seq: 0xA747119E Ack: 0xAFE5527D Win: 0x16D0 TcpLen: 32 TCP Options (3) => NOP NOP TS: 2041086962 88217525 =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 09/29-13:57:34.684223 0:E0:81:23:75:F0 -> 0:A0:CC:39:BA:F type:0x800 len:0x92 10.168.12.235:40985 -> 140.147.249.38:7090 TCP TTL:64 TOS:0x0 ID:37439 IpLen:20 DgmLen:132 DF ***AP*** Seq: 0xA747119E Ack: 0xAFE5527D Win: 0x16D0 TcpLen: 32 TCP Options (3) => NOP NOP TS: 2041086962 88217525 B4 4E 82 04 69 6E 69 74 83 02 00 E0 84 03 00 E9 .N..init........ A2 85 03 10 00 00 86 03 10 00 00 9F 6E 14 4D 69 ............n.Mi 6B 65 20 54 61 79 6C 6F 72 20 28 69 64 3D 31 36 ke Taylor (id=16 39 29 9F 6F 14 4E 65 74 3A 3A 5A 33 39 35 30 2E 9).o.Net::Z3950. 70 6D 20 28 50 65 72 6C 29 9F 70 04 30 2E 33 35 pm (Perl).p.0.35 =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 09/29-13:57:34.784590 0:A0:CC:39:BA:F -> 0:E0:81:23:75:F0 type:0x800 len:0x42 140.147.249.38:7090 -> 10.168.12.235:40985 TCP TTL:43 TOS:0x0 ID:1098 IpLen:20 DgmLen:52 ***A**** Seq: 0xAFE5527D Ack: 0xA74711EE Win: 0xFB28 TcpLen: 32 TCP Options (3) => NOP NOP TS: 88217541 2041086962 =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 09/29-13:57:40.089901 0:A0:CC:39:BA:F -> 0:E0:81:23:75:F0 type:0x800 len:0x8A 140.147.249.38:7090 -> 10.168.12.235:40985 TCP TTL:43 TOS:0x0 ID:1099 IpLen:20 DgmLen:124 ***AP*** Seq: 0xAFE5527D Ack: 0xA74711EE Win: 0xFB28 TcpLen: 32 TCP Options (3) => NOP NOP TS: 88218070 2041086962 B5 46 82 04 69 6E 69 74 83 02 05 E0 84 03 01 C0 .F..init........ 00 85 03 00 80 00 86 03 10 00 00 8C 01 01 9F 6E ...............n 02 33 34 9F 6F 1B 56 6F 79 61 67 65 72 20 4C 4D .34.o.Voyager LM 53 20 2D 20 5A 33 39 2E 35 30 20 53 65 72 76 65 S - Z39.50 Serve 72 9F 70 04 31 2E 31 33 r.p.1.13 =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 09/29-13:57:40.090097 0:E0:81:23:75:F0 -> 0:A0:CC:39:BA:F type:0x800 len:0x42 10.168.12.235:40985 -> 140.147.249.38:7090 TCP TTL:64 TOS:0x0 ID:37440 IpLen:20 DgmLen:52 DF ***A**** Seq: 0xA74711EE Ack: 0xAFE552C5 Win: 0x16D0 TcpLen: 32 TCP Options (3) => NOP NOP TS: 2041089729 88218070 =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 09/29-13:57:40.093504 0:E0:81:23:75:F0 -> 0:A0:CC:39:BA:F type:0x800 len:0xAA 10.168.12.235:40985 -> 140.147.249.38:7090 TCP TTL:64 TOS:0x0 ID:37441 IpLen:20 DgmLen:156 DF ***AP*** Seq: 0xA74711EE Ack: 0xAFE552C5 Win: 0x16D0 TcpLen: 32 TCP Options (3) => NOP NOP TS: 2041089731 88218070 B6 66 82 01 30 8D 01 00 8E 01 01 8F 01 00 90 01 .f..0........... 01 91 07 64 65 66 61 75 6C 74 B2 0A 9F 69 07 56 ...default...i.V 6F 79 61 67 65 72 BF 64 03 80 01 46 BF 65 03 80 oyager.d...F.e.. 01 42 9F 68 07 2A 86 48 CE 13 05 69 B5 2A A1 28 .B.h.*.H...i.*.( 06 07 2A 86 48 CE 13 03 01 A0 1D BF 66 1A BF 2C ..*.H.......f.., 0A 30 08 9F 78 01 01 9F 79 01 04 9F 2D 0A 43 6F .0..x...y...-.Co 75 6E 74 20 5A 65 72 6F unt Zero =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 09/29-13:57:40.303985 0:A0:CC:39:BA:F -> 0:E0:81:23:75:F0 type:0x800 len:0x42 140.147.249.38:7090 -> 10.168.12.235:40985 TCP TTL:43 TOS:0x0 ID:1100 IpLen:20 DgmLen:52 ***A**** Seq: 0xAFE552C5 Ack: 0xA7471256 Win: 0xFB28 TcpLen: 32 TCP Options (3) => NOP NOP TS: 88218092 2041089731 =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 09/29-13:57:41.074545 0:A0:CC:39:BA:F -> 0:E0:81:23:75:F0 type:0x800 len:0x56 140.147.249.38:7090 -> 10.168.12.235:40985 TCP TTL:43 TOS:0x0 ID:1101 IpLen:20 DgmLen:72 ***AP*** Seq: 0xAFE552C5 Ack: 0xA7471256 Win: 0xFB28 TcpLen: 32 TCP Options (3) => NOP NOP TS: 88218153 2041089731 B7 12 82 01 30 97 01 03 98 01 00 99 01 01 96 01 ....0........... 01 9B 01 00 .... =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 09/29-13:57:41.087121 0:E0:81:23:75:F0 -> 0:A0:CC:39:BA:F type:0x800 len:0x6A 10.168.12.235:40985 -> 140.147.249.38:7090 TCP TTL:64 TOS:0x0 ID:37442 IpLen:20 DgmLen:92 DF ***AP*** Seq: 0xA7471256 Ack: 0xAFE552D9 Win: 0x16D0 TcpLen: 32 TCP Options (3) => NOP NOP TS: 2041090240 88218153 B8 26 82 05 30 2D 31 2D 31 9F 1F 07 64 65 66 61 .&..0-1-1...defa 75 6C 74 9E 01 01 9D 01 01 B3 03 80 01 46 9F 68 ult..........F.h 07 2A 86 48 CE 13 05 69 .*.H...i =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 09/29-13:57:41.305411 0:A0:CC:39:BA:F -> 0:E0:81:23:75:F0 type:0x800 len:0x90 140.147.249.38:7090 -> 10.168.12.235:40985 TCP TTL:43 TOS:0x0 ID:1102 IpLen:20 DgmLen:130 ***AP*** Seq: 0xAFE552D9 Ack: 0xA747127E Win: 0xFB28 TcpLen: 32 TCP Options (3) => NOP NOP TS: 88218181 2041090240 B9 4C 82 05 30 2D 31 2D 31 98 01 01 99 01 02 9B .L..0-1-1....... 01 00 BC 3A 30 38 80 07 56 6F 79 61 67 65 72 A1 ...:08..Voyager. 2D A1 2B 28 29 06 07 2A 86 48 CE 13 05 65 A0 1E -.+()..*.H...e.. 1B 1C 46 61 69 6C 65 64 20 74 6F 20 72 65 74 72 ..Failed to retr 69 65 76 65 20 72 65 63 6F 72 64 20 23 31 ieve record #1 =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 09/29-13:57:41.319260 0:E0:81:23:75:F0 -> 0:A0:CC:39:BA:F type:0x800 len:0x6A 10.168.12.235:40985 -> 140.147.249.38:7090 TCP TTL:64 TOS:0x0 ID:37443 IpLen:20 DgmLen:92 DF ***AP*** Seq: 0xA747127E Ack: 0xAFE55327 Win: 0x16D0 TcpLen: 32 TCP Options (3) => NOP NOP TS: 2041090359 88218181 B8 26 82 05 30 2D 32 2D 31 9F 1F 07 64 65 66 61 .&..0-2-1...defa 75 6C 74 9E 01 02 9D 01 01 B3 03 80 01 46 9F 68 ult..........F.h 07 2A 86 48 CE 13 05 69 .*.H...i =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 09/29-13:57:41.428654 0:A0:CC:39:BA:F -> 0:E0:81:23:75:F0 type:0x800 len:0x90 140.147.249.38:7090 -> 10.168.12.235:40985 TCP TTL:43 TOS:0x0 ID:1103 IpLen:20 DgmLen:130 ***AP*** Seq: 0xAFE55327 Ack: 0xA74712A6 Win: 0xFB28 TcpLen: 32 TCP Options (3) => NOP NOP TS: 88218204 2041090359 B9 4C 82 05 30 2D 32 2D 31 98 01 01 99 01 03 9B .L..0-2-1....... 01 00 BC 3A 30 38 80 07 56 6F 79 61 67 65 72 A1 ...:08..Voyager. 2D A1 2B 28 29 06 07 2A 86 48 CE 13 05 65 A0 1E -.+()..*.H...e.. 1B 1C 46 61 69 6C 65 64 20 74 6F 20 72 65 74 72 ..Failed to retr 69 65 76 65 20 72 65 63 6F 72 64 20 23 32 ieve record #2 =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 09/29-13:57:41.442309 0:E0:81:23:75:F0 -> 0:A0:CC:39:BA:F type:0x800 len:0x6A 10.168.12.235:40985 -> 140.147.249.38:7090 TCP TTL:64 TOS:0x0 ID:37444 IpLen:20 DgmLen:92 DF ***AP*** Seq: 0xA74712A6 Ack: 0xAFE55375 Win: 0x16D0 TcpLen: 32 TCP Options (3) => NOP NOP TS: 2041090422 88218204 B8 26 82 05 30 2D 33 2D 31 9F 1F 07 64 65 66 61 .&..0-3-1...defa 75 6C 74 9E 01 03 9D 01 01 B3 03 80 01 46 9F 68 ult..........F.h 07 2A 86 48 CE 13 05 69 .*.H...i =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 09/29-13:57:41.565218 0:A0:CC:39:BA:F -> 0:E0:81:23:75:F0 type:0x800 len:0x90 140.147.249.38:7090 -> 10.168.12.235:40985 TCP TTL:43 TOS:0x0 ID:1104 IpLen:20 DgmLen:130 ***AP*** Seq: 0xAFE55375 Ack: 0xA74712CE Win: 0xFB28 TcpLen: 32 TCP Options (3) => NOP NOP TS: 88218216 2041090422 B9 4C 82 05 30 2D 33 2D 31 98 01 01 99 01 04 9B .L..0-3-1....... 01 00 BC 3A 30 38 80 07 56 6F 79 61 67 65 72 A1 ...:08..Voyager. 2D A1 2B 28 29 06 07 2A 86 48 CE 13 05 65 A0 1E -.+()..*.H...e.. 1B 1C 46 61 69 6C 65 64 20 74 6F 20 72 65 74 72 ..Failed to retr 69 65 76 65 20 72 65 63 6F 72 64 20 23 33 ieve record #3 =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 09/29-13:57:41.573038 0:E0:81:23:75:F0 -> 0:A0:CC:39:BA:F type:0x800 len:0x42 10.168.12.235:40985 -> 140.147.249.38:7090 TCP TTL:64 TOS:0x0 ID:37445 IpLen:20 DgmLen:52 DF ***A***F Seq: 0xA74712CE Ack: 0xAFE553C3 Win: 0x16D0 TcpLen: 32 TCP Options (3) => NOP NOP TS: 2041090489 88218216 =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 09/29-13:57:41.758688 0:A0:CC:39:BA:F -> 0:E0:81:23:75:F0 type:0x800 len:0x42 140.147.249.38:7090 -> 10.168.12.235:40985 TCP TTL:43 TOS:0x0 ID:1105 IpLen:20 DgmLen:52 ***A**** Seq: 0xAFE553C3 Ack: 0xA74712CF Win: 0xFB28 TcpLen: 32 TCP Options (3) => NOP NOP TS: 88218230 2041090489 =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 09/29-13:57:41.758990 0:A0:CC:39:BA:F -> 0:E0:81:23:75:F0 type:0x800 len:0x42 140.147.249.38:7090 -> 10.168.12.235:40985 TCP TTL:43 TOS:0x0 ID:1106 IpLen:20 DgmLen:52 ***A***F Seq: 0xAFE553C3 Ack: 0xA74712CF Win: 0xFB28 TcpLen: 32 TCP Options (3) => NOP NOP TS: 88218230 2041090489 =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ 09/29-13:57:41.759165 0:E0:81:23:75:F0 -> 0:A0:CC:39:BA:F type:0x800 len:0x42 10.168.12.235:40985 -> 140.147.249.38:7090 TCP TTL:64 TOS:0x0 ID:0 IpLen:20 DgmLen:52 DF ***A**** Seq: 0xA74712CF Ack: 0xAFE553C4 Win: 0x16D0 TcpLen: 32 TCP Options (3) => NOP NOP TS: 2041090584 88218230 =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ -- cgh

1 0

[Fwd: [Bug 622] New: processz3950queue fails]
by Chris Hobbs 29 Sep '03

29 Sep '03

Any thoughts on the attached complaint? This issue is drastically affecting my district's install/upgrade :( -- cgh

1 0

is everything templified?
by Benedykt 29 Sep '03

29 Sep '03

Is the upcoming release of koha-2.0.0 going to be all templified? I have found a good program that works for me: winmerge. So don't be bothered with my question about how to find changes between original and translated files in my previous post. During the process however one feels that translation effort at this stage is very tedious. One has to visually make sure that lines that changed look so only because there's a translation string in them. Otherwise one needs to accept the changes and, if needed, translate the strings, if any. Therefore I am still longing for a solution that would extract all the language strings into a file (or there could be several of them) which, in turn, could contain only original=>translated pairs. that file should then be consulted by the perl or template files for users to see them in their own language. It would speed up the translation of koha a lot. Benedict

2 1

I will not give up untill someone...
by Benedykt 29 Sep '03

29 Sep '03

...untill someone gives me an explicit reason why we do not have a localization of koha the way it is suggested on the web (cpan.org) Namely, I have read through some modules in cpan directory and have found this: Locale::PO Manipulate .po entries from gettext Locale::Maketext Framework for software localization Locale::gettext Multilanguage messages Locale::PGetText What GNU gettext does, written in pure perl Now, I am wondering whether any of the above modules would be fit to be implemented in koha project. Is it to late to even think about it? Right now, as I see it, for every theme in same language one needs redundant and complete language strings in each file. A gettext like solution might save a bit of work in the future. regards, Benedict. Disclamer: I am not a programmer and I do not have an idea what perl language is... I am just a computer operator.

4 3

[BUG] barcode mandatory or not ?
by paul POULAIN 28 Sep '03

28 Sep '03

Hi, The bug 599 has been understood... It's due to inconsistencies in Koha features : in MARC you can put barcode "mandatory" or "not mandatory". BUT in non-MARC part of Koha, barcode IS MANDATORY. If you set barcode = non mandatory in MARC parameters, your DB is broken when you let barcode empty. The question is : what is the good behaviour ? * barcode IS mandatory => manage this in checker, the tools that checks that your DB is correctly parametered. * barcode IS NOT mandatory => change non-MARC part of Koha to accept empty barcodes. From a technical point of vue, both are simple. My question is for librarians (& for our big "circulator", i mean chris, if there is something i'm missing technically) NOTE : we agree that a books without barcode can't be issued/returned, aren't we ? -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

7 6

Re: [Koha-devel] resuming translation effort
by robweir＠alum.drexel.edu 28 Sep '03

28 Sep '03

If you are looking for a windows tool, try CSdiff available from http://www.ComponentSoftware.com/products/csdiff/ Glad you're back! Rob ----- Original Message ----- > From: "Benedykt" <kb2qzv(a)poczta.wp.pl> > To: koha-devel(a)lists.sourceforge.net > Date: Sun, 28 Sep 2003 00:29:53 +0200 > Subject: [Koha-devel] resuming translation effort > > Hi all, > I've been away from the koha project for some time now. Yesterday, I checked out > koha-tmpl module and noticed a considerable amount of changes to the template files > in it. Congratulations to you folks for all the good work. > > Now, What tools are at peoples' desposal around there to quickly compare the changes > between say opac/default/en directory and opac/default/pl directory? > > All of the files differ because the polish version has translations in it. > The english version evolved and has additions that are not found in the old polish files. > And I am talking about differences to not only english words but also to the code in tmpl > files! > > Is there an easy way to accomplish the difficult job? > > Thanks for any information > Benedict > > PS. I will be interested in windows tools for some time now.

1 0

resuming translation effort
by Benedykt 27 Sep '03

27 Sep '03

Hi all, I've been away from the koha project for some time now. Yesterday, I checked out koha-tmpl module and noticed a considerable amount of changes to the template files in it. Congratulations to you folks for all the good work. Now, What tools are at peoples' desposal around there to quickly compare the changes between say opac/default/en directory and opac/default/pl directory? All of the files differ because the polish version has translations in it. The english version evolved and has additions that are not found in the old polish files. And I am talking about differences to not only english words but also to the code in tmpl files! Is there an easy way to accomplish the difficult job? Thanks for any information Benedict PS. I will be interested in windows tools for some time now.

1 0

Re: [Koha] [BUG] barcode mandatory or not ?
by baljkas＠mb.sympatico.ca 26 Sep '03

26 Sep '03

Friday, September 26, 2003 15:28 CDT Hi, all, Stephen Hedges noted that at NPL they >have in the past used [the] catalog to store pieces of information >that were not physical items, like names and addresses of local social >agencies, and websites (before we had Koha). That would allow people >to search for something like "poverty" and get hits not only on books >about poverty, but websites about poverty and the names of local >agencies that deal with poverty. That is super! I tried to convince a social service agency that this was a feasible thing to do with a library catalogue when I was a volunteer library coordinator years ago. (For the MARC'ists in the Koha community, you may note: while websites can be coded in 'regular' MARC21 (electronic resources, I believe still), so can agencies and individuals. The MARC fields are slightly different from normal (i.e. a book), but the information is online at the LC website under the rubric Community Information at URL <http://www.loc.gov/marc/community/eccihome.html> ) >If the catalog is used to store information that does not relate to a >physical item, then the barcode should not be mandatory. As for non-physical items like websites: that is an excellent point, Stephen. I ran into a problem with the Athena system because it was nigh impossible to convince it that websites didn't need a barcode and we ended up creating fake ones just so it would let us be. Plus the listserv already received the example from a barrister in the UK about libraries that had 24-7 potential patrons but not 24-7 library circ service. The military library where I last worked as a cataloguer had that situation and we actually used manual (logbook) circ instead of the system's circ module. This also allowed us to allow students/staff to sign-out newly received items if needed before cataloguing could be completed. Luckily, our MicroCat system didn't require a barcode. >However, I think the templates for adding and editing items should then >be set to return a warning, in case someone mistakenly enters a >physical item without a barcode. Also an excellent idea! Cheers, Steven F. Baljkas library tech at large Koha neophyte Winnipeg, MB, CANADA

1 0