Time  Nick             Message
06:33 reiveune         hello
07:15 cait             hi #koha
07:44 paulderscheid[m] morning #koha
07:51 PedroAmorim[m]   o/
08:05 HH               hello
08:05 HH               Test koha char
08:05 HH               chat*
08:07 paulderscheid[m] You have reached Koha chat HH
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 paulderscheid[m] Well Helsinki will be my 'summer vacation' :D
09:26 cait             it's similar for me
09:26 cait             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 cait             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
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 cait             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 cait             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 cait             I believe ther eis an open bug for moving the 001 to 035
11:50 cait             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 cait             but... i woudl not recommend diong that honestly
11:54 cait             have you checked how many records that is?
11:55 cait             and there is tons of changes
11:55 cait             and 001 shoudl be really set by Koha, there is a reason it was changed...
11:56 cait             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 domm[m]          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 cait             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
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 cait             not a Koha feature
13:09 cait             for search history there is a cron job - cleanup_database.pl you can run regularly
13:10 cait             but the auto-suggest is most likely coming from your browser#s configuration
13:16 PriyanshuSoni[m] ok ok, got it cait. Thanks
15:02 matts            Hi #koha! Is there documentation somewhere about how to write a koha cronjob script the right way?
15:02 matts            I didn't see anything in the wiki: https://wiki.koha-community.org/wiki/Category:Development
15:05 matts            For instance, should I use cronlogaction or Log4perl ?
15:05 matts            (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 tcohen[m]        it has a way to avoid concurrent runs ,etc
15:09 matts            I see that, thanks!
15:28 reiveune         bye
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 tcohen[m]        I switched to Element/Matrix
15:38 EdVealEd[m]      Hi @tcohen!
15:39 EdVealEd[m]      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.
16:17 leonardo         thks@
16:18 leonardo         my company is a reseller IT productos, We have a costumer what they need your licence
21:15 caroline         QA-cait is on fire!
21:15 caroline         cait++