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

[Bug 38800] New: erm : add a column for agreements in packages list
by bugzilla-daemon＠bugs.koha-community.org 30 Dec '24

30 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38800 Bug ID: 38800 Summary: erm : add a column for agreements in packages list 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 In the package list it would be useful to have a column for agreement(s). Not sure of how to handle that visually, as there can be several agreements for one package. Maybe all agreements could be put in the same column, as we do for print and electronic identifiers of titles. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 38799] New: erm : add period information in packages list
by bugzilla-daemon＠bugs.koha-community.org 30 Dec '24

30 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38799 Bug ID: 38799 Summary: erm : add period information in packages list 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 In the package list it would be useful to have one or serveral column for "period information", especially the cancelation deadline (and a way to filter on this deadline) Not sure of how to handle that visually, as there can be several period informations for one package -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 37501] New: Titles table in ERM needs selection tools, batch tools
by bugzilla-daemon＠bugs.koha-community.org 30 Dec '24

30 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37501 Bug ID: 37501 Summary: Titles table in ERM needs selection tools, batch tools Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: esther.melander(a)bywatersolutions.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 Similar to elsewhere in Koha, the Titles and Packages tables need a select all, clear all, individual selection boxes that can work with batch tools like batch deletion. If a library imports a 1,000 titles, deleting or removing titles in a batch is not possible. It is possible to delete individual titles by using the delete button at the end of the row, but this task becomes tedious with so many titles. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 38797] New: CSRF Token Not Validated in Koha v24.05
by bugzilla-daemon＠bugs.koha-community.org 30 Dec '24

30 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38797 Bug ID: 38797 Summary: CSRF Token Not Validated in Koha v24.05 Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: amar(a)ourlib.in QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 175986 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=175986&action=e… Removed csrf token and subitted form, still patron created successfully In Koha version 24.05, CSRF tokens are not validated during insert or update operations (e.g., creating a new patron). Even when the CSRF token is removed or invalid, Koha still processes the request and creates the new patron. Koha Version: 24.05 Steps to Reproduce: Navigate to the patron creation form in Koha. Remove the CSRF token from the input and meta tags. Submit the form to create a new patron. The new patron is created successfully, despite the missing or invalid CSRF token. Comparison with Koha v24.11: In Koha v24.11, the same test results in an error for an invalid CSRF token, which indicates proper validation. Koha v24.05 does not validate CSRF tokens correctly, potentially exposing the system to CSRF attacks. Please see attached files for additional details. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 37721] New: Add Donors to Acquisitions
by bugzilla-daemon＠bugs.koha-community.org 30 Dec '24

30 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37721 Bug ID: 37721 Summary: Add Donors to Acquisitions Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be a nice enhancement to be able to separate Donors from Vendors. Right now some libraries are using Vendors to track Donors. Overtime, this creates an unmanageable number of vendors not used for day-to-day ordering or receiving. Libraries like to create baskets and add donor items via Acquisitions because it enables them to track the value of donations. This expands some of the ideas in Bug 37674 and Bug 37677. There may be a number of approaches on how to implement this. If a Vendor had a donor flag, the donor could live on a separate table, but still be available to use when an item is "ordered" through acquisitions. If there was a Donor page with its own result list, it opens up some interesting tracking possibilities and the ability to search Donors separately from Vendors. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 7508] Collapsable items on items tab
by bugzilla-daemon＠bugs.koha-community.org 30 Dec '24

30 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7508 David Nind <david(a)davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=38790 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 35402] Update the OPAC and staff interface to Bootstrap 5
by bugzilla-daemon＠bugs.koha-community.org 29 Dec '24

29 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35402 David Nind <david(a)davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |38070 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38070 [Bug 38070] Regression in print notices -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 38795] New: ERM : wrong mapping for publication_type when importing UNIMARC records
by bugzilla-daemon＠bugs.koha-community.org 29 Dec '24

29 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38795 Bug ID: 38795 Summary: ERM : wrong mapping for publication_type when importing UNIMARC records Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal 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 bug 32782 introduced a mapping for UNIMARC records imported as a list into ERM This line is problematic for 2 reasons + my $publication_type = $label_pos67 eq 'am' ? 'monograph' : $label_pos67 eq 'as' ? 'serial' : ''; - the position 6 for electronic resource is "l", and not "a", but the habits of libraries and data providers are not always consistent - "monograph" and "serial" are not defined in the authorized value for publication type (ERM_TITLE_PUBLICATION_TYPE) I propose - to take only into account the 7th position of the label (m for ebooks, s for serial) - to use standard values defined in the authorized value : "ebook" and "journal" (or to add "monograph" and "serial" in that AV, but that seems redundant) -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 32782] New: UNIMARC support
by bugzilla-daemon＠bugs.koha-community.org 29 Dec '24

29 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32782 Bug ID: 32782 Summary: UNIMARC support Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: ERM Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com CC: jonathan.druart+koha(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com Depends on: 32030 I need UNIMARC equivalence for the following values: my $publication_title = $biblio->title; my $print_identifier = $record->subfield( '020', 'a' ) || $record->subfield( '020', 'z' ) || $record->subfield( '022', 'a' ) || $record->subfield( '022', 'y' ); my $online_identifier = $print_identifier; my ( $date_first_issue_online, $date_last_issue_online ) = $fix_coverage->( $record->subfield( '866', 'a' ) ); my ( $num_first_vol_online, $num_last_vol_online ) = $fix_coverage->( $record->subfield( '863', 'a' ) ); my ( $num_first_issue_online, $num_last_issue_online ) = ( '', '' ); # FIXME ? my $title_url = $record->subfield( '856', 'u' ); my $first_author = $biblio->author; my $embargo_info = ''; # FIXME ? my $coverage_depth = $title_url ? 'fulltext' : 'print'; my $notes = $record->subfield( '852', 'z' ); my $publisher_name = $record->subfield( '260', 'b' ); my $publication_type = ''; # FIXME ? my $date_monograph_published_print = ''; # FIXME ? my $date_monograph_published_online = ''; # FIXME ? my $monograph_volume = ''; # FIXME ? my $monograph_edition = ''; # FIXME ? my $first_editor = ''; # FIXME ? my $parent_publication_title_id = ''; # FIXME ? my $preceeding_publication_title_id = ''; # FIXME ? my $access_type = ''; # FIXME ? Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32030 [Bug 32030] Electronic resource management (ERM) -- You are receiving this mail because: You are watching all bug changes.

1 26

[Bug 37393] New: Bundle items don't show their host in the staff interface
by bugzilla-daemon＠bugs.koha-community.org 29 Dec '24

29 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37393 Bug ID: 37393 Summary: Bundle items don't show their host in the staff interface Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: ASSIGNED Severity: minor Priority: P5 - low Component: Staff interface Assignee: schodkowy.omegi-0r(a)icloud.com Reporter: schodkowy.omegi-0r(a)icloud.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com If you add an item to a bundle, it's supposed to show "Not for loan (Added to bundle); In bundle: <bundle title>". This works in OPAC, but not in staff interface. The cause is erroneous check `[% IF bundlesEnabled %]` before the parent bundle information is requested+shown. The `bundlesEnabled` variable checks if the current biblio ITSELF is of collection type, so should only be used for whether to show the button to add new items to the bundle items, NOT for querying whether current item is part of a bundle, as the items that make up the bundle aren't of collection type themselves. To reproduce: 1. Have two biblio records record 1 = normal record, not a collection record 2 = in leader 000, 7- Bibliographic level must be set to c- Collection 2. Add an item with some kind of barcode to each. 3. In record 2 in staff interface, next to the item, click "Manage bundle" and then "Add to bundle", enter the barcode of the item of record 1, and confirm. 4. Open record 1 in OPAC, you will see that the item is not for loan/part of bundle, you will see "In bundle:" followed by a link to record 2. 5. Open record 1 in staff interface, you will see that the "In bundle:" link is missing! (that's the bug) -- You are receiving this mail because: You are watching all bug changes.

1 23