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

[Bug 8016] New: Items are not tie to the transaction using "global" action.
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '15

06 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8016 Priority: P5 - low Change sponsored?: --- Bug ID: 8016 CC: gmcharlt(a)gmail.com Assignee: kyle.m.hall(a)gmail.com Summary: Items are not tie to the transaction using "global" action. QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: anthony.laquerre(a)ccsr.qc.ca Hardware: All Status: NEW Version: rel_3_6 Component: Circulation Product: Koha Created attachment 9315 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=9315&action=edit Payments Selection Hi, We have a problem with how the process of paying fine is currently done. Look at the 2 images. In the Pay fines page. There is currently a difference between buttons Group 1 : ("Pay" + "Writeoff") Group 2 : ("Pay amount","Write off all", "Pay selected") Group 1 is done on the specific item level. Group 2 is done globally using a logic to pay the oldest fine. ( That's my understanding ... :-)) If you look at image : Payments.png, you will see the difference. The payment for 10$ is done using "Pay selected". The payment for 5$ is done using "Pay". This scenario is valid for all buttons from group 1 and group 2. The problem is really the link to the item that is currently lost when using buttons from Group 2. Staff find it really hard to talk about their account because of that. It's impossible to know what the 10$ really apply to. This is a simple example, but sometime patron will return 5 books with 5$ fines for each. You will do "Pay Selected" (group 2) the 25$ will be applied but you will never be able to know what it was apply exactly. Is it possible to still link the item to the transaction using button from Group 2 ? Let me know if you need more infos. Thanks, Anthony -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 7525] New: some database fields are displayed 'as is' when they are linked to autorised values
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '15

06 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7525 Bug #: 7525 Summary: some database fields are displayed 'as is' when they are linked to autorised values Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing AssignedTo: gmcharlt(a)gmail.com ReportedBy: gaetan.boisson(a)biblibre.com QAContact: koha.sekjal(a)gmail.com We have to reuse item fields in ways they were not intended to quite often in order to respond to libraries specific demands. In some cases we will control these fields with an authorized value, but not all fields will display the authorized value description on the opac and admin interface. See: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7379 Which took care of this problem for the copynumber field. -- 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 4

[Bug 7705] New: IE postdata issue - expiring sessions when back button is used
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '15

06 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7705 Priority: P5 - low Change sponsored?: --- Bug ID: 7705 Assignee: oleonard(a)myacpl.org Summary: IE postdata issue - expiring sessions when back button is used QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: shelley.gurney(a)nzica.com Hardware: All Status: NEW Version: rel_3_6 Component: OPAC Product: Koha The majority of our users are still using IE and navigate via the browser buttons. This is causing some issues with their sessions expiring when they navigate forwards and backwards several times. Is there a fix for this in Koha, to stop this from happening? Can we trick IE into not cancelling the session. (not an apparent issue in Chrome or Firefox) -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 7224] New: Allow patrons to pick their own preferred language
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '15

06 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7224 Bug #: 7224 Summary: Allow patrons to pick their own preferred language Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N AssignedTo: frederic(a)tamil.fr ReportedBy: ian.walls(a)bywatersolutions.com QAContact: ian.walls(a)bywatersolutions.com Depends on: 6481 Allow patrons to select their own preferred language, individually. This can provide an extra level of personalization in multi-lingual environments, and could later be applied to more than just the OPAC or staff client templates (translated notices). The choice should be configurable in the OPAC, under Preferences, without the need to confirm with the librarian (like for contact info changes) The structural changes to Koha required for this development would pave the way for a whole bunch of other individual preference values (beyond just messaging and OPAC privacy preferences), making for more customizable ILS -- 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 1

[Bug 7343] New: search tag usability in MARC framework
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '15

06 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7343 Bug #: 7343 Summary: search tag usability in MARC framework Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client AssignedTo: paul.poulain(a)biblibre.com ReportedBy: gaetan.boisson(a)biblibre.com QAContact: ian.walls(a)bywatersolutions.com CC: gmcharlt(a)gmail.com After searching for a tag in a marc framework, the list of tags is shown starting with the tag we are looking for, but pages prior to the match are not shown at all, leaving users under the impression that these tags have disappeared. My take on this is that we should either make it work as a filter and only display the match, it would then be clear for the user that he has to empty the search field in order to view the complete list of tags. Or make it work as a simple search that would take us on the page of the match (and maybe highlight the result) but without discarding the previous pages. The behaviour is the same when editing subfields: if the user uses the pagination to go edit the subfields for 995 and then clicks on the name of the framework in the breadcrumb, the page shown is the result page for a search on 995, which hides all the previous pages. This is even more problematic as the user hasn't used the searched box at this point. (In that case i think the link should take the user on the first page of the framework, which is consistent with what is written on the link he has clicked: the name of the framework.) This is the behaviour in 3.6, 3.4 and 3.2. -- 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 1

[Bug 7524] New: Make it possible to generate a .koc file using the Firefox KOCT plugin
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '15

06 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7524 Bug #: 7524 Summary: Make it possible to generate a .koc file using the Firefox KOCT plugin Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: katrin.fischer(a)bsz-bw.de QAContact: koha.sekjal(a)gmail.com CC: gmcharlt(a)gmail.com I tried testing the Firefox plugin for offline circulation today, because I was not aware that the feature is still blocked by bug 5877. As the missing tables are scheduled to be added for 3.8, it's currently not possible to make use of this nice plugin for older versions of Koha. A nice enhancement would be an option to generate a standard .koc file from the plugin. The upload option is already in Koha for a longer time, so a lot of libraries could make use of the plugin without having to wait for the release of the new version and updating. -- 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 4

[Bug 7223] New: Move borrowerRelationship to Authorised Values list
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '15

06 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7223 Bug #: 7223 Summary: Move borrowerRelationship to Authorised Values list Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration AssignedTo: paul.poulain(a)biblibre.com ReportedBy: ian.walls(a)bywatersolutions.com QAContact: ian.walls(a)bywatersolutions.com CC: gmcharlt(a)gmail.com Rather than a system preference of pipe-delimited values (user unfriendly!), this list should be stored in our all-purpose Authorised Values engine. This will allow for a separation of Code and display values, as well as remove a system preference (there are too many) -- 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 1

[Bug 7594] New: Google Cover CSS suggestions
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '15

06 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7594 Bug #: 7594 Summary: Google Cover CSS suggestions Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC AssignedTo: oleonard(a)myacpl.org ReportedBy: ssammons(a)npelem.com QAContact: koha.sekjal(a)gmail.com In google-jackets.js there is hard coded "style" on line 48 using... http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=koha-tmpl/opac-tm… I suggest this is moved to a .css file, as to allow the end user to impose changes to the style. Additionally, it would be nice if a unique class can be added to all the image preview types. Currently they are all dynamic (class & id). Added a class such as "gbs-cover" or similar would allow end users to use CSS to uniquely style each book cover used. I am not able to find where this is generated or I would suggest the lines of code to change. Finally, the "No Image Available" does not appear in the HTML source code. The JS shows it creating a "span" element with a class of no-image. Is there anyway to actually have that appear in the actual source code? All suggested changes should allow for an end user to have easier and clearer control of OPAC search generated images. -- 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 5

[Bug 9992] New: Barcode generated without a branchcode
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '15

06 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9992 Bug ID: 9992 Summary: Barcode generated without a branchcode Classification: Unclassified Change sponsored?: --- Product: Koha Version: 3.10 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: chad(a)pennmanor.net CC: colin.campbell(a)ptfs-europe.com When receiving a serial with autobarcode set to <branchcode>yymm0001 the automatically generated barcode is missing the branchcode. When focusing on the barcode field the javascript inserts "13041297" instead of "CM13041297". The behavior is the same in both firefox and chrome. Our librarian is reporting this worked correctly in an earlier version of 3.10.x but stopped working with the recent upgrade to 3.10.4. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 9562] New: System preference 'insecure' shows wrong value after update to v3.10
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '15

06 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9562 Bug ID: 9562 Summary: System preference 'insecure' shows wrong value after update to v3.10 Classification: Unclassified Change sponsored?: --- Product: Koha Version: 3.10 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: fred.pierre(a)smfpl.org CC: gmcharlt(a)gmail.com There is an omission in the update script for v3.10, and it affects a critical system preference: 'insecure' On our v3.5 server the value corresponding to "Don't Allow" was recorded as "NO" - on the new system the value of "Don't Allow" is 0 (zero). WARNING: Changing the value to "Allow" (1) could completely hose your system and could require a new Koha installation! The update script did not change the table value from "No" to "0" so the 'insecure' system preference shows up as "Allow" even though the system interprets the "NO" value as "Don't Allow" for login functionality. In other words, we still have to log in, and our Koha system is fully functional. However this could lead updating clients to believe that the proper setting is "Allow" when production systems should really use "Don't Allow" P.S. My past experience of switching to "Allow" was very negative - I could no longer log in to my system at all - luckily it was a test server. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3