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

[Bug 10021] New: Remove dead(?) code related to notifys
by bugzilla-daemon＠bugs.koha-community.org 19 Oct '15

19 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10021 Bug ID: 10021 Summary: Remove dead(?) code related to notifys Classification: Unclassified Change sponsored?: --- Product: Koha Version: 3.14 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de The database table notifys and the code related to it is as far as I can tell no longer used in Koha. I am not sure how this used to work, so we would need to check very carefully before removing it. There are some things still visible in the interface: - fines table in patron account shows columns notify id and level - similar information shows in the overdues with fines report In all databases I checked there was no information stored in the databaes table or columns - they were always 0. Remaining code I found: - database table notifys - notify_id and notify_level in accountlines - C4/Overdues.pm - C4/Accounts.pm - C4/Members.pm -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 6427] New: Rewrite of the accounts system
by bugzilla-daemon＠bugs.koha-community.org 19 Oct '15

19 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6427 Bug #: 6427 Summary: Rewrite of the accounts system Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Architecture, internals, and plumbing AssignedTo: gmcharlt(a)gmail.com ReportedBy: robin(a)catalyst.net.nz QAContact: koha-bugs(a)lists.koha-community.org The accounts system is in need of a rewrite. This will solve two purposes: 1) It'll make the code a lot nicer, and things won't be doing direct table access from all over the place. Also, some unused and long dead features will be stripped out. 2) It'll allow the account code to be a lot more flexible, making features like partial payments a whole lot seamless. This is in progress, it can be viewed here: http://git.catalyst.net.nz/gw?p=koha.git;a=shortlog;h=refs/heads/bywater/wr… And accessed via: git://git.catalyst.net.nz/git/public/koha.git, in the branch "bywater/wr78012" -- 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 795

[Bug 10306] New: acquisitions shows publisher from 260 only
by bugzilla-daemon＠bugs.koha-community.org 19 Oct '15

19 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10306 Bug ID: 10306 Summary: acquisitions shows publisher from 260 only 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: nengard(a)gmail.com The acquisitions module show publisher info from the 260, but now libraries are using RDA and need the 264 to show if there is no 260. This is easy enough on XSLT styled pages, but acquisitions is not one of those. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 5079] New: Make display of shelving location and call number in XSLT results controlled by sysprefs
by bugzilla-daemon＠bugs.koha-community.org 19 Oct '15

19 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5079 Summary: Make display of shelving location and call number in XSLT results controlled by sysprefs Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: OPAC AssignedTo: oleonard(a)myacpl.org ReportedBy: jwagner(a)ptfs.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 The XSLT results list does not show shelving location (the non-XSLT display does). For both shelving location and call number, some sites want either/both to show, while sites with 30-40 branches may want to declutter the display. I'm proposing to add separate sysprefs to control whether or not XSLT results list displays (a) shelving location and (b) call number. Comments? Suggestions? -- 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 80

[Bug 9026] New: tagging improvements
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '15

16 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9026 Priority: P5 - low Change sponsored?: --- Bug ID: 9026 Assignee: gmcharlt(a)gmail.com Summary: tagging improvements Severity: enhancement Classification: Unclassified OS: All Reporter: nengard(a)gmail.com Hardware: All Status: NEW Version: master Component: Tools Product: Koha I got this email and wanted to share the idea with you all: Right now, tagging works this way: 1) I'm testing tagging, so I tag a title "test" 2) I go into tag moderation and see that, yay, my tag is there waiting, so it works! 3) I can choose to approve the tag test. This means anyone can apply the term test to anything in the catalog now. Not ideal since test can mean a lot of things. Perhaps a student is just using it to mark items they're using to make a test for a project. Not a good use of tags and I won't know that they've done it because I've already approved the tag. Lost my teachable moment. 4) So I reject it, because that's my only option. But now that means I can't use it to test again in the future unless I later go in, then approve it, then use it, then reject it again. I'm just proposing a step that allows you a third option. You have a tag sitting there. You don't want to approve or reject it, you just want to make it go away in this instance. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 5655] New: printing of fines should support more than one line
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '15

16 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5655 Summary: printing of fines should support more than one line Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Circulation AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Estimated Hours: 0.0 Today I noticed the new print link next to each account line on the patron's Fines tab. What I don't understand is why you can only print one line at a time and each receipt shows the total due. Shouldn't there be a way to select multiple lines to print on one receipt? Or not have it show the total due? I have some librarians that find having one line item and a total on the invoice. This might be simply resolved by making the total due not look like it's summing the lines above. -- 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 6

[Bug 13016] New: Add fine grace period by hour
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '15

16 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13016 Bug ID: 13016 Summary: Add fine grace period by hour Change sponsored?: --- Product: Koha Version: 3.12 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: marjorie.barry-vila(a)ccsr.qc.ca QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In fine rules, it will be fine to have possibility to add a grace period by hour when loan period is by hour. Regards, Marjorie -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 7663] New: batch add barcodes to a list
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '15

16 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7663 Priority: P5 - low Change sponsored?: --- Bug ID: 7663 Assignee: gmcharlt(a)gmail.com Summary: batch add barcodes to a list QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: nengard(a)gmail.com Hardware: All Status: NEW Version: master Component: Tools Product: Koha I would be nice if this page: /koha/virtualshelves/shelves.pl?viewshelf=13 had a bigger box so that you could add multiple barcodes at a time (like you can on label maker or the batch modification tool). -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 10198] New: Add the ability to import and export authorized values
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '15

16 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10198 Bug ID: 10198 Summary: Add the ability to import and export authorized values 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: mathieu.saby(a)univ-rennes2.fr CC: gmcharlt(a)gmail.com We can not import and export easily from staff interface a list of authorized values (in CSV or SQL). It would be useful. M. Saby -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 7802] New: A MySQLism is used to get the current date.
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '15

16 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7802 Priority: P5 - low Change sponsored?: --- Bug ID: 7802 Assignee: gmcharlt(a)gmail.com Summary: A MySQLism is used to get the current date. QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: marc(a)msys.ch Hardware: All Status: NEW Version: unspecified Component: Database Product: Koha To get todays date, the MySQL only function CURDATE() or CURRENT_DATE() is being used in many places. Neither CURDATE() nor CURRENT_DATE() must be used, but instead the standard form CAST(now() AS date). -- You are receiving this mail because: You are watching all bug changes.

1 49