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

[Bug 29325] New: commit_file.pl error 'Already in a transaction'
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '22

24 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29325 Bug ID: 29325 Summary: commit_file.pl error 'Already in a transaction' Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz To reproduce: 1. Pick a file for staging: $ kshell k$ misc/stage_file.pl --file TestDataImportKoha.mrc => SUCCESS: All good 2. Commit! k$ misc/commit_file.pl --batch-number 1 => FAIL: You see DBIx::Class::Storage::DBI::_exec_txn_begin(): DBI Exception: DBD::mysql::db begin_work failed: Already in a transaction at /kohadevbox/koha/C4/Biblio.pm line 303 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 100

[Bug 22343] New: Add SMTP settings
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '22

24 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22343 Bug ID: 22343 Summary: Add SMTP settings Change sponsored?: --- Product: Koha Version: 18.11 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: fv(a)spots.school QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- I would like to add fields to Koha>Administration for SMTP settings to make it easy to use external mail servers without having to edit files on the server. I am thinking that we could edit koha/C4/Letters.pm adding $mail{smtp} = 'my.mail.server'; I am not sure how the settings are passed to Letters.pm however. What does everyone else think? Is this the right way to do it? Thank you! FV -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 351

[Bug 28659] New: Allow Fast Cataloging to skip duplicate check
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '22

24 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28659 Bug ID: 28659 Summary: Allow Fast Cataloging to skip duplicate check 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To recreate: - Have a bib in your system with the title "E Street Shuffle" - Confirm you do not have barcode "XXX" in your system - Have Fast Cataloging enabled - Try to check out barcode "XXX" to a patron, get notice that barcode does not exist, follow link to Fast Cataloging - In your Fast Add record, enter title "E Street Shuffle" - click Save, get a popup asking if your new record is a duplicate of the existing record - click "Yes, View Existing Items" - Koha takes you to the existing bib, where you can add a new item (assuming you have permission) - that item will not maintain the XXX barcode and will not follow any of the other settings in one's Fast Add framework I don't expect all libraries to agree on how this should work. It'd be great to have a system preference with which to set whether or not to do that dupe check at all on fast add. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 29782] New: Missing entries for display locations in HTML customizations
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '22

23 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29782 Bug ID: 29782 Summary: Missing entries for display locations in HTML customizations 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: mik(a)adminkuhn.ch QA Contact: testopia(a)bugs.koha-community.org In Koha menu "Tools > HTML customizations" it is possible to create new entries for various display locations. Given the Koha instance has two languages, "English (en)" and "Deutsch Deutschland (de-DE)" an entry will show three tabs: * Default * English (en) * Deutsch Deutschland (de-DE) If you fill just text into the "Content" field of the actual language tabs you will be prompted with a popup saying "Please specify a title for Default". In fact I don't know why such a "title" is needed at all (see also bug 29515), but OK I fill one in, but do not fill any content into the "Content" field of the Default tab because I don't want or need no default content. Now it's possible to save. The content of tab "English (en)" and "Deutsch Deutschland (de-DE)" will show up in the OPAC when changing to the respective language. But Koha menu "Tools > HTML customizations" will NOT show any entry for the display location you have created! So you are not able to change its content or delete it. The problem doesn't happen if you enter text in the "Content" field of the Default tab. This means 1. It is not clear why the default tab is mandatory. 2. It shouldn't be possible to save the entry for a display location without entering text in the "Content" field of the Default tab if the consequence is that there won't be no entry for the display location in the end. -- You are receiving this mail because: You are watching all bug changes.

1 34

[Bug 29434] New: In UNIMARC instances, the authority finder uses MARC21 relationship codes
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '22

23 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29434 Bug ID: 29434 Summary: In UNIMARC instances, the authority finder uses MARC21 relationship codes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: a.roussos(a)dataly.gr QA Contact: testopia(a)bugs.koha-community.org Background information ---------------------- As per the IFLA UNIMARC Manual for Authorities format [1], the 5-- Functional Block (a.k.a. Related Access Point Block) "contains related authorized access points from which a reference is to be made to see also the access point of the record". To put it simply, this allows for linking authority records with other authority records in order to form, for example, broader/narrower term hierarchies (see sreenshots 1 and 2). Control Subfield $5 ("Relationship Control" in IFLA speak, whereas the UNIMARC Authorities framework in Koha uses the term "Tracing Control") is key to this idea, because it is used to store a single-character value that denotes the type of relationship between the authorities being linked. The actual problem ------------------ When using the authority finder plugin (authorities/auth_finder.pl), you can pick an entry from the 'Special relationship:' dropdown menu in order to set the relationship between authorities. However, in UNIMARC instances the relationship codes listed are those for MARC21 [2] (see screenshots 3 and 4). The correct codes for UNIMARC are listed in pages 93-94 of the IFLA UNIMARC Manual for Authorities. [1] https://repository.ifla.org/handle/123456789/861 [2] https://www.loc.gov/marc/authority/adtracing.html -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 28864] New: The patron search results in the Patron card creator doesn't seem to use PatronsPerPage syspref
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '22

23 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28864 Bug ID: 28864 Summary: The patron search results in the Patron card creator doesn't seem to use PatronsPerPage syspref Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: michael.hafen(a)washk12.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The patron search results in the patron card creator card batch doesn't include the value of the PatronsPerPage system preference in the per page drop down, which means it isn't using the system preference. Also, on the Patrons page, the patron search includes the PatronsPerPage value, but doesn't use it as the default. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 41

[Bug 28707] New: Translate RECEIPT notice (fr-CA)
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '22

23 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28707 Bug ID: 28707 Summary: Translate RECEIPT notice (fr-CA) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N 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: frederic(a)tamil.fr The RECEIPT notice was not yet translated in fr-CA. I hope I'm doing this correctly. I admit I'm a bit lost since the change of the translation process for SQL data. Let me know if I need to change something. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 26632] New: BatchStageMarcRecords passes a random number to AddBiblioToBatch / AddAuthToBatch
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '22

22 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26632 Bug ID: 26632 Summary: BatchStageMarcRecords passes a random number to AddBiblioToBatch / AddAuthToBatch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: MARC Bibliographic record staging/import Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org 424 $import_record_id = AddBiblioToBatch($batch_id, $rec_num, $marc_record, $encoding, int(rand(99999)), 0); 430 $import_record_id = AddAuthToBatch($batch_id, $rec_num, $marc_record, $encoding, int(rand(99999)), 0, $marc_type); This populates: my $update_counts = @_ ? shift : 1; Which is used once: _update_batch_record_counts($batch_id) if $update_counts; So...almost always we want to update, but very occasionally, randomly, don't? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 28375] New: Inefficiencies in fetching COinS
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '22

21 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28375 Bug ID: 28375 Summary: Inefficiencies in fetching COinS 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org In XSLTParseForDisplay we fetch the coins for the OPAC even on the staff interface On opac results we fetch the biblio object, this is already fetched in the searchResults subroutine Additionally - we can fetch the coins in the searchResults to move logic out of the scripts -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 30

[Bug 29358] New: Allow local definition of staff client's 'View in OPAC' links
by bugzilla-daemon＠bugs.koha-community.org 19 Oct '22

19 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29358 Bug ID: 29358 Summary: Allow local definition of staff client's 'View in OPAC' links Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Not all users of Koha use the Koha OPAC as the public facing front end. We can define the baseURL of a different OPAC with OPACBaseURL but not the rest. It would be nice if Koha had a system preference that told Koha how to build those thinks, with a {biblionumber} placeholder. That way you could tell it something like this: wwww.example.com/TEST/{BIBNUMBER} -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1