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

[Bug 21708] New: Editing a record moves field 999 to first in the marcxml
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '20

16 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21708 Bug ID: 21708 Summary: Editing a record moves field 999 to first in the marcxml Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: pasi.kallinen(a)joensuu.fi QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl 1) Import or create a new record. 2) Examine the marcxml of that record in the database - the fields are in the correct numerical order. 3) Edit the record - no need to change any data, just save it. 4) Examine the marcxml in the database - the 999 field is now right after leader and before 001. This is due to TransformHtmlToMarc in C4/Biblio.pm, specifically the $param eq 'biblionumber' case, which pushes the param in the array first, and then the sub uses $record->append_field() Perhaps the array should be sorted by field tag before appending the fields? AFAIK, this doesn't really show up anywhere in Koha, but if you ever edit the records via a script using MARC::Record, new fields cannot be easily inserted into correct position. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 38

[Bug 24856] New: invalid itemtypes.imageurl in fr-FR sample data
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '20

16 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24856 Bug ID: 24856 Summary: invalid itemtypes.imageurl in fr-FR sample data Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: minor Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org in installer/data/mysql/fr-FR/3-LecturePub/sample_itemtypes.sql and installer/data/mysql/fr-FR/4-Conservation/sample_itemtypes.sql the values of imageurl point to non-existent images. -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 8132] Batch delete tool deletes items with holds on them
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '20

16 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8132 --- Comment #64 from Victor Grousset/tuxayo <victor(a)tuxayo.net> --- > => delete of item from B4 is *not* blocked - there is a hold but it is not found I don't get it. No sign of something not being found. I have this: https://pic.infini.fr/RLxIM2cL/eYdtLmXE.png (temporary hosting for 90 days) > 3/ Remove the biblio-level hold The biblio-level hold on B2 right? I removed also the biblio-level hold on B1. > 4/ Repeat 1 > => The deletion has been effective! Is that the expected result? https://pic.infini.fr/WaQVV1Gg/rTGE1oG3.png (temporary hosting for 90 days) I guess that's not an issue. But I still have a item I can't delete. I'm not comfortable with the steps so I might have misinterpreted few things. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11300] Add a new authority linker which searches for authority links on a Z39.50 server.
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '20

16 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11300 --- Comment #33 from Phil Ringnalda <phil(a)chetcolibrary.org> --- Since the Library of Congress has separate databases (and thus separate servers, as far as Koha is concerned) for name authorities and subject authorities, it would probably save time later on to just start out with the ability to either specify more than one LinkerZ3950Server, or to specify which server to use for each authority type. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15253] Add Koha::Logger based logging for SIP2
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '20

16 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15253 --- Comment #60 from Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> --- (In reply to Kyle M Hall from comment #55) > Also modifies the log4perl.conf to lazy-open filehandles to log files, > so the same config can be used with log-files needing different > permissions. Kyle, why do you need those changes? Isn't the SIP server running with the same user as Koha? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14167] Add Koha::Logger based on Log4perl
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '20

16 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14167 Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |25172 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25172 [Bug 25172] Koha::Logger init is failing silently -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15253] Add Koha::Logger based logging for SIP2
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '20

16 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15253 Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=25172 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15253] Add Koha::Logger based logging for SIP2
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '20

16 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15253 Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jonathan.druart(a)bugs.koha-c | |ommunity.org Status|Signed Off |BLOCKED --- Comment #59 from Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> --- There are some things in this patch that do not look wrong (about the logger). I am trying to clean a bit this area on a separate bug report. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14708] The patron set as the anonymous patron should not be deletable.
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '20

16 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14708 --- Comment #11 from Andrew Fuerste-Henry <andrew(a)bywatersolutions.com> --- This technically works, but: - When merging patrons, I am able to merge another patron into my anonymous patron. Is this what we want? Could be, just wanted to make sure it'd been considered. - When I try to merge my anonymous patron into someone else, it fails as desired but the error given is "No valid patrons to merge were found." Would be nice to have something more specific about why the action cannot be completed. - When attempting to include the anonymous patron in a batch delete, Koha does not delete them and does not tell you why. This is really a larger issue, as that's standard batch patron delete behavior. I'm really just taking this opportunity to stump for bug 24483, which suggests adding some feedback about who wasn't batch deleted and why. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 17143] New: Popup Notification for decreaseloanhighholds preference
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '20

16 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17143 Bug ID: 17143 Summary: Popup Notification for decreaseloanhighholds preference Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: jzairo(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com If you have an item that meets the holds requirement by the decreaseloanhighholds preference, but doesn’t get a decrease in the actual checkout period; you still get a popup notification that the high demand feature is being used and the loan period will be decreased. The notification shouldn't populate if the decreased loan period matches or is higher than the original loan period. The current behavior in the system looks at the the number of holds and doesn't take the loan periods with an equal value into consideration when enforcing the preference. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5