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

[Bug 12768] New: Replacement cost and processing fee management
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '15

13 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12768 Bug ID: 12768 Summary: Replacement cost and processing fee management 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: francois.charbonnier(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Sponsored by Halland County Library RFC : http://wiki.koha-community.org/wiki/Overdue_Notice_Enhancement#Replacement_… Description A default replacement cost and a processing fee will be added to the item type page. The input form and the table that displays all iten types will have these two new field/column : "Default replacement cost" "Processing fee (When lost)" Two system preferences will be added. "UseDefaultReplacementCost" to enable the use of the value set on the item type level. "ProcessingFeeNote" to set the value that will populate the note in the table "accountlines" when the processing fee are applied. These elements will be used as follows : When the "longoverdue.pl" script is run : If "UseDefaultReplacementCost" is enabled and the items.replacementcost = 0 : The value of "Default replacement cost" set up in the itemtype populate the "accountlines" table. If the value of "Processing fee (When lost)" is > 0, it is also used to populate the table "accountlines." The value in the system preference "ProcessingFeeNote" is used to update the note in accountlines for this item. Otherwise, no processing fees are added. If "UseDefaultReplacementCost" is enabled and the value in items.replacementcost> 0 The default koha behavior is used. The value in items.replacementcost populate the "accountlines" table. If the value of "Processing fee (When lost)" defined in the document type is > 0, it is also used to populate the table "accountlines." The value in the system preference "ProcessingFeeNote" is used to update the note in accountlines for this item. Otherwise, no processing fees are added. If "UseDefaultReplacementCost" is disabled : The default koha behavior is used. If the value of "Processing fee (When lost)" defined in the document type is > 0, it is also used to populate the "accountlines" table. The value in the system preference "ProcessingFeeNote" is used to update the note in accountlines for this item. Otherwise, no processing fees are added. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 70

[Bug 11594] New: store both item type and document type in statistics
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '15

13 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11594 Bug ID: 11594 Summary: store both item type and document type in statistics Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com I copy here a comment originaly made on bug 9351 For some libraries, what is needed in statistical table is BOTH items.itype and biblioitems.itemtype, and maybe a clear indication (a 3rd column "circulation_type" ?) of which type is was used for circulation rights. Ex: In Rennes 2 we use item level for defining circulation rules. items.itype are codes for "Short Loan", "Normal Loan", "Long loan". biblioitems.itemtype are "Book", "Serial", "DVD" etc. For our annual report, we need to know the number of Books, Serials, DVD checked out, even if the type used for defining circulation rules are "Short loan", and not "Book". But other libraries may have different settings, and may have need to make stats on item level, or maybe cross stats on both level. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[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 12224] New: Staff should be able to print Check In slip from Check In UI
by bugzilla-daemon＠bugs.koha-community.org 12 Nov '15

12 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12224 Bug ID: 12224 Summary: Staff should be able to print Check In slip from Check In UI Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: pasi.kallinen(a)pttk.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Staff should be able to print a list of patron's returns from the Check In UI. Some of our patrons want a physical slip when they've returned the books at the counter. The Check-IN UI does not offer any way to print such a slip. Going to the patron's modification log The slip should list all the checked-in items for the patron for today. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 13014] New: Sent an email to budget owner when a suggestion can be treated
by bugzilla-daemon＠bugs.koha-community.org 12 Nov '15

12 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13014 Bug ID: 13014 Summary: Sent an email to budget owner when a suggestion can be treated 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 QA Contact: testopia(a)bugs.koha-community.org When a suggestion is created and linked to a fund, it could be great to notify the budget owner. A cronjob will be developed in order to generate an email going to the budget owner. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 62

[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 13632] New: Use a translateable file instead of the database for managing permission descriptions
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '15

10 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13632 Bug ID: 13632 Summary: Use a translateable file instead of the database for managing permission descriptions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com At the moment, we rely on strings in `permissions.description` and `userflags.flagdesc` to provide the descriptions of the permissions on the member-flags.pl page. It would make more sense to keep these descriptions in a file that can be translated and changed without changing the database. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 67