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

a couple of new projects
by Pat Eyler 28 Aug '02

28 Aug '02

Nelsonville Public Library is interested in seeing some functionality added to Koha. While they'll be announcing this themselves fairly soon, I wanted to prime the pump a bit and let people start thinking about how we could go about doing them, and what impact they might have on Koha. 1) full MARC support ... this is already on the table for the 1.4 series. I'm not sure how much we need to talk about it, but I'll toss this ball over to Paul. 2) a Z39.50 server ... we've got a client, and Steve tracked down an Z39.50 server module so the biggest bit of work would be integrating it into Koha and searching our database. 3) NCIP ... this is the hardest of the batch (I think). having NCIP would really put us into a sweet position. Interoperability with other ILSes and with things like Self Service Checkout Terminals become possible. What think ye? -pate

2 4

french space on the wiki ?
by paul POULAIN 28 Aug '02

28 Aug '02

Did someone disagree with a space in french on the wiki ? It would be use for translation purposes, and "french team" coordination. If no one disagree, it will be opened very soon. -- Paul

2 1

Spaces in search parameters
by Daniel Holth 27 Aug '02

27 Aug '02

Kohaites, It's my bug so here's my solution: I have edited search.pl to read like this: ($keyword) && (push @$forminputs, { line => "keyword=$keyword", name => "keyword", value => "$keyword"} And it goes. Each parameter in the form has a name and value, instead of being lumped together in one string. Now, the search results template is modified to look something like this but without whitespace: <a href=search.pl?startfrom=<TMPL_VAR NAME="prevstartfrom">&<TMPL_LOOP NAME=FORMINPUTS> <TMPL_VAR NAME=name>=<TMPL_VAR NAME=value ESCAPE=URL>  &</TMPL_LOOP>type=<TMPL_IF NAME="opac">opac<TMPL_ELSE>intra</TMPL_IF>>Previous Records</a> And the nice HTML::Template module URL-escapes the value of the variable. At first I tried just URLescaping the whole thing (line) but that turns the equals sign into a percent-code. I have not yet succeeded in replacing all the necessary pieces of search-results.tmpl but I can now browse my whole collection by searching for a ' ' (space). - Daniel Holth

2 1

Re: [Koha-translate] finding a home for translated docs
by Md. Aftabuddin 27 Aug '02

27 Aug '02

On Mon, 26 Aug 2002, Pat Eyler wrote: > Chris and I briefly chatted about this on irc, and he came to the > brilliant conclusion that we should put them in docs/<language name/ -- > any thoughts? > > -pate Do it now !!!!!! Md. Aftabuddin

1 0

koha@de.koha.org
by Pat Eyler 26 Aug '02

26 Aug '02

Guten Tag, I've started a mailing list for german language discussion of german installation discussions of Koha. you can subscribe by sending an email to <koha-subscribe(a)de.koha.org> and following the instructions that are returned. As things progress to the point that a german website for koha is needed (or wanted) we can get that running as well. danke, -pate

1 0

finding a home for translated docs
by Pat Eyler 26 Aug '02

26 Aug '02

Chris and I briefly chatted about this on irc, and he came to the brilliant conclusion that we should put them in docs/<language name/ -- any thoughts? -pate

1 0

branch tables in koha database
by finlay＠katipo.co.nz 26 Aug '02

26 Aug '02

Hey, I have been thinking about the branch settup in koha, and although it seems like a rash thing to do, I think a total redesign of the database branch settings is in order. At present: Each item has a "holdingbranch" field and a "currentbranch" field. Both of these store a branchcode that is the primary key into the branches table. However it turns out that this branches table stores data on two completely different conceptual things: 1) holdingbranch really refers to a collection of items. This is sometimes an actual physical location, and sometimes not. The holdingbranch setting does not (usually) change. 2) currentbranch refers to the actual current location of an item. This setting changes frequently. In the course of doing some branch transfers work I ended up setting up a complicated system of labeling the various entries in the branches table according to what really do: issuing or not, permanant collection, holding branch or currentbranch, etc. This has gotten to be a little bit complicated. And in particular now the HLT have identified a bug http://bugzilla.katipo.co.nz/show_bug.cgi?id=1390 the solution of which is really not nice in the current setting, even though it is a perfectly reasonable idea. I propose: To replace the existing branch tables (branches, branchcategories, branchrelations) with two tables: branches and collections. This does entail the rewriting existing code. However because I wrote most of that code I dont think it will be too difficult :-) Although this seems like a drastic measure given the simplicity of the bug in question, I think that it will be better for koha. Finlay

3 3

testing of 1.2.3RC9
by Tonnesen Steve 26 Aug '02

26 Aug '02

I've found a few bugs in 1.2.3RC9, mostly in the circulation interface. It looks to me like this needs some more testing... I've uploaded an RC10 to sourceforge that fixes the show stopper bugs that I found... but if anybody wants to give this one a look, I think it needs it. Steve.

2 3

1.2.3RC11
by Tonnesen Steve 26 Aug '02

26 Aug '02

Fixed up a couple of reported bugs in RC10 and put out RC11. I guarantee there are still more. Reporting bugs via: http://bugs.koha.org/ is appreciated. Steve Tonnesen.

1 0

Re: [Koha] Problem with koha-1.2.3RC10
by Dr. Ralf Allrutz 26 Aug '02

26 Aug '02

Hi Steve, thanks for your mail, in the meanwhile I found the reason and fixed it, seemed to be a formatting problem in koha/intranet/htdocs/includes/templates/default/catalogue/detail-opac.cdiff in line 67. After concatenating three lines, the title links do work. Please see attached context diff. Presumably I should post it to koha-devel? Best regards, Ralf On Sun, 25 Aug 2002, Tonnesen Steve wrote: > > I will reply to this message when I get back to work in the morning, if > nobody has responded to you by then... > > Steve Tonnesen -- f y cn rd ths y mst hv bn sng nx

1 0