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

[Bug 26634] New: Hold rules applied incorrectly when All Libraries rules are more specific than branch rules
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '21

11 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26634 Bug ID: 26634 Summary: Hold rules applied incorrectly when All Libraries rules are more specific than branch rules Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com To recreate: - At the All Libraries level, create a circ rule for a specific patron category and a specific item type that only allows 1 hold - At the branch-specific level for Branch A, create an All/All rule that allows 2 holds - confirm ReservesControll is set to patron's library - find a patron from Branch A of the category for which you made your rule - find two bibs with items of the itype got which you made your rule - place a hold on one bib. success! - try to place a hold on the second bib. you're told you cannot because the patron is only allowed 1 hold We should be enforcing the All/All rule for Branch A. If we put in a rule for the category and itype for Branch A, that rule will be enforced and we'll be allowed a second hold. In GetHoldRule, we tell get_effective_rules to return those rules ordered by 'categorycode', 'itemtype', 'branchcode.' We should just let get_effective_rule handle that ordering on its own. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 36

[Bug 26755] New: Make the guarantor search popup taller
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '21

11 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26755 Bug ID: 26755 Summary: Make the guarantor search popup taller Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: barbara.johnson(a)bedfordtx.gov QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 112042 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=112042&action=e… Current popup window When searching for a guarantor to add to a guarantee you can't see the search results in the the popup search window (guarantor_search.pl) without scrolling. Although the popup window shouldn't be too tall it would be helpful to display at least the first one or two entries which could eliminate extra scrolling and allow staff to select the record more efficiently. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 27047] New: Purchase suggestions can not search
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '21

11 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27047 Bug ID: 27047 Summary: Purchase suggestions can not search Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: apirak(a)punsarn.asia QA Contact: testopia(a)bugs.koha-community.org test plan: [1] Log in to Opac [2] Go to your purchase suggestions menu [3] Create purchase suggestions Ex. "title: harry potter" [4] Go to purchase suggestions menu [5] Type "harry potter" In <search for> field [6] The search result is not show only "harry potter" but show all purchase suggestions list. -- You are receiving this mail because: You are watching all bug changes.

1 20

[Bug 27204] New: SIP patron information request with fee line items returns incorrect data
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '21

11 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27204 Bug ID: 27204 Summary: SIP patron information request with fee line items returns incorrect data Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com There are two primary issues I've identified with requesting line items for fees via SIP: 1) The end boundary is incorrect. For example, if send a request with a BP ( starting item) of 1, and a BQ (end item) of 1, I should get just the first item. Instead I will get two items 2) Our SIP server does not check bounds. For example, if I have 3 fines, but I send a BP of 1 and a BQ of 5, I will get back 5 AVs, two of them being "empty" because the patron only has 3 accountlines! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 27261] New: PatronSelfRegistrationBorrowerUnwantedField should exclude branchcode
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '21

11 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27261 Bug ID: 27261 Summary: PatronSelfRegistrationBorrowerUnwantedField should exclude branchcode Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org If you check branchcode in PatronSelfRegistrationBorrowerUnwantedField and try to submit the self registration form you will get a ISE. Bug 22844 simplifies the process of selecting database columns. Bug 17364 adds the ability to allow exclusions. We can now easily exclude branchcode from PatronSelfRegistrationBorrowerUnwantedField and probably should do that/ -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 27321] New: Make excluded database columns in system preferences more clearly disabled
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '21

11 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27321 Bug ID: 27321 Summary: Make excluded database columns in system preferences more clearly disabled Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Bug 17364 added the ability to exclude database columns in system preferences. When something is disabled the checkbox is disabled but it is still hard to tell its disabled because the corresponding label remains the same color as all the others. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[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 24894] New: Allow configuration of search dropdowns
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '21

11 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24894 Bug ID: 24894 Summary: Allow configuration of search dropdowns Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Currently, we can customize the indices included in the basic and advances search dropdowns via jQuery. It'd be great to have some more user-friendly interface for this. It might make sense to tie it into the Elastic search engine config page, or to make it its own system preference. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 26298] New: If MaxItemsToProcessForBatchMod is set to 1000, the max is actually 999
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '21

11 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26298 Bug ID: 26298 Summary: If MaxItemsToProcessForBatchMod is set to 1000, the max is actually 999 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org So this is similar to bug 10163, but I don't think it's the same thing. I noticed that if you have 1000 in MaxItemsToProcessForBatchMod, and you try to process 1000 items, there's an error message "Too many items (1000): You are not allowed to edit more than 1000 items in a batch." The message itself is a bit confusing because 1000 is not "more than" 1000. And you're probably thinking "well, just put 999 items in your file and voilà!", but if you batch modify using the reports, the options are 10, 20, 50, 100, 200, 300, 400, 500, and 1000. If you have a lot of batches to do, the difference between 500 and 1000 is double the work. To reproduce: 1- Set MaxItemsToProcessForBatchMod to 1000 2- Go to Reports 3- Make a report for itemnumbers that will give you at least 1000 items (ex. SELECT itemnumber FROM items) 4- Save and run the report 5- In "Rows per page", choose 1000 6- Click on "Batch operations with 1000 visible records" > Batch item modification 7- Notice that the item modification form isn't there and that the message says "Too many items (1000): You are not allowed to edit more than 1000 items in a batch." -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17