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

[Bug 151] "Next Borrower" button results in Internal Server Error
by bugzilla-daemon＠wilbur.katipo.co.nz 09 Dec '02

09 Dec '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=151 tonnesen(a)cmsd.bc.ca changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From tonnesen(a)cmsd.bc.ca 2002-12-10 11:22 ------- Missing =cut line to close POD documentation before the remoteprint subroutine ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 151] New: "Next Borrower" button results in Internal Server Error
by bugzilla-daemon＠wilbur.katipo.co.nz 09 Dec '02

09 Dec '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=151 Summary: "Next Borrower" button results in Internal Server Error Product: Koha Version: 1.2.3 Platform: PC OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Circulation AssignedTo: chris(a)katipo.co.nz ReportedBy: tonnesen(a)cmsd.bc.ca QAContact: koha-devel(a)lists.sourceforge.net error log reports: Undefined subroutine &C4::Print::remoteprint called at /usr/local/koha/intranet/cgi-bin/circ/circulation.pl line 690 The remoteprint subroutine is in the Print.pm module, so I'm not sure what is going on here, exactly. It was verified three times in three separate installs. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 150] New: "Next Borrower" button results in Internal Server Error
by bugzilla-daemon＠wilbur.katipo.co.nz 09 Dec '02

09 Dec '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=150 Summary: "Next Borrower" button results in Internal Server Error Product: Koha Version: 1.2.3 Platform: PC OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Circulation AssignedTo: chris(a)katipo.co.nz ReportedBy: tonnesen(a)cmsd.bc.ca QAContact: koha-devel(a)lists.sourceforge.net ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

problem with mandatory subfields
by Ambrose Li [CCCGT] 09 Dec '02

09 Dec '02

Hi, I discovered one problem while I am trying to enter one record from our OPAC. Right now, 100c is mandatory. This is not correct. (See the examples at http://lcweb.loc.gov/marc/bibliographic/ecbdmain.html; I think 100a is mandatory, not 100c.) But assuming that 100c really is mandatory, it would really only mean that one of 100c, 110c or 111c is mandatory, since any of 100, 110, or 111 can be the main entry. Is it currently possible to specify that one of several subfields is mandatory? Or is this something that cannot yet be specified? -- Ambrose Li Chinese Cultural Centre of Greater Toronto | http://www.cccgt.org/

3 2

some more thoughts on marc linkage of call number...
by Ambrose Li [CCCGT] 09 Dec '02

09 Dec '02

Hi, I am thinking of the "093" field we use here. It has the following structure (as far as I understand): a LC classification number c Cutter number y Year of publication - can be null (if a+c already uniquely identifies a book) - if not null, can be followed by a letter (a, b, c, etc.) if a+c+year cannot uniquely identify a book v Volume number (V.1, V.2, etc.) or other things like INDEXES, MANUAL, etc. What if there is a feature where we can map more than one subfield (e.g., c+y+v here) to one Koha field (e.g., biblioitems.subclass)? Would this make any sense? -- Ambrose Li Chinese Cultural Centre of Greater Toronto | http://www.cccgt.org/

2 1

meaning of mandatory subfields
by Ambrose Li [CCCGT] 09 Dec '02

09 Dec '02

Hello, regarding the issue of mandatory subfields. What does it mean that a certain subfield is mandatory? For example take ISBN. 020a is currently marked as mandatory. does it mean that (1) a is mandatory in the 020 field, or (2) 020 is mandatory in addition to a being mandatory in 020? Should we allow "not mandatory" fields that contain "mandatory" subfileds within those "not mandatory" fields? Or am I not knowing what I'm talking about (which could very much be true)? -- Ambrose Li Chinese Cultural Centre of Greater Toronto | http://www.cccgt.org/

2 1

installer
by Tonnesen Steve 09 Dec '02

09 Dec '02

I'm not sure what to do about the installer in 1.3. The version in rel-1-2 has had a significant number of improvements, but there have also been a few changes made in 1.3. I was hoping that the safe installer would get done for 1.3, and this might still be the way to go. At the moment, though, it sounds like people are having problems with the existing installer, and it might be a good idea to move the installer from 1.2 over to 1.3 for now. Any opinions on this? It doesn't look like a lot of changes have been made to the installer in 1.3, but Paul would know best. MARC parameter selection looks like the only added feature? Steve.

2 1

library codes, installer.pl in CVS
by Ambrose Li 09 Dec '02

09 Dec '02

Hi, I am working on fixing the installer.pl. I know the problems will be fixed when the 1.2.x installer is "forward-ported" to 1.3 and/or when templating is done etc. But I don't think these will be finished very soon. In the meantime IMHO the installer should at least work in case someone wants to try 1.3.x (and perhaps help to write some code). While I am working on fixing installer.pl, I came across something I don't understand. When I am asked to create a 4-letter code for the library, it really wants a 4-letter code, and will delete any non-letters. I didn't know and entered a numeric code, and got an empty library code added to the database. Is this correct behaviour? (Reason for asking: If this is correct behaviour then the installer should double-check the library code in case it becomes empty or just one letter, etc.; if this is not correct the regexp in substitution should be corrected.) -- Ambrose Li <a.c.li(a)ieee.org> http://ada.dhs.org/~acli/cmcc/ http://www.cccgt.org/ DRM is theft - We are the stakeholders

3 2

profiling Koha
by Pat Eyler 09 Dec '02

09 Dec '02

The newest release of the DBI module includes several DBI profiling tools: DBI::Profile, DBI::ProfileDumper, and dbiprof especially. As Paul (and everyone else who's now happily working on 1.3 stuff, right?) march towards a 2.0 release, it might make sense to start playing with these tools so that we can do a round or two of profiling and tuning before we release 2.0.0. Chris, does it make sense to look at this for the 1.2 series as well? While 2.0 should be out within the next ~60 days, I'm guessing that 1.2 will remain in production for a while. -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

3 2

Re: [Koha-devel] full text search
by paul POULAIN 09 Dec '02

09 Dec '02

Larry Currie a écrit: >Hi Paul, > >Full text searching in Koha would definitely be a big plus. > >Larry Currie >California Academy of Sciences > > Here is one other opinion. Everybody agrees on the interest of this feature. I'm not suprised :-) But the question is : if the cost is to become db-dependant, is it affordable ? It seems ppl here think it is, for instance. So if ppl want to tell us why they think it should not be done, please explain here. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIBGB libre http://fr.koha.org)

1 0