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

[Bug 11130] New: Change pl Place-publication index for Marc21
by bugzilla-daemon＠bugs.koha-community.org 16 Nov '15

16 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11130 Bug ID: 11130 Summary: Change pl Place-publication index for Marc21 Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: mirko(a)abunchofthings.net QA Contact: testopia(a)bugs.koha-community.org According to ccl.properties, the pl Place-publication index is supposed to include 008/15-17 and 260$a. In record.abs, we have the index include all 260 fields. This patch removes the index for the whole field 260, leaving only $a (and 008/15-17). -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 7174] New: Authentication rewriting
by bugzilla-daemon＠bugs.koha-community.org 16 Nov '15

16 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7174 Bug #: 7174 Summary: Authentication rewriting Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing AssignedTo: paul.poulain(a)biblibre.com ReportedBy: paul.poulain(a)biblibre.com QAContact: ian.walls(a)bywatersolutions.com Blocks: 7119 Auth.pm does too many things, it must be splitted in smaller parts. In 3.6, it does : - authentifying - checking & setting permissions - setting a lot of syspref available on each template (many of them being unused in most templates) - retrieving template How to do it is still to be discussed. This entry is low priority, once we will have plack, for example, it may be obvious to use Plack authentication tools. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 45

[Bug 6279] New: Can't delete lists from the second page of lists in the OPAC
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '15

13 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6279 Bug #: 6279 Summary: Can't delete lists from the second page of lists in the OPAC Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: major Priority: P5 Component: Virtual Shelves AssignedTo: gmcharlt(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org When you're on the second page of lists and try to delete a list by opening the list you're presented with an error that the list cannot be found. http://screencast.com/t/fn0bg4bipnG -- 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 42

[Bug 7349] New: Sorting patron search result by cardnumber doesn't work
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '15

13 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7349 Bug #: 7349 Summary: Sorting patron search result by cardnumber doesn't work Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Patrons AssignedTo: adrien.saurat(a)biblibre.com ReportedBy: adrien.saurat(a)biblibre.com QAContact: ian.walls(a)bywatersolutions.com CC: gmcharlt(a)gmail.com [Mantis ref. MT2062] In Home › Patrons › Search Results, the results are always sorted by name. There is a listbox "order by" allowing 2 choices: 1) Surname. When searching with this choice, the results are indeed sorted by surname. 2) Cardnumber. When searching with this choice, the results seem to be sorted by first name. ===== What is exactly the problem then? A) Should we be able to sort by first name/surname and then Cardnumber must be renamed to First name? B) Should we be able to sort by surname/cardnumber and then the sorting must be repaired for the cardnumber option? C) Should we be able to sort by first name/surname/cardnumber and then we add a new choice and repair cardnumber? -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 15

[Bug 6828] New: Add Admin Dashboard for staff users.
by bugzilla-daemon＠bugs.koha-community.org 12 Nov '15

12 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6828 Bug #: 6828 Summary: Add Admin Dashboard for staff users. Classification: Unclassified Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: System Administration AssignedTo: paul.poulain(a)biblibre.com ReportedBy: barry(a)oslo.ie QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com The Admin main page has a lot of empty space that could be utilised for library wide information. Other ILS show local and global information on various pages e.g. - Number of currently checked out items - Number of items in my branch - Number of overdues - Total Bibs catalogued in last 7 days. How about the addition of a Koha dashboard page to use this space and present local and global library information within the users context? -- 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 26

[Bug 6069] New: Multiple level budget list on suggestions
by bugzilla-daemon＠bugs.koha-community.org 12 Nov '15

12 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6069 Bug #: 6069 Summary: Multiple level budget list on suggestions Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Acquisitions AssignedTo: henridamien(a)koha-fr.org ReportedBy: paul.poulain(a)biblibre.com QAContact: koha-bugs(a)lists.koha-community.org Librarians dealing with a suggestion have (and must have) access to all budgets. For a large library/network, it means the list can be huge and impossible to deal with. A possible solution would be to have multiple level lists : one for the top level, then one for the 2nd level, that appears when the 1st level is choosen, then one for the 3rd level (if applicable) when the 2nd level is choosen. -- 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 16

[Bug 10886] New: When intranetreadinghistory is set to not allow - staff can still view patron's history in item history
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '15

10 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10886 Bug ID: 10886 Summary: When intranetreadinghistory is set to not allow - staff can still view patron's history in item history Change sponsored?: --- Product: Koha Version: 3.10 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: danielle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When intranetreadinghistory system preference is set to not allow, the individual patron's history can not be viewed, but if you look at the item history, staff can still view patrons who have checked out that item. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 11458] New: Confusing description for syspref gist
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '15

10 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11458 Bug ID: 11458 Summary: Confusing description for syspref gist Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org The description of "gist" is: "Default tax rates are .............. (enter in numeric form, 0.12 for 12%. First is the default. If you want more than 1 value, please separate with |) " The use of "default" is confusing here. It should be "Authorized (Possible ?) tax rates are...." M. Saby -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[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 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