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

[Bug 23335] New: "There are no items that can be placed on hold."
by bugzilla-daemon＠bugs.koha-community.org 11 Mar '24

11 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23335 Bug ID: 23335 Summary: "There are no items that can be placed on hold." Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: jmmureithi(a)nationalbank.co.ke QA Contact: testopia(a)bugs.koha-community.org Created attachment 91571 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=91571&action=ed… THE MESSAGE APPEARING IN OPAC The clients/users are trying to place hold and the following message is displayed yet there are items: There are no items that can be placed on hold. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 18729] New: Librarian unable to update hold pickup library from patron pages without "modify_holds_priority" permission
by bugzilla-daemon＠bugs.koha-community.org 07 Mar '24

07 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18729 Bug ID: 18729 Summary: Librarian unable to update hold pickup library from patron pages without "modify_holds_priority" permission Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests 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 A librarian can update a hold's pickup library from the record details page, but not from the patron details or checkout pages unless he or she has the "modify_holds_priority". If the librarian does not, an error is displayed instead. This is do to the fact that on those two pages the API is used and it used the PUT for hold to update all hold fields, which requires this permission. Another endpoint for updating only the pickup location should be added that does not require the "modify_holds_priority" permission. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 70

[Bug 21302] New: Link in 780/785 should search for $t in title and $a in author
by bugzilla-daemon＠bugs.koha-community.org 05 Mar '24

05 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21302 Bug ID: 21302 Summary: Link in 780/785 should search for $t in title and $a in author Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org When a record has a 780 and/or 785 field with both $a and $t, the link should search for the value in $a in the author index and the value in $t in the title index, combined with AND. Right now, it searches for both in the title index. Steps to reproduce: 1- If its not already in your cataloguing framework, add 780 $a and $t and 785 $a and $t (check the "Editor" box) 2- Search for a record and edit it 3- Add an author name in 780 $a and 785 $a 4- Add a title in 780 $t and 785 $t 5- Make sure both indicators for both fields are 0, so it should look like 780 00 $aAuthor1 $tTitle1 785 00 $aAuthor2 $tTitle2 6- Save the record and view it in "normal" view 7- Click the link created for Author1 Title 1 -> the search is ti,phr:Author1 Title1, but it should be au,phr:Author1 and ti,phr:Title1 8- Repeat step 7 with Author2 Title2, same result If possible, it would be great if all values were searched in their rightful index with "and" in between to narrow the search. 76X - 78X $a = author (same as 1XX or 7XX) $d = publisher, publication date or place (same as 260 $a, $b, $c or 264 $a, $b, $c) $e = language (same as 008/35-37) $f = publication place (same as 008/15-17) $k = series (same as 4XX or 8XX) $o = identifier number (same as 0XX) $p = title (same as 210) $s = uniform title (same as 240 or 243) $t = title (same as 245 or 130) $u = report number (same as 027) $x = issn (same as 022) $y = coden (same as 030) $z = isbn (same as 020) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 21631] New: No warning when placing a hold with current location/pick-up location combination forbidden by Transport cost matrix
by bugzilla-daemon＠bugs.koha-community.org 05 Mar '24

05 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21631 Bug ID: 21631 Summary: No warning when placing a hold with current location/pick-up location combination forbidden by Transport cost matrix Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I might be missing a setting here, holds are so complicated and have so many settings... Plus this is in a multi-branch system situation... I was expecting to see an error or a warning for holds with a combination of current location and pick-up location that is forbidden by transport cost matrix. To reproduce: 0) Make sure you have several branches in your system (at least 3, I'll call them A, B and C) 1) Go to Administration > Global system preferences and activate UseTransportCostMatrix 2) Go to Administration > Transport cost matrix 3) Click on the cell for the combination 'From A to B', uncheck 'Disable' and enter 0 4) Leave combination 'From A to C' disabled 5) In the catalog, search for an item which is currently at library A and currently available (you can use item search for this) 6) Place a hold for this item and change the pick-up location to library B 7) Run misc/cronjobs/holds/build_holds_queue.pl 8) Go to Circulation > Holds queue 9) Choose library A, item should be in the queue 10) In the catalog, search for an item which is currently at library A and currently available (you can use item search for this) 11) Place a hold for this item and change the pick-up location to library C (there is no warning, everything seems fine) 12) Run misc/cronjobs/holds/build_holds_queue.pl 13) Go to Circulation > Holds queue 14) Choose library A, 2nd item is not in the queue Am I missing something? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 18138] New: Use MARC modification template when adding/ updating bibliographic records
by bugzilla-daemon＠bugs.koha-community.org 29 Feb '24

29 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18138 Bug ID: 18138 Summary: Use MARC modification template when adding/updating bibliographic records Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: stefan.berndtsson(a)ub.gu.se QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When importing records, MARC modification templates can be used to silently remove unwanted tags among other thing. The same thing could be useful when adding/updating bibliographic records from within Koha. I therefor propose an addition of a SysPref to set a default template to use in AddBiblio and ModBiblio before TransformMarcToKoha is called. -- You are receiving this mail because: You are watching all bug changes.

1 117

[Bug 22446] New: Koha/Patron/Categories.t is failing on March 1st (2019 only?)
by bugzilla-daemon＠bugs.koha-community.org 29 Feb '24

29 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22446 Bug ID: 22446 Summary: Koha/Patron/Categories.t is failing on March 1st (2019 only?) Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)ptfs-europe.com Target Milestone: --- koha_1 | # Failed test 'With enrolmentperiod defined and a date given in parameter, ->get_expiry_date should take this date + enrolmentperiod' koha_1 | # at t/db_dependent/Koha/Patron/Categories.t line 80. koha_1 | # got: '-1' koha_1 | # expected: '0' koha_1 | # Looks like you failed 1 test of 5. koha_1 | koha_1 | # Failed test 'get_expiry_date' koha_1 | # at t/db_dependent/Koha/Patron/Categories.t line 86. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 23478] New: Simplify report landing page
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '24

26 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23478 Bug ID: 23478 Summary: Simplify report landing page 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org I think we could combine reports-home.pl and guided_reports.pl (used saved) by having reports-home.pl show the saved reports, and having the options on the reports-home.pl page down the left side. Some of it is already there. I'm not sure about other libraries, but 99% of what we do in reports is saved. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 23532] New: AutoCreateAuthorities create authority only headings
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '24

23 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23532 Bug ID: 23532 Summary: AutoCreateAuthorities create authority only headings Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: gveranis(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl The problem: We have enable AutoCreateAuthorities and also enable BiblioAddsAuthorities and when we insert values for tag 650 , we get authorities only with 150$a filled and not other subfields. I found that on C4/Biblio.pm lines 549 - 555 map { $authfield->add_subfields( $_->[0] => $_->[1] ) if ( $_->[0] =~ /[A-z]/ && $_->[0] ne "a" && C4::Heading::valid_bib_heading_subfield( $authority_type->auth_tag_to_report, $_->[0] ) ); } $field->subfields(); Koha try to copy subfields to the new authority record. BUT the condition C4::Heading::valid_bib_heading_subfield( $authority_type->auth_tag_to_report, $_->[0]) return false. Because the $authority_type->auth_tag_to_report has value of 150 and not 650 as file C4/Heading/MARC21.pm declared. if we set on file C4/Heading/MARC21.pm also the value '150' => { auth_type => 'TOPIC_TERM', subfields => 'abvxyz', subject => 1 }, (valid based on https://github.com/Koha-Community/Koha/blob/master/installer/data/mysql/en/…) then it works , but I am not sure if it is valid to set there new fields. or better solution could be $authority_type->auth_tag_to_report take right value in condition. Could anyone propose the best solution ? Thanks, George Veranis -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 23215] New: Remove PayPal logic from Koha
by bugzilla-daemon＠bugs.koha-community.org 20 Feb '24

20 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23215 Bug ID: 23215 Summary: Remove PayPal logic from Koha Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: agustinmoyano(a)theke.io QA Contact: testopia(a)bugs.koha-community.org Depends on: 23118 Target Milestone: --- PayPal should be treated as any other payment plugin, to unify treatment of payment methods. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23118 [Bug 23118] Copy PayPal logic into plugin -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 33

[Bug 22340] New: Elasticsearch - sorting fields should have a fallback mechanism
by bugzilla-daemon＠bugs.koha-community.org 19 Feb '24

19 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22340 Bug ID: 22340 Summary: Elasticsearch - sorting fields should have a fallback mechanism Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com Target Milestone: --- As an example 264 and 260 should be sortable for publisher Some records will have one, some will have both, it should eb configurable which to use and that we should not leave the sort field empty if one field is missing -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4