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

[Bug 11175] Show the parent record's component parts in the detailed views
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '21

25 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11175 Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #126745|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 28858] New: Table Settings should control Checked out by field in Circulation history
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '21

25 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28858 Bug ID: 28858 Summary: Table Settings should control Checked out by field in Circulation history Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: sally.healey(a)cheshiresharedservices.gov.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Koha Administration > Table Settings controls all whether fields are visible/can be toggled by users. 'Checked out by' is solely controlled by a system preference (RecordStaffUserOnCheckout) - and is not an option in the Table Settings controls. To replicate: - Set system preference: RecordStaffUserOnCheckout to 'record' - Check an item out to a patron - Go to that patron's Circulation history - cgi-bin/koha/members/readingrec.pl - Note that 'Checked out by' is visible and populated - Go to Koha > Administration > Table Settings - Choose Patrons - Choose Page: checkouthistory - Choose Table id: checkouthistory-table - Note that 'Checked out by' is not an option -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 29313] New: How can do the setup of HP printer using 123.hp.setup?
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '21

25 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29313 Bug ID: 29313 Summary: How can do the setup of HP printer using 123.hp.setup? Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: About Assignee: koha-bugs(a)lists.koha-community.org Reporter: butlerkaci12(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org 123.hp.setup - Ways to Connect HP Printer to Router (Wireless Setup) • Firstly, turn on your wireless printer and use the touch screen display to set up the HP printer in a wireless manner. • Now from the touch screen, press the ‘setup’ button and select the ‘network’ option from the menu. • Thereafter select the wireless network setup wizard from the ‘network’ menu. HP printer will look for the wireless routers open in the range. Select your network from the list. • Enter the detail such as WEP/WPA for the network and then press ‘done. Now press ‘OK’ to confirm the settings. Then you have to Press ‘OK’ to print the wireless test report. • The HP printer has been set up on your wireless network. • Lastly, download and install the printer driver from the 123.hp.setup page to finish the process. https://www.howdoisetup.com/hp-printer-setup -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 5528] Analytical records support
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '21

24 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5528 Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |m.de.rooy(a)rijksmuseum.nl -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11175] Show the parent record's component parts in the detailed views
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '21

24 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11175 --- Comment #473 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- I wrote two follow-ups now. WIll attach them tomorrow. But did look a bit closer to analytical records in Koha and they are quite different from what is done here. They use 773 but thats about it. So there seems to be no reason to braid(?) them together here. Making the analytics disappear when there are components. Note: the components here work with 773 and record control numbers looked up in biblio records. Analytics works different, storing item numbers(!) in 773$9. This seems to be something that we add on top of MARC21, if I understand correctly (so no default MARC21). Conclusion: We should keep them really separate from each other. Will have to add that to my follow-up still. Which should be very trivial. Katrin: Could you confirm? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11175] Show the parent record's component parts in the detailed views
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '21

24 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11175 Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Passed QA |Failed QA --- Comment #472 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- (In reply to Marcel de Rooy from comment #471) > Why pass the same biblionumber here when running through all component > records? Beginning to understand some of what happened here ;) Finally :) We still need a bit of fixing things that may have been broken during the process. Changing status. Will be submitting a follow-up. Dont touch please (today or tomorrow). -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11175] Show the parent record's component parts in the detailed views
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '21

23 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11175 --- Comment #471 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- Still thinking about this a bit, and looking here: for my $part ( @{$components} ) { $part = C4::Search::new_record_from_zebra( 'biblioserver', $part ); push @{$parts}, XSLTParse4Display( { biblionumber => $biblionumber, Why pass the same biblionumber here when running through all component records? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 29243] New: PrepareItemrecordDisplay should not be called with empty string in defaultvalues
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '21

23 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29243 Bug ID: 29243 Summary: PrepareItemrecordDisplay should not be called with empty string in defaultvalues Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major 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 Bug 27545 expanded the use of NewItemsDefaultLocation, however, it checks for $defaultvalues undefined. There are several calls that pass '' (empty string) for default values. It is expected to be a hashref, so we should pass undef if we don't have defaults. Otherwise, we get an error when NewItemsDefaultLocation is set: Can't use string ("") as a HASH ref while "strict refs" in use at /usr/share/koha/lib/C4/Items.pm line 1605. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 29193] New: DataTables only showing 20 results on checkout search and patrons search on request.pl
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '21

23 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29193 Bug ID: 29193 Summary: DataTables only showing 20 results on checkout search and patrons search on request.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Both of these pages are set to show -1 results, i.e. all results returned While this is not great for performance, it is the expected behavior and has broken in 21.05 and master To recreate: 1 - Checkout 20.11 2 - In checkout search type 'a' 3 - You get all 53 patrons 4 - Checkout master 5 - In checkout search type 'a' 6 - You get 20 patrons 7 - Sort by name 8 - There are more patrons, but you cannot page or find them except by sorting -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 28748] New: When hold is overridden cannot select a pickup location
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '21

23 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28748 Bug ID: 28748 Summary: When hold is overridden cannot select a pickup location Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Bug 28338 added a check of hold pickup locations for each hold item on a record When selecting an item that normally is not for hold there is no pickup dropdown, the hold is placed with no location To recreate: 1 - Enable AllowHoldPolicyOverride 2 - Set 'Default checkout, hold and return policy' - Hold policy 'From home library' Hold pickup library match 'Item's home library' 3 - Find a record with items from multiple libraries 4 - Attempt to place a hold on an item that normally wouldn't be allowed 5 - Notice these items have no holds dropdown 6 - Place the hold 7 - Note the pickup location is blank -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21