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

[Bug 7130] New: quantity to receive showing wrong amount
by bugzilla-daemon＠bugs.koha-community.org 21 May '13

21 May '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7130 Bug #: 7130 Summary: quantity to receive showing wrong amount Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All URL: /cgi-bin/koha/acqui/orderreceive.pl?ordernumber=13&inv oice=345665432&gst=0&supplierid=1 OS/Version: All Status: NEW Severity: major Priority: P5 Component: Acquisitions AssignedTo: henridamien(a)koha-fr.org ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Created attachment 6135 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=6135 quantity wrong I ordered 2 copies of a title, but when I go to receive it it says I have 1 to receive and that I have received 2 - I think the data in these fields is swapped. See attached. -- 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 1

[Bug 7920] New: Establish style guide for Koha help pages
by bugzilla-daemon＠bugs.koha-community.org 21 May '13

21 May '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7920 Priority: P5 - low Change sponsored?: --- Bug ID: 7920 Assignee: nengard(a)gmail.com Summary: Establish style guide for Koha help pages QA Contact: koha.sekjal(a)gmail.com Severity: normal Classification: Unclassified OS: All Reporter: oleonard(a)myacpl.org Hardware: All Status: NEW Version: master Component: Documentation Product: Koha In my work on Bug 2780 I'm finding some inconsistency in the way the help pages are styled and punctuated. I think it would be a good idea to establish some rules about how we express some things: - How should system preference names be quoted and/or styled? - How should Koha modules be quoted and/or styled? - How should we style common elements like 'hints' and 'Important:' blocks? Also: - Should we link system preference mentions to the corresponding help page? -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 10280] New: Extend SeparateHoldings functionality to the "Add items" screen
by bugzilla-daemon＠bugs.koha-community.org 21 May '13

21 May '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10280 Bug ID: 10280 Summary: Extend SeparateHoldings functionality to the "Add items" screen Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)enger.priv.no CC: gmcharlt(a)gmail.com If you have IndependantBrnaches turned on, the table of items at the top of the "Add items" screen still displays all the items from all the libraries (with the Edit/Delete links missing for the items that belong to other libraries then the library of the logged in user). This can be a long and not very useful list if there are a lot of libraries and copies. It would be nicer if this display was governed by the SeparateHoldings syspref, and items from other libraries were e.g. put in a second tab (so they are available to look at, but not "in your face" immediately). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 2720] Overdues which debar automatically should undebar automatically when returned
by bugzilla-daemon＠bugs.koha-community.org 21 May '13

21 May '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2720 Nicole C. Engard <nengard(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nengard(a)gmail.com -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10295] New: add the ability to sort and filter batch of records in Staged Records Management Tool
by bugzilla-daemon＠bugs.koha-community.org 21 May '13

21 May '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10295 Bug ID: 10295 Summary: add the ability to sort and filter batch of records in Staged Records Management Tool Classification: Unclassified 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: mathieu.saby(a)univ-rennes2.fr In manage-marc-import.pl, we should have the ability to sort and filter batch of records by date, and status (staged, imported, cleared...) M. Saby -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8412] New: add color icon set
by bugzilla-daemon＠bugs.koha-community.org 20 May '13

20 May '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8412 Priority: P5 - low Change sponsored?: --- Bug ID: 8412 CC: gmcharlt(a)gmail.com Assignee: nengard(a)gmail.com Summary: add color icon set Severity: enhancement Classification: Unclassified OS: All Reporter: nengard(a)gmail.com Hardware: All Status: ASSIGNED Version: master Component: System Administration Product: Koha My goal here is to make it so that libraries can use one of the authorized values (shelving location or collection code) to store the color of the material and then make that searchable on the advanced search page. To do this for collection codes you'd need to add the following jqueries: intranetuserjs $(document).ready(function(){ $("#advsearch-tab-ccode a:contains('Collection')").text("Color"); $("#holdings th:contains('Collection')").text("Color"); }); opacuserjs $(document).ready(function(){ $("#advsearch-tab-ccode a:contains('Collection')").text("Color"); $('#item_ccode').text("Color"); }); And update the frameworks to change the 952$8 label to say Color. I'll add this tip to a blog post and to the manual once this set of icons has been pushed to Koha. Obviously this patch just has images, no code. -- You are receiving this mail because: You are watching all bug changes.

1 21

[Bug 8917] New: Track clicks to links external to Koha
by bugzilla-daemon＠bugs.koha-community.org 20 May '13

20 May '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8917 Priority: P5 - low Change sponsored?: --- Bug ID: 8917 Assignee: oleonard(a)myacpl.org Summary: Track clicks to links external to Koha Severity: enhancement Classification: Unclassified OS: All Reporter: chris(a)bigballofwax.co.nz Hardware: All Status: NEW Version: master Component: OPAC Product: Koha It would be nice to be able to track if patrons clicked on links inside records to visit links external to Koha. (Ebooks, databases etc). This should be stored in it's own database table, and a system preference should control if it is used, and also if it stores identifying information or not. TrackClicks - No - Yes anonymously - Yes link to borrowers if logged in Off by default. This data can then be retrieved by a crafted sql report. -- You are receiving this mail because: You are watching all bug changes.

1 83

[Bug 1993] Task Scheduler Needs Re-write
by bugzilla-daemon＠bugs.koha-community.org 20 May '13

20 May '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=1993 Galen Charlton <gmcharlt(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gmcharlt(a)gmail.com --- Comment #34 from Galen Charlton <gmcharlt(a)gmail.com> --- (In reply to comment #33) > This brings me to a more important question: Should we encourage Koha users > to allow login for apache user to make use of the Task Scheduler? Note that > is a general Apache hardening measure to not allow interactive login for the > apache user. IMO we (as Koha developers) should not stimulate Koha users to > lower security barriers to enable Koha functionality. I agree: we should not be asking users to grant special privileges to the user that Apache runs as, > Another approach to the Task Scheduler could be to have a specific cronjob, > look for Koha reports to run at specified times without allowing apache to > add generic jobs with all security risks attached.. I think writing a cronjob (and abandoning Schedule::At) is the way to go. In particular, I suggest the following implementation: - create a database table to store a queue of reports to run (or maybe generalize it a bit and call it a job queue table) - the current report scheduling functionality would just add rows to the queue with a run start time set by the user - the cronjob would periodically check the queue and run any pending reports whose run start time has passed This would be pretty light-weight, but would allow us to get fancier in the future. For example, adding functionality to schedule reports to run periodically could be done by writing code to add entries into the job queue. -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 2774] Path to theme is hard-coded in many places
by bugzilla-daemon＠bugs.koha-community.org 20 May '13

20 May '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2774 Galen Charlton <gmcharlt(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Passed QA |In Discussion -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 2774] Path to theme is hard-coded in many places
by bugzilla-daemon＠bugs.koha-community.org 20 May '13

20 May '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2774 Galen Charlton <gmcharlt(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #17611|0 |1 is obsolete| | --- Comment #14 from Galen Charlton <gmcharlt(a)gmail.com> --- Comment on attachment 17611 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=17611 Bug 2774 - Path to theme is hard-coded in many places Marking patch attachment obsolete now that it's been pushed to master, because bug should remain open for additional followup. -- You are receiving this mail because: You are watching all bug changes.

1 0