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

[Bug 9842] SIP tests : fix for 07hold.t on Cancel Hold
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '23

02 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9842 David Cook <dcook(a)prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcook(a)prosentient.com.au --- Comment #5 from David Cook <dcook(a)prosentient.com.au> --- (In reply to Katrin Fischer from comment #4) > I am not sure how to set up the config files in order to make these tests > pass (or not). Could someone else confirm if they are still failing or not > maybe? I don't know if anyone even uses them anymore. In Bug 26700, I propose that we remove them. If someone is using them, they need to move them into the t/ directory I think. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 18586] New: Create module to mint RDF subject URIs
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '23

02 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18586 Bug ID: 18586 Summary: Create module to mint RDF subject URIs Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl In the relational database, we use biblionumber as the ID for bibliographic records, but a triplestore we need to use a RDF URI. So I'm going to put together a module with a little method for minting URIs. While we could just agree on a convention, it probably makes sense to use the convention in the module and then use the module elsewhere to keep things consistent. -- You are receiving this mail because: You are watching all bug changes.

1 30

[Bug 18713] New: Add support for named graphs and rfds:seeAlso to Koha:: RDF
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '23

02 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18713 Bug ID: 18713 Summary: Add support for named graphs and rfds:seeAlso to Koha::RDF Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When I download RDFXML via OAI-PMH, I delete existing named graphs and create new named graphs. This functionality isn't specific to OAI-PMH, so I'm putting it in Koha::RDF. There is also a method for adding rdfs:seeAlso to a $subject and an $object. In my case, I'm linking a Koha record to an imported record. It's a generic relationship though, which will be useful in many other scenarios, so it's going in Koha::RDF too. -- You are receiving this mail because: You are watching all bug changes.

1 54

[Bug 26248] New: Simplify keep_text Javascript function
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '23

02 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26248 Bug ID: 26248 Summary: Simplify keep_text Javascript function 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The keep_text function in koha-tmpl/intranet-tmpl/prog/js/staff-global.js is functional but not very readable. We can simplify it. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 28477] New: INTRANET and OPAC loggers should print to STDERR instead of to file
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '23

02 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28477 Bug ID: 28477 Summary: INTRANET and OPAC loggers should print to STDERR instead of to file Change sponsored?: --- Product: Koha Version: master 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org Bug 25284 notes that Plack will fail to start up if the /var/log/koha/<site>/opac-error.log file isn't writeable by the specific Koha Linux user. It has a workaround for chowning all the log files, but that's really not the best way to go. We shouldn't be messing around with the log files that belong to the Apache web server. Instead, we should be printing to STDERR using the Log4Perl logger. For CGI Koha using Apache, that text will wind up in the correct web server log file automatically. For Plack Koha, it would wind up the correct web server log file as well... or thanks to Bug 16357 they'll wind up special log files created and owned by Koha. It's as easy as changing the Log4Perl configuration as follows: FROM: log4perl.appender.INTRANET=Log::Log4perl::Appender::File log4perl.appender.INTRANET.filename=__LOG_DIR__/intranet-error.log log4perl.appender.OPAC=Log::Log4perl::Appender::File log4perl.appender.OPAC.filename=__LOG_DIR__/opac-error.log TO: log4perl.appender.INTRANET=Log::Log4perl::Appender::Screen log4perl.appender.INTRANET.stderr = 1 log4perl.appender.OPAC=Log::Log4perl::Appender::Screen log4perl.appender.OPAC.stderr = 1 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 33702] Patrons should only see their own ILLs in the OPAC
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '23

02 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33702 Mason James <mtj(a)kohaaloha.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mtj(a)kohaaloha.com --- Comment #17 from Mason James <mtj(a)kohaaloha.com> --- (In reply to Lucas Gass from comment #16) > Backported to 22.05.x for 22.05.13 hi team, all 3 following packages include the 3x 33702 patches 22.11.06 22.05.13 21.11.21 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 33757] New: Help manual link in Label Creator points to wrong place
by bugzilla-daemon＠bugs.koha-community.org 01 Jun '23

01 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33757 Bug ID: 33757 Summary: Help manual link in Label Creator points to wrong place Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org In 22.11, when in Label creator and you click on Help, you are taken to https://koha-community.org/manual//22.11/en/html/tools.html#label-creator-l… but should be taken to https://koha-community.org/manual//22.11/en/html/cataloging.html#creating-l… -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 22959] New: Using the help feature when in the Patron Category Admin page, should bring user to that section in the manual
by bugzilla-daemon＠bugs.koha-community.org 01 Jun '23

01 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22959 Bug ID: 22959 Summary: Using the help feature when in the Patron Category Admin page, should bring user to that section in the manual Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Target Milestone: --- With the introduction of the new help button opening up the manual in Koha 18.11, clicking on Help when in the patron category set up in the administration module does not bring the user to that portion of the manual, instead it goes to the main page of the manual. It should go here : https://koha-community.org/manual/18.11/en/html/administration.html#patron-… -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 15003] Help should be a wiki, not translatable via po-files
by bugzilla-daemon＠bugs.koha-community.org 01 Jun '23

01 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15003 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|NEW |RESOLVED --- Comment #2 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Closing this one as the suggestions were based on the old help system that used templates in Koha. Remaining issues could be filed as new bugs. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 6796] Overnight checkouts taking into account opening and closing hours
by bugzilla-daemon＠bugs.koha-community.org 01 Jun '23

01 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6796 Sam Lau <samalau(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |samalau(a)gmail.com Status|Needs Signoff |Failed QA --- Comment #38 from Sam Lau <samalau(a)gmail.com> --- I'm in the process of testing this and so far shortening the loan period seems to be working for me, but extending the loan period isn't working as expected. Steps taken to replicate my issue 1) Set library opening time to 8:30am closing time to 9pm 2) set loan period to be 3 hours. 3) Set the "ConsiderLibraryHoursWhenIssuing" preference to the extend option. 4) checked out an item. My checkout time and date was 06/01/2023 19:07 - with the loan period I selected (3 hours), the book would be due on 06/01/2023 @ 22:07, but since the library closes at 9pm (21:00), the due date should be extended to the next day at opening time. 5) The shown due date is 06/03/2023 at 08:30 - The due date that was expected was 06/02/2023 at 08:30 so it skipped over a day for some reason. -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0