April 2023 - Koha-bugs - lists.koha-community.org

[Bug 32164] New: Add link to MARC modification templates to batch record modification page
by bugzilla-daemon＠bugs.koha-community.org 16 May '23

16 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32164 Bug ID: 32164 Summary: Add link to MARC modification templates to batch record modification page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: Academy Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When no MARC modification templates are defined and you open up the page for the batch record modification, we show a hint: /cgi-bin/koha/tools/batch_record_modification.pl No MARC modification template is defined. You have to create at least one template for using this tool. It would be nice if we linked to the MARC modification tools there directly. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 28852] New: Extend options in SelfCheckoutByLogin syspref
by bugzilla-daemon＠bugs.koha-community.org 16 May '23

16 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28852 Bug ID: 28852 Summary: Extend options in SelfCheckoutByLogin syspref Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Right now, the koha selfcheck will only allow use of either cardnumber or username+password. We should extend those options. First, it'd be good to make the password requirement a separate question, thereby allowing cardnumber+password and username alone. Second, we should allow the possibility that a unique patron attribute might be used at checkout on a selfcheck (with or without a password). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 33521] New: Column item_priority in OPAC holdingst can never show
by bugzilla-daemon＠bugs.koha-community.org 16 May '23

16 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33521 Bug ID: 33521 Summary: Column item_priority in OPAC holdingst can never show Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I was trying to document what all the columns in Administration > Table settings > OPAC > holdingst were exactly and I'm having trouble with item_priority. Katrin looked at the opac-details.tt template and said there was a logic error. To test: 1. Change OPACShowHoldQueueDetails to show holds and priority levels 2. Place an item-level hold on an item 3. In the OPAC, log in as the user with the hold 4. Go to the bibliographic record --> In the holdings table, there is an "Item holds" column with hold AND priority information but no Item hold priority column I wonder if the column is useful at all... I don't mind having both information in the same column. But I would only show the item holds column if there is an item-level hold. Right now it shows if there is any hold, even just a record-level hold, and I find it confusing. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 31576] New: Cannot place hold even when AllowHoldPolicyOverride should allow it
by bugzilla-daemon＠bugs.koha-community.org 16 May '23

16 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31576 Bug ID: 31576 Summary: Cannot place hold even when AllowHoldPolicyOverride should allow it Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests 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 This bug appears in Koha 21.11 only ( behavior changes to bug 31575 with 22.05 and later ). If only some item holds can be forced, but others cannot ( because they have to pickup locations ), the place holds button remains disabled even though the hold can be placed. Test Plan: 1) Set one circ rule to allow 0 holds 2) For Library A, set "Hold pickup library match" to "item's hold group" 3) Enable AllowHoldPolicyOverride 4) Set ReservesControlBranch to "item's home branch" 5) Create a record with an item for Library A, one for Library B, and one for Library C This should create a scenario where A's item cannot be held, and B and C's items must be overridden 6) Note you cannot place the hold because the button is disabled. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18

[Bug 33328] New: x-marc-schema should be renamed x-record-schema
by bugzilla-daemon＠bugs.koha-community.org 16 May '23

16 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33328 Bug ID: 33328 Summary: x-marc-schema should be renamed x-record-schema Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com CC: tomascohen(a)gmail.com Before it is too late, we need to rename the HEADER param. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 33629] New: allow pbuilder to use network via build-git-snapshot
by bugzilla-daemon＠bugs.koha-community.org 16 May '23

16 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33629 Bug ID: 33629 Summary: allow pbuilder to use network via build-git-snapshot Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: mtj(a)kohaaloha.com QA Contact: testopia(a)bugs.koha-community.org CC: mtj(a)kohaaloha.com this bug tracks the progress of allowing pbuilder to use network via build-git-snapshot -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 33488] New: Branch transfer limits should have an index on fromBranch
by bugzilla-daemon＠bugs.koha-community.org 16 May '23

16 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33488 Bug ID: 33488 Summary: Branch transfer limits should have an index on fromBranch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org In a consortium with many libraries, the branch transfer limits can become complex and have many rows - we have seen 750k+ At this size, searching on limits can take 1/2 a second or more - and when a record has many items this begins to add up fast Adding an index to the fromBranch column greatly reduces the cost of a lookup: CREATE INDEX fromBranch_index ON branch_transfer_limits (fromBranch); -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 32921] New: SelfCheckTimeout doesn't logout if SelfCheckReceiptPrompt modal is open
by bugzilla-daemon＠bugs.koha-community.org 16 May '23

16 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32921 Bug ID: 32921 Summary: SelfCheckTimeout doesn't logout if SelfCheckReceiptPrompt modal is open Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: 1. Set the 'SelfCheckTimeout' system preference to something low for testing. 2. Make sure 'SelfCheckReceiptPrompt' is set to 'Show'. 3. Log in to SCO and press finish but leave the modal open. 4. Wait until the 'SelfCheckTimeout' time has expired, nothing happens. This is a problem for some libraries because not every patron realizes there is another action after pressing 'Finish' and they walk away. Leaving open a screen that shows their username and checkouts. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 33545] New: Adding faceting to API result sets
by bugzilla-daemon＠bugs.koha-community.org 16 May '23

16 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33545 Bug ID: 33545 Summary: Adding faceting to API result sets Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com CC: tomascohen(a)gmail.com Sometimes it would be great to have some additional data about the overall results returned by an api resultset query. For example, if an API query returns a list of things that include a library they're attached to, it might be nice to be able to get a list of all libraries that appear in the resultset. (not just the current page). This way, we could display a select filter of just the libraries associated with the current api request to allow further filtering.. i.e. facetting. We floated the idea of x-koha-facets for requesting this, but we haven't yet come up with a good way to get this data or return it. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 33529] New: Increase flexibility of action buttons in tables
by bugzilla-daemon＠bugs.koha-community.org 16 May '23

16 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33529 Bug ID: 33529 Summary: Increase flexibility of action buttons in tables Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart+koha(a)gmail.com Reporter: matt.blenkinsop(a)ptfs-europe.com CC: jonathan.druart+koha(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com In the usage statistics modules there is a need for some additional "action" buttons on top of the standard "edit" and "delete" (e.g. "Download" or "Run now"). This bug changes the way the action buttons are passed to the new KohaTable component so that extra customisation can be added where needed -- You are receiving this mail because: You are watching all bug changes.

1 11