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

[Bug 18559] New: Koha:: Clubs - methods should not get the return type in parameter
by bugzilla-daemon＠bugs.koha-community.org 18 Sep '23

18 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18559 Bug ID: 18559 Summary: Koha::Clubs - methods should not get the return type in parameter Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: kyle(a)bywatersolutions.com Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 12461, 18553 Koha::Clubs->get_club_enrollments and Koha::Clubs->get_enrollable_clubs take a $return_scalar parameter. The return value type should not be a parameter. We should return _new_from_dbic or Koha::Objects->search in any cases. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12461 [Bug 12461] Add patron clubs feature https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18553 [Bug 18553] Incorrect "Loading..." tag on moremember.tt when no clubs defined -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 20502] New: Record URL broken, when there is more than one 856 on the record
by bugzilla-daemon＠bugs.koha-community.org 18 Sep '23

18 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20502 Bug ID: 20502 Summary: Record URL broken, when there is more than one 856 on the record Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Course reserves Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: kyle(a)bywatersolutions.com When there is more than one 856 in the record, the Record URL in the course reserves table creates a broken link. Example form the sample data: http://www.loc.gov/catdir/enhancements/fy1010/2009039494-b.html%20|%20http:… -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 30

[Bug 18768] New: Add the ability to authenticate patrons against other ILSs via SIP2
by bugzilla-daemon＠bugs.koha-community.org 18 Sep '23

18 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18768 Bug ID: 18768 Summary: Add the ability to authenticate patrons against other ILSs via SIP2 Change sponsored?: Sponsored Product: Koha Version: master Hardware: All URL: https://github.com/kylemhall/Koha/commits/sip2_client OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org This feature allows Koha use to use other ILSs as an authenticate target in a manner someone similar to how we authenticate LDAP. It allows Koha to be configured with a list of external SIP2 servers to authenticate against. Koha will find the correct server to use based on the order and cardnumber prefix chosen, send a patron information request and handle the patron login based on the response. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 17350] New: Add option to delete data stored in saved_reports
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '23

16 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17350 Bug ID: 17350 Summary: Add option to delete data stored in saved_reports Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org This is a follow-up bug to bug 14435 which reactivates an old feature that allows you to store the results of a run report in saved_reports. Now that this will work again, there should also be an option to clean up the data stored - either from the script, the GUI or ideally from both. -- You are receiving this mail because: You are watching all bug changes.

1 23

[Bug 20636] New: Add unit tests to verify borrowernumber columns are mapped for patron merging
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '23

16 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20636 Bug ID: 20636 Summary: Add unit tests to verify borrowernumber columns are mapped for patron merging Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 9302 We should add unit tests to check that: A) Automate checking that all borrowernumber fields that are foreign keys to borrowers.borrowernumber are in our mapping B) Automate testing all non-fk fields that are *named* borrowernumber are in our mapping. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9302 [Bug 9302] Add ability to merge patron records -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 20677] New: strict.t and valid-templates.t fail with Devel::Cover is used
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '23

16 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20677 Bug ID: 20677 Summary: strict.t and valid-templates.t fail with Devel::Cover is used Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org koha_1 | t/db_dependent/00-strict.t (Wstat: 65280 Tests: 683 Failed: 0) koha_1 | Non-zero exit status: 255 koha_1 | Parse errors: Tests out of sequence. Found (1) but expected (2) koha_1 | Tests out of sequence. Found (2) but expected (3) koha_1 | Tests out of sequence. Found (3) but expected (4) koha_1 | Tests out of sequence. Found (2) but expected (5) koha_1 | Tests out of sequence. Found (4) but expected (6) koha_1 | Displayed the first 5 of 683 TAP syntax errors. koha_1 | Re-run prove with the -p option to see them all. koha_1 | xt/author/valid-templates.t (Wstat: 65280 Tests: 853 Failed: 0) koha_1 | Non-zero exit status: 255 koha_1 | Parse errors: Tests out of sequence. Found (1) but expected (3) koha_1 | Tests out of sequence. Found (3) but expected (4) koha_1 | Tests out of sequence. Found (4) but expected (5) koha_1 | Tests out of sequence. Found (5) but expected (6) koha_1 | Tests out of sequence. Found (2) but expected (7) -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 20713] New: Add Russian UNIMARC authority structures
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '23

16 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20713 Bug ID: 20713 Summary: Add Russian UNIMARC authority structures Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: synapse.ova(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr Right now there is no russian UNIMARC authority structures. There is russian folder, but the structure is in ukrainian (partly in french). Steps to Reproduce: 1. Install ru-RU language 2. Run installer using ru-RU / Russian language 3. Select UNIMARC MARC flavour 4. Verify mandatory files are loaded without problems 5. Check adding of some authority type (for example, Name Personal — Имя лица) Actual Results: Installed structures in ukrainian language. Only default structure is mandatory. Expected Results: Installed russian structures without problems. All structures used in code are installed as mandatory Additional Information: C4\AuthoritiesMarc.pm (lines 396-409) checks for some specific authority types. These should be considered as mandatory for UNIMARC installations. Structures SAUT, SCO and STU have the same auth_tag_to_report as other structures and are not present in latest french structure → so could be safely removed All these structures (unlike french) have visible fields from unimarc 5th block (related access point). Because we can relate current record with any other authority type (for example Name Personal with Geographical Name). These authority structures can be added to almost any Koha version -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 20716] New: UDC Classification Colon search
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '23

16 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20716 Bug ID: 20716 Summary: UDC Classification Colon search Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: paul.longbottom(a)snh.gov.uk QA Contact: testopia(a)bugs.koha-community.org We have changed system preference (IntranetNumbersPreferPhrase) from "don't" to "do", system preference for the OPAC the (OPACNumbersPreferPhrase) from "don't" to "do". To allow more precise searching of our Universal Decimal Classification (UDC) classification which has led to greater precision for our retrieved results from searching. However in the UDC classification notation there is used a colon which means that both concepts in a title have equal weight. A search for the UDC call number 34:339.5(411) gets no hits whereas if you substitute a point for a colon the results can be obtained 34.339.5(411). Can the colon symbol be validated as a recognised character in the search string for the call number phrase search. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 20717] New: Add captcha on OPAC user login screen.
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '23

16 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20717 Bug ID: 20717 Summary: Add captcha on OPAC user login screen. 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: amitddng135(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Add captcha on OPAC user login screen. -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 20733] New: Delete api key or add a deleted flag?
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '23

16 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20733 Bug ID: 20733 Summary: Delete api key or add a deleted flag? Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST api Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org >From bug 20612 comment 23. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3