Time |
S |
Nick |
Message |
04:11 |
|
|
dps joined #koha |
04:13 |
|
|
bwv582 joined #koha |
04:16 |
|
bwv582 |
I'm trying to upgrade to the current stable version but koha-upgrade-schema is erroring out with: ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Cannot change column 'itemnumber': used in a foreign key constraint 'tmp_holdsqueue_ibfk_1' at /usr/share/koha/lib/C4/Installer.pm line 741 |
04:27 |
|
|
bag joined #koha |
05:08 |
|
davidnind |
bwv582: this error is bug 35687 - you may be able to update the database using the queries in the patches |
05:08 |
|
huginn` |
Bug https://bugs.koha-community.or[…]_bug.cgi?id=35687 blocker, P5 - low, ---, koha-bugs, Needs Signoff , Upgrade to 23.06.00.013 may fail |
06:56 |
|
|
bshum joined #koha |
07:16 |
|
|
reiveune joined #koha |
07:16 |
|
reiveune |
hello |
08:00 |
|
magnuse |
\o/ |
08:02 |
|
|
lds joined #koha |
08:11 |
|
|
fridolin joined #koha |
08:11 |
|
|
cait joined #koha |
08:13 |
|
cait |
good morning #koha |
08:14 |
|
fridolin |
y-hello-w #koha |
08:17 |
|
ashimema |
morning |
08:18 |
|
cait |
hi fridolin |
08:19 |
|
cait |
fridolin: I haven't heard back from fredericdem and lukeg yet, and no string frezes |
08:19 |
|
cait |
but I'll try to sort out the security branch in a bit |
08:20 |
|
cait |
fridolin: are you back in France now? |
08:20 |
|
fridolin |
cait: yes i am |
08:20 |
|
fridolin |
i live in Avignon south of France |
08:20 |
|
cait |
nice :) |
08:20 |
|
fridolin |
string freeze sent this morning |
08:21 |
|
cait |
yep, you are good :) |
08:21 |
|
fridolin |
so cheese every day :D |
08:21 |
|
fridolin |
and wine |
08:21 |
|
cait |
no cheese in Tahiti? |
08:21 |
|
fridolin |
bearly not |
08:21 |
|
cait |
that must have been hard |
08:21 |
|
fridolin |
I'll be at HackFest in Marseille this year |
08:22 |
|
cait |
I hope I'll be too |
08:22 |
|
cait |
waiting for instructions on registration |
08:22 |
|
fridolin |
but not in KohaCon sadly |
08:22 |
|
cait |
so I can write my travel request |
08:22 |
|
fridolin |
we are on organisation currently, dont hesitate to contact Paul |
08:23 |
|
cait |
already did ;) |
08:29 |
|
krimsonkharne[m] |
morning all :) |
08:29 |
|
cait |
good morning |
08:30 |
|
krimsonkharne[m] |
waves |
08:31 |
|
krimsonkharne[m] |
I have a meeting an hour earlier, hope I can make it to the general meeting today.. |
08:31 |
|
cait |
I won't be around, I need to leave early today |
08:55 |
|
ashimema |
My team and I are all going to hackfest |
09:05 |
|
fridolin |
ashimema great \o/ we will try new bars ;) |
09:09 |
|
ashimema |
I think the powers that be had a bit of a meeting about how to fit us all in yesterday 😛 |
09:52 |
|
cait |
yeah, there has been some worry - that's why I was asking for info |
09:54 |
|
NikolayGospodinov[m] |
Hello. I have the following problem. After reindexing the zebra, when I search for a document in Koha it returns no result. This is the result from the reindexing the zebra: Records exported: 485445 12:04:13 [00:09:20]... (full message at <https://matrix.org/_matrix/med[…]MRiApQaaqaQuMzGHl>) |
09:56 |
|
cait |
how do you index? |
09:56 |
|
cait |
as someone said yesterday it doess look like it could be a permissionissue |
09:56 |
|
cait |
what's the command you use for reindexing? |
09:57 |
|
NikolayGospodinov[m] |
sudo koha-rebuild-zebra -v -f library |
10:04 |
|
cait |
and the output is ok? |
10:05 |
|
magnuse |
see the link to matrix.org above. looks like something is not right: "zebra_lock_create fail fname=/var/lock/koha/k7000/authorities/norm..LCK [No such file or directory]" |
10:05 |
|
cait |
ah that is the output |
10:05 |
|
cait |
I think maybe ty and make sure tthe files exist and are owned by your koha's instance user? |
10:06 |
|
ashimema |
dare I saw I'm considering dropping matrix.. I thought it was getting better, but with each feature introduced it seems to get less reliable on the irc bridging front ☹️ |
10:07 |
|
ashimema |
I really wish we could migrate wholesale to a modern chat system though ☹️ |
10:07 |
|
magnuse |
ashimema: like mattermost or rocket? |
10:08 |
|
ashimema |
mmm |
10:08 |
|
ashimema |
I dunno.. we've tried various times in the past to use those but we've never managed to get the adoption |
10:08 |
|
ashimema |
isn't mattermost another bridging thing ? |
10:09 |
|
ashimema |
it's been a while since I looked into this stuff |
10:09 |
|
NikolayGospodinov[m] |
ok |
10:09 |
|
cait |
the only thing I'd like is an easy way for people to get in |
10:10 |
|
cait |
like not having to jump hoops getting an invite etc. - but if we need to bite that bullet.... we can still discuss it |
10:10 |
|
ashimema |
kinda fed up of all the chat clients I have to run though... telegram, signal, slack, whatsapp, matrix, irc, discord, zoom, element.. that's a crazy set to just manage to stay in touch with various projects I'm involved in ☹️ |
10:11 |
|
ashimema |
I'm in the "community" slack too.. but I agree it's hurdles to join, and there's not a momentum of people in there either |
10:11 |
|
cait |
yeah.... it's a lot for personal use already too |
10:13 |
|
aw-bib[m] |
tcohen was very fast on bug 29930 and I just signed off his test case (which I now try to understand). do I need to change the status somehow or is `signed off` what it should be? |
10:13 |
|
huginn` |
Bug https://bugs.koha-community.or[…]_bug.cgi?id=29930 normal, P5 - low, ---, janik.hilser, Signed Off , 'cardnumber' overwritten with userid when not maped (LDAP auth) |
10:14 |
|
magnuse |
ashimema: nah, mattermost is like slack. the swedish koha network moved from slack to mattermost recently |
10:14 |
|
ashimema |
yeah, I was impressed.. he beat me 🙂 |
10:14 |
|
ashimema |
the challenge is hosting something |
10:15 |
|
ashimema |
oftc hosting irc for free for us is a big win |
10:15 |
|
magnuse |
yeah |
10:15 |
|
cait |
aw-bib[m]: signed-off is correct |
10:16 |
|
cait |
ideally you could add your sign-off line to the patch |
10:16 |
|
cait |
I think you reattached only one, but not both |
10:16 |
|
cait |
do you need some help with that? |
10:17 |
|
cait |
signing off mulitple patches that is |
10:22 |
|
magnuse |
ashimema: "community" slack = the koha-US one? |
10:22 |
|
ashimema |
yeah, they sent a mail out a while ago opening it up |
10:23 |
|
ashimema |
but it's still rather Koha-US branded |
10:23 |
|
ashimema |
well... the signup is at least |
10:23 |
|
ashimema |
there's 131 people signed up to it, but very low traffic |
10:24 |
|
ashimema |
and so far all I see it US activity |
10:24 |
|
ashimema |
I like the look of Mattermost |
10:24 |
|
ashimema |
it's come a long way since I last looked |
10:36 |
|
* magnuse |
joined the Koha-US slack a while back |
10:36 |
|
magnuse |
yeah, Mattermost seems good from what i have seen so far. i was happy with rocket when i tested it a few years back too |
10:37 |
|
ashimema |
I liked rocket, but yeah.. it was empty.. people didn't migrate so I killed it off again |
10:39 |
|
ashimema |
Do we have any kind of plan as to when +strings is more appropriate than adding 'embed' ? |
10:39 |
|
ashimema |
thinking about bug 35744 in particular |
10:39 |
|
huginn` |
Bug https://bugs.koha-community.or[…]_bug.cgi?id=35744 enhancement, P5 - low, ---, jonathan.druart+koha, Signed Off , Implement +strings for GET /patrons/:patron_id |
10:40 |
|
aw-bib[m] |
@cait I added only one as bz told me that the other is already there. so I changed the initial HEAD~2 to HEAD. |
10:40 |
|
huginn` |
aw-bib[m]: downloading the Perl source |
10:40 |
|
cait |
what we'd usually do is |
10:40 |
|
cait |
git so 2 |
10:40 |
|
cait |
git bz attach -e HEAD~2.. |
10:41 |
|
cait |
overwriting what is already there with the new signed-off patches |
10:42 |
|
cait |
when you uploaded only one of both, the sequence of the patches on the bug changed - that can cause problems, in this case it's probably alright, but in other patch sets it could create issues |
10:42 |
|
aw-bib[m] |
ok, I was unsure about the overwrite. but of course I can do this. takes a moment. |
10:45 |
|
aw-bib[m] |
cait: better now? |
10:46 |
|
cait |
perfect :) |
10:49 |
|
aw-bib[m] |
. o O ( updating own readme ) |
11:22 |
|
|
oleonard joined #koha |
11:35 |
|
magnuse |
aw-bib[m]++ |
11:41 |
|
davewood |
our background jobs are stuck. 4 workers are running, rabbitmq is running. /cgi-bin/koha/admin/background_jobs.pl shows Progress null/1 |
11:41 |
|
davewood |
i am seeing the same issue on various koha instances. |
11:43 |
|
davewood |
actually the jobs are not stuck but something might have spammed the job queue because i am seeing lots of jobs with the same create timestamp |
11:43 |
|
davewood |
different koha versions too. 23.05.04.000 and 22.11.06.000 Rosalie to name two |
11:55 |
|
tcohen |
morning #koha o/ |
12:03 |
|
|
jzairo joined #koha |
12:31 |
|
krimsonkharne[m] |
more meetings incoming today, I won't be able to join the general meeting later |
12:32 |
|
ashimema |
seems to be the season for meetings 😜 |
12:32 |
|
ashimema |
I'm juggling two at a time mostly today |
12:41 |
|
cait |
tcohen++ # rebase help and general awesomeness |
12:58 |
|
|
lds joined #koha |
13:03 |
|
|
thd joined #koha |
13:11 |
|
magnuse |
ashimema: is there a season that is not for meatings? ;-) |
13:11 |
|
magnuse |
*meetings |
13:11 |
|
ashimema |
I wish |
13:11 |
|
thd |
tcohen: I have a question about traefik. |
13:38 |
|
tcohen |
hola thd |
13:38 |
|
thd |
hola |
13:38 |
|
tcohen |
what is it? |
13:38 |
|
|
fridolin joined #koha |
13:39 |
|
thd |
I have been trying to configure Traefik on my own VPS to use my pre-existing TLS certs. |
13:40 |
|
|
emlam joined #koha |
13:41 |
|
tcohen |
thd: that's well documented as far as I can tell |
13:41 |
|
tcohen |
https://doc.traefik.io/traefik/https/tls/ |
13:42 |
|
thd |
tcohen: When I have tried the supposed well documented method I am lucky to have a 404 error. |
13:43 |
|
tcohen |
do you have a working traefik and are trying to add TLS for a specific site? |
13:43 |
|
thd |
tcohen: Traefik is working with self signed certs. |
13:44 |
|
tcohen |
letsencrypt? |
13:44 |
|
thd |
There seems to be no reason to obtain redundant certs when I already have wildcard certs for most of my domains. |
13:45 |
|
tcohen |
ah, yes |
13:45 |
|
thd |
Yes, letsencrypt certbot using rfc1236. |
13:46 |
|
tcohen |
I have only used the traefik-negotiated letsencrypt certs with it |
13:46 |
|
tcohen |
my sysadmin is back at the end of the month, I know he has set some godaddy certs with traefik for a customer |
13:48 |
|
thd |
Also, where do the logs go when a container reboots continuously from some trivial docker-compose error. |
13:49 |
|
thd |
Who do you find an error from a continuously restarting container? |
13:49 |
|
thd |
s/Who/How/ |
13:49 |
|
tcohen |
how are you running it? |
13:50 |
|
thd |
sudo docker compose -up d |
13:51 |
|
|
khall_ joined #koha |
13:51 |
|
tcohen |
if your docker compose has the --logs and --access parameters for the command... |
13:51 |
|
tcohen |
you should be able to |
13:51 |
|
tcohen |
docker logs -f <service> |
13:51 |
|
ashimema |
should there be a jitsi link for the meeting later |
13:52 |
|
|
georgew joined #koha |
13:54 |
|
thd |
Well that works. |
13:57 |
|
aude_c[m] |
<ashimema> "should there be a jitsi link for..." <- If these are on Jitsi now, we can make one? |
13:57 |
|
ashimema |
seems there isn't one.. I'm happy going irc only.. I have a feeling there's not going to be all that many attendees.. the agenda is short too |
13:58 |
|
* fridolin |
is present but at home with kids so IRC is fine |
13:58 |
|
thd |
I have not quite understood the distinction between static and dynamic Traefik configurations other than obtaining acme certificates may not work properly with a static Traefik configuration which might be accidentally invoked by picking some option which only works in static mode or using a commands section in docker-compose . |
13:59 |
|
aude_c[m] |
In this case: gentle warning that there will be an IRC meeting starting in 2min https://wiki.koha-community.or[…]g_17_January_2024 |
13:59 |
|
|
michelle joined #koha |
14:00 |
|
thd |
Is this an actual IRC meeting? |
14:00 |
|
|
Brendan__CLAMS joined #koha |
14:01 |
|
aude_c[m] |
Yes for today, unless people express a preference for using Jitsi. |
14:01 |
|
aude_c[m] |
(like, right now) |
14:01 |
|
ashimema |
#startmeeting General IRC meeting 17 January 2024 |
14:01 |
|
huginn` |
Meeting started Wed Jan 17 14:01:33 2024 UTC. The chair is ashimema. Information about MeetBot at http://wiki.debian.org/MeetBot. |
14:01 |
|
huginn` |
Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. |
14:01 |
|
huginn` |
The meeting name has been set to 'general_irc_meeting_17_january_2024' |
14:01 |
|
ashimema |
#chair aude_c |
14:01 |
|
huginn` |
Warning: Nick not in channel: aude_c |
14:01 |
|
huginn` |
Current chairs: ashimema aude_c |
14:01 |
|
ashimema |
#link https://wiki.koha-community.or[…]g_17_January_2024 Agenda |
14:01 |
|
ashimema |
#topic Introductions |
14:01 |
|
ashimema |
#info Please introduce yourself for the minutes with an #info |
14:02 |
|
oleonard |
#info Owen Leonard, Athens County Public Libraries, Ohio, USA |
14:02 |
|
aude_c[m] |
#info Aude Charillon, PTFS Europe, UK |
14:02 |
|
ashimema |
#info Martin Renvoize, PTFS Europe, UK |
14:02 |
|
georgew |
#info George Williams, Northeast Kansas Library System |
14:02 |
|
ashimema |
oooh, there are a few people here 🙂 |
14:02 |
|
ashimema |
#info Katrin asked Aude and I to step in and chair, she sends her apologies, she has a clash. |
14:02 |
|
emlam |
#info Emily Lamancusa, Montgomery County Public Libraries, USA |
14:02 |
|
Brendan__CLAMS |
#info Brendan Lawlor, CLAMS, Hyannis, MA, USA |
14:02 |
|
jzairo |
#info Jessica Zairo, ByWater |
14:03 |
|
tcohen |
#info Tomas Cohen Arazi |
14:03 |
|
thd |
#info Thomas Dukleth, Agogme, New York City [power and light is back on] |
14:04 |
|
aude_c[m] |
#topic Announcements |
14:04 |
|
ashimema |
brill, lots of friendly people 🙂 |
14:04 |
|
aude_c[m] |
Almost regretting not setting up Jitsi link |
14:04 |
|
aude_c[m] |
#info Happy new year everyone! 👋 |
14:04 |
|
aude_c[m] |
Any other announcements? :) |
14:05 |
|
Brendan__CLAMS |
it's my first time attending an IRC meeting, so I'm kinda glad you didn't set up a jitsi this time |
14:05 |
|
ashimema |
#info No specific announcements from the RM, we've started pushing enhancements and she's working through the queues now. Please keep QAing, that queue is rather high. |
14:05 |
|
thd |
I notice that there is no Jitsi link for next week's development meeting. |
14:06 |
|
* ashimema |
hasn't done the jitsi links before.. so I'm not sure how they're done.. hence not getting one in there when I noticed a little last minute a few minutes ago |
14:06 |
|
aude_c[m] |
#action aude_c to let cait know there is no Jitsi link for next week's development meeting |
14:07 |
|
aude_c[m] |
It's super easy and I could do it in seconds if people here wish to see each other's faces |
14:07 |
|
ashimema |
No marcelr, so I'll re-iterate the call to arms around QA in his stead |
14:07 |
|
* oleonard |
is happy to stick with IRC today |
14:07 |
|
fridolin |
#info Fridolin Somers, Biblibre, France |
14:07 |
|
thd |
ashimema: They seem to be fairly generic unless I have missed something. |
14:07 |
|
ashimema |
#info QA queues are high, lets bolster efforts a little team 😉 |
14:08 |
|
ashimema |
I think that's all the noted announcements I had.. does anyone else here have anything they'd like recorded? |
14:08 |
|
ashimema |
ooh, hackfest |
14:10 |
|
ashimema |
#info There will be a Marseille Hackfest again this year, a little later though from 8th - 12th April. Biblibre have moved offices, so numbers may be a little more limited, but they are investigating additional office space options right now. |
14:10 |
|
ashimema |
lets move on then |
14:10 |
|
ashimema |
#topic KohaCon24 update |
14:10 |
|
aude_c[m] |
#topic KohaCon24 update |
14:10 |
|
aude_c[m] |
#info Caroline posted an update. |
14:11 |
|
aude_c[m] |
#link https://2024.kohacon.org/kohac[…]uilding-together/ |
14:11 |
|
aude_c[m] |
#info Dates for KohaCon 2024 announced! 23 to 27 September |
14:11 |
|
aude_c[m] |
#info The call for proposals is open too. Use the link from the website or go straight to https://sondagebiblio.org/inde[…]hp/835536?lang=en |
14:11 |
|
Brendan__CLAMS |
is there any way to participate in the hackfest remotely? |
14:11 |
|
ashimema |
excellent 🙂 |
14:12 |
|
|
kellym joined #koha |
14:12 |
|
fridolin |
Brendan__CLAMS: Hi, it is not usally with a virtual connexion |
14:12 |
|
fridolin |
any with the small place it migth be difficult |
14:12 |
|
fridolin |
but everyone still is on IRC |
14:12 |
|
ashimema |
The Marseille Hackfest tends to take a fairly organic approach.. i.e. the agenda gets built as we go.. However, there's often some zoom/jitsi etc interactions.. so if you're interested in joining any particular discussions or bringing anything in particular up I'm sure something can be arranged. |
14:13 |
|
fridolin |
yep |
14:13 |
|
Brendan__CLAMS |
Cool! thank you |
14:13 |
|
fridolin |
we have the same need with corporate meetings |
14:13 |
|
ashimema |
For example, we've had join EDI calls with the Swedish user groups in the past |
14:13 |
|
caroline |
sorry, I just came in, but I think everything has been said |
14:13 |
|
ashimema |
and erm demonstrations.. |
14:14 |
|
fridolin |
we may also record and broadcast some talks |
14:14 |
|
ashimema |
keeping an 'ear' on irc is the best way to not miss something that's a little on the spur of the moment. |
14:14 |
|
aude_c[m] |
Anything else on Hackfest or KohaCon? |
14:14 |
|
ashimema |
as for the KohaCon hackfest section.. I'll leave Caroline to elaborate there if there's anytihng to say 🙂 |
14:15 |
|
caroline |
Nothing is set in stone. The "conference" part is for sure streamed online. We have no plan for streaming hackfest workshops, but we can surely do jitsi meets to include remote people |
14:17 |
|
ashimema |
#info KohaCon24 conference very likely to be streamed, HackFest may include Jitsi meets to allow remote attendance, but more informally at the moment. |
14:17 |
|
ashimema |
shall we move on.. |
14:17 |
|
ashimema |
#topic Actions from last meeting |
14:17 |
|
caroline |
conference *for sure* streamed :) |
14:17 |
|
aude_c[m] |
#info All actions completed :D |
14:17 |
|
ashimema |
Looks like we just have one leftover action which I think is a copy/paste from the last agenda 🙂 |
14:18 |
|
aude_c[m] |
Unless anyone wants to own up to another action? 😅 |
14:18 |
|
aude_c[m] |
#topic General business |
14:18 |
|
ashimema |
not guitly.. this time |
14:19 |
|
|
Dyrcona joined #koha |
14:19 |
|
aude_c[m] |
#info Do we want to start naming releases - or not? There was some discussion on bug 35504 |
14:19 |
|
huginn` |
Bug https://bugs.koha-community.or[…]_bug.cgi?id=35504 blocker, P5 - low, ---, martin.renvoize, Pushed to stable , Release team 24.05 |
14:19 |
|
aude_c[m] |
#link https://bugs.koha-community.or[…]_bug.cgi?id=35504 |
14:19 |
|
huginn` |
Bug 35504: blocker, P5 - low, ---, martin.renvoize, Pushed to stable , Release team 24.05 |
14:20 |
|
ashimema |
22.11 actually had the first codename, 'Rosalie' as a dedication to Rosalie Blake. |
14:20 |
|
ashimema |
The discussion on bug 35504 was around adopting codenames more regularly and perhaps celebrating the current cycle having our first female in the Release Manager role. |
14:20 |
|
thd |
Is the bug citation the correct bug number? |
14:21 |
|
ashimema |
yeah.. discussion was 'an asside' in that bug |
14:21 |
|
aude_c[m] |
Yes, but the discussion is in the early comments |
14:21 |
|
aude_c[m] |
https://bugs.koha-community.or[…]g.cgi?id=35504#c2 |
14:21 |
|
huginn` |
Bug 35504: blocker, P5 - low, ---, martin.renvoize, Pushed to stable , Release team 24.05 |
14:21 |
|
ashimema |
the codename was not added in the bug before we discus the idea here and get some sort of consensus. |
14:21 |
|
oleonard |
I find the date numbering system to be so useful I don't think the naming of releases needs to be standard, but I'm happy to see it happen for special occasions. |
14:22 |
|
fridolin |
+1 |
14:22 |
|
ashimema |
I agree.. I suppose the question is.. 'Is our first female rm a special occassion 😜 ' |
14:22 |
|
fridolin |
++ |
14:22 |
|
caroline |
I think that would be something to celebrate! |
14:22 |
|
ashimema |
I certainly wouldn't want to switch away from the date system.. codenames are 'extras' in my eyes |
14:23 |
|
oleonard |
I have a feeling cait would not want the release to be named after her |
14:23 |
|
ashimema |
I suppose 3.14 sorta had a codename too.. it was 'Pie' |
14:23 |
|
caroline |
It doesn't have to be her name |
14:23 |
|
aude_c[m] |
#info Several people agree that naming of releases doesn't need to happen as the standard, but could happen for special occasions |
14:23 |
|
fridolin |
we may use somthing close like "Catarina" |
14:24 |
|
ashimema |
haha, indeed.. when I suggested he idea to her, she was more onboard with naming it after another famous women in tech 😜 |
14:24 |
|
Brendan__CLAMS |
how about Henriette for the programmer who created marc |
14:24 |
|
aude_c[m] |
That sounds cool |
14:24 |
|
oleonard |
A dubious distinction XD |
14:24 |
|
thd |
;) |
14:24 |
|
Brendan__CLAMS |
lol |
14:25 |
|
ashimema |
I like that.. catches 'Library' and 'Technology' in one hit |
14:25 |
|
Brendan__CLAMS |
and women in library and tech |
14:25 |
|
oleonard |
And it's a cool name |
14:26 |
|
fridolin |
a french touch |
14:26 |
|
aude_c[m] |
#info Should we treat our first woman Release Manager as a "special occasion" and therefore name the 24.05 release? If so, what could this name be? (that our RM herself would agree with) |
14:26 |
|
aude_c[m] |
Are we talking about Henriette Avram? https://www.loc.gov/loc/lcib/0605/avram.html |
14:26 |
|
ashimema |
Shall I open a bug for it and we can put suggestions there for a vote next meeting? |
14:26 |
|
|
TriveniChandriki[m] joined #koha |
14:26 |
|
TriveniChandriki[m] |
Good evening all |
14:26 |
|
thd |
I assume that everyone now knows that MARC is well preserved inside BibFrame as some major academic libraries objected to everything being left out of the original simple design of BibFrame |
14:27 |
|
TriveniChandriki[m] |
Can we increase barcode text |
14:27 |
|
oleonard |
TriveniChandriki[m]: we are in a meeting at the moment |
14:27 |
|
aude_c[m] |
#info Suggestion of Henriette Avram, who created MARC |
14:27 |
|
TriveniChandriki[m] |
Oh sorry carry on |
14:28 |
|
aude_c[m] |
#action ashimema to open a new bug to collect suggestions, so a vote can take place at a future meeting. |
14:28 |
|
Brendan__CLAMS |
maybe the LOC job was just a cover lol |
14:29 |
|
ashimema |
#info bug 35829 opened to collect suggestions for a release codename. |
14:29 |
|
huginn` |
Bug https://bugs.koha-community.or[…]_bug.cgi?id=35829 enhancement, P5 - low, ---, koha-bugs, NEW , Codename for 24.05 |
14:29 |
|
caroline |
ashimema++ |
14:29 |
|
thd |
Much of what LC does is a cover for something. It is Congress' library, though, not the president's. |
14:30 |
|
aude_c[m] |
Any other business (not on the agenda but that people would like to put forward now)? |
14:30 |
|
ashimema |
OK.. did we have any other topics or business people would like to raise/discuss? |
14:30 |
|
ashimema |
haha |
14:30 |
|
ashimema |
thanks aude_c |
14:30 |
|
aude_c[m] |
😉 |
14:31 |
|
ashimema |
ok.. seems it's rather quiet on that front |
14:31 |
|
ashimema |
#topic Set date and time for the next meeting |
14:31 |
|
ashimema |
I've lost track.. what's the cadence of general meetings these days? |
14:32 |
|
aude_c[m] |
🤷♀️ |
14:32 |
|
thd |
They might be only twice a year now. |
14:32 |
|
caroline |
I think it's every 6 months or something... |
14:32 |
|
ashimema |
last one was July by the looks |
14:32 |
|
ashimema |
so 2 a year? |
14:32 |
|
georgew |
I think the last meeting was in July of 2023 |
14:32 |
|
ashimema |
yup |
14:33 |
|
aude_c[m] |
In 2023 there are wiki pages for meetings in April and July... and January 2024 (need to fix that category) |
14:33 |
|
ashimema |
the developer meetings are more frequent and we can always choose to call an extra one from one of those. |
14:33 |
|
fridolin |
maybe at the end of this cycle |
14:33 |
|
aude_c[m] |
But if you want a decision for naming 24.05, you'll need to vote at an earlier meeting |
14:33 |
|
ashimema |
we'll want one in early May I would think.. to vote the next team |
14:33 |
|
thd |
... with the provision for calling some extra general meeting if really necessary. |
14:33 |
|
ashimema |
that's scary.. already thinking about the next cycle now |
14:34 |
|
ashimema |
lets say early may |
14:34 |
|
fridolin |
sounds good |
14:34 |
|
ashimema |
and we can perhaps vote on names at a dev meeting with extended invites |
14:34 |
|
aude_c[m] |
Right, this was the 3rd Wednesday in January. Third Wednesday in May is 15th. How does that sound? Or the week before? |
14:35 |
|
georgew |
I think May 8 is better |
14:35 |
|
ashimema |
I reckon 8th |
14:35 |
|
ashimema |
as 22nd is the proposed release date in general |
14:35 |
|
fridolin |
oh it is a holiday in France, May 8 |
14:35 |
|
fridolin |
second WW |
14:36 |
|
ashimema |
ok.. |
14:36 |
|
ashimema |
15th better for the french frido? |
14:36 |
|
fridolin |
15th sound better indeed |
14:36 |
|
ashimema |
still gives us a week to collar any extra's we want to pull in for the team |
14:36 |
|
ashimema |
OK.. 15th |
14:36 |
|
fridolin |
we have May 1 and 8 free so many are on extended holidays |
14:36 |
|
ashimema |
does this time work well for people? |
14:36 |
|
georgew |
I'll make it work |
14:37 |
|
Brendan__CLAMS |
sounds good to me |
14:37 |
|
oleonard |
Yes, this time is good |
14:37 |
|
ashimema |
#info Next meeting: 15 May 2024, 14 UTC |
14:37 |
|
aude_c[m] |
Thanks everyone! |
14:37 |
|
ashimema |
we can tweak the time a little if I've got timezones and daylight savings wrong 😜 |
14:38 |
|
fridolin |
thanks a lot for chairing |
14:38 |
|
ashimema |
#info Thanks to everyone who attended 🙂 |
14:38 |
|
ashimema |
#endmeeting |
14:38 |
|
huginn` |
Meeting ended Wed Jan 17 14:38:14 2024 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
14:38 |
|
huginn` |
Minutes: https://meetings.koha-communit[…]-01-17-14.01.html |
14:38 |
|
huginn` |
Minutes (text): https://meetings.koha-communit[…]4-01-17-14.01.txt |
14:38 |
|
huginn` |
Log: https://meetings.koha-communit[…]17-14.01.log.html |
14:38 |
|
caroline |
ashimema++ aude_c++ |
14:38 |
|
ashimema |
thanks for your help there aude_c |
14:40 |
|
|
marie-luce joined #koha |
14:40 |
|
oleonard |
aude_c[m]++ |
14:40 |
|
oleonard |
ashimema++ |
14:41 |
|
* ashimema |
slinks off to his next meeting.. |
14:41 |
|
thd |
Henriette++ |
14:42 |
|
caroline |
TriveniChandriki[m], I don't think it's possible to increase the font of the barcode numbers, if that's what you meant |
14:43 |
|
kellym |
aude_c++ @ashimema++ |
14:43 |
|
caroline |
re bug 30819 |
14:43 |
|
huginn` |
Bug https://bugs.koha-community.or[…]_bug.cgi?id=30819 normal, P5 - low, ---, thibaud.guillot, NEW , Not able to adjust size of the plain text barcode below the actual barcode |
14:44 |
|
ashimema |
you might be able to do something with CSS somewhere for those barcode numbers? |
14:44 |
|
ashimema |
pass |
14:45 |
|
oleonard |
Do we not display the hold cancellation reason anywhere? |
14:45 |
|
oleonard |
Is it only used in notices? |
14:47 |
|
oleonard |
Oh now I see it on the holds history page in the staff interface |
14:47 |
|
caroline |
Yes I just tried it, it's on that page |
14:47 |
|
caroline |
checking the opac too |
14:47 |
|
oleonard |
Shouldn't it also be in the OPAC? |
14:49 |
|
caroline |
yeah, it's not in the OPAC.... I don't know if we want it there? I think for transparency it's good, but a lot of libraries want stuff hidden in hte opac for practical reasons |
14:50 |
|
caroline |
It's an authorised value correct? We could show the "OPAC description" of the reason so libraries could put a user-friendly reason in the OPAC description and a staff reason in the description... |
14:51 |
|
ashimema |
yup |
14:51 |
|
ashimema |
that's what I'd expect |
14:51 |
|
ashimema |
though do we fallback to staff description if opac is empty.. I can't remember |
14:51 |
|
caroline |
normally yes |
14:51 |
|
ashimema |
might be nice if you could hide from opac just by leaving the value blank |
14:51 |
|
ashimema |
but that would be a big change to current flows |
14:52 |
|
caroline |
I always instruct clients to write an OPAC description only if they want it to be different in the OPAC |
14:52 |
|
caroline |
otherwise, the regular description is used both in staff and opac |
14:53 |
|
ashimema |
exactly |
14:53 |
|
ashimema |
so it would be an entirely different thing to hide in opac instead |
14:53 |
|
ashimema |
anywho.. I'm spitballing |
14:53 |
|
ashimema |
😉 |
14:53 |
|
oleonard |
Put in the OPAC description for every hold cancellation reason: "To reiterate, the hold was cancelled" |
14:53 |
|
caroline |
lol! |
14:54 |
|
caroline |
yeah, it would have to be a preference imo, or maybe a different table column that we could hide in table settings |
14:57 |
|
aude_c[m] |
Regarding the General meeting... I think you guys use the magic script to generate the next meeting page? Leaving that to the people who know 😬 |
14:58 |
|
aude_c[m] |
I've added the links of the minutes and date of next meeting to today's page (and fixed the categories), but someone still needs to generate the next meeting page and add it to Next IRC meetings |
14:59 |
|
ashimema |
I'll ask Joubu about it.. the script hasn't worked for me in a while |
15:01 |
|
aude_c[m] |
Thanks |
15:01 |
|
aude_c[m] |
ashimema++ |
15:02 |
|
Brendan__CLAMS |
is this a place where I can ask about how a part of Koha code works? |
15:02 |
|
oleonard |
Yes |
15:02 |
|
georgew |
The way to have an authorized value description be visible in the staff interface and appear blank in the OPAC is to put a blank space in the OPAC description for that authorized value |
15:03 |
|
caroline |
thanks georgew! I wondered if that was possible or if it only considered the space as "nothing" therefore using the regular description |
15:03 |
|
Brendan__CLAMS |
I started working on this bug https://bugs.koha-community.or[…]_bug.cgi?id=35746 got something partly implemented but now I'm stuck |
15:04 |
|
huginn` |
Bug 35746: enhancement, P5 - low, ---, blawlor, NEW , Multiple selections for parameters used in the IN function |
15:04 |
|
georgew |
I've used that trick in the past. I'm imagining it still works |
15:04 |
|
oleonard |
georgew: The only problem with that is if the authval is displayed inside parentheses you'll get "( )" |
15:04 |
|
georgew |
Yes. |
15:05 |
|
georgew |
I had to step away for a minute so I only caught part of the conversation, so I'm not sure what the context is. Which authorized value are you messing around with? |
15:06 |
|
oleonard |
georgew: We're talking about whether hold cancellation reasons should appear in the OPAC on the patron's holds history page |
15:06 |
|
oleonard |
Brendan__CLAMS: That will be very cool if you're able to get it working (I'm no help unfortunately) |
15:09 |
|
Brendan__CLAMS |
the main problem is that all the sql_param_names and the sql_params in the url get stored as arrays, and then handled one at a time, the multi select just sends extra sql_params in the url and I need to somehow handle that in guided_reports.pl |
15:10 |
|
Brendan__CLAMS |
actually the main problem is I've never written perl code before :) |
15:10 |
|
georgew |
I don't think Ihave any libraries using hold cancellation reasons, so I'm can't help much there. |
15:14 |
|
caroline |
might be controversial, but I've asked chatgpt for help in perl in the past (I don't know perl either) |
15:15 |
|
oleonard |
What controls whether a hold cancellation notice is sent? |
15:16 |
|
emlam |
I don't totally follow how the template/.pl file interactions work either, but this line from later in the file looks like it may be the structure you need: my @ids = $input->multi_param('ids'); |
15:17 |
|
emlam |
(it pulls the report ids if you have selected multiple reports to delete) |
15:19 |
|
emlam |
oh wait never mind. Obviously I didn't understand how the templates work enough to understand your question ^_^;; |
15:20 |
|
Brendan__CLAMS |
ya my understanding is that multi_param function grabs an array (maybe wrong terminology as I'm new to perl) of all the url params that have the same name |
15:22 |
|
Brendan__CLAMS |
but in the SQL reports, all parameters are in one array, so I need to possibly change how that works by changing the name prop on the multi select, or figure some other way to parse it to get the multiselect values separately |
15:24 |
|
Brendan__CLAMS |
my other thought is to write javascript that if the form has a multiselect it would prevent the default submission of the form and format the multi select values into one sql_param, so then the perl should more or less just do it's current thing |
15:25 |
|
Brendan__CLAMS |
that seems possible although kinda hackish |
15:37 |
|
|
khall joined #koha |
15:38 |
|
|
blawlor joined #koha |
16:02 |
|
caroline |
do any of you know if the misc/cronjobs/create_koc_db.pl script is useful for the external offline circ tools or only the deprecated built-in one? |
16:03 |
|
oleonard |
I think it's used by the Windows program |
16:03 |
|
oleonard |
Not sure about the Firefox addon (does that still work?) |
16:04 |
|
caroline |
oh ok thanks! |
16:04 |
|
caroline |
I think marie-luce tested the firefox plugin recently and she told me it works |
16:05 |
|
caroline |
we have never tested the windows one as we all have ubuntu computers |
16:16 |
|
|
khall_ joined #koha |
16:22 |
|
caroline |
If there are any TT experts, or anyone who uses TT a lot (no need to be an expert) around, could you check what I wrote here https://gitlab.com/koha-commun[…]1a8681a_2735_2809 |
16:22 |
|
ashimema |
it all reads sane to me caroline |
16:22 |
|
ashimema |
aude_c already asked here 😜 |
16:22 |
|
caroline |
ah oops lol! |
16:22 |
|
caroline |
thanks ashimema! |
16:22 |
|
ashimema |
hehe |
16:23 |
|
ashimema |
no harm in asking for more eyes 😜 |
16:23 |
|
caroline |
I had asked last week, but in the evening here and there weren.'t a lot of people around |
16:24 |
|
caroline |
I admit I don't understand completely the thing with the periods like 245.0.a.0 |
16:28 |
|
ashimema |
hmm |
16:29 |
|
ashimema |
why does the api 'List biblios' endpoint require full cataloguing permissions! |
16:33 |
|
tcohen |
catalogue != cataloguing |
16:33 |
|
tcohen |
catalogue => staff access |
16:34 |
|
tcohen |
cataloguing permissions is 'editcatalogue' |
16:35 |
|
ashimema |
ah yes |
16:35 |
|
ashimema |
such a mess |
16:35 |
|
ashimema |
permissions are horrible |
16:37 |
|
ashimema |
any further thoughts on bug 29509 tcohen? |
16:37 |
|
huginn` |
Bug https://bugs.koha-community.or[…]_bug.cgi?id=29509 normal, P5 - low, ---, martin.renvoize, In Discussion , GET /patrons* routes permissions excessive |
16:38 |
|
tcohen |
can take a look later |
16:38 |
|
tcohen |
packing to go work downtown now |
16:38 |
|
ashimema |
okies |
16:43 |
|
reiveune |
bye |
16:43 |
|
|
reiveune left #koha |
16:56 |
|
fridolin |
bye bye |
16:56 |
|
|
fridolin left #koha |
17:45 |
|
|
emlam joined #koha |
18:45 |
|
|
khall joined #koha |
18:46 |
|
|
saa joined #koha |
18:47 |
|
saa |
while staging records through browser if the number of records are more the stage records fails how to handle data import with more than 50000 records importing into batch in one go |
18:50 |
|
|
kellym joined #koha |
18:52 |
|
|
kellym left #koha |
18:59 |
|
caroline |
saa, you can use the bulkmarcimport.pl script found under misc/migration_tools if I remember correctly |
19:01 |
|
|
saa joined #koha |
19:01 |
|
caroline |
also, I've found that the interface will give an error as if the import has failed, but it continues in the background anyway. If you check the database (like select count(*) from biblio) you'll see the number of records continues to increase even after the interface has stopped |
19:08 |
|
|
khall_ joined #koha |
20:37 |
|
bwv582 |
davidnind: Thank you. I see what looks like two patch files there. Do I need them both? |
20:59 |
|
davidnind |
bwv582: Sorry, I don't know enough to advise you on how to manually make the changes - the database structure needs to be changed, so I think it is the statements in the "Upgrade to 23.06.00.013 may fail" patch |
20:59 |
|
davidnind |
As always, testing on a development/testing system is recommended |
20:59 |
|
pastebot |
"davidnind" at 127.0.0.1 pasted "Databse structure for master" (54 lines) at https://paste.koha-community.org/35769 |
21:02 |
|
davidnind |
^^ if you share the output from the two database statements I used in the paste, and add them to the bug (along with your database version) it may provide some clues to help others troubleshoot |
21:04 |
|
ashimema |
I think I missed some chatter there... |
21:07 |
|
davidnind |
About what changes to make manually to fix an upgrade issue - bug 35687 |
21:07 |
|
huginn` |
Bug https://bugs.koha-community.or[…]_bug.cgi?id=35687 blocker, P5 - low, ---, koha-bugs, Needs Signoff , Upgrade to 23.06.00.013 may fail |
21:07 |
|
davidnind |
(if that was the chatter you were referring to.... 8-) ) |
21:31 |
|
caroline |
on bugzilla, is there any way to make the "Text to go in release notes" box bigger in the browser? I mean like in some places you can drag the corner of a text box to make it bigger when the text is long |
21:31 |
|
caroline |
When release notes are long, I find they are hard to read... |
21:32 |
|
caroline |
or maybe adapt the length to the content? I don't know which would be easier, if any is possible at all |
21:38 |
|
davidnind |
For me, I can only make it bigger when I edit it |
21:39 |
|
caroline |
ah maybe that is the difference... it is not normally editable so it is fixed... |
21:40 |
|
davidnind |
It would be ideal if all the text in the release note field was displayed when viewing it though... |
21:40 |
|
davidnind |
Not sure whether that is configurable in Bugzilla or not |
21:40 |
|
davidnind |
I do try to keep them succinct, but sometimes it is not possible |
22:16 |
|
|
cait joined #koha |
22:50 |
|
bwv582 |
davidnind: Thanks. I am still trying to get clear on what the error actually means. Looking at the bugzilla page will help, I think. |
22:51 |
|
bwv582 |
I thought it was going to be an easy apt upgrade |
22:51 |
|
bwv582 |
I should have known better! |
23:36 |
|
|
dpk joined #koha |