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

Re: [Koha] New Questions- Strike the other 2
by Pat Eyler 21 Nov '02

21 Nov '02

Sky, I think you'll have better luck finding answers to questions like these on the development list. I've CC:ed your questions there. -pate On Thu, 21 Nov 2002, Sky King wrote: > Sorry, I answered my own 2 previous questions. Just had not searched > long enough earlier. > > Is there a way to change the classification to accept letters. The two > libraries I am testing this (koha) out for use the Library of Congress > Classification system and I need the Dewey Field which corresponds to > the Classification to be able to use the LC call number. > > Sky V. King > Adminstration/Library Intern > > _______________________________________________ > Koha mailing list > Koha(a)lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha >

1 0

call numbers
by robweir＠alum.drexel.edu 21 Nov '02

21 Nov '02

I submitted the following question to the general list, but received no response. Any chance someone on the development list would have a couple minutes to give me some guidance? Any help would be much appreciated! Thanks, Rob ----- Original Message ----- Date: Tue, 19 Nov 2002 13:37:11 -0500 X-Priority: 3 To: koha(a)lists.katipo.co.nz Subject: Data Conversion - Call Numbers I am converting data from an old system and need some help on which fields in Koha should be used to store the various components of the existing book call numbers. I'm a computer guy, not the librarian, so forgive me if my terminolgy is off. Given the following sample call number: R 220.7 J32c V.1 I am guessing that the first line 'R' for Refernce Book would be an itemtype defined in the itemtype table and then entered in the biblioitems.itemtype field for each book. The second line of course would be stored in biblioitems.dewey field. I'm stuck on the third line which I think is referred to as the Cutter number. Where should that be stored? I see a biblioitems.subclass field, but it is only char(3) which isn't long enough since cutter numbers are typicaly four characters. I think a few of the call numbers have a dewey line and two lines of cutter numbers. If there are two cutter lines, where should that second cutter line be stored? And then for the last line, would biblioitems.volumeddesc be the correct field? One more example call number from the old system: BIOG MORR H C.2 I can probably use biblioitems.itemtype for the first line. I'm stuck again on the second line. And I think the last line needs to be stored in the items table since it is specific to each copy of a book with multiple copies. But which field? I am hoping that once I get the data converted and everything stored in the proper fields, that a client who looks up a book using the OPAC interface will be able to see the entire call number for use in locating the book on the shelves. Will that be the case? Or are my librarians using a call number system that is incompatible with Koha? Thanks in advance for any help! Rob

2 1

code cleaning (2)
by paul POULAIN 21 Nov '02

21 Nov '02

Ok, I've deleted unused scripts (aka scripts claimed by nobody, and that are not mine ;-) ) I've deleted the "includes" directory in the koha-html part of koha : it includes only templates and .inc files that are also in koha/koha-tmpl/intranet. I've a some remaining questions... About koha-html : ============= * What is koha-html/intranet-html/opac done for ? isn't it old html ? (seems the same as koha-html/opac-html, which is the true opac html path) ? * is koha-html/opac-html/includes used somewhere ? Root koha directory : =============== In the root koha directory, there are some scripts that are for koha (addwebsite.pl, admin-home.pl)... and some that are for installation or command-line tasks (barcodes.pl, ChangeLog, fixBranches.pl, Hints, HOWTO-testing, INSTALL, install*, koha.mysql, koha.t, koha.upgrade, LICENSE, News, README, sampledata-1.2, testKoha, TODO if i don't mind). I think the code would be clearer if we put all of them in a specific directory. misc/ already contains some tools that are related to install, maintaining... So, I propose that all SCRIPTS not needed to run koha are moved to the misc directory. All the INFORMATIVE files (INSTALL, LICENSE,...) are moved in misc/info directory. (We could move the marc/ directory to misc/ too, as it's only db install stuff. Various questions : ============== * Is there a way to prevent deleted directories to remain in file system : some of them are present in koha and koha-html ? Questions/ideas/suggestions welcomed. -- Paul

2 2

Koha users page
by Pat Eyler 21 Nov '02

21 Nov '02

I've just set up a page on the wiki for recording libraries (public, private, whatever) that are using (or evaluating) Koha. Please tak a moment and sign yourselves up. Ideally, this can be a resource for getting Koha User Groups started, for pooling resources in developing projects for Koha, and for helping convince other libraries that Koha is in fact a reasonable choice. Oh, yeah -- here's the URL: http://www.saas.nsw.edu.au/wiki/index.php?page=KohaUsers thanks, -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

New configuration/install script
by Andrew Arensburger 20 Nov '02

20 Nov '02

As I mentioned on IRC a while back, I've been working on a new configuration/installation script for Koha. Now I've uploaded a first draft to the CVS main branch, to give people a look at it. Just run "safe-installer". This is nowhere near complete, but it should be enough for people to tell whether I'm on the right track or not, and whether I should continue. Currently, this script only installs and/or upgrades the Koha database. Some features of note: - The current 'installer.pl' asks a question, makes a change to the system, asks the next question, makest the next change, and so forth. 'safe-installer', on the other hand, asks all of the questions up front, and only then installs everything. This way, if you interrupt it before it's done, you don't wind up with a half-completed installation. - 'safe-installer' doesn't actually do anything itself. There's a Makefile to do the real work of creating the database, installing the web files, etc. This way, you don't have to be root to do the configuration. You might not even have to be root to do the installation. - 'safe-installer' works by creating a "Make.conf" file that contains the configuration values that will be used by 'make'. The advantage of this is that if someone wants to write a Koha RPM/port/apt/package/whatever, they can simply create "Make.conf" and use 'make install', thereby bypassing the interactive installer. - I've thrown in "install-sh", because Koha really ought to be portable, but not every OS has a BSD-compatible 'install' tool, nor does every OS support 'mkdir -p'. 'install-sh' does all of this, and is in the public domain, which should be GPL-compatible. A note in passing: one fairly interesting aspect of this script is that it involves a completely different type of optimization than I'm used to. Normally, when you're trying to estimate the speed of a program, you assume that all atomic operations (integer addition and multiplication, if-then, comparisons, etc.) all take the same amount of time. Here, however, an 'if' statement could take tens of seconds, if it involves getting input from the user. So the trick is to optimize for user time by asking as few questions as possible (in the average case, at least), while at the same time keeping them clear enough to give Joe Average User an idea of what's going on. -- Andrew Arensburger This message *does* represent the arensb(a)ooblick.com views of ooblick.com Build a better mousetrap and the world will immediately get their fingers caught in it.

4 3

[Bug 128] Failure to load MARC records gives no feedback
by bugzilla-daemon＠wilbur.katipo.co.nz 19 Nov '02

19 Nov '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=128 ------- Additional Comments From a.c.li(a)ieee.org 2002-11-20 09:41 ------- Oh, it is DBD::mysql::st execute failed: MySQL server has gone away at /usr/local/koha/intranet/cgi-bin/acqui.simple/marcimport.pl line 823, <fh00001EXPORT\.TXT> line 1. I guess it's a MySQL config problem, but Koha should still catch the error condition and produce some feedback, I think... ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 124] Issue due date
by bugzilla-daemon＠wilbur.katipo.co.nz 19 Nov '02

19 Nov '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=124 tonnesen(a)cmsd.bc.ca changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From tonnesen(a)cmsd.bc.ca 2002-11-19 07:49 ------- Discussion on the mailing list made this out as a feature instead of a bug, although a warning should be issued in case the due date is set in error to a date which is already passed. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

3 2

koha 1.3.2 => question before releasing
by paul POULAIN 18 Nov '02

18 Nov '02

Hi everybody, I plan to release a 1.3.2 version soon. what works in this version : * you can manage MARC biblios (add, modify...) and items * you can "link" a MARC subfield to any "old-DB" field : both db are managed in parallel, and if you modify a value in a MARC biblio, the corresponding value is modified in old-DB. * you can "link" a MARC subfield to 4 differents behaviours : - "free value" => whatever you want - "authorised value" => any value of a specified category. You can define as many categories as you want, and as many values as you want - "authority value" => any value in authority file. - "plug_in value" => the value is calculated through a "plugin" script. This possibility still needs documenting, but works nicely. So, i'm entering a "beta-test" phase now. It means i'm playing with koha, and tracking things i hadn't imagined... I encounter a "little problem" : some values, like, for example "biblioitem.itemtype" are mapped to a specific table. But if you don't use an "itemtypes" value in the MARC subfield "itemtype", koha goes woo-woo, as consistency is broken. My question is : can someone give me a complte list of such links. I'm speakins of links between biblio, biblioitems and items and other tables. What i already know : * no links in biblio * biblioitems.itemtype => itemtypes.itemtype * items.booksellerid => booksellerid * items.homebranch => ??? * items.holdingbranch => ??? Am i missing others ? Note : i'm working since nov,1st with a "french UNIMARC" version : works nicely, as nicely as the "english USMARC" one. I'm quite happy ;-) -- Paul

1 0

[Bug 126] MySQL password not quoted
by bugzilla-daemon＠wilbur.katipo.co.nz 18 Nov '02

18 Nov '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=126 tonnesen(a)cmsd.bc.ca changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From tonnesen(a)cmsd.bc.ca 2002-11-19 07:47 ------- Patch applied. Thanks. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 128] Failure to load MARC records gives no feedback
by bugzilla-daemon＠wilbur.katipo.co.nz 18 Nov '02

18 Nov '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=128 tonnesen(a)cmsd.bc.ca changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED OS/Version| |All ------- Additional Comments From tonnesen(a)cmsd.bc.ca 2002-11-19 07:45 ------- The Upload facility was not intended to handle bulk importing of MARC records. There is a command line tool (bulkmarcimport.pl) for importing large quantities of MARC records. Still, I'm not sure where this error is coming from. The uploadedmarc's marc field is defined as LONGBLOB which is capable of storing much more than 1.7MB. Is there any error in the apache error log files when you attempt to upload the file? ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0