IRC log for #koha, 2022-01-17

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

All times shown according to UTC.

Time Nick Message
06:33 lmstrand joined #koha
07:03 reiveune joined #koha
07:04 reiveune hello
07:30 cait joined #koha
07:38 cait joined #koha
07:42 cait1 joined #koha
07:43 cait1 good morning #koha
07:56 marcelr joined #koha
07:56 marcelr hi #koha
07:58 alex_a joined #koha
07:58 alex_a Bonjour
08:01 lds joined #koha
08:05 matts hello
08:06 marcelr hello matts and alex_a
08:06 alex_a Bonjour marcelr
08:06 matts hi marcelr !
08:08 * cait1 waves
08:09 marcelr hi cait1
08:09 cait1 glad to see you around marcelr, always
08:09 marcelr cait1 did you see aleisha's last comment on recalls ?
08:10 having impression that we are on different tracks
08:10 which might end up in recalls postponed again
08:12 cait1 i think she wrote that in her last email as well
08:13 that she wanted to split the patch set up
08:14 I understood it's not about new functionality. only the base work
08:17 marcelr ok, no problem, it will needs signoffs again, qa postponed etc
08:17 cait1 hmm
08:17 marcelr and rebasing it a few times was waste of time for me
08:17 cait1 we are enough to manage sign-off and QA theoretically
08:18 i think this is an issue of communication
08:18 we had asked a lot of times for it to be split up into smaller chunks, now you askfor it not to be
08:18 marcelr i tried to be nice :)
08:18 cait1 I think we'll work it out
08:19 just saying we need to be on the same page to not have people do too much work
08:19 marcelr we'll see then, it drops from my priority list now
08:19 cait1 hm
08:20 it's still on mine, but I hope for help with code review still
08:25 marcelr sure
08:25 have been qaing for some time already ;)
08:33 magnuse marcelr++ cait++
08:52 marion joined #koha
09:50 marion_ joined #koha
10:23 ashimema Sooo many of us have sunk many hours into QAing that one over the years
10:23 Morning #koha
11:04 marcelr hi ashimema
12:12 lukeg joined #koha
12:12 marion_ joined #koha
12:19 davewood hi ... im trying to create PDFs for each borrower who has overdue item. the idea is to use koha/bin/conrjobs/overdue_notices.pl to create a CSV file with all the info and use that to create the PDF files. However, I am stuck trying to get more details out of the system. like the books signature (952$o) or how to address the user (Mr, Mrs, ...) ... academic title (yes this is an austrian library :) )
12:21 cait1 I haven't used the CSV feature - are the fields hardcoded or configurable?
12:21 if you only need help witht he datbase names and such it would be not too hrd I think
12:22 koha-jenkins joined #koha
12:22 davewood some are configurable ... not so easy to see the effect though. currently trying to get results, the statement i used some weeks ago doesnt yield them anymore.
12:23 perhaps I should come back once I got that going again
12:23 cait1 ok, let us know when you get there and we'll try to help
12:24 davewood if what I need isnt possible without code changes I would try to add more config options and check back here in order to get it integrated upstream. maintaining backwards compatibility of course.
12:25 cait1 we'll also love to help with that :)
12:36 koha-jenkins joined #koha
12:49 Joubu oleonard: please have a look at bug 25317, last comment
12:49 huginn Bug https://bugs.koha-community.or[…]_bug.cgi?id=25317 enhancement, P5 - low, ---, koha-bugs, CLOSED FIXED, Move translatable strings out of additem.js.inc
12:50 Joubu oleonard: yes, it's not added by this bug actually
12:57 domm hey, ES question: I have indexed some auths some time ago, when I inspect it via `curl http://localhost:9200/koha_lib[…]ties/_doc/:authid` everything looks fine (i.e. I have authtype: GEOGR_NAME and various other fields filled with data)
12:57 AnkeB joined #koha
12:58 domm I fiddled a bit with the search mappings (added 451a to heading-main), and re-indexed one auth
12:59 which now is broken (no authtype, and a lot less fields (in fact, only heading-main and match-heading))
12:59 any idea / hints what could have gone wrong?
13:03 hm, seems something is wrong with the ES mappings, because http://localhost:9200/:auth_in[…]/_mapping/?pretty only returns a few (not enough) fields
13:04 Joubu Shouldn't the whole catalogue be reindexed if mappings changed?
13:05 domm I also tried that, but the problem is that the auth-mappings are now wrong
13:08 ah, hm, weird
13:08 intranet/cgi-bin/koha/admin/searc​hengine/elasticsearch/mappings.pl now also only lists a very small subset of mapping
13:09 so it seems that when I used that form ("Search engine configuration (Elasticsearch)") in Intranet to add a new entry it somehow deleted all my other mappings?
13:10 Joubu hum, that would be a bad bug
13:11 you can reset to the original ones using the "reset" options, top of the page I think
13:11 it will reset to the default mappings
13:13 domm ok, I'll try the reset and will then check if I can reproduce a bug, or if I was just stupid (though two times the same stupidity on different machines would require an unusal large amount of stupidity on my part)
13:15 reset worked :-)
13:15 (easier than fetching the mappings from another system...)
13:25 related question: are there some docs somewhere, which search-field ('heading-main', 'author-title' etc) is used where in Koha?
13:30 Joubu I don't think we have such docs. But 'git grep' should provide you some hints :)
13:33 domm Joubu: yeah, but a bit of overview would be nice :-)
13:49 Joubu: it is a reproducible bug (at least in 21.05): bug 29893
13:49 huginn Bug https://bugs.koha-community.or[…]_bug.cgi?id=29893 critical, P5 - low, ---, koha-bugs, NEW , ElasticSearch Config UI deletes mappings
13:50 domm and quite a bad one, because it just deletes user config without any notice (unless I'm missing something..)
13:59 marcelr joined #koha
13:59 marcelr hi #koha
14:26 marion joined #koha
15:51 marie-luce joined #koha
16:35 cait1 left #koha
17:20 cait joined #koha
17:22 cait joined #koha
17:23 cait joined #koha
17:28 cait joined #koha
18:08 fridolin joined #koha
18:49 milktoast joined #koha
18:50 milktoast hello all... We have a question about converting an existing library manager to koha
18:52 We are currently using "primasoft" Handy Library Manager and would like to convert it to an open source Library manager
18:53 can we, and if so, how do we move the "primasoft" to  Koha
19:28 koha-jenkins Project Koha_Master_U20 build #281: UNSTABLE in 4 hr 53 min: https://jenkins.koha-community[…]a_Master_U20/281/
19:33 reiveune left #koha
21:29 domm F
21:29 ups, sorry, bad focus...
22:23 lukeg joined #koha

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

koha1