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

[Bug 2222] Field auth_subfield_structure.frameworkcode should be removed
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '22

01 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2222 --- Comment #7 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- Created attachment 132835 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=132835&action=e… Bug 2222: Adjust SQL fr-FR unimarc complet Obligatoire default I tested this sql script as follows: (sql) delete from auth_subfield_structure; delete from auth_tag_structure; delete from auth_types; (bash) mysql -h YOUR_HOST -p YOUR_CLONE < FILE_NAME Signed-off-by: Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 2222] Field auth_subfield_structure.frameworkcode should be removed
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '22

01 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2222 --- Comment #6 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- Created attachment 132834 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=132834&action=e… Bug 2222: Adjust SQL fr-FR Obligatoire file authorities_normal_marc21.sql Test plan: I tested this sql script as follows: (sql) delete from auth_subfield_structure; delete from auth_tag_structure; delete from auth_types; (bash) mysql -h YOUR_HOST -p YOUR_CLONE < FILE_NAME Signed-off-by: Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 2222] Field auth_subfield_structure.frameworkcode should be removed
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '22

01 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2222 --- Comment #5 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- Created attachment 132833 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=132833&action=e… Bug 2222: Adjust SQL en marc21/unimarc yml and sql file Test plan: Run a new install for en/marc21 testing the yml file. I tested the unimarc sql file as follows: (sql) delete from auth_subfield_structure; delete from auth_tag_structure; delete from auth_types; (bash) mysql -h YOUR_HOST -p YOUR_CLONE < FILE_NAME Signed-off-by: Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 2222] Field auth_subfield_structure.frameworkcode should be removed
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '22

01 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2222 --- Comment #4 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- Created attachment 132832 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=132832&action=e… Bug 2222: Adjust kohastructure Test plan: See next patch. Signed-off-by: Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 2222] Field auth_subfield_structure.frameworkcode should be removed
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '22

01 Apr '22

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

1 0

[Bug 30421] New: Error 500 while trying to put a hold on a record
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '22

01 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30421 Bug ID: 30421 Summary: Error 500 while trying to put a hold on a record 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: arthur.suzuki(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When trying to put a hold on a record from staff interface: https://staff-master.sandboxes.biblibre.eu/cgi-bin/koha/reserve/request.pl?… Template process failed: undef error - The given date (2004) does not match the date format (iso) at /kohadevbox/koha/Koha/DateUtils.pm line 204. at /kohadevbox/koha/C4/Templates.pm line 127 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 30429] New: Empty searchbox when there is one result
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '22

01 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30429 Bug ID: 30429 Summary: Empty searchbox when there is one result 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: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org When you perform a search that brings a unique result, the searched terms are kept in the search box which can be useful in some cases but when you scan barcode all day, it's quite annoying to delete the previous search before searching the new one. As the string '&found1=1' is added at the end of url, would it be possible to empty the searchbox in that specific case ? It saw it was introduced by Bug 23475 that asks precisely for the opposite behaviour and that I sign it, but now we have this in production, I realise it's not ergonomic at all for my colleagues. Maybe a (new...) syspref to let each library choose the favourite behaviour ? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 26003] New: Could the holds queue be live rather than built via cron
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '22

01 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26003 Bug ID: 26003 Summary: Could the holds queue be live rather than built via cron Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I get the feeling that the functionality of the holds queue could be achieved via triggers after various actions rather than require a regular full rebuild via a cron job. I'm thinking the action of placing a hold, the action of checking in items and checking out items... these are the main things that can affect the holds queue data and such actions should be able to trigger a small calculation to update the holds queue for the related item, branch etc. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 30428] New: Simplify authorities/merge_ajax.pl
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '22

01 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30428 Bug ID: 30428 Summary: Simplify authorities/merge_ajax.pl 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 Looking at this script within the context of bug 2222. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 2222] Field auth_subfield_structure.frameworkcode should be removed
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '22

01 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2222 --- Comment #3 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- (In reply to Katrin Fischer from comment #2) > Could there be a use case for multiple frameworks for an auth_type or would > that not work anyway? That does not work. An authtype is a framework. I am not aware of a realistic use case for this scenario. -- You are receiving this mail because: You are watching all bug changes.

1 0