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

[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 12366] New: Better handling of Zebra errors when searching empty indexes
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '16

11 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12366 Bug ID: 12366 Summary: Better handling of Zebra errors when searching empty indexes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: gmcharlt(a)gmail.com Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Currently, if you turn on "OpacSuppression" (i.e. Hide) or "dontmerge" (i.e. Do), Zebra will return errors, if the OpacSuppression index is empty or if the Koha-Auth-Number index is empty. You'll encounter the "dontmerge" problem if you try to merge together two authorities when there are no biblio records in the database that have already been linked to an authority. I suppose this could be an edge case, but getting a software error on the screen saying "ZOOM error 114 Unsupported Use attribute" (addinfo: Koha-Auth-Number") from diag-set 'Bib-1" isn't really that helpful. We should either add a warning on the system preference "dontmerge" (that says that you must have one biblio already attached to an authority if you don't want errors when set to "Do") or handle the error from Zebra more gracefully. Admittedly, handling the error generated by OpacSuppression is probably harder. At the moment, I think it'll say that there are no results (as Zebra will error out). I suppose that might be the best we can do...but it's still sub-optimal. Another idea is to populate OpacSuppression with a dummy record, although that's also sub-optimal. I suppose this might just be one of the downsides of using Zebra... But a warning is probably a good idea in any case for "dontmerge", although I suspect that most people probably use the "Don't" setting, or already have at least one biblio linked to an authority... -- You are receiving this mail because: You are watching all bug changes.

1 2

[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 11700] New: C4::AuthoritiesMarc::merge enhancements/fixes
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '16

08 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11700 Bug ID: 11700 Summary: C4::AuthoritiesMarc::merge enhancements/fixes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: MARC Authority data support Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Bug 7419 patches contains several enhancements and fixes for subroutine C4::AuthoritiesMarc::merge. This bug is complicated to test so I will remove changes to this subroutine from bug 7419 and put it here. So maybe it will increase the chances to push these patches into master. -- You are receiving this mail because: You are watching all bug changes.

1 67

[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 12721] New: Wrong fieldnames or trailing | in system preference StatisticsFields lead to crash
by bugzilla-daemon＠bugs.koha-community.org 07 Jan '16

07 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12721 Bug ID: 12721 Summary: Wrong fieldnames or trailing | in system preference StatisticsFields lead to crash Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: veron(a)veron.ch QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To reproduce: 1) Edit system preference StatisticFields Set it to: location|itype|ccode Search a patron and display statistics Result: OK, statistics displas 2) Add a trailing | to StatisticFields: location|itype|ccode| Display statistics Result: Software error: Can't use an undefined value as an ARRAY reference at /usr/lib/perl5/DBI.pm line 2054. Display statistics 3) Put a space between ccode and trailing | location|itype|ccode | Display statistics Result: Statistic displays default table with Shelving locaton, Item type and Collection code 4) Remove trailing | and misspell one field: lcation|itype|ccode Display statistics Result: Software error: Can't use an undefined value as an ARRAY reference at /usr/lib/perl5/DBI.pm line 2054. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 12586] New: Record matching rules - Required match checks doesn't work with MARCXML
by bugzilla-daemon＠bugs.koha-community.org 07 Jan '16

07 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12586 Bug ID: 12586 Summary: Record matching rules - Required match checks doesn't work with MARCXML 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: olli-antti.kivilahti(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When trying to Match MARCXML-records from Zebra using Required match checks, C4::Matcher::_passes_required_checks() tries to make a MARC::Record out of MARCXML while thinking it is USMARC. This leads to matching records getting not-matched, and subsequently importing the same records again and again. Very hard to debug or create a test case. I accidentally noticed this while building an automatic acquisitions record overlay mechanism. There are no big errors, simply no match is found, even though a match exists. --------- TEST PLAN --------- 1. Create a Matcher with "Required match checks" in addition to normal checks. 2. Find matches using the C4::Matcher->get_matches() and notice that you don't find matches. 3. Somebody who is actually using this Matcher could help me out here with defining a test plan. -- You are receiving this mail because: You are watching all bug changes.

1 15