IRC log for #koha, 2023-05-19

All times shown according to UTC.

Time S Nick Message
00:10 dcook Hmm looks like the bugs.koha-community.org cert has expired. Looks like the autorenewal must not be working
00:17 jenneen[m] I did paste a record yesterday, however it doesn't seem to have worked. I've had another go but please let me know if it didn't come through.
00:18 aleisha dcook: ill let chris know!
00:22 dcook aleisha: Cheers!
00:23 dcook jenneen[m] You'd see a link in this chat if it worked
00:23 dcook I'll do an example..
00:23 pastebot "dcook" at 127.0.0.1 pasted "Test" (1 line) at https://paste.koha-community.org/13577
00:23 dcook You need to choose the channel at the very least
00:25 davidnind jenneen: I'm assuming this is the one with your records https://paste.koha-community.org/13575
00:26 davidnind I'm out for the rest of the afternoon, but will try this evening (unless someone beats me to it!)
00:26 jenneen[m] Yep, and I clicked paste it so it should be there by now
00:26 jenneen[m] Great thanks, davidnind
00:29 dcook At a glance, those dates in 952$r will cause problems
00:29 dcook They're not valid timestamps
00:30 dcook Same with 952$d
00:30 dcook Like I was saying yesterday, I don't think Koha is the issue. It's probably with the data.
00:30 dcook Haven't tried it myself yet as I have a few things I need to get done asap
01:16 aleisha rangi says he fixed the cert
02:22 aleisha joined #koha
03:31 Oak joined #koha
03:38 Oak joined #koha
03:48 davidnind thanks aleisha (and rangi)
03:49 jenneen[m] I remove the time 00.00.00.000000 from the $d field and see if that makes a difference
03:49 jenneen[m] * I'll remove
04:00 jenneen[m] I just checked the date format setting in our system and it was set for dd/mm/yyyy. I've now changed it to read yyyy-mm-dd as per the recoreds to be imported. I'll also remove the time stamp
04:14 dcook The date format setting won't affect the data processing. Just the display
04:16 jenneen[m] Yep. I just uploaded the edited record. it still didn't transpose the 945 to 952 so still not showing the item barcodes
05:04 dcook Not sure what you mean about transposing the 945 to 952
05:32 thibaud_g joined #koha
05:33 mtj jenneen[m]: the most common problem with importing marc records with items, is that some mandatory/required fields are missing
05:35 mtj ...or that an item's values for branchcode or itemtype dont exist in koha
05:45 mtj =952  \\$aLIB$bLIB$cNF$d1995-10-07​-00.00.00.000000$eBooks$fNot for loan$g26.00$l15$o398.9203 OXFO$p009895254$r2019-04-08-00.00.00.000000$t2$yBK$2ddc$8Reference
05:46 mtj $fNot for loan
05:46 mtj ^ thats probably an incorrect value?
06:00 marcelr joined #koha
06:00 marcelr o/
06:23 marcelr @later tell tcohen please push 33777
06:23 huginn marcelr: The operation succeeded.
06:49 ashimema morning
06:49 ashimema anyone want to look at the new form release notes and let me know what they think ?
06:49 ashimema https://gitlab.com/koha-commun[…]notes_22_12_00.md
06:49 ashimema it's what Tomas suggested..
06:49 ashimema instead of
06:51 ashimema ordering by Security, New, Enh, Crit, Other at the top level and then per module inside those.. it reverses it to Per module, then the order above as sub headings for each module
06:57 marcelr ashimema: i did like all security stuff together
06:58 ashimema I agree on that front
06:59 ashimema I think 'security' should be it's own thing regardless of component (and probably at the top).. and a 'highlights' section for stand out cool stuff maybe..
06:59 ashimema I'm not sure about the rest really
06:59 marcelr the rest is fine with me
07:00 marcelr no strong pref on that one
07:04 tundunf joined #koha
07:04 tundunf hi all :)
07:08 fridolin joined #koha
07:09 alex_ joined #koha
07:10 cait joined #koha
07:10 cait hi #koha
07:12 tundunf hello! @cait
07:13 cait hello
07:15 ashimema Morning cait
07:15 ashimema Morning tundunf
07:15 cait morning ashimema
07:18 tundunf morning!
07:22 tundunf I have a small cataloguing question: does anyone know why the 952$1 field (Lost) wouldn't be visible to us in the edit screen of the Item record? The subfield is checked to display in the editor in our MARC framework and is also pointing to the LOST authorized value
07:22 cait if you chance the frameworks that shoudl make it visible
07:22 cait did you change the correct frameworks? you might need to update all of them
07:22 cait oh and which version of Koha?
07:24 tundunf sorry version 21.11!
07:24 tundunf I changed the Book framework, I'll check the others
07:28 tundunf The editor box is checked for the subfield in all the other frameworks
07:34 cait joined #koha
07:36 fridolin1 joined #koha
08:02 aw-bib joined #koha
08:04 aw-bib[m] joined #koha
08:53 marcelr ashimema: could you signoff on bug 33778 ?
08:53 huginn Bug https://bugs.koha-community.or[…]_bug.cgi?id=33778 enhancement, P5 - low, ---, koha-bugs, Needs Signoff , Move t/Auth_with_shibboleth.t to db_dependent
08:53 ashimema deffo.. will take a look once I'm out of my meeting
08:54 marcelr sure
09:00 fridolin1 left #koha
09:04 ashimema cait
09:05 ashimema if your looking at release notes today I'd love some help refining the changes requested by Tomas
09:05 ashimema and suggested by you
09:05 ashimema they're not generated with his alternate ordering style.. and people here I think quite like the change
09:06 ashimema I've then added a 'highlights' section at the top which I'm not so sure about.. it's gets populated using a new field from bugzilla (I've only set one bug with that flag for now as a test)..
09:06 ashimema and I wanted to also move all security bugs to the top as their own section too.. as per marcelr's suggestion.
09:06 cait not sure we can autopopulate highlights easily - it might have been something that the RM needs to write
09:07 cait so which is the change they quite like?
09:07 ashimema the re-ordering
09:07 cait but you said they are not generated that way yet?
09:07 ashimema so order by module then New/Enh/Bug
09:07 ashimema instead of by category then module
09:08 cait so they are generated like that?
09:08 ashimema original: https://gitlab.com/koha-commun[…]notes_22_12_00.md
09:08 ashimema new: https://gitlab.com/koha-commun[…]notes_22_12_00.md
09:08 cait can we please get rid if the 'here' link in the first page?
09:08 cait linked here make me aggressive
09:09 cait You can learn about the system components (like OS and database) needed for running Koha here.
09:09 cait what are we doing about the security bugs? LI like that they don't stand out as much anymore, but they are now alphabetic between Installation and label
09:10 cait I think combining new and enh was good, not sure about having the bugs all mixed in too
09:12 ashimema lol
09:12 ashimema I hadn't noticed it.. I never really read the top boilerplate
09:13 ashimema yes.. I was going to group the security back together at the top.. like where the Highlights section now is.. probably instead of it in fact as you don't like the idea of tying highlights to bugzilla
09:14 cait i am not sure we will end up with something different to the new features now
09:14 cait we coud still use it to give the RM some notes maybe?
09:14 ashimema as for bugs..
09:14 ashimema I was also discussing that with the team here this morning
09:14 cait at the moment I need to scroll all over those..
09:14 cait this makes it a little tedious
09:15 cait what does the team say?
09:15 ashimema I was going to be controbersial and outright remove them from these feature release notes for any bug that's already released in a maintenance version
09:15 cait but then we can remve all, can'twe?
09:15 cait the other bugs should ont have hit anyone yet
09:15 cait and I am toying with the idea of removing all bugs
09:16 ashimema their alternative suggestion was to move all bugs into one larger section at beneath the by module feature/enh stuff and adding the 'released in' versions too
09:16 ashimema that way these notes still summarise everything in one place
09:17 cait i like that
09:17 cait especially the released in
09:17 cait it would make it visible that we have already taken care of those
09:17 ashimema so
09:17 cait like.. an addendum section, not the main bit
09:17 cait the message woudl be much better
09:18 cait is it hard to pull the versions too?
09:19 ashimema ## Security... (full message at <https://matrix.org/_matrix/med[…]uTKwMFOFGUCEcawZy>)
09:19 ashimema something like that?
09:20 ashimema now that the rmaints are all consistently using the push script to update bugzilla, the field we have is pretty good actually.. so shouldn't be too hard to pull the versions
09:20 ashimema this was meant to be a 10 minute job.. I reckon it'll have taken an hour once that's all done..
09:20 ashimema but I like it
09:21 cait do we need to put security so high up or could it be with the bugs?
09:21 ashimema pass
09:21 cait i guess usually we'd want them high up
09:21 cait it just looks a little odd because feature release
09:21 cait suggestion for the bug fixes: same grouping as enh
09:22 ashimema we could swap where security goes depending on if it's a main or feature release
09:22 cait hm no, leave it as it's in the paste
09:22 ashimema so you'd still want bugfixes grouped by module.
09:22 ashimema makes sense
09:23 ashimema the other thing I've done.. which you can't see in the way gitlab renders it..
09:24 ashimema is that I've made our translations, sponsors, contributors lists a 2 column layout
09:26 ashimema On a totally different topic
09:26 ashimema do you understand why translations get all out of whack each release cait?
09:26 cait what do you mean?
09:27 cait 'out of whack'?
09:27 ashimema as in, sometime completely the wrong translation gets assigned to a string..
09:27 cait that doesn't happen with German really
09:27 ashimema let me find an example.. I thought I'd quickly check what 23.05 looked like for en_gb
09:27 cait i had some odd ones, but those were suggestions, not submitted
09:28 ashimema https://translate.koha-communi[…]27734466&offset=0
09:28 ashimema why has 'Link to resource' been picked up and translated to '0 to order' ?
09:29 ashimema clearly '0 to order' was a translation for some string in a previous version.. but it doesn't really appear to match this string..
09:29 cait it's definitely odd
09:29 ashimema it's OK, but not great, when it's highlighted as an error so we know to fix it
09:30 cait I could only assume that something with the lines changed in a way that moved this into the former spot in the template?
09:30 ashimema but we've found it often happens silently and it's only when customers spot it we find totally random translations
09:30 cait like the line number matches
09:30 cait I haven't had reports on that
09:33 ashimema We get it a lot
09:33 ashimema and it's infuriatingly painful to work through
09:33 cait I can only assume maybe it's to do with uploading?
09:33 cait i never touch the files
09:34 ashimema we don't either now
09:34 cait i was just wondering if ther emight have been a bug in the merging process
09:36 ashimema and as for this one
09:36 ashimema https://translate.koha-communi[…]27734541&offset=0
09:36 ashimema I've fixed that in 22.11 when I went through fixing everything.. so I'm really confused by it being in 23.05
09:37 cait I had a "Papiamento" showing up - but it was only one string
09:45 aude_c[m] <cait> "btw caroline++ aude_c++ - you..." <- Thanks @cait. It's really all caroline doing an absolutely impressive and top-notch job adding all those bugs to the manual! I am mostly the proof-reader at the moment 😅
09:45 aude_c[m] caroline++
09:45 cait i think you are both awesome :)
09:46 aude_c[m] Regarding translations: I found the same as you ashimema when I was on it yesterday... Just like you said, it's easy to correct when it comes up as part of an error, but it does mean there are potentially a lot of inconsistencies 😬
10:12 khall joined #koha
10:18 oleonard o/
10:26 oleonard Does anyone know of a plugin which adds a tab to the biblio details page?
10:34 cait yes
10:34 cait the coral plugin
10:34 cait we didn't get it to really connect ot Coral, but the tab was visible
10:34 cait and then domm or his coworker did one for opac iirc
10:35 cait aude_c[m]: regarding translations, i can't get rid of the "1" missing there: https://translate.koha-community.org/de/23.05/
10:37 cait PedroAmorim[m]: around by chance?
10:42 oleonard Thanks cait
10:44 aude_c[m] @cait The incomplete or the critical?
10:44 huginn aude_c[m]: I suck
10:45 aude_c[m] Ah, yes the incomplete says there's nothing... Weird
10:45 aude_c[m] I think I've seen that elsewhere, but if it was en-GB I probably ignored it because there are so many other issues to tackle!! 😬
10:45 cait yes... and annyoing :)
10:45 aude_c[m] Sorry, not much help
10:46 cait I just needed someone to understand the problem... comiserate?
10:46 dcook_ joined #koha
10:46 PedroAmorim[m] cait: yes
10:46 cait oh dcook - late appearance :)
10:46 aude_c[m] Yes, I definitely commiserate 😆
10:47 cait PedroAmorim[m]: seeing your nice diagram I was wondering if you have a workflow/backend for libarries sending materials  (the other direction basically, being the library that provides the materials instead of the one requesting it)
10:47 cait basically do you have more fun diagrams? heh
10:47 cait or does anyone know if we have docs for the koha-to-koha-backend maybe?
10:49 PedroAmorim[m] cait: afraid not, not for that specifically. I make these as I go and mostly for myself. this one I made while developing ReprintsDesk backend
10:49 PedroAmorim[m] https://snipboard.io/XrluFM.jpg
10:49 PedroAmorim[m] might get around to that one you're talking about specifically if/when I ever get to work with the Koha2Koha backend
10:50 ashimema the Koha2Koha backend is in the pipeline for a big clean up
10:50 ashimema with the idea of moving it to ISO standards instead of our funky use if z3950 and ils-di
10:50 ashimema Koha really doesn't do much ILL wise in terms of being a provider
10:50 ashimema we aim to fix that
10:51 ashimema next cycle.. or the one after 😜
10:51 ashimema depends on the sponsor
10:53 cait we will work it out in our backend before maybe... but I am not sure yet how to make parts fit
10:53 cait working ont htat a bit today, so trying to get some ideas :)
10:54 cait PedroAmorim[m]++ ashimema++
10:54 cait and while we .. I are asking questions: anyone a good synonym for interface (vendor interfaces, the new acq feature?)
10:55 cait I am struggling to find a good translation for interface
11:03 cait hm Accounts maybe
11:10 aude_c[m] That's a hard one. I'm not sure Accounts accurately reflects it either...
11:10 aude_c[m] In French I'd go for something like "portail" which directly in English is "portal" as in "a way to get through"
11:11 aude_c[m] (though I don't think "portal" in English is really used in that sense)
11:12 oleonard gateway?
11:13 ashimema nice
11:13 * oleonard wonders if he somehow fixed Bug 33774 while doing Bug 33528 and didn't realize it
11:13 huginn Bug https://bugs.koha-community.or[…]_bug.cgi?id=33774 major, P5 - low, ---, oleonard, NEW , Loading club table in every tab in patron details
11:13 huginn Bug https://bugs.koha-community.or[…]_bug.cgi?id=33528 enhancement, P5 - low, ---, oleonard, Needs Signoff , Use template wrapper for tabs: Patron details and circulation
11:14 aude_c[m] s/sense/context/
11:14 ashimema how this: https://gitlab.com/koha-commun[…]ype=heads&plain=0
11:16 aude_c[m] looks good!
11:19 cait oleonard++ aude_c++ :)
11:19 cait ashimema: here is still there :P
11:20 ashimema yes yes
11:20 ashimema it's on the list
11:20 ashimema I was trying to get the formatting right first
11:20 cait still looking, but it does look nice :)
11:23 cait next might be some work on the mail maps
11:23 cait ... and more notes writing
11:24 cait ashimema++
11:24 * ashimema is trying to now unbreak the rmaint notes generation ;P
11:26 cait ashimema: pm
11:26 oleonard Always a bit of a shock to see this https://snipboard.io/3qtGLX.jpg :D
11:26 cait what did you do there? some customization abvoe the web installer?
11:27 oleonard It happens when Koha realized there's a database update when trying to AJAX-load another page
11:28 cait ok, I hadn't seen that yet:)
11:41 tcohen marcelr++
11:43 oleonard Bug 33774 has a patch
11:43 huginn Bug https://bugs.koha-community.or[…]_bug.cgi?id=33774 major, P5 - low, ---, oleonard, Needs Signoff , Loading club table in every tab in patron details
11:50 cait oleonard++ marcelr++
11:51 tcohen oleonard++ cait++ ashimema++ kidclamp++ khall++
11:51 tcohen happy friday everyone
11:52 cait heh
11:52 tcohen Joubu++
12:05 khall joined #koha
12:05 khall Joubu++ thanks for fixing 33580!
12:15 mtj hey #koha, any chance we could get bug 33371 added to 23.05 ?
12:15 huginn Bug https://bugs.koha-community.or[…]_bug.cgi?id=33371 normal, P5 - low, ---, mtj, Needs Signoff , Add 'koha-common.service' systemd service
12:15 khall joined #koha
12:16 mtj ..would be great to finally have koha install/upgrade without a 'failure' message :)
12:19 tcohen :-D
12:47 khall joined #koha
12:56 ashimema OK.. I think I'm done on the release notes generation tool for now..
12:56 ashimema need to go for a swim
12:56 ashimema I'd be interested in peoples general feedback on both maint and feature release notes.. they now differ more
12:57 ashimema see 22.11.06 and 22.12.00 pre-releases for details.
12:57 ashimema https://gitlab.com/koha-commun[…]tes/-/tree/master
12:59 cait ashimema++
13:06 Dyrcona joined #koha
13:35 marie-luce joined #koha
13:41 oleonard Why might the "confirm" button be disabled on the receive orders page?
13:46 caroline I think you have to edit the quantity?
13:47 oleonard https://snipboard.io/DU1vRk.jpg
13:47 caroline In quantity, it says receiving 0 out of 1
13:48 caroline if you edit the line to receive 1, the confirm button should be activated
13:48 caroline (it's a couple of extra steps from before...)
13:49 oleonard Okay, weird. Thanks caroline
13:50 caroline I'm not sold on the new way of doing it yet... Though I only saw it yesterday, I haven't had time to really look at it
13:50 cait caroline: extra?
13:50 cait can yo still do the old way?
13:50 caroline well before if you clicked receive, it brought youu directly to the receive page, now you have to click Edit to see the receive page
13:51 cait it should not be extra clicks
13:51 oleonard Related to Bug 8179 I assume?
13:51 huginn Bug https://bugs.koha-community.or[…]w_bug.cgi?id=8179 new feature, P5 - low, ---, agustinmoyano, Pushed to master , Receiving multiple order lines at once
13:51 cait yeah, but we need to fix it not to require more clicks than before
13:51 cait I was not aware it changed how you did things the old way too
13:52 caroline yes, you don't have the choice of receiving just one
13:53 caroline I could be mistaken, but I just went as I usually did and ran into the same problem as oleonard, having to click Edit
13:53 cait with a change like this, I'd have preferred to see lots of librairan sign offs
13:54 cait (at the risk of making people grumpy, but leaving for a week of conferencing...)
13:54 oleonard If I click the "Receive" link from parcel.pl should it include a "multiple_orders" parameter?
13:54 oleonard "orderreceive.pl?multiple_orders=20&invoiceid=12"
13:55 khall joined #koha
13:57 oleonard Yeah I guess it doesn't work the old way. I would have thought the Receive link might have had a parameter to tell Koha to use the old way
13:59 cait I think a checkbox was mentioned once
13:59 cait the test plans on the bug are not up-to-date
13:59 oleonard :(
14:01 cait I really feel the receive link should get you to the old form or at least to the modal directly
14:02 cait and then if you use the checkboxes to mark multiple the multi-receive makes more sense, but not if using the link
14:02 caroline do you want me to create a new bug report?
14:02 cait might be good?
14:02 cait adding extra clicks is never good and acq is already so click heavy
14:03 caroline I know for sure I will get comments, although I might be able to persuade clients to use the checkboxes instead... but it's a big change
14:03 cait there is also no wy to get back to the list of pending orders, is there? if you clicked on receive and htink "I'll do thema ll later"?
14:03 cait I don't think it works for all libraries
14:04 caroline If you click on Confirm, it will bring you back
14:04 cait but i can only confirm after editing
14:05 caroline true, but that is kind of like before... you had to save your receive before receiving another one
14:05 cait so it makes no sense to have that step if i need to finish receiving
14:05 caroline it's only the edit part that is extra I think
14:05 cait yeah,b ut then i don't need the in between screen
14:06 caroline yeah no, that one is not useful
14:06 cait either it allows me to make a list first... or it does allow me to directly receive, but having this in between thing doesn't work well
14:06 cait it's also missing page-sections
14:08 cait if i have a long invoice, now i need to process things like twice... first make the list on the page, and then go through the somewhat shorter list again to receive... but I need the items in hand then for the second step, so i might need to search for the item in each list
14:08 cait instead of only once... I don't get the advantage yet
14:09 cait if you think about print materials and adding items in acq
14:09 cait how will it require you to handle the items and when do you need to pick them up
14:10 cait to write an inventory number inside, to put a label or barcode in them etc.
14:11 caroline I'm writing up the bug, I'll give you the link so you can add all your comments ;)
14:12 cait I should just go home and do laundry :)
14:13 cait ... leaving htat here for later: i feel the ones you received/edited should be highlighted in the list, so it's easier to spot the missing one
14:13 cait s
14:13 cait the sorting by quantity doesn't work right
14:17 cait hm and if i forgot something in my list... i can only cancel it and start over? no way to change the selection?
14:18 tcohen you can click back
14:18 tcohen on the browser?
14:18 cait then the list is ost
14:18 cait hm ok, the checkboxes remain
14:18 cait i think a link would be nice, people are often scared of the back button
14:18 tcohen phew, at list 1% is ok
14:18 caroline lol!
14:19 caroline cait bug 33784
14:19 huginn Bug https://bugs.koha-community.or[…]_bug.cgi?id=33784 enhancement, P5 - low, ---, koha-bugs, NEW , Single receive - clicking the Receive link in parcel.pl should lead to the receive form
14:28 cait caroline: it's 2 extra clicks - edit and then finish receive after saving the edit
14:29 cait if you only do a single line
14:29 caroline yes, I hignlighted the extra clicks in the bug report with asterisks
14:29 cait caroline: I see you already did that :)
14:32 cait caroline is the calm one :)
14:33 caroline lol!
14:36 * cait goes to meditate - bbl :)
14:37 caroline all of this from an innocent question from oleonard-away XD
14:38 cait I guess :)
14:38 cait oleonard++
14:38 cait caroline++
15:14 oleonard-away I wonder if libraries would like a way to create a new record from a suggestion without using acquisitions
15:23 caroline maybe, I have a lot of clients who use suggestions, but don't use acquisitions, but I think they mostly do copy-cataloging
15:32 oleonard If anyone else is curious, Bug 27120 has a simple plugin attached for testing plugin-generated tabs on the biblio detail page
15:32 huginn Bug https://bugs.koha-community.or[…]_bug.cgi?id=27120 normal, P5 - low, ---, fridolin.somers, CLOSED FIXED, Send biblio to Koha plugins hook 'intranet_catalog_biblio_tab'
15:37 caroline Is it normal that we can archive system debit types? https://snipboard.io/orCuJT.jpg
15:38 caroline ashimema, maybe?
15:49 cait joined #koha
15:53 ashimema erm
15:53 ashimema no
15:53 ashimema that doesn't sound right
15:54 ashimema I don't remember there being an archive option at all.. did I add that?
15:54 caroline I thought it was maybe due to the noissuescharge thing, that we can now edit debit types to include them or not?
15:55 caroline Only the manual fee had both the edit and archive buttons before, the others had none
15:58 ashimema I don't know I'm afraid
15:58 ashimema it does sound wrong
15:58 caroline I'll write a bug report and cc you is that ok?
15:58 ashimema I'm about to go cook dinner though so don't really have time to dig
15:59 ashimema sure
15:59 caroline no problem! bon appétit!
16:00 ashimema https://bugs.koha-community.or[…]attachment=149874
16:00 ashimema that patch looks suspect to me
16:01 ashimema yes..
16:01 ashimema that's a bug
16:01 ashimema can you link to that bug pretty please?
16:01 ashimema bug 32450
16:01 huginn Bug https://bugs.koha-community.or[…]_bug.cgi?id=32450 enhancement, P5 - low, ---, matt.blenkinsop, Pushed to master , Make it possible to exclude debit types from charges counted for circulation restriction (noissuecharge)
16:01 caroline Ok I'll reference that one
16:02 ashimema ta 🙂
16:02 caroline I'm going to luch, but I'll do it this afternoon
16:07 ashimema @later tell caroline the fix is simple: https://gitlab.com/mrenvoize/K[…]6216f6d853889d46f
16:07 huginn ashimema: The operation succeeded.
16:07 ashimema untested
16:42 PedroAmorim[m] @tcohen around?
16:43 PedroAmorim[m] I want to discuss bug 33786 because this is also affecting the work I'm doing with 30719
16:43 PedroAmorim[m] * tcohen:  around?
16:44 caroline_catlady joined #koha
16:49 tundunf joined #koha
16:49 bshum joined #koha
16:49 huginn joined #koha
16:49 nugged joined #koha
17:39 tcohen bCK
17:39 tcohen PedroAmorim[m]: ?
17:40 caroline ashimema++ thanks for the fix! I tested locally and it works
17:40 PedroAmorim[m] im half here yes, I left a comment and patch in 33786
17:42 tcohen what is DT using to identify the table?
17:42 PedroAmorim[m] likely the table id? I dont know
17:45 tcohen thinking out loud here
17:45 tcohen but
17:45 tcohen what  if we made the table ID include the borrowernumber...
17:45 tcohen thus making it unique
17:46 tcohen and initialize the DT using the class for the selector?
17:46 PedroAmorim[m] thats worth a try, I can try that, but what about the table settings?
17:46 PedroAmorim[m] dont those require the id to match?
17:46 tcohen oh, you're right
17:47 tcohen but isn't it hardcoded somewhere?
17:47 tcohen like
17:47 tcohen settings = $.GetTableSettings('string')
17:48 PedroAmorim[m] it may be, I can explore that possibility for sure
17:49 tcohen var table_settings = [% TablesSettings.GetTableSettings( 'cataloguing', 'concerns', 'table_concerns', 'json' ) | $raw %];
17:49 tcohen on detail.tt
17:49 tcohen so the parameters are hardcoded
17:51 PedroAmorim[m] that may work! I'll give this a shot when I can and report back! thanks!
19:22 khall joined #koha
19:52 khall joined #koha
19:53 khall joined #koha
21:27 bag joined #koha
22:05 cait joined #koha

| Channels | #koha index | Today | | Search | Google Search | Plain-Text | plain, newest first | summary