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

[Bug 32651] New: Search borrowers by library doesn't work
by bugzilla-daemon＠bugs.koha-community.org 23 Apr '23

23 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32651 Bug ID: 32651 Summary: Search borrowers by library doesn't work Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: koha(a)univ-lyon3.fr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Hi, I tried this on a sandbox on master. In the "Search patrons", click on the sort of "burger menu" to select a library in the library field. Launch your search, you have all the patrons in the results (as if you have selected "any" in Library field). Sonia -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 31349] New: Add option to not update items.permenent_location when editing items.location
by bugzilla-daemon＠bugs.koha-community.org 23 Apr '23

23 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31349 Bug ID: 31349 Summary: Add option to not update items.permenent_location when editing items.location Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Generally, when one edits the shelving location (items.location) of an item, Koha also updates the permanent shelving location (items.permanent_location) to match. However, some libraries prefer to make it possible to edit the location without updating the permanent location. This allows one to set an item to a temporary location that automatically clears at checkin using the UpdateItemLocationOnCheckin syspref. That setup currently relies upon editing frameworks to make permanent location an editable field. That setup has proven fragile, as shown in bug 27837, bug 28832, bug 30909, and bug 31187. I suggest adding a more specific mechanism for this workflow in hopes that it will remain more stable and usable. In the item edit and item batch mod screens, we could put a checkbox next to the field for shelving location. The checkbox is labeled "Update permanent shelving location" and is checked by default. If one un-checks it, that edit will only update shelving location, not permanent location. The checkbox could be hidden with CSS if one doesn't want to use this feature. Or, if folks prefer, we could create a system preference to show/hide it. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 33085] New: OPAC translation to Galician
by bugzilla-daemon＠bugs.koha-community.org 23 Apr '23

23 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33085 Bug ID: 33085 Summary: OPAC translation to Galician 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: adolfo.rodriguez(a)xercode.es QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr Though the Galician language is available in Koha, there are hardly any texts actually translated. I work in several Koha that use Galician as main language, so it would come in handy to improve the Galician po files. I have focused now in the OPAC, as it's the public part, but the intention is to cover later on the Intranet. To test: 1 Enable Galician in OPAC 2 Check that it's mainly in English 3 Recreate templates in Galician 4 Check that OPAC now shows up in Galician -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 33589] New: Turn "register here" into "register" or rephrase without using "here"
by bugzilla-daemon＠bugs.koha-community.org 22 Apr '23

22 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33589 Bug ID: 33589 Summary: Turn "register here" into "register" or rephrase without using "here" Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Accessibility guidelines tell you to avoid 'here' in links and I strongly agree. You should always describe clearly what's going to happen when you click on the link. I feel we should remove the 'here' from 'register here' when patron self registration is activated. What do you think? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12104] Add print label to serials receive
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '23

21 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12104 Michaela Sieber <michaela.sieber(a)kit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |michaela.sieber(a)kit.edu -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12532] Redirect guarantee email to guarantor
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '23

21 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12532 Marius <marius.mandrescu(a)inlibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #149233|0 |1 is obsolete| | --- Comment #98 from Marius <marius.mandrescu(a)inlibro.com> --- Created attachment 150071 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=150071&action=e… Bug 12532: Send email to guarantee and guarantor; -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12532] Redirect guarantee email to guarantor
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '23

21 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12532 Marius <marius.mandrescu(a)inlibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #149233|1 |0 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 30949] New: Error 500 in z3950_search.pl
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '23

21 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30949 Bug ID: 30949 Summary: Error 500 in z3950_search.pl Change sponsored?: --- Product: Koha Version: 22.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: egpetridis(a)yahoo.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Created attachment 135974 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=135974&action=e… koha intranet error I wonder how may one debug errors 500 in z3950_search.pl, especially when searching against multiple targets. Searching for ISSN 1061-2688 in the following targets (among many others) host: webcat.lib.unc.edu port: 210 DB: innopac host: afton.lib.unc.edu port: 210 DB: INNOPAC I get the following error: Home Error 500 An error has occurred! Error 500 This message may have been caused by any of the following reasons: You made use of an external link to an item that is no longer available You followed an outdated link e.g. from a search engine or a bookmark You tried to access a page that needs authentication An internal link in the client is broken and the page does not exist What's next? Use top menu bar to navigate to another part of Koha. To report a broken link or any other issue, please contact the Koha administrator. Send email Error logs to be uploaded. Please don't focus on the server mentioned in them, as I located the servers above in previous tries but decided to file a bug report on subsequent searches that produced said error. In different previous searches I've encountered the same problem while searching against targets host: NLS.ALMA.EXLIBRISGROUP.COM port: 210 DB: 44NLS_INST (https://www.nls.uk/catalogues/z39-50/) host: ELIBRARY.MEL.ORG port: 210 DB: INNOPAC for example. Again, these are merely the targets I had managed to narrow down in the past. I noticed that tag 915 is mentioned in the logs (...Field 915 must have at least one subfield...), whereas no such tag is defined in standard koha frameworks such as BKS and SER. Could this be the culprit, data that koha doesn't expect to receive? Those very targets work fine when queried for different books/magazines, so it must be something contained in specific results. The error may also have to do with the fact that all Z39.50 servers defined in my installation have "Del952.xsl,Del9LinksExcept952.xsl" in the "XSLT File(s) for transforming results" field. Both XSLT files are stock, as provided in a packages installation. Some 10 years ago I had made the same question, but got nowhere. https://lists.katipo.co.nz/public/koha/2012-August/033847.html -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 9313] Show fine amount on 'Overdues with fines' report
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '23

21 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9313 --- Comment #5 from Caroline Cyr La Rose <caroline.cyr-la-rose(a)inlibro.com> --- As for which calculation, to me it should be the total accrued for that checkout, not each offset. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 32495] New: Required fields in API and UI form don't match
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '23

21 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32495 Bug ID: 32495 Summary: Required fields in API and UI form don't match Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart+koha(a)gmail.com Reporter: matt.blenkinsop(a)ptfs-europe.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 The required fields in the API for adding a new agreement and the form on the UI to add it don't match. The API endpoint for POST "/api/v1/erm/agreements" requires "name, status, is_perpetual" The form on the UI requires the fields above (is_perpetual is a checkbox with a default value selected) but also requires "Description". Description should either be added to the API or the flag on the UI should be removed. -- You are receiving this mail because: You are watching all bug changes.

1 24