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

[Bug 14597] New: Reverting a batch where a record overlaid a now deleted record will fail
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '15

10 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14597 Bug ID: 14597 Summary: Reverting a batch where a record overlaid a now deleted record will fail Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl If batch of records is used to overlay existing records, and one of those records is deleted, any attempt to revert this batch will fail. The unanimous consensus is that deleted records should stay deleted ( https://lists.katipo.co.nz/public/koha/2015-June/043048.html ). -- You are receiving this mail because: You are watching all bug changes.

1 40

[Bug 14509] New: Koha still allows spaces at the end, beginning or as your password
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '15

10 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14509 Bug ID: 14509 Summary: Koha still allows spaces at the end, beginning or as your password Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Authentication Assignee: gmcharlt(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org This is a follow-up bug for bug 10177 which fixed the 'change password' page to not allow your password to have spaces at the beginning or ending or to consist solely of spaces. But there are still 2 other pages to fix: - Patron account > Edit patron - OPAC > Change password -- You are receiving this mail because: You are watching all bug changes.

1 31

[Bug 14339] New: Installer broken by bug 13967
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '15

10 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14339 Bug ID: 14339 Summary: Installer broken by bug 13967 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org The introduction of the new Koha::Config::SysPrefs package slightly changed the behaviour on syspref retrieval by not catching DB errors (notably when there is no DB structure :-/, which should be detected and redirected to the installer/maintenance depending on the interface) -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 14031] New: Itemnumber should be a numeric search in ccl.properties
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '15

10 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14031 Bug ID: 14031 Summary: Itemnumber should be a numeric search in ccl.properties Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: gmcharlt(a)gmail.com Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl At the moment, if you do a search in the OPAC or staff client for "itemnumber:1", you'll get no results even when you have an item with an itemnumber of 1. That's because Zebra defaults to a word list search, but there is no word index for itemnumber. It's a numeric index. So, to find that item, you'll have to try "itemnumber,st-numeric:1". However, by tweaking ccl.properties, we can make "itemnumber:1" work as well. We already do this for "notforloan" which we know will always be numeric. Current ccl.properties: notforloan 1=8008 4=109 itemnumber 1=8010 4=109 is the PQF/RPN for "st-numeric". So... let's just add "4=109" to itemnumber, and be merry! -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 10824] New: OAI-PMH repository/server not handling time in "from" argument
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '15

10 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10824 Bug ID: 10824 Summary: OAI-PMH repository/server not handling time in "from" argument Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org Currently, if you try to use time in a "from" argument with the Koha OAI-PMH repository/server, you'll get unexpected results. Case 1: There are 3 records with the following timestamps: 2013-09-02 10:29:40 2013-09-05 13:44:33 2013-09-05 13:44:34 However, if you sent a request using "2013-09-02 8:29:40" or "2013-09-02T8:29:40Z" (the latter being the 'proper' way), you'll only retrieve the last 2 records of the 3 record set. This is because we're using this code to check the "from" and "until" arguments: "WHERE DATE(timestamp) >= ? AND DATE(timestamp) <= ?" We need to strip DATE() from around the timestamps. If we just compare the normal timestamp, MySQL can handle properly compare the timestamp against the following strings: "2013-09-02" "2013-09-02 8:29:40" "2013-09-02T8:29:40Z" (NB This one produces a warning (not an error) so it's less than ideal) I'm proposing that we remove DATE() and include a regex to strip UTC designators T and Z. This way, we'll always be passing in "2013-09-02" or "2013-09-02 8:29:40" which work perfectly. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 14805] New: No idea to disallow the deletion of multiple patron card batches
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '15

10 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14805 Bug ID: 14805 Summary: No idea to disallow the deletion of multiple patron card batches Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: j.kylmala(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org In koha/patroncards/manage.pl?card_element=batch you cannot select multiple batches for deletion. We don't want the user to go through them one by one if the user wants to delete all the batches. -- You are receiving this mail because: You are watching all bug changes.

1 31

[Bug 10855] New: Additional fields for subscriptions
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '15

10 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10855 Bug ID: 10855 Summary: Additional fields for subscriptions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Some customer requests are about creating custom fields for serials. In order to avoir new specific fields for each customers, this feature will add a new module to create fields dynamically. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 283

[Bug 14917] New: RDA: 700/710/711 fix path for icon in XSLT
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '15

10 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14917 Bug ID: 14917 Summary: RDA: 700/710/711 fix path for icon in XSLT Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: wsalesky(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Fix broken path to icon in 7xx fields. Bug introduced in http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13382#c45 -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 14734] New: Enhance 264 display in OPAC and Staff XSLT
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '15

10 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14734 Bug ID: 14734 Summary: Enhance 264 display in OPAC and Staff XSLT Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: wsalesky(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Make 264 repeatable in display with labels that match the coding in the indicators. So: Dynamically display as Producer, Publisher, Distributor, Manufacturer, and/or Copyright Date information, that is, read 2nd indicators under 264 and translate them to different descriptors: (brief/full display) _0 → Producer _1 → Publisher _2 → Distributor _3 → Manufacturer _4 → Copyright Date (display copyright symbol [If I recall correctly, this is a known bug]) example: 264 _1 --> Publisher: New York : Basic Books, [2005] 264 _4 --> Copyright date: ©2005 Display subfields a, b, c, 3 Use if/then/else regarding 260 and 264: If there is no 264, then display 260, else display 264 This enhances changes made in: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12724, http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12725, http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12726. -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 14054] New: 246 XSLT Improvements
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '15

10 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14054 Bug ID: 14054 Summary: 246 XSLT Improvements Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 13386 246 2nd indicator specifies type of other title, would be nice to display that when 1st indicator 1. Probaby it would go into brackets like relator terms and would be overridden by subfield i -- You are receiving this mail because: You are watching all bug changes.

1 20