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

[Bug 23838] New: Add ability to view item renew history
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '23

10 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23838 Bug ID: 23838 Summary: Add ability to view item renew history Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It should be possible, when viewing a patron's circulation history, to view details of an item's renewals. Each renewal should be displayed as: Renewed on <renewal date> by <renewed by> -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 119

[Bug 34529] New: Offline circulation should be able to accept userid as well as cardnumber
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '23

10 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34529 Bug ID: 34529 Summary: Offline circulation should be able to accept userid as well as cardnumber Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Like everywhere else in Koha, offline circulation should be able to use userid as well as cardnumber to look up the patron for a transaction ( checkouts and fine payments ). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 29

[Bug 33928] New: Improve translation of title tags: Various
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '23

10 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33928 Bug ID: 33928 Summary: Improve translation of title tags: Various Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: testopia(a)bugs.koha-community.org Blocks: 33906 This patch will modify various templates in the staff client so that translatable strings in the <title> tag are wrapped in the correct translation function, e.g. [% t('Translate me') %] - about.tt - auth.tt - errors/errorpage.tt - intranet-main.tt Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33906 [Bug 33906] [OMNIBUS] Improve translation of title tags -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 34397] New: Inconsistencies in Classification sources page titles, breadcrumbs, and header
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '23

10 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34397 Bug ID: 34397 Summary: Inconsistencies in Classification sources page titles, breadcrumbs, and header Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org While testing bug 33909, I had to look at all the pages in the administration module. In doing so, I found some inconsistencies between the various pages. For the Classification sources page, here is what should be changed to make it consistent with the other pages in the module: Page title - Change 'Classification sources' to 'Classification configuration' (should we change to simply 'Classification'? No other section has 'configuration') - Change 'Add classification source' to 'New classification source' - Add classification source code in single quotes to 'Modify classification source' - Change 'Add filing rule' to 'New filing rule' - Add filing rule code in single quotes to 'Modify filing rule' - Change 'Add splitting rule' to 'New splitting rule' - Add splitting rule code in single quotes to 'Modify splitting rule' Breadcrumb - Change 'Add classification source' to 'New classification source' - Add classification source code in single quotes to 'Modify classification source' - Change 'Add filing rule' to 'New filing rule' - Add filing rule code in single quotes to 'Modify filing rule' - Change 'Add splitting rule' to 'New splitting rule' - Add splitting rule code in single quotes to 'Modify splitting rule' Page header - Change 'Add classification source' to 'New classification source' - Add classification source code in single quotes to 'Modify classification source' - Change 'Add filing rule' to 'New filing rule' - Add filing rule code in single quotes to 'Modify filing rule' - Change 'Add splitting rule' to 'New splitting rule' - Add splitting rule code in single quotes to 'Modify splitting rule' There is no special page for deletion confirmation, simply a browser prompt. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 33749] New: Move Koha::MetadataRecord::stripWhitespaceChars into a RecordProcessor filter
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '23

10 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33749 Bug ID: 33749 Summary: Move Koha::MetadataRecord::stripWhitespaceChars into a RecordProcessor filter Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Bug 30358 introduced the static method Koha::MetadataRecord::stripWhitespaceChars. This method should've been put on a RecordProcessor filter. I open this bug for handling that. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 34406] New: Inconsistencies in Identity providers/domains page titles, breadcrumbs, and header
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '23

10 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34406 Bug ID: 34406 Summary: Inconsistencies in Identity providers/domains page titles, breadcrumbs, and header Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org While testing bug 33909, I had to look at all the pages in the administration module. In doing so, I found some inconsistencies between the various pages. For the Identity providers page, here is what should be changed to make it consistent with the other pages in the module: Page title - Change 'Edit identity provider' to "Modify identity provider 'code'" or "Modify identity provider 'description' (code)" - Add a level for "Email domains for 'code'" or "Email domains for 'description' (code)" - Change 'Edit identity provider domain' to "Modify email domain 'domain'" Breadcrumb - Change 'Edit identity provider' to "Modify identity provider 'code'" or "Modify identity provider 'description' (code)" - In Domains, put code in single quotes (or descriptions in single quotes and code in parentheses) - Change Domains to Email domains - Change 'Edit domain' to "Modify email domain 'domain'" Page header - Change 'Edit identity provider' to "Modify identity provider 'code'" or "Modify identity provider 'description' (code)" - Change 'Identity provider email domains' to "Email domains for 'code'" or "Email domains for 'description' (code)" - Change 'New email domain' to "New email domain for 'code'" or "New email domain for 'description' (code)" - Change 'Edit identity provider domain' to "Modify email domain 'domain'" There is no special page when deleting an email domain, only a modal. There is no special page when deleting an identity provider, only a modal. -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 34098] New: Improve translation of some strings in the patron import template
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '23

10 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34098 Bug ID: 34098 Summary: Improve translation of some strings in the patron import template Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr There are a few strings on the patron import page which don't translate well, often because a sentence is broken up with HTML or TT markup. -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 34114] New: OMNIBUS: Replace the use of jQueryUI sortable
by bugzilla-daemon＠bugs.koha-community.org 09 Nov '23

09 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34114 Bug ID: 34114 Summary: OMNIBUS: Replace the use of jQueryUI sortable Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: testopia(a)bugs.koha-community.org Blocks: 29222 As discussed in Bug 29222, jQueryUI sortable should be replaced. The last time I checked it was used in these places: - Administration -> MARC frameworks -> Subfield structure -> Tab reordering. - Administration -> Authority types -> Subfield structure -> Tab reordering. - Administration -> System preferences -> Language and OPACLanguage reordering - Cataloging -> Basic MARC editor -> Subfield reordering. - Tools -> Stock rotation -> Stage reordering. It looks like Drupal switched to this library: https://github.com/SortableJS/Sortable Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29222 [Bug 29222] OMNIBUS: Replace the use of jQueryUI -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 30250] New: Default values from the framework should be applied when editing as new (duplicating)
by bugzilla-daemon＠bugs.koha-community.org 09 Nov '23

09 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30250 Bug ID: 30250 Summary: Default values from the framework should be applied when editing as new (duplicating) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Bug 29146 has created a problem for one of our Koha libraries. When they duplicate a record (i.e 'Edit as new') they want empty fields to be filled with framework defaults. Although, due to this fix, they no longer get them. Duplicating records is like creating new records (just with some pre-filled fields), so this must be considered. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 78

[Bug 33139] New: New facetable boolean Elasticsearch field 'has-eresource'.
by bugzilla-daemon＠bugs.koha-community.org 08 Nov '23

08 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33139 Bug ID: 33139 Summary: New facetable boolean Elasticsearch field 'has-eresource'. Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: andreas.jonsson(a)kreablo.se We would like to have a facetable boolean field in the Elasticsearch index to quickly filter records that have a link to an electronic resource in 856$u. The facets should have labels that makes the purpose clear. We can use "Digitally available" and "Only in print" for the negative. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10