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

[Bug 28128] New: Cataloging Record Uploading Process
by bugzilla-daemon＠bugs.koha-community.org 28 Jun '22

28 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28128 Bug ID: 28128 Summary: Cataloging Record Uploading Process Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: cmkelleymls(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org About three months ago, my library moved its Koha ILS to a new machine. The transition was not ideal but it was smooth enough. We still catalog a bit on the old machine and last week we extracted and uploaded a bunch of records to the new machine. The upload process stalled. After days of trying to find out why the uploading process would stall, I noticed that the 952 $7 in a few records was miscoded as a 952 $9 instead. Once I reverted the 952 $9 to 952 $7, all was well. This also happened when a transfer record had a 999 field. If the record number in 999 $c and 999 $d did not exist, the uploading processing would stall. So I deleted the 999 fields or corrected them to what was in the other copy of the ILS; and again all was well. I have been reading online about this phenomenon and I haven't found a reason or solution to the stall. Mind you, other operations continue to run: the editing of existing records and the entry of new records; circulation; calendar changes, etc. It's just the automatic record uploading through the user interface that stalls. Well, here are two possible solutions: check for 952 $9 fields and 999 fields in the records that are to be uploaded. They may be the source of stall. Their presence may not be the only source, mind you, but their presence is a possibility. P. S. It would be nice if instead of stalling, the uploader would write the MARC record to some sort of upload log with a reason; and then try uploading the next record. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 31052] New: How Do I Get Cash App ++ with no delays?
by bugzilla-daemon＠bugs.koha-community.org 27 Jun '22

27 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31052 Bug ID: 31052 Summary: How Do I Get Cash App ++ with no delays? 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: reedallen999(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Cash app is based on certain policies and you should know about such things. The increasing need for digital payment applications has made it the most imperative. These days, users are coming up with queries like How Do I Get Cash App ++. That is the most efficient aspect and every cash app user should try their best to explore the strategy aspects. You can choose to find the platform to handle the cash app system easily. https://www.emailsupport-contact.com/blog/how-do-i-get-cash-app-plus-plus/ -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 30150] New: Dutch option in language limits is garbled
by bugzilla-daemon＠bugs.koha-community.org 27 Jun '22

27 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30150 Bug ID: 30150 Summary: Dutch option in language limits is garbled Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: ephetteplace(a)cca.edu QA Contact: testopia(a)bugs.koha-community.org Created attachment 130998 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=130998&action=e… screenshot of bug To recreate: - add Dutch "dut" to the AdvancedSearchLanguages option - go to the advanced search page /cgi-bin/koha/opac-search.pl - click open the Language select menu - note that the text for Dutch is "nedərlɑns (Dutch)" It should render as "nedərlɑns (Dutch)" but instead the numerical character references for the fourth and seventh characters are rendered literally, as if they were escaped. I haven't looked into this further so I don't know _why_ this is happening but Koha's OPAC uses charset=utf-8 so I think we should be able to simply use the actual characters without any references. Perhaps it's a problem with the encoding of strings in the database? But when I run a report to pull all the rows from the `language_descriptions` table, the word "nedərlɑns" renders correctly. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 15348] Change/Edit estimated delivery date per order line
by bugzilla-daemon＠bugs.koha-community.org 27 Jun '22

27 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15348 --- Comment #37 from Aleisha Amohia <aleisha(a)catalyst.net.nz> --- Have hopefully fixed up the error and fixed the author email address on my two patches. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15348] Change/Edit estimated delivery date per order line
by bugzilla-daemon＠bugs.koha-community.org 27 Jun '22

27 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15348 Aleisha Amohia <aleisha(a)catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #120656|0 |1 is obsolete| | --- Comment #36 from Aleisha Amohia <aleisha(a)catalyst.net.nz> --- Created attachment 136563 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=136563&action=e… Bug 15348: (follow-up) Fix breadcrumbs, title, JS error, permissions -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15348] Change/Edit estimated delivery date per order line
by bugzilla-daemon＠bugs.koha-community.org 27 Jun '22

27 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15348 Aleisha Amohia <aleisha(a)catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #120655|0 |1 is obsolete| | --- Comment #35 from Aleisha Amohia <aleisha(a)catalyst.net.nz> --- Created attachment 136562 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=136562&action=e… Bug 15348: trivial code simplification -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15348] Change/Edit estimated delivery date per order line
by bugzilla-daemon＠bugs.koha-community.org 27 Jun '22

27 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15348 Aleisha Amohia <aleisha(a)catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #120654|0 |1 is obsolete| | --- Comment #34 from Aleisha Amohia <aleisha(a)catalyst.net.nz> --- Created attachment 136561 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=136561&action=e… Bug 15348: (QA follow-up) Remove superflous filters The QA script highlighted the addition of some unneeded extra TT filters. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15348] Change/Edit estimated delivery date per order line
by bugzilla-daemon＠bugs.koha-community.org 27 Jun '22

27 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15348 Aleisha Amohia <aleisha(a)catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #120653|0 |1 is obsolete| | --- Comment #33 from Aleisha Amohia <aleisha(a)catalyst.net.nz> --- Created attachment 136560 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=136560&action=e… Bug 15348: Add estimated delivery date field to individual orders This patch allows you to specify an estimated delivery date per order. The specified estimated delivery date is also considered when searching for late orders and exporting late orders. You can also edit the estimated delivery date from the late orders page. Test plan: 1. Update database, rebuild schema, restart services 2. Go to Acquisitions, search for a vendor, and create a new basket 3. Add an order to the basket. When filling in the accounting details, notice the new 'estimated delivery date' field, but don't add a date. Save the order. 4. Confirm no date shows in the estimated delivery date column in the orders table. 5. Modify the order. Add a date in the estimated delivery date field and save the order. 6. Confirm the date now shows in the orders table. 7. Close the basket. 8. Go to the Late Orders page. 9. Put estimated delivery date from and to parameters in the search filters on the left. Ensure the from and to dates encapsulate the date you entered in the estimated delivery date field for the order. 10. Click Filter and ensure the order shows. 11. Select the checkbox next to the order. Click the Export as CSV button. 12. Open the CSV and confirm the estimated delivery date that you entered shows as expected in the file. 13. Click Edit under the estimated delivery date. Confirm the estimated delivery date modal pops up with the correct order line number in the modal header. 14. Remove the estimated delivery date and click Save. 15. Confirm that the estimated delivery date calculated by Koha now shows in the late orders table. 16. Select the checkbox next to the order. Click the Export as CSV button. 17. Open the CSV and confirm the calculated estimated delivery date shows in the CSV. 18. Confirm tests pass: t/db_dependent/Koha/Acquisition/Order.t Sponsored-by: Bibliotheksservice-Zentrum Baden-Württemberg (BSZ) Signed-off-by: Christian Stelzenmüller <christian.stelzenmueller(a)bsz-bw.de> Signed-off-by: Martin Renvoize <martin.renvoize(a)ptfs-europe.com> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15348] Change/Edit estimated delivery date per order line
by bugzilla-daemon＠bugs.koha-community.org 27 Jun '22

27 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15348 Aleisha Amohia <aleisha(a)catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 30996] New: ModBiblio breaks MARC::File::XML
by bugzilla-daemon＠bugs.koha-community.org 27 Jun '22

27 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30996 Bug ID: 30996 Summary: ModBiblio breaks MARC::File::XML Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org This is a weird issue. It could very well be something particular to my setup, but I am at a loss as to what it might be, so here goes... This is happening on a regular Koha 20.11.13.000, installed with the Debian packages, on Ubuntu 20.04.3. I have a script that downloads records from the Swedish national library Libris, does some checking and some massaging, and then imports the records into Koha with either AddBiblio or ModBiblio. The script can be found here: https://github.com/Libriotech/ftp2koha About a month ago messages like these started to show up in the logs for some of the imported records: Wide character in warn at /usr/share/perl5/MARC/Charset.pm line 384. no mapping found at position 1 in ビードマルク, マッティン, at /usr/share/perl5/MARC/Charset.pm line 384. Records that produce this error show broken chars, with chars like äöå shown as a diamond with a question mark in it. The records look ok before they are imported, and tools like yax-marcdump does not show errors for them. Position 9 in the leader is "a", to indicate the records are UTF8. Three records in one file are attached. I have tried to reduce the problem down to a minimal case, and come up with this script: -------------------------------------------------------------------- #!/usr/bin/perl use Modern::Perl; use C4::Biblio qw( ModBiblio ); use MARC::File::XML ( BinaryEncoding => 'utf8', RecordFormat => 'MARC21' ); my $records = MARC::File::XML->in( 'export_2022_06_16_1120_orig.marcxml' ); # Start transaction my $schema = Koha::Database->new()->schema(); $schema->storage->txn_begin(); my %map = ( 'p4rdqd4nm9f4dhv3' => 349078, 'jzzcjbt4gt0f0z8w' => 348789, '1fmgws1lzrk71k2t' => 349079, ); RECORD: while ( my $record = $records->next() ) { say $record->leader; say "=========^=============="; $record->encoding( 'UTF-8' ); my $id = $record->field( '001' )->data; my $biblionumber = $map{ $id }; if ( $ARGV[0] > 1 ) { say ModBiblio( $record, $biblionumber, '' ); } } # End transaction $schema->storage->txn_rollback(); -------------------------------------------------------------------- The results of running that script are different depending on if ModBiblio gets called or not. With "0" as the argument it does not get called and everything looks ok. Leader pos 9 is "a": $ sudo koha-shell -c "perl -MCarp::Always test_minimal.pl 0" norrbott cim a 7i 4500 =========^============== ngm a 7i 4500 =========^============== cim a 7i 4500 =========^============== With "2" as argument, ModBiblio does get called, and there are errors related to encoding (from the call to $records->next()), from the second and third record. Notice also that leader pos 9 for record number two and three is now empty! So when ModBiblio is triggered, the UTF8 indicator is suddenly gone, and as far as I can see, this is what is causing the encoding errors: $ sudo koha-shell -c "perl -MCarp::Always test_minimal.pl 2" instancename cim a 7i 4500 =========^============== 1 Wide character in warn at /usr/share/perl5/Carp/Always.pm line 18. no mapping found at position 1 in ビードマルク, マッティン, at /usr/share/perl5/MARC/Charset.pm line 384. MARC::Charset::utf8_to_marc8("\x{30d2}\x{3099}\x{30fc}\x{30c8}\x{3099}\x{30de}\x{30eb}\x{30af}, \x{30de}\x{30c3}\x{30c6}\x{30a3}\x{30f3},") called at /usr/share/perl5/MARC/File/XML.pm line 480 MARC::File::XML::decode(MARC::File::XML=HASH(0x56070fb9c278), "<record><leader> ngm a 7i 4500</leader><controlfiel"...) called at /usr/share/perl5/MARC/File.pm line 110 MARC::File::next(MARC::File::XML=HASH(0x56070fb9c278)) called at test_minimal.pl line 19 ngm 7i 4500 =========^============== Use of uninitialized value in join or string at /usr/share/perl5/MARC/Field.pm line 696. MARC::Field::as_usmarc(MARC::Field=HASH(0x560718749560)) called at /usr/share/perl5/MARC/File/USMARC.pm line 274 MARC::File::USMARC::_build_tag_directory(MARC::Record=HASH(0x5607186ea458)) called at /usr/share/perl5/MARC/File/USMARC.pm line 313 MARC::File::USMARC::encode(MARC::Record=HASH(0x5607186ea458)) called at /usr/share/perl5/MARC/Record.pm line 474 MARC::Record::as_usmarc(MARC::Record=HASH(0x5607186ea458)) called at /usr/share/koha/lib/C4/Biblio.pm line 3054 C4::Biblio::ModBiblioMarc(MARC::Record=HASH(0x560718457c30), 348789, "") called at /usr/share/koha/lib/C4/Biblio.pm line 381 C4::Biblio::ModBiblio(MARC::Record=HASH(0x560718457c30), 348789, "") called at test_minimal.pl line 30 1 cim 7i 4500 =========^============== 1 Things I have checked: - /usr/share/koha/lib/C4/Biblio.pm has not been updated since well before the problems started - I can not see any plugins that do suspicious things Anyone got a hunch what might be causing this, or where to start looking for a solution? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5