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

[Bug 14390] New: On renewal, the last fine is not marked as accounttype 'F' when item is checked in.
by bugzilla-daemon＠bugs.koha-community.org 12 Jan '16

12 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14390 Bug ID: 14390 Summary: On renewal, the last fine is not marked as accounttype 'F' when item is checked in. Change sponsored?: --- Product: Koha Version: 3.18 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When an item with a fine is renewed, the old fine is closed (i.e. accounttype is set to 'F'). A new fine is created, with an updated description. The new find is not closed when the item is checked back in. select date, amount, description, accounttype, amountoutstanding, lastincrement, timestamp from accountlines where itemnumber = 35540 and borrowernumber = 24990\G *************************** 1. row *************************** date: 2015-05-05 amount: 0.500000 description: O'Connor's annotated criminal codes plus. 05/04/2015 11:59 PM accounttype: F amountoutstanding: 0.500000 lastincrement: 0.500000 timestamp: 2015-06-08 12:42:27 *************************** 2. row *************************** date: 2015-06-08 amount: 4.500000 description: O'Connor's annotated criminal codes plus. 05/26/2015 11:59 PM accounttype: FU amountoutstanding: 4.500000 lastincrement: 0.500000 timestamp: 2015-06-08 02:02:40 2 rows in set (0.00 sec) Looking in old_issues, you can see that the item was renewed, and that date_due does match the second description... only the first accountlines entry is marked woth accounttype 'F' on return, however. select date_due, returndate, lastreneweddate, renewals, timestamp, issuedate from old_issues where itemnumber = 35540 and borrowernumber = 24990\G *************************** 1. row *************************** date_due: 2015-05-26 23:59:00 returndate: 2015-06-08 12:42:27 lastreneweddate: 2015-05-05 00:00:00 renewals: 1 timestamp: 2015-06-08 12:42:27 issuedate: 2015-04-13 09:23:20 To replicate: 1) check out an item 2) let the item go overdue and start accruing fines 3) renew the item 4) let the item go overdue again. Note that a second accountlines entry has been added 5) return the item. Note that the new fine is set with accounttype 'FU'. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 30

[Bug 8038] New: Enable network printing when UsePrintQueues is on
by bugzilla-daemon＠bugs.koha-community.org 12 Jan '16

12 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8038 Priority: P5 - low Change sponsored?: --- Bug ID: 8038 CC: gmcharlt(a)gmail.com Assignee: kyle.m.hall(a)gmail.com Summary: Enable network printing when UsePrintQueues is on Severity: enhancement Classification: Unclassified OS: All Reporter: srdjan(a)catalyst.net.nz Hardware: All Status: NEW Version: unspecified Component: Circulation Product: Koha Work to be done: * If UsePrintQueues is on send slips to network printer using C4::Print::printslip() and open the print window as a fall back, rather than calling browser print() immediately How to test: * Set UsePrintQueues to No. Issue and transfer slips should be printed from the browser (pop-up), calling browser print() immediately (as it is now). * Set up a print queue on the server (sysadmin help, needs to provide queue name), add it to the printers; select the printer on the "Select Library" screen, or set it as the branch printer * Set UsePrintQueues to Yes. Issue and transfer slips should be printed from the printer queue, browser pop-up should just open and display, without calling browser print() immediately. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 8034] New: Enable server print queue selection
by bugzilla-daemon＠bugs.koha-community.org 12 Jan '16

12 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8034 Priority: P5 - low Change sponsored?: --- Bug ID: 8034 CC: gmcharlt(a)gmail.com Assignee: kyle.m.hall(a)gmail.com Summary: Enable server print queue selection Severity: enhancement Classification: Unclassified OS: All Reporter: srdjan(a)catalyst.net.nz Hardware: All Status: NEW Version: unspecified Component: Circulation Product: Koha Re-enable server print queue selection that was disabled due to being disfunctional. Work to be done: * Add system preference UsePrintQueues. Print queue selection will be enabled only if UsePrintQueues is true. * Place admin/printers.pl link on the admin page. Should be visible UsePrintQueues dependent. * Add branches.default_printqueue that will be used if not set in session * Uncomment printer selection in "Set Library". Feature will be visible UsePrintQueues dependent. A follow-up bug will be created for printing using the selection. How to test: * Check that UsePrintQueues syspref is available * When UsePrintQueues is "No", check: - "Printers" link on the "Admin" page is not present - "Set Library" does not have printer selection - branch maintenance does not have default printer queue selection * When UsePrintQueues is "Yes", check: - "Printers" link on the "Admin" page is present - follow the link and add some printer queues - branch maintenance does have default printer queue selection - "Set Library" does have printer selection; select one - selected printer sticks for the session * -- You are receiving this mail because: You are watching all bug changes.

1 59

[Bug 11884] New: SlipCSS should be CSS not a file
by bugzilla-daemon＠bugs.koha-community.org 12 Jan '16

12 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11884 Bug ID: 11884 Summary: SlipCSS should be CSS not a file 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: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com SlipCSS looks for a path to a file. It would be better if it was like the UserCSS fields for Intranet and OPAC so that the average user can just enter CSS in that field instead of needing access to a web server to upload their CSS file. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 5572] New: refinements to function merge sub merge in C4::AuthoritiesMarc
by bugzilla-daemon＠bugs.koha-community.org 12 Jan '16

12 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5572 Summary: refinements to function merge sub merge in C4::AuthoritiesMarc Change sponsored?: --- Product: Koha Version: rel_3_2 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: MARC Authority data support AssignedTo: gmcharlt(a)gmail.com ReportedBy: januszop(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org CC: ian.walls(a)bywatersolutions.com Estimated Hours: 0.0 Created attachment 2941 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=2941 Proposed patch When merging/editing authority records bibliographic records are to be corrected. This is done by merge from C4::AuthoritiesMarc. There has been a change in this function from 30 Sept./6 Oct. (commit e9c0a11d41f107425d7f53dcc09e57e3e00ee608) [between 3.2.0 beta and 3.2.0 RC] (http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5264) The original behavior in 3.0 was: when authority has been changed, then in the corresponding fields in the bibliographic records all the subfields of such fields controlled by authority will be dropped and created anew with only subfields which have a value in the authority. The new behavior is much better: in the bibliographic record only subfields which have a value in the authority_to (the new authority) will be changed. BUT what there was a subfield present (with value) in authority (and in bibliographic) and the value is now deleted form authority? It will still stay in all bibliographic, whereas it should not. Hence my proposal: subfields not active in authority framework will be preserved; subfields active in the authority framework (i.e. controlled by this authority type) should be set as in the authority record - either have the value of corresponding subfield in authority or be empty. Regards, Janusz -- 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 57

[Bug 14892] New: Initial checkin of an item to be transferred shows incorrect holding location
by bugzilla-daemon＠bugs.koha-community.org 12 Jan '16

12 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14892 Bug ID: 14892 Summary: Initial checkin of an item to be transferred shows incorrect holding location 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: nick(a)quecheelibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If an item from another branch is checked in (with AutomaticItemReturn=Do) a transfer message yellow box appears, but in the checkins table the item shows the home branch for both Home and Holding locations. A second checkin updates the table correctly -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 10988] New: Allow login via Google OAuth2
by bugzilla-daemon＠bugs.koha-community.org 12 Jan '16

12 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10988 Bug ID: 10988 Summary: Allow login via Google OAuth2 Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: gmcharlt(a)gmail.com Reporter: vanoudt(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Created attachment 21740 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=21740&action=edit oauth login helper Here at PBC, we use google apps for education to provide email for our students, and also koha for our library systems. Although we synchronise our koha accounts and google accounts, it would be much nicer for patrons to be able to simply login using OAuth2. I'm working on getting this going, basing my work on bug 9587. More details to come - but wanted to get this bug set up and start getting advice from the Koha experts. As it currently stands, the oauth2 authentication is working perfectly - on https. (Switching between the two causes issues with the cookies, as one would expect). opac/svc/oauthlogin handles all of the oauth2 magic. Opening this page will log you in. There is LOTS of room for improvement in the oauth2 login... mostly because perl is not my weapon of choice. More obviously: 1. the clientid, clientsecret need to be moved systempreferences (I've stripped ours from the attached file - these can be obtained from https://code.google.com/apis/console and then choosing "API Access" 2. Google recommends verifying and decrypting the id_token locally, which means caching some information and updating it daily. That would make things a lot faster, but does add to the complication. As was stated for the personas implementation: "The nice thing about it is, the user doesn't have to do anything, like linking their account. As long as the email address they are using... is the same as the one in Koha it will just work." -- You are receiving this mail because: You are watching all bug changes.

1 77

[Bug 14217] New: Add a DOM syntax for specifying conditions on indexes
by bugzilla-daemon＠bugs.koha-community.org 12 Jan '16

12 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14217 Bug ID: 14217 Summary: Add a DOM syntax for specifying conditions on indexes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org It would be great to have a way on the XML syntax to specify conditions for fields to get indexed. For example: we could want to index the 100$a subfield on "Author" only if the 1st indicator is not 'z'. The current syntax doesn't allow us to specify that. -- You are receiving this mail because: You are watching all bug changes.

1 29

[Bug 11084] New: Delete biblios on Leader 05 =d
by bugzilla-daemon＠bugs.koha-community.org 12 Jan '16

12 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11084 Bug ID: 11084 Summary: Delete biblios on Leader 05 =d Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: drnoe(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Position 05 of the leader in MARC 21 indicates the record's status. A lower case “d” indicates that the record is to be deleted (http://www.loc.gov/marc/authority/adleader.html) Koha should allow for deletion of bibliographic records that contain a “d” in the LEADER position 05 when by overlaying existing records. -- You are receiving this mail because: You are watching all bug changes.

1 63

[Bug 14573] New: Correcting messages on OPAC error pages so they make more sense
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '16

11 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14573 Bug ID: 14573 Summary: Correcting messages on OPAC error pages so they make more sense Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: aleishaamohia(a)hotmail.com QA Contact: testopia(a)bugs.koha-community.org 400.pl: "This error means that the Koha is pointed an invalid link." - doesn't make much sense 401.pl: "This error means that the you are trying to access a link that you're not authorized to see" - unnecessary 'the'. Also could be improved by providing a hyperlink for the user to log in rather than saying "Try logging in"? 402.pl: Same as 401 403.pl: "This error means that you are forbidden for some reason to see this page." - could be worded better ('for some reason') 404.pl: "This message can have following reasons" - doesn't really make sense "An internal link in our catalog home page is broken and the page does not exist" - are the words 'home page' necessary here? 500.pl: "An error occurred while try to process your request." - should say 'trying' -- You are receiving this mail because: You are watching all bug changes.

1 8