- Koha - lists.katipo.co.nz

Z39.50 daemon
by vimal kumar 28 Feb '06

28 Feb '06

Dear Koha Users, When I try to start Z39.50 daemon using following command with root power, # cd /usr/local/koha/intranet/scripts/z3950daemon # ./z3950-daemon-launch.sh I got the following message, # This account is currently not available. Why it hesistate to start and how can I launch this daemon? Vimal Kumar Asian School of Business Technopark Trivandrum-695 581 vimal0212(a)yahoo.com --------------------------------- Yahoo! Mail Use Photomail to share photos without annoying attachments.

3 2

Re: Koha and LDAP
by KL Nasveschuk 28 Feb '06

28 Feb '06

Yes, work fine. Kent On Mon, 2006-02-27 at 16:50 -0600, Mark Flach wrote: > Did you ever get LDAP and Koha working? > > Mark Flach >

1 0

Re: [Koha] New to KOHA
by Steven F.Baljkas 28 Feb '06

28 Feb '06

Monday, February 27, 2006 20:52 CST Hi, Marie, Just one quick notendum, as I know you have received useful responses on the more germane matters from Stephen, Joshua, et al, already ... > From: "Marie Wardall" <mwardall(a)dce.k12.wi.us> > Date: 2006/02/26 Sun PM 02:01:21 CST > To: <koha(a)lists.katipo.co.nz> > Subject: [Koha] New to KOHA > > Our school district is building a new K-5 building to open in the fall and we > are looking into opening the library using KOHA. I will be the librarian in > the new building and have been looking into and trying things out in the KOHA > demo. Our new school would be the pilot school for KOHA in the district and > if things went well then it would be implemented throughout the district. > [snip] > > *One last thing for now, as I am sure I will have others as I investigate > more and am able to work through the setting up of the system preferences, is > that in the Cataloging on the demo there is a Default MARC record framework > and a Test MARC record framework I could choose from. I'm thinking I could > set up different frameworks here for the different types of materials that I > catalog such as book, video, DVD, CD, equipment and an easy MARC for when I > don't need or want a complete MARC record. Once I set up those different > MARC frameworks when I would catalog I could just choose the framework and > put in the information that was needed for that type of material or > item...right? Just a vocabulary suggestion here, really; since many ILS and cataloguers would refer to them as such, we may want to stick with the term 'template' for different set-ups to catalogue different material types (especially). Also, I don't know that you need to have an easy MARC record per se: by that, I think you mean a record with just certain core fields, right? When would *you* (your library system) not want a complete MARC record? There are always the distinctions between 1st level and 3rd level description (nobody expects that you would do 3rd for everything ... I hope! If so, push for a pay increase ;-D). You do realise that you do not have to have all fields represented for a record to be a valid MARC record. It is perfectly valid, for example, to decide that, for certain kinds of materials, certain fields are omitted. Many school libraries don't subject video materials to subject analysis (I personally think that a mistake, but hey, I'm a cataloguer) or decide that maps, globes and posters get 1st level description where books and videos get 2nd. I don't think even LC uses 3rd level for everything. IIRC, Follett, among many others (Sagebrush, Mandarin), makes reference to easy MARC records to mean quickie records created when something new pops up or just as often, when the ILS has mysteriously lost an item ;-). If that is what you are worried about, Marie, I think you may find it is less a concern with Koha than with most ILS. In fact, I cannot remember anyone ever noting/complaining about Koha losing records in the nearly 4 years I have followed the listserv faithfully. Good luck with your migration to Koha. Hopefully, it will be a success for you and give impetus to Anne and team in piloting Koha in other Wisconsin schools. Best wishes, Steven F. Baljkas library tech at large Koha neophyte Winnipeg, MB, Canada

1 0

Re: [Koha] New to KOHA
by Marie Wardall 27 Feb '06

27 Feb '06

Yes storing barcodes in a scanner and then dumping them into the circ station is what I mean. We close down the library for two plus days and scan everything in the library for inventory. We run reports against the shelves for missing items that have not been scanned and we can tell then what items were mysteriously lost that year. Marie >>> KL Nasveschuk <klnasveschuk(a)klnconsulting.net> 2/27/2006 11:56 AM >>> Marie, Are you just trying to scan barcodes versus typing in a barcode? We have tested this briefly and it works with Koha. Ex. scan a barcode, pull record from catalog advanced search. I guess what really matters is how it is setup in Koha. If you are looking to store barcodes in the scanner, then download as part of inventory, I don't believe Koha will do that. Someone correct me if I am wrong. Kent On Mon, 2006-02-27 at 08:29 -0600, Marie Wardall wrote: > So the Dolphin Scanners that we have right now that we use for inventory could be re-programmed to work with the KOHA system if we had someone do that for us. Our Network Manager I'm thinking could do this. > > Thanks! > Marie > > Marie J. Wardall > IMC Coordinator > Rothschild Elementary School > 810 First Street > Rothschild, WI 54474 > mwardall(a)dce.k12.wi.us > Phone: 715-359-3186 ext.5424 > FAX: 715-355-3723 > Fate gives us the hand, and we play the cards. > Arthur Schopenhauer > > >>> "Stephen Hedges" <shedges(a)skemotah.com> 2/26/2006 3:06 PM >>> > Marie Wardall said: > [...] > > *Barcodes-Our current barcodes are 5 digits long with a leading T for a > > material barcode and a leading P for a patron barcode. > > Joshua noted that Nelsonville Public Library still uses the Follett patron > barcodes, so I can give you some extra information here. > > Follett uses Interleaved 2-of-5 symbology in their barcodes, but the > scanned codes are then manipulated by their system so the user only sees a > "T" or a "P" and no more than five digits. If you scan these barcodes > with a non-Follett scanner in a text editor, you will see that the > barcodes are actually always 10 digits long: the visible digits (no "T" > or "P") with leading zeros to pad the number to 7 digits, plus three more > digits that tell the Follett software a little more about the barcode > (such as if it is a "T"itle or a "P"atron barcode). For example, if the > Follet library card had the number "P 1234" printed on it, an > off-the-shelf scanner would read something like "0001234999." > > Most vendors of barcode scanners know how to program their products for > Follett systems, so they can sell to schools that use Follett. Those same > vendors can help you program your scanners to simply remove the last three > digits. Then the barcode example above would look like "0001234" when > scanned into Koha. Staff quickly get used to making this conversion in > their heads if they need to type in a number manually. Works fine. (But > don't expect the Follett folks to help you with the scanner programming, > of course!) >

3 2

Re: [Koha] New to KOHA
by Marie Wardall 27 Feb '06

27 Feb '06

So the Dolphin Scanners that we have right now that we use for inventory could be re-programmed to work with the KOHA system if we had someone do that for us. Our Network Manager I'm thinking could do this. Thanks! Marie Marie J. Wardall IMC Coordinator Rothschild Elementary School 810 First Street Rothschild, WI 54474 mwardall(a)dce.k12.wi.us Phone: 715-359-3186 ext.5424 FAX: 715-355-3723 Fate gives us the hand, and we play the cards. Arthur Schopenhauer >>> "Stephen Hedges" <shedges(a)skemotah.com> 2/26/2006 3:06 PM >>> Marie Wardall said: [...] > *Barcodes-Our current barcodes are 5 digits long with a leading T for a > material barcode and a leading P for a patron barcode. Joshua noted that Nelsonville Public Library still uses the Follett patron barcodes, so I can give you some extra information here. Follett uses Interleaved 2-of-5 symbology in their barcodes, but the scanned codes are then manipulated by their system so the user only sees a "T" or a "P" and no more than five digits. If you scan these barcodes with a non-Follett scanner in a text editor, you will see that the barcodes are actually always 10 digits long: the visible digits (no "T" or "P") with leading zeros to pad the number to 7 digits, plus three more digits that tell the Follett software a little more about the barcode (such as if it is a "T"itle or a "P"atron barcode). For example, if the Follet library card had the number "P 1234" printed on it, an off-the-shelf scanner would read something like "0001234999." Most vendors of barcode scanners know how to program their products for Follett systems, so they can sell to schools that use Follett. Those same vendors can help you program your scanners to simply remove the last three digits. Then the barcode example above would look like "0001234" when scanned into Koha. Staff quickly get used to making this conversion in their heads if they need to type in a number manually. Works fine. (But don't expect the Follett folks to help you with the scanner programming, of course!) -- Stephen Hedges Skemotah Solutions, USA www.skemotah.com -- shedges(a)skemotah.com

3 2

Re: [Koha] New to KOHA
by Stephen Hedges 27 Feb '06

27 Feb '06

Marie Wardall said: > So the Dolphin Scanners that we have right now that we use for inventory > could be re-programmed to work with the KOHA system if we had someone do > that for us. Our Network Manager I'm thinking could do this. So those are actually handheld computers, right? That's much fancier hardware than I'm used to using. Usually a standard barcode scanner (unless it's a very cheap one) can be programmed by scanning a series of special barcodes. The trick is finding the programming manual -- but most are available online. Stephen -- Stephen Hedges Skemotah Solutions, USA www.skemotah.com -- shedges(a)skemotah.com

1 0

I can connect to Koha locally, but not from another machine
by Craig Andersen 27 Feb '06

27 Feb '06

I can connect and use Koha locally, either by using http://machinename or by http://127.0.0.1 and it works fine. If I try to connect to it using http:/IPaddress or http://machine name from another machine I get following error: NOT FOUND the requested URL/ was not found on this server. I checked the Apache error log which showed: [error] [client ipaddress] file does not exist /htdocs If I type the ip address into the browser on the server, rather than http://127.0.0.1 I get the Not Found error. I'm at a loss. When I first installed Koha I'm pretty sure that I was able to connect to it from another machine, but now when I'm ready to start testing some things out, it seems to get lost after connecting to the apache server. I'm using Firebox to connect. Same thing happens with IE. The server is running Debian Sarge and apache2. Any ideas or help would be appreciated Thanks in advance Craig

2 1

Re: [Koha] New to KOHA
by Stephen Hedges 27 Feb '06

27 Feb '06

Marie Wardall said: [...] > *Barcodes-Our current barcodes are 5 digits long with a leading T for a > material barcode and a leading P for a patron barcode. Joshua noted that Nelsonville Public Library still uses the Follett patron barcodes, so I can give you some extra information here. Follett uses Interleaved 2-of-5 symbology in their barcodes, but the scanned codes are then manipulated by their system so the user only sees a "T" or a "P" and no more than five digits. If you scan these barcodes with a non-Follett scanner in a text editor, you will see that the barcodes are actually always 10 digits long: the visible digits (no "T" or "P") with leading zeros to pad the number to 7 digits, plus three more digits that tell the Follett software a little more about the barcode (such as if it is a "T"itle or a "P"atron barcode). For example, if the Follet library card had the number "P 1234" printed on it, an off-the-shelf scanner would read something like "0001234999." Most vendors of barcode scanners know how to program their products for Follett systems, so they can sell to schools that use Follett. Those same vendors can help you program your scanners to simply remove the last three digits. Then the barcode example above would look like "0001234" when scanned into Koha. Staff quickly get used to making this conversion in their heads if they need to type in a number manually. Works fine. (But don't expect the Follett folks to help you with the scanner programming, of course!) -- Stephen Hedges Skemotah Solutions, USA www.skemotah.com -- shedges(a)skemotah.com

2 1

New to KOHA
by Marie Wardall 26 Feb '06

26 Feb '06

Our school district is building a new K-5 building to open in the fall and we are looking into opening the library using KOHA. I will be the librarian in the new building and have been looking into and trying things out in the KOHA demo. Our new school would be the pilot school for KOHA in the district and if things went well then it would be inplemented throughout the district. Currently our district uses Library software from Follett. The other librarians in the district have a lot of concerns about KOHA and are hesitant on change. I want to be able to show them that the things they are used to now and some of the improvements they would like to see can be achieved with KOHA. So here are some things that come to mind after looking at the demo and speaking with my collegues: *Currently, when checking out a student, the picture of the student appears on the screen so that we can verify who the student is. This is more important at the secondary level, but also relied on in the elementary level when you are getting to know who the child is. Is this possible in KOHA? *WE use a Student Management System called Starbase to dump student records into Follett each Fall. This is crucial in getting ready for classes each fall because it is a very big time saver. The little I know about how different systems work I would think that we would be able to do the same with KOHA...am I correct? *Barcodes-Our current barcodes are 5 digits long with a leading T for a material barcode and a leading P for a patron barcode. Looking at the demo it appeared that the barcodes are 8 digits long. Can this be changed when going through the setup of the system preferences? If we would go with KOHA and the rest of the district would get switched over we would need to be able to keep the same barcode numbers on books because re-barcoding the collections would be an enormous job. *One last thing for now, as I am sure I will have others as I investigate more and am able to work through the setting up of the system preferences, is that in the Cataloging on the demo there is a Default Marc record framework and a Test Marc record framework I could choose from. I'm thinking I could set up different frameworks here for the different types of materials that I catolog such as book, video, DVD, CD, equipment and an easy MArc for when I don't need or want a complete marc record. Once I set up those different MArc frameworks when I would catalog I could just choose the framework and put in the information that was needed for that type of material or item...right? Thank-you for any insight or comments you can give regarding these questions/comments. My questions are lees technical than the others I've seen here, but are important in educating myself and they others in my district about what KOHA can do for us. Marie J. Wardall Teacher-Librarian Rothschild Elementary School Rothschild, WI 54474 715-359-3186 ext.5424 mwardall(a)dce.k12.wi.us

2 1

Re: Re: [Koha-win32] Re: [Koha] Tag 880
by Steven F.Baljkas 25 Feb '06

25 Feb '06

Friday, February 24, 2006 19:21 CST Hi, Carol, Joshua, et al., Just catching up with the e-mail a little late today. Carol had posed a question a while back on getting actual Chinese characters both in MARC records and out in the Koha OPAC display. I had suggested MARCEdit might be able to help with some things in the past, but if memory serves -- I'm not 100% on this and you would have to check the MARC standards online or in print to confirm this but--, the $6 linking fields have to be generated by the ILS itself to provide such linkages. Most of the ILS I have experienced simply cannot do this. (I assume that Voyager and Aleph can because they are known for multiscript abilities.) I don't think Koha can (not that that is a bad thing for this stage in its development, considering the complexity and rarity of the need for $6 linkages). The purpose of the 880, Joshua, according to my erstwhile go-to guy on the history and evolution of MARC coding, was to hold non-Roman script characters. I gather that, although computers may have been able to code for them for a long while now (since the 1960s? via hexadecimal and ASCII and Lord knows probably other codes), there weren't any ILS at the beginning that could make use of them. Hence, 880 and associated fields were contrived so that data could be preserved against loss (recall our discussion of backing things up: I tell you, we cataloguers are THE pre-eminent packrats of humanity - no iota to be lost! ;-D). If I recall my original advice to you, Carol, it was to ***try to see if Koha could display the original Chinese script correctly in the 100 and 245 fields*** (and for that matter, the other core descriptive fields, although I know I didn't say that before). I know that there have been questions -- some of them intiated by you, IIRC -- on UTF8 etc. that are relevant to this. I just don't know what Koha's status is on using non-Roman scripts. Sorry. It would be really good to know how that works though. From what I am used to seeing in other ILS, it usually requires that the cataloguers enter special codes -- either hexadecimal or system proprietary ones -- in order to ensure that special characters will display properly for patrons (usually, the cataloguers end up having to look at codes or messy weird stuff in place of real letters or logograms). Continuing the re-iteration of my original advice to you, Carol: if you are able to put the actual Chinese characters into the 100 and 245, you could use a 700$a or 900$a to provide access to the author entry transcribed, and perhaps a 242 (technically TRANSLATION of title, which is never a bad thing), 246, 700$t, 730 and/or 740 fields to provide transcribed title access. Although anyone who knows me knows I actually like the cataloguing rules, what I am proposing (other than the 900$a which is free to do with as you please) bends if not breaks the cataloguing rules. However, it should work, given that Joshua has assured us that Koha can access 700 fields (at least from 2.2.5 on) and 246s. A quick word about transcriptions, because I know this topic has caused headaches for Chinese-language cataloguers. In 2000, LC prescribed that the Pinyin system of romanization was to supersede the previously used Wade-Giles system. Carol, ***if you are retrieving older MARC21 (really USMARC, etc.) records, you may very well have to move the transcribed fields and create the now REQUIRED pinyin transcriptions.*** (There is not, so far as I know, a requirement to DELETE the older Wade-Giles transcriptions, but someone working directly in the field may well correct me on that point .) Now, Carol, please also note: you can take all this with a grain of salt (ignore it) if you don't care about having your library comply with the ALA-LC practices mandated in this case. I have seen libraries request and rely on their own transliteration systems for Russian and Ukrainian so I know that ALA-LC practices are not always heeded when it comes to dealing with non-Roman script cataloguing matters. I hope that this re-iteration and amplification will help somewhat. I am very interested to learn how this resolves for you and I do hope it will work out well. Best wishes with this tricky problem! Cheers, Steven F. Baljkas library tech at large Koha neophyte Winnipeg, MB, Canada ============================================================ From: Carol Ku <carolcool01(a)yahoo.com> Date: 2006/02/24 Fri PM 03:41:35 CST To: Joshua Ferraro <jmf(a)liblime.com> CC: Koha Mailing List <koha(a)lists.katipo.co.nz>, Koha Windows <koha-win32(a)nongnu.org> Subject: Re: [Koha-win32] Re: [Koha] Tag 880 You are perfectly right. I noticed that most libraries such as Library of Congress, they represent Chinese pinyin in tag 100, and this piece of info is linked to tag 880 $6100 and with other related subfields etc... We would like to do the following: 1) save the pinyin and Chinese in Koha. 2) Display Chinese info in OPAC 3) Allow user to search using pinyin if they don't have Chinese input Since Koha display only one line item for title, author etc, we are thinking may be we need to use MARCEdit to tweak tag 100 to 880 $6100. I was advised by others that I should instead designate new tag e.g. 900 for tag 880 $6100, 901 for tag 880 $6245 etc. To make things more complicated, MARCEdit does not seem to recognize the $6 link either. So it will treat all tag 880 as one tag. Joshua Ferraro <jmf(a)liblime.com> wrote: On Fri, Feb 24, 2006 at 12:26:29PM -0800, Carol Ku wrote: > i think the $6 linking field is different from a regular > subfield a, b or c > etc. > > In MARC, all the information on the book will be stored in the native > language in tag 880. Then they use $6 linking field to tie 880 to tag 100 > for Name etc... so e.g. 880 $6100 a.... so this tag means information > stored here is the author name (designated by code $6100) in e.g Chinese. > $6 is not a regular subfield.... OK ... first let's discuss what you're trying to do. I have had two years of Chinese language classes so I know that there are several ways to represent Chinese. Are you attempting to put 'pinyin' in the 100a and then link to the actual characters in 880? What is your goal in using the 880? Cheers, -- Joshua Ferraro VENDOR SERVICES FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf(a)liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS _______________________________________________ Koha mailing list Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha

3 4