Re: [Koha] Framework Reports

Hi again, Elaine! In our latest exchange, on 7 Oct. 2021 at 02:00 [JST], you wrote: We're on 21.05 > Elaine > VWML > Hmmm. This gives me pause and reconsider migrating to 21.05 instead of 20.05. Maybe my bug was spotted earlier than I reported and fixed. Or it

[Koha] Reports timing out, prevents access to web interfaces

Good afternoon, I'm experiencing an issue where if I'm working in the staff interface and kick off a long-running Report, I'm unable to navigate to or use Koha in any other browser tab, or in any other browser, either in the staff or public interface. I've confirmed that this affects other

Re: [Koha] stack number cannot be stored in Koha 21.05

Hi Katrin > ah ok, that was a local change then? Yes, it definitely seems so. > Because it looks like it has always been tinyint: > > https://git.koha-community.org/Koha-community/Koha/src/branch/master/installer/data/mysql/kohastructure.sql#L3015 > >

Re: [Koha] stack number cannot be stored in Koha 21.05

Hi Michael, ah ok, that was a local change then? Because it looks like it has always been tinyint: https://git.koha-community.org/Koha-community/Koha/src/branch/master/installer/data/mysql/kohastructure.sql#L3015

Re: [Koha] stack number cannot be stored in Koha 21.05

Hi Katrin > 952$j is mapped to items.stack by default that has the datatype > tinyint(1) in the database. A common problem I have encountered here > is that it won't save when you try to store something non-numeric or > outside the range of tinyint. Could that be the issue? Yes, this would

[Koha] Next Cataloging SIG!

Hi, all! The next Koha-US Cataloging Special Interest Group ("Cat SIG") meeting is this Thursday, October 7, 2021, at 8 PT, 9 MT, 10 CT, 11 ET, and you don't have to be a member of Koha-US to join us! You don't even need to self-identify as a cataloger! Join us for our usual roundtable of

Re: [Koha] stack number cannot be stored in Koha 21.05

Hi Michael, 952$j is mapped to items.stack by default that has the datatype tinyint(1) in the database. A common problem I have encountered here is that it won't save when you try to store something non-numeric or outside the range of tinyint. Could that be the issue? Katrin On 06.10.21 20:47,

[Koha] stack number cannot be stored in Koha 21.05

Hi In our library we use Koha 21.05.02 on Debian GNU/Linux 11. As we found out it not possible to store the content of field 952$j (stack / shelving control number) in the Koha database. I have also tested this on my demo installation with Koha 21.05.00 and on another demo installation with

Re: [Koha] Framework Reports

We're on 21.05 Elaine VWML On Tue, Oct 5, 2021 at 6:31 PM Charles Kelley wrote: > Hello, Elaine, et al! > > In our latest exchange, on 6 Oct. 2021 at 05:50 [JST], I received the > following through the Koha Discussion Group: > > Thank you for your reply. > > ODS

Re: [Koha] Excluding fields from the OPAC search

Hi, unfortunately the problem is a bit more complicated. :( I think since our switch from grs-1 to dom indexing, the kw index includes the whole record, where before that switch it was 'everything that is indexed'. So changing the configuration of individual fields/indexes won't make a

Re: [Koha] Excluding fields from the OPAC search

> (e. g. > MARC 952$e the source of acquisition, or MARC 952$x the non-public note) If these are indexed by default I think that should be considered a bug. -- Owen -- Web Developer Athens County Public Libraries (740) 737-6006 https://www.myacpl.org

[Koha] Excluding fields from the OPAC search

Hi In our library we use Koha 18.11.01 with Debian GNU/Linux 9. Is it possible to switch off fields in the OPAC for the keyword search or for the search in general so that they cannot be searched? (e. g. MARC 952$e the source of acquisition, or MARC 952$x the non-public note) How do other