IRC log for #koha, 2023-07-31

← Previous day | Today | Next day → | Search | Index

All times shown according to UTC.

Time Nick Message
06:17 thibaud_g joined #koha
06:30 thibaud_glt joined #koha
06:33 reiveune joined #koha
06:33 reiveune hello
07:10 cait joined #koha
07:15 cait hi #koha
07:44 paulderscheid[m] morning #koha
07:51 PedroAmorim[m] o/
08:04 HH joined #koha
08:05 HH joined #koha
08:05 HH hello
08:05 Test koha char
08:05 chat*
08:07 paulderscheid[m] You have reached Koha chat HH
08:16 thibaud_g joined #koha
08:18 Pascal joined #koha
09:22 cait paulderscheid[m]: please leave a message after the beep?
09:23 paulderscheid[m] Haha, seems we lost the connection
09:25 cait paulderscheid[m]: are we the last ones not on vacation?
09:25 paulderscheid[m] Maybe
09:25 Well Helsinki will be my 'summer vacation' :D
09:26 cait it's similar for me
09:26 but also taking a week off after Helsinki (catching up on sleep etc. ;) )
09:26 paulderscheid[m] Haha, good call
09:34 cait hm what is the difference betwee  NoIssuesChargeGuarantees  and  NoIssuesChargeGuarantorsWithGuarantees?
09:35 paulderscheid[m] Sounds like the first one are guarantees and the second one are guarantors that are linked to those guarantees
09:35 cait oh yes.
09:35 I am not sure if that didnt get lsot in translaton
09:36 paulderscheid[m] It's a mouthfull
09:36 cait I think we also have a translation error there, fixing it
09:51 khall_ joined #koha
10:44 oleonard joined #koha
10:51 oleonard Hi #koha
10:54 tcohen[m] hola #koha o/
11:28 cait hola tcohen
11:46 domm[m] How can I prevent / allow that when importing auth_headers via SRU 001 will be set to the value auf auth_header.authid?
11:46 cait youc an't
11:47 and I blame marcelr ;)
11:47 domm[m] I think I remember that there was some plugin that would allow setting 001 to auth_header.authid?
11:47 cait I remember when we changed/discussed that, it's not a configurable behaviour. You might also see some issues if you change it in Koha
11:48 maybe you are thinking bout the feature to set 001 = biblionumber for bibliographic records?
11:48 domm[m] probably :-)
11:48 cait tbh - I have an issue with the auths too... we use a custom bullkmarcimport to enforce 001 = authid - but i would not recommend that
11:49 domm[m] so when doing SRU Import 001 will always be set to authid?
11:49 cait yes
11:49 I believe ther eis an open bug for moving the 001 to 035
11:50 I thinkt hat might be hte best soution if you need to match later on
11:53 domm[m] yeah, because we have a lib that first wanted to have 001=authid, so we mapped those ids during migration. now they want to import the whole of GND (auth, not biblio) for easier/faster catalogouing, therefore we changed 001 back to GND-ID. But if they use SRU to import auths, we end up with auths where 001=auth_id (and 035 = GND-ID), and I'm not sure how/if we can then later match those when GND provides updates
11:54 cait GND is only auth, not biblio :)
11:54 but... i woudl not recommend diong that honestly
11:54 have you checked how many records that is?
11:55 and there is tons of changes
11:55 and 001 shoudl be really set by Koha, there is a reason it was changed...
11:56 I wonder how you could import them with a different value in the first place hm.
11:58 domm[m] ok, I guess I'll wirit
11:58 s/wirit/write up our plan and post it to the users list for feedback?/
12:00 cait I don't find numbers, but I expect the GND file to be huge and quite some work to maintian it in Koha
12:00 especially maintaining it with merges/deletes etc.
12:00 domm[m] well, the customer wants it (because their old software did it), so...
12:00 cait but the ID issue is separate I guess, I don#t remember why exactly we encorce the 001 now, but marcelr might remember, I know he worked on the auth code quite a bit
12:16 thibaud_g joined #koha
13:09 PriyanshuSoni[m] cait: Hey cait, can i erase search suggestions of the search bars. It appears automatically when i click the search bar in opac window and also let me know how to erase search history of catalogs and patrons in staff interface.
13:09 cait it's a browser feature
13:09 not a Koha feature
13:09 for search history there is a cron job - cleanup_database.pl you can run regularly
13:10 but the auto-suggest is most likely coming from your browser#s configuration
13:14 emlam joined #koha
13:16 PriyanshuSoni[m] ok ok, got it cait. Thanks
14:09 cait left #koha
15:00 bag joined #koha
15:02 matts Hi #koha! Is there documentation somewhere about how to write a koha cronjob script the right way?
15:02 I didn't see anything in the wiki: https://wiki.koha-community.or[…]egory:Development
15:05 For instance, should I use cronlogaction or Log4perl ?
15:05 (I would go for Log4perl, but since most of the cron scripts use cronlogaction, I'm not entirely sure)
15:06 tcohen[m] cronlogaction
15:07 matts Thanks tcohen[m] ! Any other recommendation that comes to mind ?
15:07 tcohen[m] Include Koha::Script
15:07 matts yep
15:08 tcohen[m] look at Koha::Script
15:08 it has a way to avoid concurrent runs ,etc
15:09 matts I see that, thanks!
15:10 EdVealEd[m] joined #koha
15:28 Dyrcona joined #koha
15:28 reiveune bye
15:29 reiveune left #koha
15:32 EdVealEd[m] Hi
15:34 caroline Hi Ed!
15:35 EdVealEd[m] I am playing with different web based IRC means to see what let's me past my city IT department. I will be bouncing in and out trying to authenticate.  :)
15:36 caroline good luck!
15:38 tcohen[m] Hi Ed
15:38 I switched to Element/Matrix
15:38 jzairo joined #koha
15:38 EdVealEd[m] Hi @tcohen!
15:39 That is what I am using now but it doesn't seem to let me authenticate or see who else is online in the "People" section.
15:46 JBoyer joined #koha
15:58 oleonard joined #koha
16:17 leonardo joined #koha
16:17 leonardo thks@
16:18 my company is a reseller IT productos, We have a costumer what they need your licence
16:33 khall joined #koha
16:48 jzairo joined #koha
19:22 cait joined #koha
20:01 jzairo joined #koha
21:15 caroline QA-cait is on fire!
21:15 cait++
21:19 caroline joined #koha

← Previous day | Today | Next day → | Search | Index

koha1