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

[Bug 20107] New: Editing a public note in Course Reserves
by bugzilla-daemon＠bugs.koha-community.org 28 Mar '20

28 Mar '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20107 Bug ID: 20107 Summary: Editing a public note in Course Reserves Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Course reserves Assignee: koha-bugs(a)lists.koha-community.org Reporter: jzairo(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 71076 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=71076&action=ed… cgi-bin/koha/course_reserves/add_items.pl If you add a public note in the course reserve module in the item on cgi-bin/koha/course_reserves/add_items.pl it will appear on the OPAC. If you need to edit or remove that public note located at cgi-bin/koha/course_reserves/add_items.pl you can click edit under the actions column on cgi-bin/koha/course_reserves/course-details.pl. When editing, the field will appear blank, even though you may have an existing note in there. You can add a new note in the blank field which will replace the existing note. Currently the only way to erase the existing note in there is to create a new note or type a blank space which will remove the existing note. it would be helpful to be able to see what is actually in the note field on cgi-bin/koha/course_reserves/add_items.pl to edit or remove. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 18757] New: Problem when importing only items in MARC records
by bugzilla-daemon＠bugs.koha-community.org 28 Mar '20

28 Mar '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18757 Bug ID: 18757 Summary: Problem when importing only items in MARC records Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org When importing records with Stage MARC records for import, one can use matching rules to only import items into existing records. Those imported items are stored as XML to be staged. The bug is that when MARC Flavour is UNIMARC the XML serialization fails because its is looking in field 100$a which does not exist. -- You are receiving this mail because: You are watching all bug changes.

1 24

[Bug 17915] New: warning in Stage MARC records for import when matching rule with offset
by bugzilla-daemon＠bugs.koha-community.org 27 Mar '20

27 Mar '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17915 Bug ID: 17915 Summary: warning in Stage MARC records for import when matching rule with offset Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org When using Stage MARC records for import with a matching rule where an offset is defined, the input string may be empty or shorter than the offset. This generated a warning : stage-marc-import.pl: substr outside of string at /home/koha/src/C4/Matcher.pm line 822. -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 19359] New: Reporting module selenium test
by bugzilla-daemon＠bugs.koha-community.org 23 Mar '20

23 Mar '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19359 Bug ID: 19359 Summary: Reporting module selenium test Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: alexbuckley(a)catalyst.net.nz Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org The test patch attached to this bug report will test the following functionality: * Log into the Koha intranet * Navigate to the Reports module * Create a custom catalog report report * Run the report -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 18715] New: Enhance Koha feature release change tool by making sysprefs searchable, and announce the new version in staff client with translatable news item
by bugzilla-daemon＠bugs.koha-community.org 23 Mar '20

23 Mar '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18715 Bug ID: 18715 Summary: Enhance Koha feature release change tool by making sysprefs searchable, and announce the new version in staff client with translatable news item Change sponsored?: Sponsored Product: Koha Version: 17.05 Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: alexbuckley(a)catalyst.net.nz Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 18645 Take the bug 18645 new feature and add the following three enhancements: * Display the new sysprefs of the current version in a new tab in the About page for easy future access. * Make version number a search criterion for system preferences through adding a new column 'version' to the 'systempreference' table and including it in the search url * Announcing the new version on the staff client through creating a news item at the end of the installation process, this news item will appear for all libraries. This news item will contain standard text with the release number and links to new features and preferences. Library staff will be able to edit it adding some library specific information. The text will be translated to the language chosen at the start of the installation process. Thanks to Marc Veron for these ideas Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18645 [Bug 18645] Creation of Koha feature release change tool displayed after running Koha update -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 17221] New: orphan comma in shelf browser
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '20

18 Mar '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17221 Bug ID: 17221 Summary: orphan comma in shelf browser Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: ephetteplace(a)cca.edu QA Contact: testopia(a)bugs.koha-community.org Created attachment 54997 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=54997&action=ed… screenshot of bug Example screenshot attached, here's the bib record in our catalog: https://library.cca.edu/cgi-bin/koha/opac-detail.pl?biblionumber=21729&shel… Basically, since starting_homebranch is null in the template file, nothing is printed out, but the next IF condition wrongly assumes that the first must have been true and prints out a comma before it's text string. Steps to recreate: - in settings, set ShelfBrowserUsesHomeBranch to "Don't Use" - set ShelfBrowserUsesLocation to "Use" - visit an item, click the "Browse shelf" link in the Holdings' tab's Call Number column - note the extraneous comma in the <h5> tag that appears Patch coming shortly, it appears that simply adding an additional condition around the comma itself should resolve this problem. -- You are receiving this mail because: You are watching all bug changes.

1 23

[Bug 18933] New: Unable to set SMS number in OPAC messaging preferences to empty
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '20

18 Mar '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18933 Bug ID: 18933 Summary: Unable to set SMS number in OPAC messaging preferences to empty Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org This is inconsistent with the Staff Client side, where the SMS number can be set to empty. Also I think that since this is borrower information, it should be their choice whether they provide this info or not and should have the ability to remove it -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 18230] New: Generate Koha::Patron:: Modification verification_token in ->new
by bugzilla-daemon＠bugs.koha-community.org 17 Mar '20

17 Mar '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18230 Bug ID: 18230 Summary: Generate Koha::Patron::Modification verification_token in ->new Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: lari.taskula(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org Currently verification_token is generated outside of the class. Move this logic into Koha::Patron::Modification->new. -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 17424] New: REST API: Preference to control access to own objects without permission
by bugzilla-daemon＠bugs.koha-community.org 17 Mar '20

17 Mar '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17424 Bug ID: 17424 Summary: REST API: Preference to control access to own objects without permission Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org Introduce a preference to enable/disable access to own objects for patron's without required permissions. Bug 14868 added "allow-owner" parameter that allows owner of the object to perform operations on themselves even if they do not have required permissions to otherwise do so (e.g. get own patron data or renew your own checkouts even if you don't have borrowers/circulating permissions). This means patrons can perform basic OPAC operations via REST API. However, there should be an option to disable this functionality; as Katrin pointed out in https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13895#c43 , > I can imagine both happening: > - libraries wanting to shut down any OPAC account functionality, but still > be able to renew in staff, so the circulation conditions are set up this > way. In this case, there should be a way to lock the API (opacuserlogin > might be a way) > - libraries shutting down the OPAC, because they use something else like an > external discovery layer. In this case they'd still want to use the API, but > might turn off the OPAC as far as possible. I propose a system preference for enabling/disabling access to own objects in REST API. This way libraries can disable opacuserlogin and any OPAC API functionality with the new preference. In the second case, libraries can disable opacuserlogin but still allow OPAC functionality via REST API. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 17479] New: REST API: Save information on owner access
by bugzilla-daemon＠bugs.koha-community.org 17 Mar '20

17 Mar '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17479 Bug ID: 17479 Summary: REST API: Save information on owner access Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org There are two ways of accessing a resource via REST API; either: - you have the required permission - you do not have the permission but you are owner of the object, e.g. you want to GET your own patron information In many cases we want to perform additional operations if the user is accessing his own object. Usually this additional operation is checking a system preference. Example: Patron wants to update his own patron information via REST API. We have to check OPACPatronDetails system preference for this. If it is on, we should forward the changes for approval from a librarian. Currently, in controller, we can check this opac-like access by checking that the user does not have permissions and that the patron he is accessing is himself. This would require another haspermission() call. Instead, we could set a flag into $c->stash in Koha/REST/V1.pm in the case of ownership access. After this, in controller, we only need to check $c->stash for this flag. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22