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

[Bug 22323] New: cronjob runreport.pl CSV encoding issue
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '22

27 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22323 Bug ID: 22323 Summary: cronjob runreport.pl CSV encoding issue Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Target Milestone: --- Cronjob runreport.pl runs SQL reports and can export as CSV. This export needs to be UTF-8 encoded. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 19540] New: opac-reserve does not correctly warn of too_much reserves
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '22

26 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19540 Bug ID: 19540 Summary: opac-reserve does not correctly warn of too_much reserves Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: david.bourgault(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When attempting to place more holds than allowed, opac-reserve.pl only checks against the SysPref 'maxreserves' and not the issuingrules 'holdsallowed'. If the issuing rule's limitation is lower than maxreserve, the opac-reserve page shows a message saying you cannot place any more holds but the explanatory message does not show. To reproduce: 0) Set MaxReserve to a high value (50 is default); 1) Set an issuing rule's "Holds allowed" to a low number (1 or 2); 2) Place as many holds as you can (for the corresponding (categorycode, itype, branchcode, etc). When you reach the maximum allowed by the issuing rule, you'll see a message telling you cannot place any more holds, but the explanatory message saying that you cannot place more than %d holds will not show. (It will show "No items available instead". Bug is present on 16.05 and master -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 27086] New: Add a both/most restrictive option for ReservesControlBranch
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '22

25 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27086 Bug ID: 27086 Summary: Add a both/most restrictive option for ReservesControlBranch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Some libraries would like to be able to check both a patron's branch, and an items branch when determining if an item can be held. This is related to reciprocal borrowing, where one library does not allow holds on dvds from other libraries, but other libraries do. They want the home library's rule to affect their patrons when placing holds on DVDs from other libraries In this scenario we would check the rules based on both settings, using the most restrictive rule found -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 28669] New: Marc field 942 is overwritten when importing a new record
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '22

25 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28669 Bug ID: 28669 Summary: Marc field 942 is overwritten when importing a new record Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: klas.blomberg(a)skovde.se QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Marc field 942 is overwritten when importing catalogue records via Z39.50 or Staged Marc records management. Overwritten normally means deleted as union catalogues doesn't supply Koha-specific fields. The information in 942 is often quite crucial for getting the system to work correctly -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 28577] New: Add column for copynumber on overdue report (overdue.pl)
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '22

25 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28577 Bug ID: 28577 Summary: Add column for copynumber on overdue report (overdue.pl) Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: marjorie.barry-vila(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Hi, It would be fine to see field copynumber from items on overdue circulation report (/cgi-bin/koha/circ/overdue.pl) and in columns_settings on circ-overdues Thanks, Marjorie -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 25716] New: Add ability to specify additional options in koha-conf.xml for z3950_responder.pl when using koha-z3950-responder
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '22

25 Oct '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25716 Bug ID: 25716 Summary: Add ability to specify additional options in koha-conf.xml for z3950_responder.pl when using koha-z3950-responder Change sponsored?: --- Product: Koha Version: master 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 29

[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 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