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

[Bug 29986] New: Descriptions of system internal debit types and credit types should be editable
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '22

21 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29986 Bug ID: 29986 Summary: Descriptions of system internal debit types and credit types should be editable Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, martin.renvoize(a)ptfs-europe.com The descriptions of system internal debit types and credit types are not translatable from the GUI. We should make that work, as the descriptions are used for display for example on the cashup summary print outs (see bug 27779) As this leaves no way for people to fix translations for their use but SQL, I'd consider this is in a grey area to be a little more bug than enhancement. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 29695] New: Centralize columns' descriptions
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '22

21 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29695 Bug ID: 29695 Summary: Centralize columns' descriptions Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org We have columns.def that contains the descriptions for DB columns and some json files that are used for syspref's values selection. 1. We duplicate them 2. columns.def is translatable but json files are not 3. columns.def is a XML file we are parsing with regexs We should have a single and better way to deal with those descriptions. -- You are receiving this mail because: You are watching all bug changes.

1 69

[Bug 14462] aqorders.sort*_authcat unused?
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '22

21 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14462 --- Comment #1 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- These fields still seem to be unused. I suggest we change that and set them to the authorised value category linked to the sort* fields. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 13976] Sorting search results by popularity is alphabetical
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '22

21 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13976 Nick Clemens <nick(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|minor |normal -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 31756] New: Biblionumber not numerically sorting natively when using Zebra
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '22

21 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31756 Bug ID: 31756 Summary: Biblionumber not numerically sorting natively when using Zebra Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Searching - Zebra Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au When bug 30879 was pushed, we didn't know how to natively sort numbers, but we do now. This issue seeks to replace the workaround with the native implementation. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 13976] Sorting search results by popularity is alphabetical
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '22

21 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13976 Nick Clemens <nick(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=31756 CC| |dcook(a)prosentient.com.au -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13976] Sorting search results by popularity is alphabetical
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '22

21 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13976 Nick Clemens <nick(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #141068|0 |1 is obsolete| | --- Comment #9 from Nick Clemens <nick(a)bywatersolutions.com> --- Created attachment 144115 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=144115&action=e… Bug 13976: Sort popularity numerically in Zebra To test: 1 - Create a new template at Tools->Marc modification template 2 - Add action: Copy 999$c to 942$0 3 - Create a report: SELECT biblionuber FROM biblios 4 - Run report, show all, do a batch modification to all records using template above 5 - Search for 'a' (make sure you are using Zebra) 6 - Sort by popularity 7 - Note records are sorted wrong 8 - Apply patch 9 - Restart all 10 - Reload search results 11 - Success! Sorted correctly -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14367] History for MARC records. Roll back changes on a timeline or per field.
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '22

21 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14367 Hammat wele <hammat.wele(a)inlibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Patch doesn't apply CC| |hammat.wele(a)inlibro.com --- Comment #68 from Hammat wele <hammat.wele(a)inlibro.com> --- Applying: Bug 14367: Add MARC record history .git/rebase-apply/patch:393: trailing whitespace. warning: 1 line adds whitespace errors. Using index info to reconstruct a base tree... M C4/Biblio.pm M cataloguing/addbiblio.pl M koha-tmpl/intranet-tmpl/prog/css/addbiblio.css M koha-tmpl/intranet-tmpl/prog/en/modules/cataloguing/addbiblio.tt M koha-tmpl/intranet-tmpl/prog/js/cataloging.js .git/rebase-apply/patch:393: trailing whitespace. warning: 1 line adds whitespace errors. Falling back to patching base and 3-way merge... Auto-merging koha-tmpl/intranet-tmpl/prog/js/cataloging.js Auto-merging koha-tmpl/intranet-tmpl/prog/en/modules/cataloguing/addbiblio.tt CONFLICT (content): Merge conflict in koha-tmpl/intranet-tmpl/prog/en/modules/cataloguing/addbiblio.tt Auto-merging koha-tmpl/intranet-tmpl/prog/css/addbiblio.css CONFLICT (content): Merge conflict in koha-tmpl/intranet-tmpl/prog/css/addbiblio.css Auto-merging cataloguing/addbiblio.pl CONFLICT (content): Merge conflict in cataloguing/addbiblio.pl Auto-merging C4/Biblio.pm CONFLICT (content): Merge conflict in C4/Biblio.pm error: Failed to merge in the changes. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 32309] New: Store saved_reports values as hash
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '22

21 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32309 Bug ID: 32309 Summary: Store saved_reports values as hash Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org CC: nick(a)bywatersolutions.com When using the --store-results option in runreport.pl, the resulting stored data would be more easily usable if stored as a hash. So, say we have a patron named Andrew Fuerste-Henry and a report "select surname, firstname from borrowers." Currently, that will show up in saved_reports as: [["surname","firstname"],["Fuerste-Henry","Andrew"]] That makes it hard to do something like find all the surnames connected to a given firstname. The data would be easier to work with if we instead stored it as a hash, like: ["surname" : "Fuerste-Henry" , "firstname" : "Andrew"] -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 1993] Task Scheduler Needs Re-write
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '22

21 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=1993 Michaela Sieber <michaela.sieber(a)kit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |michaela.sieber(a)kit.edu -- You are receiving this mail because: You are watching all bug changes.

1 0