- Koha - lists.katipo.co.nz

Re: [Koha] installing issues please help
by Jose 09 Jul '04

09 Jul '04

Ok, MJ you said : Does it still work if you add -h localhost to the mysql command? U mean when entering to mysql? (./mysql -uroot -h localhost -pxxx) I'll try it out... what if it fails? Another thing... there is not such file '/var/lib/mysql/mysql.sock' I've entered to /var/lib/mysql and there si no 'mysql.sock' archive Thanks, Cheers. J0se

2 1

installing issues please help
by zero＠vtr.net 09 Jul '04

09 Jul '04

Hi i'm getting this error once and over. Everything is just set up as described in the installation guide for Red Hat E3: ERROR: CREATING DATABASE Creating the MySQL database for Koha... 0 DBI connect('Koha:localhost','kohaadmin',...) failed: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) at /usr/local/koha/intranet/modules/C4/Context.pm line 368 connected to your DB. Checking & modifying it Can't call method "prepare" on an undefined value at scripts/updater/updatedatabase line 629. Problem updating database... I really need help, I'm doing this as root, I have created the password for the root user in mysql, and I can enter to mysql with it and create and/or drop databases and all. Both mysql and apache daemon are running, i have all the perl modules needed. I mean don't know what is happening. if there would be something else to do pleae tell what is it! Should I look at those lines mentioned above? Ok I'll wait thnx fornow bye. J0se -=;(=-

2 1

Re: [Koha] issues help request
by Anthony S. 09 Jul '04

09 Jul '04

Hi (Bonjour) G.H., Someone else maintains Wiki. RSVP, Tony On Thu, Jul 08, 2004 at 09:08:56AM +0200, Gerard Henry wrote: > hello, > i look at your page with mozilla, and it shows: > "lib/Request.php:116: Warning[2]: ob_start(): output handler 'ob_gzhandler' cannot be used after 'URL-Rewriter'"

2 2

RE:re: [Koha] MARC Import (fwd)
by MJ Ray 09 Jul '04

09 Jul '04

This subscriber hasn't white-listed their mailing list subscriptions. I assume that they are bouncing every list email in this way. Please unsubscribe them. (By the way folks, I believe these challenge-response systems are harmful, so I usually only confirm spams to them.) ---------- Forwarded message ---------- Date: 2004-07-09 13:00:04 +0100 From: AntiSpam UOL <brunocpt.sspam(a)uol.com.br> Subject: RE:re: [Koha] MARC Import [...] Hi, You´ve just sent a message to brunocpt(a)uol.com.br In order to confirm the sent message, please click here This confirmation is necessary because brunocpt(a)uol.com.br uses Antispam UOL, a service that avoids unwanted messages like advertising, pornography, viruses, and spams. [...] -- MJR/slef My Opinion Only and not of any group I know http://www.ttllp.co.uk/ for creative copyleft computing "Before we try to work out if he's competent, let's work out if he's conscious." (anon. exam marker)

1 0

re: [Koha] MARC Import
by Hans Henderson 09 Jul '04

09 Jul '04

> Extra info: Cost-free but not free software. MJ - Not sure of the distinction. Do you just mean it's not "truly free", as in open-source? For everyone's information, I've downloaded it to my Win2000 machine, and it works nicely. Here's the statistical report on some of my recently downloaded MARC records. I've massaged it a bit, and used "0" to show tags present in all records, "a" for tags present in most of them, down to "x" for rare ones. Very helpful in figuring out my MARC-to-Koha DB linking prior to importing. I'm also using BookWhere to display the record contents in a very browsable and readable way, it also reports and let me filter based on topical Subject listings. And finally, MARCEdit to actually the records. TAG FREQ MAX_LENGTH 001 0 15 003 0 6 005 0 17 008 0 41 015$a m 16 016$a x 24 020$a 0 126 035$a m 42 040$a m 11 049$a x 2 049$k x 12 049$l x 1 049$m x 1 050$a x 11 082$a m 15 082$2 m 12 082$d m 1 092$a m 19 100$a l 23 100$d l 13 245$a a 45 245$c a 97 245$b a 33 250$a x 8 260$a a 11 260$b a 27 260$c a 12 300$a a 9 300$b a 35 300$c a 12 400$a x 15 400$d x 5 400$t x 13 400$v x 1 440$a a 29 440$n a 22 440$p a 21 440$v a 5 490$a x 20 490$n x 8 490$p x 7 490$v x 1 500$a l 142 505$a x 93 600$a x 15 600$x x 14 650$a 0 33 650$v 0 25 650$x 0 19 650$z 0 25 650$y 0 12 651$a x 27 651$v x 17 651$x x 7 651$y x 20 700$a 0 29 700$d 0 13 700$t 0 40 700$q 0 17 700$c 0 4 800$a x 15 800$d x 5 800$t x 13 800$v x 2 852$a 0 5 852$b 0 13 852$h 0 10 852$p 0 9 852$y 0 8 852$5 0 9 852$9 0 8 852$m 0 17 852$z 0 18 852$3 0 15 852$7 0 9 971$a m 7 971$b m 6 972$a x 7 972$a x 6 973$a x 7 973$a x 6 997$a x 84

3 2

re: [Koha] Biblio records as book set "container" records - hierarchical groupings, et seq.
by Hans Henderson 09 Jul '04

09 Jul '04

Steven, Thanks so much for your response! >my head is still swimming slightly ;-) ... Sorry, as my girlfriend says, sometimes I think too much <g> > What I would propose as a 'counter-offer' is using a series tag 440 (or 490 - 830 if necessary), based on the understanding that these sets of books really are parts of series that are meant to be used in the way that you are doing. > If you created/imported a simpler MARC record for each title, you could make the links with their hierarchical series by creating a useful local 440 (series tracing). Yes, here's an example of how Oxford University does it with a 440: 440 0$a Oxford reading tree.$n Stage 1,$p Kipper stories In this case it *is* a *real* series - they are all books. How does Koha make use of this entry? Can the user just click and pull up a list of all the other books in that series? So if I have a CD-ROM designed to work with all the Stage 1 Reading Tree books (not just the Kipper stories), could I add: 440 0$a Oxford reading tree.$n Stage 1 to the CD's MARC record before importing into Koha, and Koha will do something meaningful with it? Note the CD-ROM would be an entirely different Itemtype, different shelving location, different call number series, etc. > Granted, this may not be a perfectly kosher use of the 440 -- what you choose might not be recognised anywhere else as a series --, but what you are proposing otherwise really would require detailed Analytics (library jargon) that would give any cataloguer a headache. I'd love to learn more about "Analytics" - even though it is jargon (I've seen it in the MARC specifications), twenty minutes of browsing with Google didn't show much of use - any pointers to online Library Science tutorials? >In any case, what I am proposing would allow OPAC users the ability to find each individual title without necessarily making each individual record overwhelming (20-30 title- and/or author-title added entries plus the problem of deciding a legitimate 245 entry). Each record would have the 440 showing what group it belongs to as well as the call number which would show where it is collocated/located on the shelves. So 440 (mapped to an appropriate Koha field - any suggestions?) becomes a searchable field in the OPAC, returning all resources containing matching strings? That's (more than <g>) enough for now to inflict on everyone in the list, discussion of the your call numbering system ideas to continue off-list.

1 0

re: [Koha] Biblio records as book set "container" records - hierarchical groupings
by Hans Henderson 09 Jul '04

09 Jul '04

> Take a look at the US MARC site at Library of Congress for the 440 field and its subfields: www,loc.gov/marc/bibliographic/ecbdsers.html Anne, Thanks for all your tips on the MARC fields. However, before I get too immersed in the MARC aspect of this, I'd like to find out whether Koha makes use of these fields in linking BiblioItems to a "series" Biblio when importing. I can put all the information I like into the MARC records beforehand, but then if I have to go and do something else in Koha anyway. . . >I checked WorldCat at OCLC for Oxford reading and found an Oxford Firefly series. Could you point me to the z39.50 server information? Many libraries don't list many of our books, it's a bit of an Easter egg hunt <g> To everyone: What I'd really like is when the user puts in a search query and gets back a list of Reader titles, for Koha to also display the related "other" records - teachers' notes, audio, etc. I realise I can try to train the users on how to structure their searches properly, but it would be better if the Reader record could display the specific links to resources that support that title. If I have to, I'll manually add the list to each biblioitem, but that's a lot of work. But if I do decide to go this way, can this be done as a link for the user to just click on? I'm afraid if I list the call number, then when the call number needs to be changed I'll be doing endless find and replace editing on all the related records. . . Thanks, Hans

1 0

re: [Koha] Koha's call number vs. our library's call number
by Hans Henderson 09 Jul '04

09 Jul '04

Stephen, Thanks for answering. > I'd recommend you put your call number in biblioitems.classification and not mess with dewey (everything should still work OK). Use some sort of unique numbering system for barcode. -- SH My numbering system is indeed unique, but is unique for every item/copy of a title, not for each biblioitem (see my original message for the scheme's details). And that number also functions as the barcode, which is why I thought that would be a good field. Are you saying it's necessary to use a biblioitem field for searching/OPAC display purposes? I can see that would make sense, but if 2.2 is going to use itemcallnumber, maybe I can use barcode in the meantime? If not, I suppose I could put the first five parts of the number - unique to each biblioitem - in the field you suggest, and then put the whole call number in the barcode field of the related items. I'd just have to remember to change both levels if the number has to change. And I still need to know if it's OK to ignore the Koha call number - it might have Dewey in it or it might be empty for a lot of records - is that OK? Thanks, Hans >> I've created an alphanumeric local call number unique to each item (copy of a title) I'm also using this as a barcode number. the first part of the number shows the level, then the set, then the titles, and then the individual copies. So Q010A04 means "the fourth copy of title A in set 010 at reading difficulty level Q". >> I plan to put this local call number into Koha's barcode field in the items table, and link that field to MARC 852c - please confirm I got at least that right, or should I use a 9xx?

1 0

Biblio records as book set "container" records - hierarchical groupings
by Hans Henderson 09 Jul '04

09 Jul '04

We're starting off using Koha to track "graded readers". Nearly all of these are in hierarchical sets. For example: Oxford====>Reading Tree===>Stage 1==>Kipper=>Readers: Oxford====>Reading Tree===>Stage 1==>Kipper=>Playscripts: Oxford====>Reading Tree===>Stage 1==>Kipper=>Big Books: Oxford====>Reading Tree===>Stage 1==>Kipper=>Teacher's guide: Oxford====>Reading Tree===>Stage 1==>Kipper=>Take-home cards: Oxford====>Reading Tree===>Stage 1==>Kipper=>Audio cassettes: Oxford====>Reading Tree===>Stage 1==>Kipper=>CDs: Oxford====>Reading Tree===Stage 1==>Biff & Chip=>Big Books: Oxford====>Reading Tree===Stage 1==>Biff & Chip=>Teacher's guide: Oxford====>Reading Tree===Stage 1==>Biff & Chip=>Take-home cards: Oxford====>Reading Tree===Stage 1==>Biff & Chip=>Audio cassettes: Oxford====>Reading Tree===Stage 1==>Biff & Chip=>CDs: Note the above is a sample list of *sets*. Within each set may be anywhere between three and twenty titles (or for some item types only one), and of course then there are usually multiple items of each title. Our shelving/numbering system (at least for this Item type) is to put all the books in order of reading difficulty level. I've created an alphanumeric local call number, which is the first part of the barcode that shows the level, then the set, then the titles, and then the copies. So Q010A04 means "the fourth copy of title A in set 010 in reading difficulty level Q". I've collected all my MARC records into text files by set. The file name for this set would be Q010.mrc, which would contain the MARC records for titles A, B, C, etc. I plan to import these one set file at a time, and if any MARC fields could be added to the records before importing to facilitate what I'm trying to do that would be relatively easy. I've done some initial reading of the MARC documentation and found some fields that seem designed to handle such relationships between separate titles (e.g. 440), but I only want to invest time in figuring out how to add them to my records if it will be useful within Koha after importing the MARC records. Some of the MARC records list multiple ISBNs reflecting some of this information, but they aren't complete, nor even consistent within a series! It is critical for people to see what related resources are available when they are browsing a given Reader in the OPAC, but some people want to just use the readers and ignore the rest, so I don't want to artificially create monolithic sets forcing people to borrow more than they need. As a separate but related issue, people placing orders to replenish our inventory should know which ISBNs to use for ordering - via set ISBNs rather than individually. Some ISBNs might be for six copies of one title within the series, others might be for one copy of each book in the series, another might be for six copies of each Reader plus one of each Big Book and take-home card plus one Teacher's Guide covering everything. And so on, with many permutations for each publisher. If necessary this information can be stored outside the system, but if it's possible for Koha to show these relationships that would be ideal. Even better would be for the budgeting and acquisitions modules to take advantage of such data. Regarding Koha's non-MARC database structure, I take it that Biblios are supposed to be exactly such "containers" for Biblioitems (e.g. the ISBN is an attribute of the Biblioitem, not the Biblio. However I'm not clear on how to use them as such in practice. My initial import will be for the Reader titles only, so I assume the Biblios thus created can function as the "master" record for subsidiary types where there is a simple relationship - ex a regular Reader has a corresponding Playscript, Bigbook or Take-home card. I also assume that I want to have separate Biblioitem records for each - in fact they are each separate Itemtypes, stored in different shelving locations. But what about when one Teacher's guide (or cassette/CD) covers all the books in a given set, or perhaps even a whole series comprising multiple sets (ex. at the Stage 1 level above)? When I import a new MARC record for such a "subsidiary" Biblioitem, how can I link it to the pre-existing "master" Biblio? They obviously won't have the same ISBNs. Is it possible to create "dummy Biblios" and then associate "real" ones as subsidiaries under them? If so, is it possible to have more than one level in the hierarchy? Phew! I really hope I'm making things more complicated than necessary, and there's a usual library management practice to handle this reflected in Koha and/or MARC information. I appreciate your even reading this far, much less actually attempting an answer <g> Hans

2 1

Re: [Koha] MARC Import (fwd)
by Pat Eyler 08 Jul '04

08 Jul '04

oops, should've sent this too the list -pate ---------- Forwarded message ---------- Date: Thu, 8 Jul 2004 14:40:33 -0400 (EDT) From: Pat Eyler <pate(a)eylerfamily.org> To: MJ Ray <mjr(a)dsl.pipex.com> Subject: Re: [Koha] MARC Import On Thu, 8 Jul 2004, MJ Ray wrote: > On 2004-07-08 18:27:15 +0100 "Bigwood, David" <bigwood(a)lpi.usra.edu> > wrote: > > > [...] MARC RTP is free and available in > > versions for Windows, Linux, and Solaris. > > Extra info: Cost-free but not free software. Also, it looks like no > source is available, so you probably need the same dll/so file > versions as the developers. Is it worth approaching the developers to encourage them to open their sources? -pate > > -- > MJR/slef My Opinion Only and not of any group I know > http://www.ttllp.co.uk/ for creative copyleft computing > "To be English is not to be baneful / To be standing by > the flag not feeling shameful / Racist or partial..." > (Morrissey) > _______________________________________________ > Koha mailing list > Koha(a)lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha >

1 0