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

Koha 2.2.0 (officially stable) is for tomorrow morning...
by Paul POULAIN 11 Feb '05

11 Feb '05

Unless otherwise stated, Koha 2.2.0 will be release tomorrow morning. I've tested installer, upgrade from Koha 2.0.2, both works fine. I've no news from es_AR and zh_TW translations, so the 2.2.0 will be released with french and english only. The 2.2.1 will be released when more translations will be OK. Nelsonville : is the NPL template fully functionnal in CVS ? Can I mention it in the release notes ? It's dinner time for me. No champagne, but a virtual bottle for tomorow morning (Maybe we could organize a virtual drink at, say, 2000GMT) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

3 2

Dewey still a double?
by Andrés Tarallo 06 Feb '05

06 Feb '05

Where reading our isntallation to put it on production. Today we were trying to understand some behaviour on koha, so we went to read source code and the database structure. We noticed that the dewey in the biblioitem table still is a double, we thought that this was changed a few month ago, since it doesn't have sence (at least for us). Andres

3 2

Requested feature (biblio title order)
by Paul POULAIN 03 Feb '05

03 Feb '05

Hi, In 2.2, when you order a search by title, stopwords at the beginning are still used in the ordering. "A simple software" will be ordered before "The last minute". In France (& I think in other countries it's the same), we are supposed to have "A" and "The" ignored at the beginning of the title having "(A) simple software" after "(the) last minute". To add this feature in Koha we could : * add a field in biblio.title. Call it biblio.titlenostopword (anybody a suggestion for a better name ;-) ?) * in Biblio.pm, in OLDnewbiblio / OLDmodbiblio => put the title with stopwords removed in this new field * don't order on biblio.title but on the new field. Quite simple to do, a day of work not more. Do we think it's an important feature that could be in 2.2.x or not ? I vote yes. the risk of unstability is really low, for a nice feature. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

3 6

re: Add biblio bug
by Harvey Lee 03 Feb '05

03 Feb '05

Hi Greg, There is a simple fix for this. The problem is in the template addbiblio.tmpl. In the lines that call the javascript function AddField(), change from: href="javascript:AddField()" to: href="javascript:AddField("")" I'm doing this from memory so I hope the placement of the quotes above is correct! This code needs to be fixed in 10 places (once per tab). What seems to be happening is that the tag value is being sent to the javascript function as an integer so leading zeros (as in the ISBN tag) are being stripped. Lee In addbiblio.pl.... I click on the + sign to add a seccond ISBN number for a biblio entry. Instead of adding a seccond ISBN field, it adds a new LCCN field. This bug has existed in earlier versions of KOHA as well, but I never got around to reporting it. To ensure the problem is not in my database, I did a clean insteall, and found this happened whilst adding my first biblio entry. Greg

2 1

MARC tags/subfields downloaded v/s displayed
by Harvey Lee 03 Feb '05

03 Feb '05

Hi all, I've got a question concerning the downloaded MARC tags/subfields from Z3950. If a certain MARC tag/subfield is present in the Z3950 downloaded record, but I choose not to display this tag/subfield in the MARC view (i.e., tab = - 1 or 'ignored'), is the tag/subfield supposed to be stored in marc_subfield_table? Maybe I misinterpreted what I read a while back, but I thought ALL of the MARC data was stored even though it may not be displayed. I'm finding that only those tag/subfields that are visible on download are stored. But AFTER the downloaded biblio is saved into the catalogue, I can then show/hide the subset of subfields that actually made it into the marc_subfield_table. I'm running Koha2.0.0. Is this design intent or is this a bug that there is a fix for already? Can anyone comment? Thanks, Lee

2 1

Subject maintenance?
by Rachel Hamilton-Williams 03 Feb '05

03 Feb '05

Hi ya, I'm just checking, but I'm having trouble working out where/how/if you do subject maintenance in 2.2? I've added some subjects to a biblio (using the edit biblio stuff in the MARC View) and so I see I could go and just edit all the subjects per biblio by hand - but that seems like a bit of a leap backwards. In 1.3 we had (well I think we did, HLT certainly do), the ability to get up a list of subjects, and then edit them, delete duplicates etc, and have it work for all the biblios. Is that functionalty in this version (and I'm just blind/using the wrong templates) OR is it not in this version (in which case I'll stop looking) Cheers R

2 1

Design Dilemas
by Rachel Hamilton-Williams 03 Feb '05

03 Feb '05

Hi guys, I've got a dilema, that I need some help resolving I think. As you know I've been doing some new concepts for the koha templates, and have (as per usual) inadvertantly done some things that I think involve more than just changing the CSS. Specifically, * on the opac homepage making the language options *not* a drop but instead clickable links * generally re-arranging the "order" things I've also added in some new functionality, but I'm happy to let that go :-) SO my question is a ground level "how do the templates work" If I think there are things "wrong" with the CSS templates, that can't be fixed in styles, what should I do? If I get changes made to the CSS template, what will break? Over the last couple of years there have been some specific aspects of the layout of the pages that clients have consistently wanted changed, and while we did make a version of templates that addressed those issues for 2.0, of course they don't work now with 2.2. There are some issues, which are essentially one of colour, font, size, etc and they are easily addressed. But other issues - where essentially I think something is in the "wrong place" or the "wrong sort of interface" - ie links not drop downs and vice versa - what should I do. I can get it coded into "katipo" templates, but as I understand it, unless Paul you adopt those changes to your templates, when we upgrade, it may all fall appart? Should I "bug" architecture issues with particular pages, and perhaps supply the soloutions? OR is everyone else basically happy with how they are? Help :-) cheers R

2 1

Reports patches
by Ernesto Silva - Webmaster 03 Feb '05

03 Feb '05

Paul, We are using apache2 and some of the paths (require directives) doesn't work. I've discovered a posible "bug" in intranet/cgi-bin/reports/manager.pl and this may be a patch. --- /usr/local/koha2/intranet/cgi-bin/reports/manager.pl 2005-01-19 10:09:02.315406544 -0300 +++ manager.pl 2005-01-25 16:21:29.159390944 -0300 @@ -41,7 +41,7 @@ }); $template->param(do_it => $do_it, report_name => $report_name); -my $plugin = "./".$report_name.".plugin"; +my $plugin = C4::Context->config('intranetdir')."/cgi-bin/reports/".$report_name.".plugin"; require $plugin; if ($do_it) { my $results = calculate(\@values); Regards Ernesto.

2 1

Add biblio bug
by Greg Kuhnert 03 Feb '05

03 Feb '05

In addbiblio.pl.... I click on the + sign to add a seccond ISBN number for a biblio entry. Instead of adding a seccond ISBN field, it adds a new LCCN field. This bug has existed in earlier versions of KOHA as well, but I never got around to reporting it. To ensure the problem is not in my database, I did a clean insteall, and found this happened whilst adding my first biblio entry. Greg

2 1

bar code not unique
by T & J Kotula 03 Feb '05

03 Feb '05

Hi, I remember reading on the list lately about the bar code not having to be unique. Well I would like to enforce it to be unique. I'm not a perl programmer, but I had a look in acqui.simple/additem.pl and I'm puzzled by the comment on line 81 saying "check for bar code # being unique". Could someone tell me what I need to do to make it verify the number being unique. Many thanks. tomasz kotula.

2 1