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

Hi
by Simon deWeerdt 05 Dec '02

05 Dec '02

Hi Guys Koha newbie introduced by Pat Eyler. I see you develop in Perl. May try out your product and then see about pitching in. -- Simon deWeerdt Onside Projects Ltd. http://www.onside.net/

1 0

[Bug 138] installer.pl does not check the validity of user's choice of library code
by bugzilla-daemon＠wilbur.katipo.co.nz 04 Dec '02

04 Dec '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=138 ------- Additional Comments From a.c.li(a)ieee.org 2002-12-05 18:41 ------- Created an attachment (id=16) Revised proposed patch (only difference is fixing a bug in "includes" setup in koha.conf) ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

Re: [Koha-devel] tandom thought
by Pat Eyler 04 Dec '02

04 Dec '02

Right now, I'm shooting for something like this (note, raw data): CVS submitters: 4 finlayt 8 tipaul 48 tonnesen 72 fmmarzoa Hottest files: 1 koha/koha-tmpl/intranet-tmpl/default/es/reports/reports-home.tmpl 1 koha/koha-tmpl/intranet-tmpl/default/es/user/userpage.tmpl 2 koha-doc/de/test.txt 2 koha-doc/de/test2.txt 4 koha/C4/Auth.pm Each line in the list of files should probably be annotated (and selected from a larger list of the top 20, so that only meaningful files are selected). Each column should also be annotated. Given the paucity of files with multiple commits, maybe I should make the report a monthly feature instead. November's main branch report would look like: committers: # commits committer 1 rangi 6 hdl 10 lavide 12 dragon28 24 fmmarzoa 28 tonnesen 241 finlayt 291 tipaul hot files: # commits file 4 koha/misc/buildrelease 4 koha/misc/installer.pl 5 koha/koha-tmpl/opac-tmpl/hlt/en/loggedin.tmpl 5 koha/koha-tmpl/opac-tmpl/hlt/en/opac-userdetails.tmpl 5 koha/koha-tmpl/opac-tmpl/hlt/en/includes/main.css 5 koha/opac/opac-user.pl 6 koha/C4/Search.pm 7 koha/koha-tmpl/opac-tmpl/hlt/en/opac-auth.tmpl 8 koha/updater/updatedatabase 9 koha/koha-tmpl/opac-tmpl/hlt/en/opac-user.tmpl (I'd still need to add some explanations" thoughts? -pate On Wed, 4 Dec 2002, Nicholas S. Rosasco wrote: > I'd say a summary of the meaning of the commits (ie, X number went into feature > or bug Y) might be more useful to those who watch it for updates on where we > are. > > Just a shot in the dark, > Nick > > > Quoting Pat Eyler <pate(a)eylerfamily.org>: > > > I'm thinking about adding a cvs history summary into the newsletter ... > > maybe # of commits by developer by branch, and/or the 5 (or 10) most > > committed files ... any thoughts? > > > > -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 > > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: Microsoft Visual Studio.NET > > comprehensive development tool, built to increase your > > productivity. Try a free online hosted session at: > > http://ads.sourceforge.net/cgi-bin/redirect.pl?micr0003en > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel(a)lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/koha-devel > > > > > > >

1 0

[Bug 141] "System parameters" page calls itself "Koha admin page"
by bugzilla-daemon＠wilbur.katipo.co.nz 04 Dec '02

04 Dec '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=141 a.c.li(a)ieee.org changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Page footer refers to admin |"System parameters" page |page as "system parameters" |calls itself "Koha admin | |page" ------- Additional Comments From a.c.li(a)ieee.org 2002-12-05 16:09 ------- Should we change the heading to "System parameters"? ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 144] New: Missing mandatory subfields not correctly highlighted
by bugzilla-daemon＠wilbur.katipo.co.nz 04 Dec '02

04 Dec '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=144 Summary: Missing mandatory subfields not correctly highlighted Product: Koha Version: CVS Platform: PC Status: NEW Severity: normal Priority: P2 Component: Acquisitions (Simple) AssignedTo: tonnesen(a)cmsd.bc.ca ReportedBy: a.c.li(a)ieee.org QAContact: koha-devel(a)lists.sourceforge.net Suppose I enter a biblio record and is missing 3 mandatory subfields. I enter one and press Items>>. Koha now tells me that I am missing 2 mandatory subfields, but the one that I filled in is still highlighted in red. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 143] New: Deletion of subfield gives wrong feedback
by bugzilla-daemon＠wilbur.katipo.co.nz 04 Dec '02

04 Dec '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=143 Summary: Deletion of subfield gives wrong feedback Product: Koha Version: CVS Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Parameters AssignedTo: tonnesen(a)cmsd.bc.ca ReportedBy: a.c.li(a)ieee.org QAContact: koha-devel(a)lists.sourceforge.net If I try to delete a subfield, Koha asks whether I am confirming to delete *another* subfield, even though it will really delete the subfield I ask it to delete (instead of the one it asks me to confirm). Scenario: I use Add New to add a "093" field (uses in my library to mean "local call number", LC-style). Added subfield a "LC Call Number" linked to biblioitems.dewey. Added subfield c "Cutter Number" linked to biblioitems.subclass. I then suspected that c might be defined incorrectly so I press the Delete on the right of subfield c. Koha asks me Subfield LC Class Number CONFIRM DELETION If I press Yes, subfield c (Cutter Number) is deleted as I intended, even though Koha asks me to confirm deletion of LC Class Number (subfield a). ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 134] Cannot add MARC subfield
by bugzilla-daemon＠wilbur.katipo.co.nz 04 Dec '02

04 Dec '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=134 ------- Additional Comments From a.c.li(a)ieee.org 2002-12-05 06:08 ------- Yes, the patch to updatedatabase is already uploaded. Please commit to CVS after double-checking. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 134] Cannot add MARC subfield
by bugzilla-daemon＠wilbur.katipo.co.nz 04 Dec '02

04 Dec '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=134 ------- Additional Comments From d.strainchamps(a)wanadoo.fr 2002-12-05 05:57 ------- I think that's updatedatabase that we have to change ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 134] Cannot add MARC subfield
by bugzilla-daemon＠wilbur.katipo.co.nz 04 Dec '02

04 Dec '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=134 a.c.li(a)ieee.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEW Component|Parameters |Installation ------- Additional Comments From a.c.li(a)ieee.org 2002-12-05 05:53 ------- The value_builder field does not seem to be in scripts/marc/marcschema.sql, which I assume is left as documentation. Should marcschema.sql be updated as well? ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 134] Cannot add MARC subfield
by bugzilla-daemon＠wilbur.katipo.co.nz 04 Dec '02

04 Dec '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=134 ------- Additional Comments From a.c.li(a)ieee.org 2002-12-05 05:50 ------- Created an attachment (id=15) Proposed patch to resolve the problem, by changing the db structure ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0