April 2013 - Koha-bugs - lists.koha-community.org

[Bug 9892] New: export_borrowers.pl cannot handle tab-separated output
by bugzilla-daemon＠bugs.koha-community.org 19 May '15

19 May '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9892 Bug ID: 9892 Summary: export_borrowers.pl cannot handle tab-separated output Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Command-line Utilities Assignee: gmcharlt(a)gmail.com Reporter: jcamins(a)cpbibliography.com misc/export_borrowers.pl allows the user to specify a separator character, but there is no way to specify a tab. -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 10011] New: Branch limitiations are not saved on creating a new patron category
by bugzilla-daemon＠bugs.koha-community.org 19 May '15

19 May '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10011 Bug ID: 10011 Summary: Branch limitiations are not saved on creating a new patron category Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de CC: gmcharlt(a)gmail.com When creating a new patron category the branch limitations are not saved. When you edit a created patron category the limitations are saved correctly. To test: 1) Create a new patron category 2) Pick one or more libraries to limit to 3) Save and verify that the table of patron categories doesn't show your selected limitations. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 7107] New: 'used in' column on analytics not populating
by bugzilla-daemon＠bugs.koha-community.org 18 May '15

18 May '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7107 Bug #: 7107 Summary: 'used in' column on analytics not populating Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: major Priority: P5 Component: Cataloging AssignedTo: gmcharlt(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org CC: ian.walls(a)bywatersolutions.com I have added records two ways. The first: Catalog a record using fast add Click edit and choose to link to host Enter host Barcode and click okay Reindex search engine Look at host record Click Analytics tab on left Nothing in used in column The other way was to use the default framework when cataloging, but following all the same steps. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug.

1 13

[Bug 8399] New: Problems with mandatory field alert message for authorities
by bugzilla-daemon＠bugs.koha-community.org 18 May '15

18 May '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8399 Priority: P5 - low Change sponsored?: --- Bug ID: 8399 CC: jcamins(a)cpbibliography.com Assignee: gmcharlt(a)gmail.com Summary: Problems with mandatory field alert message for authorities Severity: normal Classification: Unclassified OS: All Reporter: katrin.fischer(a)bsz-bw.de Hardware: All Status: NEW Version: master Component: MARC Authority data support Product: Koha Created attachment 10725 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=10725&action=edit screenshot When creating a new authority (example: PERS_NAME) and only entering 100$a, on saving the record an alert will show the missing mandatory fields. In the alert the descriptions of the messages are cut off and the tab number is missing (see screenshot). -- You are receiving this mail because: You are watching all bug changes.

1 21

[Bug 8480] New: auth_subfield_structure is not cleared when deleting an authority type
by bugzilla-daemon＠bugs.koha-community.org 18 May '15

18 May '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8480 Priority: P5 - low Change sponsored?: --- Bug ID: 8480 CC: gmcharlt(a)gmail.com Assignee: koha-bugs(a)lists.koha-community.org Summary: auth_subfield_structure is not cleared when deleting an authority type Severity: normal Classification: Unclassified OS: All Reporter: gaetan.boisson(a)biblibre.com Hardware: All Status: NEW Version: master Component: Staff Client Product: Koha To reproduce : - in authtypes.pl create a new authority type - have a look at it's MARC structure and fill it with the default type for instance - delete it - in the database the auth_subfield_structure table was not properly cleared : auth_type and auth_tag_structure were properly cleared but all the subfields for the test authority type are still there. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 9987] New: biblioitemnumber is useless for orders.
by bugzilla-daemon＠bugs.koha-community.org 18 May '15

18 May '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9987 Bug ID: 9987 Summary: biblioitemnumber is useless for orders. Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)biblibre.com The DB field aqorders.biblioitemnumber seems to be unused and useless. It should be removed. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 7806] New: Illegal dates are used to signal non existing dates.
by bugzilla-daemon＠bugs.koha-community.org 18 May '15

18 May '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7806 Priority: P5 - low Change sponsored?: --- Bug ID: 7806 Assignee: gmcharlt(a)gmail.com Summary: Illegal dates are used to signal non existing dates. QA Contact: koha.sekjal(a)gmail.com Severity: major Classification: Unclassified OS: All Reporter: marc(a)msys.ch Hardware: All Status: NEW Version: unspecified Component: Database Product: Koha The illegal date '0000-00-00' is being used in Koha to signal a non-existing date. MySQL allows for such illegal dates. A database like PostgreSQL, which is much more strict when it comes to correct data, does not allow illegal values as date values. If a date is inexistant/invalid etc. an SQL NULL must be used instead. -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 8962] New: Create a new index for OPAC simple search, more specific than "any"
by bugzilla-daemon＠bugs.koha-community.org 18 May '15

18 May '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8962 Priority: P5 - low Change sponsored?: --- Bug ID: 8962 Assignee: gmcharlt(a)gmail.com Summary: Create a new index for OPAC simple search, more specific than "any" Severity: enhancement Classification: Unclassified OS: All Reporter: mathieu.saby(a)univ-rennes2.fr Hardware: All Status: NEW Version: unspecified Component: Searching Product: Koha In the current record.abs, the index "any" is defined as "all any". So, all the fields indexed in other indexes are also indexed in "any". So, for example, in my unimarc catalogue, if I search for "fre" in the opac, I get 342825 results, because it is the code for french language in 101a field, index in "ln". Idem if I search for "lc" or "rameau" (equivalent to LCSH in France), or "texte" And with fuzzy or autotruncate activated, it is, very very annoying. My idea is : - to keep the "all any" - to create a more specific index, matching only important field, but in any event NOT matching coded fields and some boring notes... - use this index in opac simple search (and maybe in staff interface simple search but this could be discussed...) Todo : - check bib1.att & ccl.properties to see if some index not used in Koha today could be used. If nothing usable, create completely new index. - edit record.abs for unimarc, marc21 and normarc biblios - edit DOM config files for unimarc, marc21 and normarc biblios - check if it is necessary to edit zebra config files for authorities - edit the templates - maybe edit some perl files Mathieu Saby Rennes 2 University -- You are receiving this mail because: You are watching all bug changes.

1 68

[Bug 9139] New: Sending empty vendor or biblio when adding subscriptions gives error
by bugzilla-daemon＠bugs.koha-community.org 18 May '15

18 May '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9139 Bug ID: 9139 Summary: Sending empty vendor or biblio when adding subscriptions gives error Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All URL: /cgi-bin/koha/serials/subscription-add.pl OS: All Status: NEW Severity: normal Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de CC: colin.campbell(a)ptfs-europe.com I can only reproduce this in Firefox, not in Chromium. To reproduce: - Add a new subscription - Put cursor in first field for 'Vendor' or 'Biblio' and hit enter - Perl error page is shown: No record at /home/katrin/kohaclone/C4/Serials.pm line 1382 Sending an empty field should open the search pop up and not give a perl error message. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 6059] New: Problem with changing quantity on uncertain prices list
by bugzilla-daemon＠bugs.koha-community.org 17 May '15

17 May '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6059 Bug #: 6059 Summary: Problem with changing quantity on uncertain prices list Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All URL: /cgi-bin/koha/acqui/uncertainprice.pl?booksellerid=2&o wner=1 OS/Version: All Status: NEW Severity: major Priority: P5 Component: Acquisitions AssignedTo: henridamien(a)koha-fr.org ReportedBy: katrin.fischer(a)bsz-bw.de QAContact: koha-bugs(a)lists.koha-community.org On the list for managing uncertain prices there is a column for quantity that can be edited. When creating your items on order the possibility to create items there does not make sense. When changing the quantity the uncertain price will be unset and the quantity changes to your entered number. But no additional items will be created and there is no warning about that. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug.

1 12