Time  Nick           Message
00:07 koha-jenkins   Yippee, build fixed!
00:07 wahanui        Congratulations!
00:07 koha-jenkins   Project Koha_20.05_U18 build #77: FIXED in 45 min: https://jenkins.koha-community.org/job/Koha_20.05_U18/77/
00:12 koha-jenkins   Project Koha_20.05_D10 build #85: SUCCESS in 45 min: https://jenkins.koha-community.org/job/Koha_20.05_D10/85/
00:16 oleonard       @later tell tcohen Can you get a set of items from the API by passing a biblionumber?
00:16 huginn         oleonard: The operation succeeded.
00:19 koha-jenkins   Project Koha_20.05_U16 build #74: SUCCESS in 38 min: https://jenkins.koha-community.org/job/Koha_20.05_U16/74/
00:19 koha-jenkins   Project Koha_20.05_U20 build #75: UNSTABLE in 1 hr 8 min: https://jenkins.koha-community.org/job/Koha_20.05_U20/75/
00:57 koha-jenkins   Project Koha_20.05_D11 build #37: STILL UNSTABLE in 44 min: https://jenkins.koha-community.org/job/Koha_20.05_D11/37/
01:41 koha-jenkins   Project Koha_20.05_D11 build #38: STILL UNSTABLE in 43 min: https://jenkins.koha-community.org/job/Koha_20.05_D11/38/
03:33 koha-jenkins   Project Koha_19.05_D9 build #277: UNSTABLE in 37 min: https://jenkins.koha-community.org/job/Koha_19.05_D9/277/
03:35 koha-jenkins   Project Koha_19.05_U18 build #279: UNSTABLE in 38 min: https://jenkins.koha-community.org/job/Koha_19.05_U18/279/
03:40 koha-jenkins   Project Koha_19.05_D9_MDB10.3 build #25: STILL UNSTABLE in 46 min: https://jenkins.koha-community.org/job/Koha_19.05_D9_MDB10.3/25/
03:40 koha-jenkins   Project Koha_19.05_D9_MDB10.3 build #26: FAILURE in 8.2 sec: https://jenkins.koha-community.org/job/Koha_19.05_D9_MDB10.3/26/
04:11 koha-jenkins   Project Koha_19.05_D9 build #278: STILL UNSTABLE in 38 min: https://jenkins.koha-community.org/job/Koha_19.05_D9/278/
04:13 koha-jenkins   Project Koha_19.05_U18 build #280: STILL UNSTABLE in 37 min: https://jenkins.koha-community.org/job/Koha_19.05_U18/280/
04:30 koha-jenkins   Project Koha_19.05_D9_MDB10.3 build #27: NOW UNSTABLE in 46 min: https://jenkins.koha-community.org/job/Koha_19.05_D9_MDB10.3/27/
06:53 alex_a         Bonjour
06:55 ashimema[m]    mornin'
07:20 cait1          good morning #koha
07:47 dcook          morning all
07:47 dcook          I'm off for the night :D
07:51 magnuse        \o/
07:51 * magnuse      dreamt of marseille this morning, before waking up
08:36 cait1          oh marseille...
08:36 wahanui        marseille is coming up end of march, some time before that would be nice
08:58 nlegrand       I'm missing Marseille... Next hackfest will be grand.
10:24 oleonard       Hi #koha
10:41 tcohen         morning
10:42 oleonard       Hi tcohen
10:42 tcohen         oleonard yes
10:42 tcohen         he
10:59 ashimema[m]    morning tcohen
10:59 tcohen         moerning
12:03 koha-jenkins   Project Koha_19.11_D8 build #280: SUCCESS in 33 min: https://jenkins.koha-community.org/job/Koha_19.11_D8/280/
12:07 koha-jenkins   Project Koha_19.11_D9 build #250: SUCCESS in 36 min: https://jenkins.koha-community.org/job/Koha_19.11_D9/250/
12:10 koha-jenkins   Project Koha_19.11_U20 build #75: SUCCESS in 39 min: https://jenkins.koha-community.org/job/Koha_19.11_U20/75/
12:22 koha-jenkins   Project Koha_19.11_U18 build #244: SUCCESS in 51 min: https://jenkins.koha-community.org/job/Koha_19.11_U18/244/
12:37 koha-jenkins   Project Koha_19.11_D8 build #281: SUCCESS in 30 min: https://jenkins.koha-community.org/job/Koha_19.11_D8/281/
12:44 oleonard       I was not aware of search_for_data_inconsistencies.pl until today
12:45 koha-jenkins   Project Koha_19.11_D10 build #77: SUCCESS in 41 min: https://jenkins.koha-community.org/job/Koha_19.11_D10/77/
12:45 oleonard       It would be cool to have those tests available in the interface for admin/catalogers
12:48 oleonard       Joubu around?
12:53 koha-jenkins   Project Koha_19.11_D9 build #251: UNSTABLE in 43 min: https://jenkins.koha-community.org/job/Koha_19.11_D9/251/
12:59 fridolin       hi
13:02 oleonard       Hi fridolin
13:04 fridolin       we have new Dell laptops whoooo
13:04 fridolin       i7 and 16Go RAM
13:04 tcohen         \o/
13:05 cait1          :) congrats
13:07 tuxayo         fridolin: low power i7 or normal ones? It got confusing in the last years.
13:09 fridolin       heuuu
13:09 fridolin       Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz
13:09 oleonard       fridolin, I didn't get one!
13:10 fridolin       XD
13:10 tuxayo         fridolin: yay it's nice. Now you can send patches to have things like Zebra indexation and others to use all these threads :P
13:11 tuxayo         We got you!
13:11 liliputech_asu tuxayo: ^^
13:11 koha-jenkins   Project Koha_19.11_U20 build #76: SUCCESS in 49 min: https://jenkins.koha-community.org/job/Koha_19.11_U20/76/
13:12 liliputech_asu i got the smaller one, it's "only" i5, much lighter, too bad we won't travel much in the coming months ;)
13:12 kohaputti      I wonder if there will be any new translation updates before 20.11 release for koha, there is some syntax error in the fi-FI translation which is now fixed in Pootle but is waiting to be merged to Koha source code
13:14 koha-jenkins   Project Koha_19.11_U18 build #245: SUCCESS in 36 min: https://jenkins.koha-community.org/job/Koha_19.11_U18/245/
13:16 tuxayo         kohaputti: you mean there is something fixed in Pootle and you are waiting the next point release to have it?
13:16 tuxayo         It's only this way, as for 20.11, if it's fixed in stable (20.05), when 20.11 will created in Pootle, you will have the fix because next stable (20.11) is created by copying current stable IIUC
13:17 kohaputti      tuxayo, next point release meaning 20.11? It would be nice to have it also for 20.05 given the syntax error cause internal server error in the acquisition module
13:17 liliputech_asu brrrr... scary translation...
13:18 kohaputti      liliputech_asu, yeah, you can modify the templating code with translations.
13:18 kohaputti      which was the issue here
13:19 kohaputti      tuxayo, and yeah, the translation error fix is accepted in pootle
13:19 liliputech_asu oh, yes indeed. we also got some errors on the dutch version of koha, in 19.11, where columns names were translated. DataTable doesnt like that.
13:20 liliputech_asu There should be some way of signalling "one must not translate this!" in the templates
13:27 oleonard       liliputech_asu: Bugs like Bug 26392 should help
13:27 huginn         Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26392 enhancement, P5 - low, ---, julian.maurice, Signed Off , Wrap all translatable strings in opac-main.tt
13:27 tuxayo         +1
13:29 liliputech_asu ooooh :) nice... thx oleonard thx jajm ^^
13:29 tuxayo         liliputech_asu: «some errors on the dutch version of koha, in 19.11»
13:30 tuxayo         Something very important the translators should be told, they should always also copy their translations to the more recent versions of Koha. Otherwise it will be kind of lost and they will have to translate again the same string for the next version.
13:30 tuxayo         Whereas if it's also in stable (20.05), it will be copied when 20.11 will be created. And so on in the next cycle and thus it will never be lost.
13:30 oleonard       jajm++
13:31 tuxayo         https://translate.koha-community.org/nl_NL/19.11/
13:31 tuxayo         https://translate.koha-community.org/nl_NL/20.05/
13:31 tuxayo         the problem is happening very heavily
13:33 tuxayo         The staff interface is 66% translated in 19.11 and 14% in 20.05. This huge work won't copied to the next versions and thus will have to be redone
13:36 tuxayo         kohaputti: same bad news for you
13:36 tuxayo         Not the same magnitude
13:36 tuxayo         https://translate.koha-community.org/fi/19.11/
13:36 tuxayo         https://translate.koha-community.org/fi/20.05/
13:37 tuxayo         We can see that 19.11 is more complete than 20.05
13:40 tuxayo         liliputech_asu: BTW same for french :o
13:40 tuxayo         https://translate.koha-community.org/fr/19.11/
13:40 tuxayo         https://translate.koha-community.org/fr/20.05/
13:40 tuxayo         This seems to be a terrible pitfall
14:06 kohaputti      anybody else can reproduce with ES search that you cannot search for "/"?
14:07 kohaputti      I wonder if it is a config issue or something wrong with code
14:08 kohaputti      bug 26178 seems to be also about /
14:08 huginn         Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26178 normal, P5 - low, ---, oleonard, NEW , When executing a title search in the OPAC for titles that contain "/" in the main title, the search results do not display the entire title. Is "/" a "stop term"?
14:08 kohaputti      but a slightly different issue
14:13 oleonard       kohaputti are you able to reproduce bug 26178? I couldn't.
14:13 huginn         Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26178 normal, P5 - low, ---, oleonard, NEW , When executing a title search in the OPAC for titles that contain "/" in the main title, the search results do not display the entire title. Is "/" a "stop term"?
14:14 kohaputti      oleonard, I don't have elasticsearch using OPAC at hand now unfortunately
14:14 kohaputti      but I think my search would not get even that far
14:14 kohaputti      because the search fails totally
18:39 * cait         waves
18:47 caroline       he cait!
18:47 caroline       hi
18:47 cait           hi caroline :)
20:15 caroline       any idea why the pickup location dropdown would be limited to 1 library in the OPAC? I'm looking for clues b/c I went through all the holds syspref, the circ rules, I even checked if JQuery was hiding the other libraries... i'm running out of ideas... I'm sure it's super simnple too
20:16 cait           did you check branches?
20:16 caroline       yes
20:16 cait           there is a setting there for hiding the libary from pickup
20:16 caroline       they all have the pickup location to yes
20:17 cait           hm
20:17 cait           is the location the patron home library?
20:17 cait           or something other obvious?
20:17 caroline       the weird thing is that in the intranet, the pickup location is automatically set to the user's library, but in the OPAC, it's the first library (that may be a coincidence, but it's not the user's library, even though the user's library has an item)
20:18 cait           OPACHoldsIfAvailableAtPickup ?
20:18 wahanui        i think OPACHoldsIfAvailableAtPickup is only for OPAC, and that's why it's not in a module
20:18 caroline       it's set to Allow
20:18 caroline       and I tried Don't allow and I couldn't reserve anymore
20:19 cait           hm
20:19 cait           the hold pickup library match setting at the bottom of circulation rules?
20:19 caroline       hm, I'll check again
20:20 cait           hm i'd check default and library specific
20:21 caroline       nothing is set (default rules, user's library and the pickup library)
20:21 cait           sorry, what is set?
20:22 cait           oh no rule entered?
20:22 cait           in the last table?
20:22 caroline       the rule isn't set https://snipboard.io/kz6nxH.jpg
20:23 cait           caroline: maybe try to set something, could be an odd side effect?
20:24 caroline       I set the rule for the user's library, and it's still not in the drop down
20:25 cait           sorry :(
20:25 caroline       thanks for your help cait!
20:25 caroline       cait++
20:26 caroline       I have the feeling it's not a rules issue, but an OPAC issue
20:26 caroline       bc it works fine in the intranet
20:30 lari           transfer limits perhaps?
20:30 caroline       I was wondering about that, I've never used them...
20:31 caroline       but the only branch checked for each branch is itself... is that normal?
20:34 lari           i think the default is to have everything checked
20:34 lari           as allowed
20:35 caroline       So I'm guessing this system doesn't allow any transfers...