February 2020 - Koha-bugs - lists.koha-community.org

[Bug 17229] New: ILS-DI HoldTitle and HoldItem should check if patron is expired
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '21

11 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17229 Bug ID: 17229 Summary: ILS-DI HoldTitle and HoldItem should check if patron is expired Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: minor Priority: P5 - low Component: Web services Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org ILS-DI HoldTitle and HoldItem don't check patron category setting BlockExpiredPatronOpacActions. -- You are receiving this mail because: You are watching all bug changes.

1 86

[Bug 17429] New: Document the --plack option for koha-list
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '21

11 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17429 Bug ID: 17429 Summary: Document the --plack option for koha-list Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Command-line Utilities Assignee: gmcharlt(a)gmail.com Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Bug 13791 added the --plack and --noplack options to koha-list, but forgot to document them in the man page. -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 24272] New: Add a command line script to compare the syspref cache to the database
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '21

11 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24272 Bug ID: 24272 Summary: Add a command line script to compare the syspref cache to the database Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: nick(a)bywatersolutions.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 24447] New: POD of C4::Members::Messaging::GetMessagingPreferences() is misleading
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '21

11 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24447 Bug ID: 24447 Summary: POD of C4::Members::Messaging::GetMessagingPreferences() is misleading Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: Academy Severity: minor Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org Part of the POD for this subroutine looks like this: 42 my $preferences = C4::Members::Messaging::GetMessagingPreferences( { borrowernumber => $borrower->{'borrowernumber'}, 43 message_name => 'DUE' } ); 44 45 my $preferences = C4::Members::Messaging::GetMessagingPreferences( { categorycode => 'LIBRARY', 46 message_name => 'DUE' } ); It looks like the value for message_name should be a value from letter.code, but it should be a name from message_attributes.message_name: 75 AND message_transports.is_digest = borrower_message_preferences.wants_digest 76 WHERE message_attributes.message_name = ? 77 END_SQL 78 79 my @bind_params = ( $params->{'message_name'} ); Note: This subroutine is set to be renamed and moved by Bug 18595, but the POD seems to be untouched there. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 22152] New: Hide printing the tools navigation when printing reports
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '21

11 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22152 Bug ID: 22152 Summary: Hide printing the tools navigation when printing reports Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Hide the navigation showing up on the left side when printing a report page. (see 22147 for reference) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 20702] New: Bind results of GetHostItemsInfo to the EasyAnalyticalRecords pref
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '21

11 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20702 Bug ID: 20702 Summary: Bind results of GetHostItemsInfo to the EasyAnalyticalRecords pref Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org As a follow-up of bug 20697 restricting the call to GetAnalyticsCount when the preference is enabled, and resolving an associated Zebra error. GetHostItemsInfo is part of the easy analytics feature from bug 5528. We can either bind all calls of this sub to the preference, or return an empty list when the pref is disabled. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 24222] New: Simplify interface for adding/changing mappings
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '21

11 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24222 Bug ID: 24222 Summary: Simplify interface for adding/changing mappings Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: mkstephens(a)lancasterseminary.edu All search fields are in a single group and are not marked as being strictly for authorities or bibliographic records. On the search engine configuration page, when adding mappings to either the bibliographic records tab or the authorities tab, all search fields are available from the drop down menu at the bottom of the page. It would be really nice if there was a way to distinguish between the two groups of search fields so that these drop down menus would only show the fields for that record type. An alternative might be to reconfigure the way this page displays. Show the tables in a collapsed view based on search field. Expand a search field to see its mappings along with an empty field with "+ Add". This solution would allow a user to add mappings under the appropriate search field without having to manually select the field from a drop down.This would also make it easier to double-check to make sure you're entering the correct mapping since you'd be entering it in context, instead of at the bottom of a long list. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 20238] New: Show description of ITEMTYPECAT instead of code in itemtypes summary table
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '21

10 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20238 Bug ID: 20238 Summary: Show description of ITEMTYPECAT instead of code in itemtypes summary table Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When working with grouped item types using ITEMTYPECAT authorised values, looking at the item types table, it shows the code, not the description. On editing an item type, we show the description - so there is some confusing mismatch there. Both should show the description. To check: - Add a value to the ITEMTYPECAT authorised value category - Edit an item type and pick that value as search category - Save - Verify the code shows up in the table, but not the description -- You are receiving this mail because: You are watching all bug changes.

1 34

[Bug 23816] New: Password Enhancements
by bugzilla-daemon＠bugs.koha-community.org 09 Feb '21

09 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23816 Bug ID: 23816 Summary: Password Enhancements 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: joy(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Allow specified categories to be exempt from the system preferences of "Require Strong Password" and "Minimum Password Length". The goal is to force staff to have long complex passwords while simultaneously allowing patrons to have non-strong, shorter passwords if they wish. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 112

[Bug 23019] New: Ability to create 'matching profiles' when importing records
by bugzilla-daemon＠bugs.koha-community.org 09 Feb '21

09 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23019 Bug ID: 23019 Summary: Ability to create 'matching profiles' when importing records Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: joy(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- This development will allow you to have the ability to create “matching profiles” for use on the “Stage MARC Records for Import” screen. This would make it possible to choose a profile rather than manually filling in each of the fields for record type, encoding, record and item matching rules and actions each time a batch of MARC records is imported. For example, we might create “matching profiles” for different vendors or formats, and it would save time to select the appropriate profile (maybe from a drop-down list on the page) and have the fields populate automatically. Specs: Ability to set up profiles and save them while working in the Tools->StageMarcRecords module. Ability to manage/edit profiles in the Admin area (similar to Record->Matching Rules). Create an API to pull the profile data into Import Tool when selected on the Import Screen. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 93