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

[Bug 186] New: HTML tag appears in MARC structure
by bugzilla-daemon＠wilbur.katipo.co.nz 27 Jan '03

27 Jan '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=186 Summary: HTML tag appears in MARC structure Product: Koha Version: CVS Platform: All OS/Version: All 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 When I try to edit the structure of tag 852, I find that the 852$8 contains the describes "<ul>" ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

another question about the MARC editor
by acli＠ada.dhs.org via news-to-mail gateway 27 Jan '03

27 Jan '03

Hi, I have another user question for the MARC editor. I don't know if it is a bug or it is because I don't know how to use it correctly (or perhaps I have not done the setup correctly). After editing the MARC21 structure (with 2 remaining errors - branch and homebranch unmapped, but I think these are ok for my testing purposes), I tried to enter an item. I successfully got to the Items screen and entered an item. However, the item does not appear in the catalogue. Is this because I have not set up the MARC structure or links correctly? Thanks. -- Ambrose LI Cheuk-Wing <a.c.li(a)ieee.org>

2 1

[Bug 185] New: Barcode not auto-calculated when autobarcode is on
by bugzilla-daemon＠wilbur.katipo.co.nz 27 Jan '03

27 Jan '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=185 Summary: Barcode not auto-calculated when autobarcode is on Product: Koha Version: CVS Platform: All OS/Version: All 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 In the CVS, when autobarcode is 1, if we leaave the barcode blank when an item is entered, it remains blank; it is not auto-calculated. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

Re: Koha: MARCcataloguing problem (important)
by paul POULAIN 27 Jan '03

27 Jan '03

roberto sturman a écrit: > Hi Paul, > > Does version 1.3.3 of Koha allow to insert/edit repeatible subfields > as requested by the MARC standards? > > UNIMARC EXAMPLES: > > 1. example: tag 701, subfield b (repeatible subfield of a repeatible > field) > > $aIFLA$bGeneral Research Libraries division$bNational Libraries Section It's possible with 1.3.3 : just enter General Research Libraries division | National Libraries Section (with a | as separator) in the $b subfield. > 2. example, tag 200 (the field is not repeatible, but its subfields > are so and no subfield order is set!!!) > > $aFirst title of publication$efirst title, first subtitle$efirst > title, second subtitle$aSecond title$esecond title subtitle > > (BASED ON INVENTED BOOK: The theory of relativity: the original text > published by Einstein: a commentary; Einstein's thoughts about the > use of nuclear energy: an essay) > I can't find any way to insert the repeatible subfields in the forms. This one is a true nightmare ! In fact, at the moment, you can't enter such a schema. The only way to do this it to "reorder" fields and use the | separator. In a future version, we could add a way to "duplicate" a field in the GUI. Note it's most a GUI problem than a DB one. The db should manage it without problems. Hope this Helps -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

[Bug 184] New: Branch codes canonicalized differently in Koha than in installer
by bugzilla-daemon＠wilbur.katipo.co.nz 27 Jan '03

27 Jan '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=184 Summary: Branch codes canonicalized differently in Koha than in installer 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 In the installer, branch codes get changed to uppercase, plus being restricted to a small set of characters. If, however, the administrator adds a branch via the Koha interface (admin/branches.pl), any string of 4-character symbols are accepted as a valid code, and the codes do not get changed to uppercase either. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 160] New book funds don't show up in list unless they have a budget
by bugzilla-daemon＠wilbur.katipo.co.nz 27 Jan '03

27 Jan '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=160 a.c.li(a)ieee.org changed: What |Removed |Added ---------------------------------------------------------------------------- OS/Version|other |All Platform|PC |All Version|1.2.3 |unspecified ------- Additional Comments From a.c.li(a)ieee.org 2003-01-27 22:10 ------- In the CVS version, book funds don't show up in the list *even if* there is a budget for them. Incidentally, the budgets don't appear in the list either. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 183] Invalid URL while trying to define local MARC structure
by bugzilla-daemon＠wilbur.katipo.co.nz 27 Jan '03

27 Jan '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=183 a.c.li(a)ieee.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From a.c.li(a)ieee.org 2003-01-27 21:16 ------- Replaced the "put" method with the "post" method. The changed template seems to work correctly. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 183] New: Invalid URL while trying to define local MARC structure
by bugzilla-daemon＠wilbur.katipo.co.nz 27 Jan '03

27 Jan '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=183 Summary: Invalid URL while trying to define local MARC structure 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 While trying to put tag 700 into tab 1 for testing, the Squid proxy reported "Invalid URL". After a few glances it seems that the URL is "invalid" because it is too long. Perhaps the solution is to use POST instead of GET for the form. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 179] Install.pm should not check for Perl 5.6.0
by bugzilla-daemon＠wilbur.katipo.co.nz 26 Jan '03

26 Jan '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=179 a.c.li(a)ieee.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Additional Comments From a.c.li(a)ieee.org 2003-01-27 12:14 ------- marcimport.pl uses MARC::Charset, which requires Perl 5.8.0. Should we check for 5.8.0 instead? Red Hat 7.x has only Perl 5.6.x, and installing 5.8.0 will require recompiling all the Perl modules. Should we just put aside marcimport.pl for the time being, or should we just force everyone to upgrade their Perl? ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 179] Install.pm should not check for Perl 5.6.0
by bugzilla-daemon＠wilbur.katipo.co.nz 26 Jan '03

26 Jan '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=179 a.c.li(a)ieee.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From a.c.li(a)ieee.org 2003-01-27 05:19 ------- Fixed in Install.pm ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0