February 2015 - Koha-bugs - lists.koha-community.org

[Bug 12109] New: Authority subfield configuration page for controlled fields is broken
by bugzilla-daemon＠bugs.koha-community.org 18 May '15

18 May '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12109 Bug ID: 12109 Summary: Authority subfield configuration page for controlled fields is broken Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org To reproduce: 1) Go to Administration > Authority types 2) Open subfields configuration for one of the controlled fields 3) Verify that the new tab is not shown on top, but at the bottom of the page -- You are receiving this mail because: You are watching all bug changes.

1 8

[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 13536] New: Date due without time on CHECKOUT alert
by bugzilla-daemon＠bugs.koha-community.org 18 May '15

18 May '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13536 Bug ID: 13536 Summary: Date due without time on CHECKOUT alert Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org In the issues table date_due is a datetime field. If you do not have hourly loans, the 23:59:00 on the CHECKOUT notice may be somewhat confusing. (When does the library close?) In the patch submitted I virtually add a date_due_without_time column to the issues table by adding such a field in the SELECT statement in Letters.pm, routine _parseletter_sth. If you want to remove the time from the notice, now you can just edit the notice and replace <<issues.date_due>> by <<issues.date_due_without_time>>. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[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 13606] New: Batch modification for records is limited to ~500
by bugzilla-daemon＠bugs.koha-community.org 18 May '15

18 May '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13606 Bug ID: 13606 Summary: Batch modification for records is limited to ~500 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: jonathan.druart(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Bug 11395 uses the session to store the report sent to the interface (update on biblio XX OK, etc.). If the session is stored in mysql, the max size of the sessions.a_session will be reached easily (TEXT field). I found a first problem: The C4::BackgroundJob module append to the session each job information. Example for 2 jobs launched during the same session: --- _SESSION_ATIME: '1421843399' _SESSION_CTIME: '1421843222' _SESSION_ID: a5ffa813fc694706245cfe51dedc7697 _SESSION_REMOTE_ADDR: 192.168.113.2 branch: NO_LIBRARY_SET branchname: NO_LIBRARY_SET cardnumber: koha emailaddress: koha(a)exampe.org firstname: koha flags: 1 id: koha ip: 1.2.3.4 job_94357aff68a60dee98819f627c8a7f57: !!perl/hash:C4::BackgroundJob extra_values: messages: - biblionumber: 1 code: biblio_modified type: success - biblionumber: 2 code: biblio_modified type: success - biblionumber: 3 code: biblio_modified type: success - biblionumber: 4 code: biblio_modified type: success - biblionumber: 5 code: biblio_modified type: success report: total_records: 5 total_success: 5 view: report invoker: /cgi-bin/koha/tools/batch_record_modification.pl jobID: 94357aff68a60dee98819f627c8a7f57 name: FIXME progress: 5 results: ~ sessionID: a5ffa813fc694706245cfe51dedc7697 size: 5 status: completed job_98a251e034eec15b87027ea9c5c0a8cd: !!perl/hash:C4::BackgroundJob extra_values: messages: - biblionumber: 6 code: biblio_modified type: success - biblionumber: 7 code: biblio_modified type: success - biblionumber: 8 code: biblio_modified type: success - biblionumber: 9 code: biblio_modified type: success - biblionumber: 10 code: biblio_modified type: success report: total_records: 5 total_success: 5 view: report invoker: /cgi-bin/koha/tools/batch_record_modification.pl jobID: 98a251e034eec15b87027ea9c5c0a8cd name: FIXME progress: 5 results: ~ sessionID: a5ffa813fc694706245cfe51dedc7697 size: 5 status: completed It's useless to keep old job information. To reproduce: 1/ Create a file with 500 biblionumbers: mysql -e "select biblionumber from biblio limit 500;" | tail -n 500 > /tmp/biblionumbers.txt 2/ Define a marc modification template 3/ Load the /tmp/biblionumbers.txt in the batch biblio modification tool 4/ Repeat 3 You will get: Syck parser (line 1534, column 6): syntax error at /usr/lib/i386-linux-gnu/perl5/5.20/YAML/Syck.pm line 75. The sessions.a_session field has reach its maximum size and the yaml stored in it is not complete and not well formed. To fix that I would like to 1/ Remove previous job information on creating a new one 2/ Increase the size of sessions.a_session from TEXT (64kb) to MEDIUMTEXT (32mb) -- You are receiving this mail because: You are watching all bug changes.

1 60

[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 12516] New: The module C4::Tags needs more unit tests
by bugzilla-daemon＠bugs.koha-community.org 18 May '15

18 May '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12516 Bug ID: 12516 Summary: The module C4::Tags needs more unit tests Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: yohann.dufour(a)biblibre.com QA Contact: gmcharlt(a)gmail.com Some subroutines of the module C4::Tags are not tested. -- You are receiving this mail because: You are watching all bug changes.

1 6

[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 13591] New: Rss sample templates have hardcoded urls
by bugzilla-daemon＠bugs.koha-community.org 18 May '15

18 May '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13591 Bug ID: 13591 Summary: Rss sample templates have hardcoded urls Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: colin.campbell(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org The sample templates in misc/cronjobs/rss have hardcoded urls the should be using suspref OPACBaseURL The contents of rss are rather neglected but many sites seem to want to use this, while most may want some customizations the samples should work out of the box in a sensible fashion at present if you create a list of new acquisitions The links are hardcoded to nz -- You are receiving this mail because: You are watching all bug changes.

1 9