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

[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 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 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 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 9743] New: Mandatory opac hold notes under specified conditions
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '16

11 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9743 Bug ID: 9743 Summary: Mandatory opac hold notes under specified conditions Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl CC: gmcharlt(a)gmail.com Make new opac holds notes mandatory under conditions controlled by syspref and depending on record status. To illustrate: we examine MARC21 300$a; if it contains multiple parts/volumes, but there is only one item, we ask the user to specify a part in the notes. In this case we could implement by: call this situation reason 1, add it in code and template, and specify reason 1 in the syspref. The syspref may contain a number of such reasons like: 1,2&3,4 meaning check successively 1, or 2 and 3, or 4 for new hold requests. This allows for future extension and flexible configuration. When extending this further, we should probably add a small interface on top of the syspref instead of typing 1,2&3 etc. but imo this may be sufficient to start with. This development is part of bug 9721 (umbrella report for hold changes to meet special library needs). The patch builds on bug 9722 which allows opac users to add hold notes. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 56

[Bug 7440] New: Vestiges of NoZebra should be removed
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '16

11 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7440 Bug #: 7440 Summary: Vestiges of NoZebra should be removed Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: major Priority: P3 Component: Searching AssignedTo: gmcharlt(a)gmail.com ReportedBy: jcamins(a)cpbibliography.com QAContact: ian.walls(a)bywatersolutions.com Depends on: 6227 NoZebra has been deprecated since 3.4.0. It is time to remove the vestiges of NoZebra from the code and eliminate the syspref so that people stop thinking they can use it. -- 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 34

[Bug 11324] New: "Delete All Items" fails except on "Normal Tab" 3.14
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '16

08 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11324 Bug ID: 11324 Summary: "Delete All Items" fails except on "Normal Tab" 3.14 Change sponsored?: --- Product: Koha Version: 3.14 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: library(a)stas.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com "Delete all items" on Edit dropdown menu when viewing a biblio record will only delete records when in the "Normal" tab. When viewing another tab, clicking this command does nothing. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 10551] New: Merging records allows duplicaton of non-repeatable subfields
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '16

08 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10551 Bug ID: 10551 Summary: Merging records allows duplicaton of non-repeatable subfields Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de CC: jcamins(a)cpbibliography.com, m.de.rooy(a)rijksmuseum.nl To test: - Add 2 records to a list - Go to the list, select those 2 and merge them using the button on top - Select either record as the destination record - Select 245$a from the second tab to be also added to the record - Verify no warning is given. - Finish merge process. - Verify that the new record shows 2 245$a subfields. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 8000] New: Test mode for notices
by bugzilla-daemon＠bugs.koha-community.org 07 Jan '16

07 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8000 Priority: P5 - low Change sponsored?: --- Bug ID: 8000 Assignee: henridamien(a)koha-fr.org Summary: Test mode for notices QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: wizzyrea(a)gmail.com Hardware: All Status: NEW Version: unspecified Component: Notices Product: Koha Koha should have a test mode for notices so a library can see what all of the notices will look like before go live, or to troubleshoot difficulties. Test mode would do the following: -redirect all mails to a specified (by default the defined library email address) address - Ability to specify a patron as a "test" patron -- You are receiving this mail because: You are watching all bug changes.

1 114

[Bug 10744] New: ExpireReservesMaxPickUpDelay has minor workflow conflicts with hold(s) over report
by bugzilla-daemon＠bugs.koha-community.org 07 Jan '16

07 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10744 Bug ID: 10744 Summary: ExpireReservesMaxPickUpDelay has minor workflow conflicts with hold(s) over report Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: gmcharlt(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Turning on ExpireReservesMaxPickUpDelay means that the hold(s) over part of the holds awaiting pickup report (circ/waitingreserves.pl) can be confusing. Specifically, if the hold cancellation cronjob runs before the library opens, the hold(s) over list will never contain any contents -- all of the holds that have hit the max pickup delay will have been cancelled. Having a report that will never produce results can be (and has been for at least one of our customers) confusing. I can think of a couple options for improving this: - suppress the display of the hold(s) over tab if ExpireReservesMaxPickUpDelay is on. - have the hold(s) over report display the list of waiting holds that were canceled - today or - the last time cancel_expired_holds.pl was run - as alternative or in conjunction with one of the other options, have cancel_expired_holds.pl create a report of cancelled waiting holds to assist with clearing the items from the holds shelf -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13