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

[Bug 38154] New: Batch checkout fails if AllFinesNeedOverride is set to Require and patron has any fines
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '25

06 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38154 Bug ID: 38154 Summary: Batch checkout fails if AllFinesNeedOverride is set to Require and patron has any fines Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To replicate: -Set AllFinesNeedOverride to Require -Add fines to patron account below the amount set in noissuescharge -Enter barcodes into batch item checkout for patron, and click Check out -Click 'Checkout or renew' button on the Batch checkout confirmation screen (keep all items selected) -Note that no items have actually checked out -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 18595] New: Move C4::Members::Messaging to Koha namespace
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '25

06 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18595 Bug ID: 18595 Summary: Move C4::Members::Messaging to Koha namespace Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: lari.taskula(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org Bug 17499 adds Koha-objects for messaging preferences. -- You are receiving this mail because: You are watching all bug changes.

1 159

[Bug 38821] New: Create reords for packages
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '25

06 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38821 Bug ID: 38821 Summary: Create reords for packages Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(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 It could be nice to have the ability to create bibliographic record for packages. Particularly but not only for packagages for which the concept of "titles" is irrelevant (ex: Scopus, Visible Body...) -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 38830] New: If an ERM report covers several data sources, prevent the choice of a report type that does not exist for all data sources
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '25

06 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38830 Bug ID: 38830 Summary: If an ERM report covers several data sources, prevent the choice of a report type that does not exist for all data sources Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(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 If an ERM report covers several data sources, it might be a good idea to prevent the choice of a report type that does not exist for all data sources. Currently it's easy to make a mistake, and the result is a void report. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 38809] New: erm : abilty to create reports for several data sources
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '25

06 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38809 Bug ID: 38809 Summary: erm : abilty to create reports for several data sources Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(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 Currently an ERM usage report can only concern one data source. It could be useful to draw reports on multiple data source. For example I may want to list the 100 most frequently used ebooks of my library, regardless of the providers. I don't think it is possible at present. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 38254] New: Patron auto-complete search explodes when dateexpiry is NULL
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '25

06 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38254 Bug ID: 38254 Summary: Patron auto-complete search explodes when dateexpiry is NULL Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons 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, kyle.m.hall(a)gmail.com This was moved from bug 31143: > We either need to fix the auto-complete patron search or have the > script re-calculate the dateexpiry from the patron category. I am > leaning towards making the patron search deal with NULL. borrowers.dateexpiry can be NULL so the code needs to be fixed. I have not tried it but this would be the idea: iff --git a/koha-tmpl/intranet-tmpl/prog/js/staff-global.js b/koha-tmpl/intranet-tmpl/prog/js/staff-global.js index 73a4a0251e1..28060fb35da 100644 --- a/koha-tmpl/intranet-tmpl/prog/js/staff-global.js +++ b/koha-tmpl/intranet-tmpl/prog/js/staff-global.js @@ -694,10 +694,13 @@ function patron_autocomplete(node, options) { } let new_date = new Date(); let today = Date.parse($date_to_rfc3339($date(new_date.toString()))); - let expiration = Date.parse( - $date_to_rfc3339($date(item.expiry_date.toString())) - ); - let expired = today > expiration; + let expired = false; + if (item.expiry_date){ + let expiration = Date.parse( + $date_to_rfc3339($date(item.expiry_date.toString())) + ); + expired = today > expiration; + } return $("<li></li>") .addClass(loggedInClass) .data("ui-autocomplete-item", item) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 36454] New: Staff - Provide indication if a patron is expired when creating an ILL request
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '25

06 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36454 Bug ID: 36454 Summary: Staff - Provide indication if a patron is expired when creating an ILL request Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: pedro.amorim(a)ptfs-europe.com CC: katrin.fischer(a)bsz-bw.de, martin.renvoize(a)ptfs-europe.com, nick(a)bywatersolutions.com, pedro.amorim(a)ptfs-europe.com, rebecca.bradshaw(a)nnuh.nhs.uk, tomascohen(a)gmail.com Creating an ILL request, when staff adds a patron, there is no indication that the patron is expired, if said patron is indeed expired. Part of the problem tackling this, I believe, is that the 'create form' is ILL backend specific, so this should be tackled at each ILL backend level. Having said that, with bug 35570 in the pipeline, we could perhaps consider adding this little enhancement as a follow-up to that. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 47

[Bug 37478] New: bulkmarcimport.pl can die on bad records
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '25

06 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37478 Bug ID: 37478 Summary: bulkmarcimport.pl can die on bad records Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz bulkmarcimport.pl will die on xml parsing errors when trying to convert the saved metadata (marcxml) back into a MARC::Record object Two cases we have seen are an invalid characters: :9: parser error : PCDATA invalid Char value 31 <controlfield tag="003">aPGcC</controlfield> and invalid/missing subfield: :91: parser error : attributes construct error <subfield code=""">Among nineteenth-century women's rights reformers, Elizab It turns out MARC::Record can read the incoming file - we can convert it to xml to save as metadata, but only on trying to create the record out of the xml do we die. This may point to a bug in MARC::Record -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 45

[Bug 36117] New: Can svc/bib_profile be removed?
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '25

06 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36117 Bug ID: 36117 Summary: Can svc/bib_profile be removed? Change sponsored?: --- Product: Koha Version: unspecified 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: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Is this used? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 38824] New: Document the use of type field in packages (ERM)
by bugzilla-daemon＠bugs.koha-community.org 04 Jan '25

04 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38824 Bug ID: 38824 Summary: Document the use of type field in packages (ERM) Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)ptfs-europe.com, philip.orr(a)lmscloud.de The use of "type" field is not explained. What are the meaning of the standard default values, and the recommended use of this field? The standard default value in ERM_PACKAGE_TYPE AV are "complete" and "local" In EBSCO knowlegde base, the values are "complete", "variable", "selectable" and "custom", with meanings explained here : https://connect.ebsco.com/s/article/What-are-the-available-Package-Types-in… If EBSCO eHoldings are used in Koha (with HoldingsIQ API), I suppose those values are going to be used ? So maybe the standard values in ERM_PACKAGE_TYPE should be updated to reflect that ? But is this field of any use if you do not use EBSCO eHoldings? Do you need to select the value "local" ? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1