Time Nick Message 00:13 dps Could someone help me with how to apply the patches for bug 35687, I'm not sure how to do this sort of thing. Is it the 'patch' command with those files? https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35687 00:13 huginn` 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35687 blocker, P5 - low, ---, kyle, Passed QA , Upgrade to 23.06.00.013 may fail 00:13 huginn` 04Bug 35687: blocker, P5 - low, ---, kyle, Passed QA , Upgrade to 23.06.00.013 may fail 00:40 dps I don't know where to find the files that need to be patched. 02:15 tuxayo dps: hi :) so you have a production koha that needs this? 02:16 tuxayo How is it installed? via the koha debian repo? some custom git install? Some custom packaging install? 02:18 tuxayo Was the problematic upgrade already applied to the production instance? 02:22 tuxayo Does that break any functionality that can't wait for the upcoming (current or next week I think) minors releases that should include the fix? 03:41 dps It's installed via the debian repo. And yes, the upgrade is stuck on a production instance. If there's a fix coming this week, I could probably wait for it. All functionality is broken since the upgrade couldn't complete. 03:42 tuxayo dps: Do you have a backup of before the migration attempt? The debian packages make this very easy along with restoring: https://wiki.koha-community.org/wiki/Commands_provided_by_the_Debian_packages#koha-dump 03:44 dps I backed up the database with a mysqldump and also exported data from the tools menu. I could look at rolling back the debian packages. 03:45 dps It looked like the patches weren't that complicated, I just couldn't find where to insert them. 03:45 tuxayo dps: and you call still use koha-dump before trying to restore the DB backup. Note that simple DB backup don't include at least uploaded files and zebra index. 03:46 dps I see. No, I didn't use koha-dump before the upgrade as I wasn't aware of it. I'm pretty new to Koha. 03:49 tuxayo > It looked like the patches weren't that complicated, I just couldn't find where to insert them. 03:49 tuxayo dps: If you are considering applying patches directly on top of files managed by a Debian package a better alternative is to apply directly the SQL that the patches contain: https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=161221&action=diff 03:50 tuxayo The cleanest is still to rollback the package upgrade and DB and wait. 03:52 tuxayo You shouldn't have data inconsistency due to only having a DB backup because Koha wasn't used since the upgrade attempt. (because it's inacessible) So Zebra data, uploaded files and eventual other things are still in perfect sync with the DB content. 03:53 tuxayo Zebra or ElasticSearch/OpenSearch, i don't know your Koha search engine. 03:55 dps It's using Zebra 03:56 dps Thanks for the tips. As you suggest, I'll try rolling back the packages and wait for the minor release that fixes it. 03:58 dps I don't know if I trust myself to apply the SQL directly. 04:15 tuxayo dps: The upgrade will reblow up if you miss apply the SQL. But yeah if you are unlucky it won't be the case and it will continue and crash latter after some usage. 04:17 tuxayo Don't forget koha-dump for backups. 04:17 tuxayo I hope the rest of you Koha usage goes smoothly :) 04:17 tuxayo *your 04:20 Raghav I want KOHA for my Library 05:08 saa our koha admin page getting logged out again and again 05:08 saa we had tried to add ip range but it seems it is not working 05:09 saa when i try to edit library name and try to click to edit library details it says Something went wrong when loading the table. 401: Unauthorized. 05:10 saa how to sort out this issue pl. help 07:06 jim_ hello 07:06 jim_ need one help 07:07 jim_ if i add date on items.more_subfields_xml is there a particular format i need to follow or can i add any format to fetch data 07:32 Joubu mtj: around? 07:34 reiveune hello 07:49 Joubu wiki sends emails again 07:50 Joubu domm++ MarkHofstetter++ rangi++ thanks! 08:14 jim_ hello 08:14 jim_ any solution for me 08:25 mtj Hi joubu. About.. 08:28 Joubu mtj: hi :) did you see the different errors people get with koha-l10n deb package? 08:28 Joubu well, you reported one, so you saw that one :D 08:29 Joubu there is also: https://lists.koha-community.org/pipermail/koha-devel/2024-January/048473.html 08:29 Joubu "koha-common : Depends: koha-l10n but it is not going to be installed" 08:29 Joubu any idea of how we could fix them? 08:36 mtj Yep.. Will send a patch today 08:49 mtj Back in 60 mins.. 09:11 saa can anyone help our koha admin page logs out often and for every click asks to reenter login and password 09:13 saa we get error as something went wrong when loading the table. 401:Unauthorized 09:27 davidnind saa: I don't know specifically, but I assume you have 1) Restarted everything on the server (including Plack) 2) Cleared your browser cache (or at least used another fresh browser to see if it still occurs) 3) Checked the timeout, SessionRestrictionByIP, and staffClientBaseURLsystem preferences 09:28 davidnind otherwise, I don't have any other ideas 09:32 davidnind jim_: I don't understand your question or the problem you are having and trying to resolve 09:37 saa Checked the timeout, SessionRestrictionByIP, and staffClientBaseURLsystem preferences i had changed staffclient access by IP and since then now everytime admin page logs out 09:38 saa when i try to click on library option it give error as Something went wrong when loading the table 401:Unauthorized 09:38 saa how can i remove that IP range now so that we continue to access our staff client 09:38 saa browse often logs out 09:39 saa is there any way by which from terminal i can remove that ip range and check if things are working ok 09:41 saa or is there any other way to solve the issue so that my library staff can easily work on staff client page 09:45 Joubu empty the system preference's value in DB using the mysql cli 09:46 saa will that not be risky 09:46 saa can i only change that single particular value 09:46 saa we have made many changes in system preferences 09:46 saa is there any perl program to chaange these settings 09:47 saa is there any way i can only edit sessionbyip details 09:48 saa so that our often logging in and out issue willl be resolved 09:51 Joubu you need to change the value in the DB then restart the different services. That's the only way to modify sysprefs if you do not have access to the UI. 09:53 saa will that solve the problem of getting error as Something went wrong when loading the table. 401:Unauthorized. especially the koha admin page logs out with every click 09:53 saa and if u can suggest how to change that would help 09:54 davidnind you can update the system preference in the database with a sql query: 1) koha-mysql instancename 2) SQL query to see the current value, for example: select * from systempreferences where variable='SessionRestrictionByIP'; 3) update the values using an normal SQL query, for example: update systempreferences set value='XXXX' where variable='SessionRestrictionByIP'; 09:55 saa can i exactly copy above in my mysql client 09:56 cait fridolin: PM! 09:56 davidnind however, if you have added some values to Administration > Libraries > [Libraryname] > IP, then you would need to update the entry in the database table for the library (these are recorded in the branches table) 09:57 davidnind saa: we (I) don't know what is causing the issue, so we are just suggesting some things for you to try 09:58 saa i remember i have added value in sessionbyip 09:58 saa and restarted all services 09:58 saa and since then our client logs out by every click 09:59 saa so please suggest which two tables would I need to check and correct 10:00 davidnind if you are not familiar with MySQL or MariaDB and SQL commands, then please backup your database first before trying anything 10:01 saa yes 10:02 saa select * from systempreferences where variable='SessionRestrictionByIP'; +------------------------+-------+---------------------------------------------------------------------------------------------------------------------+-------------+-------+ | variable | value | options | explanation | type | +------------------------+-------+------- 10:02 saa when I ran above command i dont see any IP added 10:03 saa SessionRestrictionByIP | 1 | Check for change in remote IP address for session security. Disable only when remote IP address changes frequently. | | YesNo 10:04 Joubu which error do you see when you are logged out? 10:05 davidnind and no, you need to customise the SQL query in 3 above - options for value (where I had 'XXXX') are 1 (which = yes) and 0 (which = no) (Enable check for change in remote IP address for session security) 10:05 saa Kohaclient often logs out and when i click on Libraries it says Something wen wrong when loading the table 401:Unauthorised 10:06 Joubu forget about the 401. Please tell me which error you see on the screen when you are logged out. 10:06 saa and my intranet-error.log says stname to be kohaadmin.ncl.res.in for uri /cgi-bin/koha/errors/400.pl [Wed Jan 24 15:26:31.076888 2024] [proxy_http:error] [pid 46225] (70014)End of file found: [client 164.52.0.94:43479] AH01095: prefetch request body failed to 0.0.0.0:0 (httpd-UDS) from 164.52.0.94 () [Wed Jan 24 15:26:38.808758 2024] [proxy:warn] [pid 46226] [client 164.52.0.94:48915] AH01092: no HTTP 0.9 request (with no host line) on incoming request and pre 10:07 saa When I try to click on Library name with edit it throws error as Something went wrong when loading the table 401:Unauthorised 10:07 saa and above is intranet error log 10:09 Joubu did you modify apache config? 10:09 Joubu how did you install Koha? 10:10 saa no apache is not modified 10:10 saa i only changed hosts file 10:11 saa because i found my koha client was accessible from outside 10:11 saa i wanted to restrict it with only IP range 10:11 saa our opac is configured with 443 and staff client runs on http 10:14 Joubu so you are saying this problem just appeared right after you have modified the value of the system preference SessionRestrictionByIP? 10:15 saa yes 10:16 davidnind Did you also add some values to Administration > Libraries > [Libraryname] > IP (the hint for this field is 'Can be entered as a single IP, or a subnet such as 192.168.1.'), then to remove them you need to update the branches table (select * from branches) - this is in the branchip column) 10:18 Joubu then do what davidnind told you, open the mysql cli with the following command: `koha-mysql $INSTANCE` (replace $INSTANCE with your koha instance name). Then run the following query: 10:18 Joubu UPDATE systempreferences SET value="0" WHERE variable='SessionRestrictionByIP'; 10:20 davidnind thanks Joubu! 10:20 davidnind What did you change in your hosts file? (Not sure if that is relevant or not) 10:21 Joubu and restart the services with: service memcached restart && service apache2 restart && service koha-common restart 10:22 saa when i run select * from branches i can see ip details 10:22 Joubu The goal of SessionRestrictionByIP is not to restrict access to Koha btw 10:24 saa in my branchip there is IP value when I run command as select * from branches 10:24 Joubu do one thing at a time 10:24 saa by running above UPDATE command it will solve my problem right? 10:25 Joubu no idea! 10:25 davidnind What is the value for the AutoLocation system preference? (SQL query - select * from systempreferences where variable="AutoLocation" (1 = Yes, 0 = No) 10:25 saa it is 1 10:25 Joubu you told us the problem appeared right after you modified SessionRestrictionByIP, you are asking how to revert the change, we answer you 10:26 davidnind That controls whether the values you entered in the IP field for a library are used 10:27 saa ok I will run UPDATE command now and should I restart memcached, apache2, plack 10:29 davidnind What value is set for your AutoLocation system preference? 10:29 saa 1 10:31 davidnind to turn that off, the SQL query is: update systempreferences set value ='0' where variable='AutoLocation'; 10:33 saa yes now it is changed 10:33 saa to 0 10:33 saa should i restart my koha-common, apache2, plack, memcached 10:33 saa is it necessary 10:34 davidnind it won't hurt (hopefully), and it will clear anything in memory - I would myself, but I'm not a system administrator 10:41 saa I am sorry still it does same thing 10:41 saa it logs out and same error comes 10:44 Joubu which error do you see on the screen? 10:44 saa Wed Jan 24 15:26:55.279305 2024] [proxy:warn] [pid 46286] [client 164.52.0.94:58035] AH01092: no HTTP 0.9 request (with no host line) on incoming request and preserve host set forcing hostname to be /cgi-bin/koha/errors/400.pl [Wed Jan 24 15:26:55.279414 2024] [proxy_http:error] [pid 46286] (70014)End of file found: [client 164.52.0.94:58035] AH01095: prefetch request body failed to 0.0.0.0:0 (httpd-UDS) from 164.52.0.94 () ~ 10:44 saa my intranet log 10:45 Joubu the Koha UI 10:46 Joubu you should see the login form with a red message on top of it 10:46 saa the system logs in 10:46 saa only when I click on any tab it again logs out 10:47 saa and when I click on any tab it logs out 10:49 Joubu and...? 10:49 Joubu it logs you out and you should see the login form, with a red messge on top of it 10:49 saa sorry there is no red message 10:49 saa it comes with login/password page 10:49 saa and if I enter login password it takes 10:50 saa but with every click it logs out and log in back 10:50 saa if I enter correct login and password 10:50 Joubu which OS are you using? 10:50 saa Ubuntu 20.4 10:50 saa koha 23.05 10:51 Joubu You should search for 10:51 Joubu the apache error "AH01092" 10:51 Joubu if you think it's related to the logout, and that Koha does not provide more info 10:51 Joubu I don't have any more ideas, sory 10:51 Joubu sorry 10:52 davidnind while they shouldn't be in effect (as you've disabled AutoLocation), you can remove the IP address in the branches table: update branches set branchip=NULL where branchcode='XXX'; (where XXX = the branchcode) 10:52 saa let me try this command as well 10:53 davidnind you said you changed your host file - what changes did you make to that? That may explain the errors in the logs(?) 10:54 saa i only added 127.0.1.1 as one link for my admin page and 127.0.1.1 opac with IP details 10:56 davidnind I'd reverse the change you made there to see if it gets you back to a working system - you said the host file right, and not the Apache configuration? 10:56 saa no i did not change apache file 10:57 saa i only changed hosts file 11:01 saa hello update branches set branchip=NULL where branchcode='XXX' this worked 11:01 saa thanks tons to davidnid and joubu 11:01 saa i greatly appreciate your support 11:02 saa i struggled a lot and now it has been working 11:02 saa again and again thank you 11:02 saa saved my work 11:02 davidnind it's a very long time since I did any networking configuration, so I don't know what effect the change you made to the hosts file would have 11:03 Joubu this means the services have not been restarted properly, the change to AutoLocation should have been enough 11:03 davidnind could you show the result of this query: select * from systempreferences where variable='AutoLocation'; 11:03 davidnind as Joubu says, that should have been enough 11:06 Joubu the thing is... with AutoLocation active should not be able to login at all 11:07 davidnind good point 11:11 davidnind maybe networking was not restarted properly, I really don't know what having a hosts entry for 127.0.1.1 would do 11:12 davidnind troubleshooting 101: reverse the changes you made that led to things not working (if you can...) 11:18 davidnind Joubu: maybe it is a bug. I added a made up IP address to CPL > IP, then set AutoLocation to Yes - got similar results - can access some pages, but then logged out 11:18 Joubu can you report please? 11:19 Joubu [off] it's security 11:20 davidnind I will do that now 11:22 davidnind So add as a security bug instead of as a normal one? 11:27 ashimema anyone here know virtualshelves much? 11:27 oleonard HI #koha 11:28 ashimema I'm confused by /includes/virtualshelves/merge/selection.tt 11:28 ashimema first off.. it's in the includes directory but nested down and has .tt suffix 11:28 ashimema and second it doesn't actually appear to be INCLUDEd anywhere 11:28 ashimema it's it an ancient leftover to just kill? 11:28 ashimema or does it do something 11:30 oleonard It sure looks like an ancient leftover to me. I don't think I've ever noticed it before! 11:31 ashimema you touched it a while ago to add button classes 11:31 ashimema 😜 11:31 ashimema but I don't think it was used then either.. lol 11:32 oleonard I'm not always paying attention when I write patches XD 11:32 ashimema lol 11:37 oleonard Aug 25 23:56:13 2009 - Adding Merge of two biblios from a virtualshelf 11:38 tcohen goor morning #koha o/ 11:40 ashimema morning tcohen 11:42 oleonard ashimema: the corresponding script doesn't exist anymore 11:43 ashimema awesome, thanks oleonard 11:51 AndreJaneiro[m] good morning everyone. 11:51 AndreJaneiro[m] i am trying to get a sql report on the renewed borrowers in a time line, is it possible? 11:53 krimsonkharne[m] good morning all! 11:54 krimsonkharne[m] Andre Janeiro: you could check borrowers.date_renewed, however, that field is overwritten every time the borrower is renewed afaik 11:55 krimsonkharne[m] so if you were looking for borrowers renewed in 2022 and some had renewed again in 2023, they would have the newer 2023 date in borrower.date_renewed and might not be found by your SQL report 11:56 davidnind Joubu: Bug 35890 logged 11:56 huginn` 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35890 is not accessible. 11:58 krimsonkharne[m] Andre Janeiro: I suppose you could also check action_logs, as if you have borrower changes enabled for logging then you should have an entry in action_logs for each renewal 11:59 krimsonkharne[m] so you could do something like SELECT timestampl 12:00 krimsonkharne[m] s/timestampl/timestamp, module, action, object, info FROM action_logs WHERE module="MEMBERS" AND action="RENEW" AND timestamp BETWEEN ..../ 12:01 krimsonkharne[m] e.g. 12:01 krimsonkharne[m] SELECT timestamp, module, action, object, info FROM action_logs WHERE module="MEMBERS" AND action="RENEW" AND timestamp BETWEEN TIMESTAMP(<<Date from|date>>) AND TIMESTAMP(<<Date to|date>>, "23:59:59") 12:02 krimsonkharne[m] note I'm not a developer nor an SQL expert... 12:05 mtj https://gitlab.com/koha-community/koha-l10n/-/merge_requests/13 12:05 mtj hi Joubu, install fix looks like that ^ 12:09 AndreJaneiro[m] tks krimsonkharne i will try 12:10 krimsonkharne[m] np, hope it helps :) 12:12 Joubu mtj: is it a fix for both problems? 12:12 Joubu mtj: we need it for stable branches as well 12:13 mtj which 2 problems? 12:14 Joubu mtj: https://lists.koha-community.org/pipermail/koha-devel/2024-January/048473.html 12:14 Joubu koha-common : Depends: koha-l10n but it is not going to be installed 12:14 mtj it fixed that problem 12:14 Joubu not the same as https://gitlab.com/koha-community/koha-l10n/-/issues/1 12:15 Joubu trying to overwrite '/usr/share/koha/misc/translator/po/am-Ethi-installer-MARC21.po', which is also in package koha-common 23.05.04-2 12:15 mtj i think it fixes bothg problems 12:18 cait I coworker asked me earlier if it can be that the i10n package is getting updated with a pinned/hold koha-common package 12:19 cait he was going to investigate a bit more... but could this have anything to do with what you are discussing? 12:27 mtj hi cait, its probably related 12:29 mtj the problem is caused because both the old koha-common pkg, and the new koha-l10n pkg own the /usr/share/koha/misc/translator/po files 12:30 mtj apt detects the conflict, and complains 12:30 cait we are building our own packages, but we use i18n of course, if you have anynotes of things we need to be aware of that would be appreciated 12:32 mtj ...we can fix the conflct by telling apt that koha-l10n will 'break and replace' koha-common pkg 12:33 mtj https://gitlab.com/koha-community/koha-l10n/-/merge_requests/13/diffs?commit_id=15b7e0612920019b203eb69b4999a2d2ba4c305f 12:33 marcelr o/ 12:34 mtj https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-in-other-packages 12:34 mtj ... has a bit more info ^ 12:36 mtj For example, if a package foo is split into foo and foo-data starting at version 1.2-3, foo-data would have the fields, in its control file. 12:36 mtj Replaces: foo (<< 1.2-3) 12:36 mtj Breaks: foo (<< 1.2-3) 12:36 mtj hi marcelr :) 12:37 marcelr hi mtj 12:38 marcelr cait, the first issue is the name; i typed an i too but it is l10n 12:38 marcelr l of languages 12:40 paulderscheid[m] cait around? 12:44 Joubu marcelr, tcohen: moving on bug 35819? 12:44 huginn` 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35819 critical, P5 - low, ---, tomascohen, Failed QA , "No job found" error for BatchUpdateBiblioHoldsQueue (race condition) 12:45 thd pauldersheid[m]: I have been delayed posting my configuration, etc. findings for Discourse. Repairs at my place and other things interrupted me. I even lost my primary electric circuit for a week with a short in a hard wired lamp fixture. 12:46 paulderscheid[m] Sorry to hear that thd 12:48 marcelr Joubu: i wait for tcohen to move (as author) 12:49 thd pauldersheid[m]: I am having decades old repairs fixed from damage from leaks etc. before I occupied the place. However, the people doing work which the landlord sent to work only spoke Russian and old did half a good job. Consequently, I have to finish the work myself with a neighbour who works in construction. 12:52 thd pauldersheid[m]: Have you tested docker-mailserver which includes Postfix or some other means of routing email for Discourse? A mail server is needed for Discourse and the documentation only recommends proprietary mail services which is bad and also leads to trouble when bounced messages result in account cancellation. 12:53 cait I am here 12:53 cait meeting in 5 12:54 paulderscheid[m] We have a mail server from a community member readily available. 12:54 paulderscheid[m] Hi cait I'm a little confused, how would you map biblio and biblioitems in RDA terms? 12:54 paulderscheid[m] biblio => Expression, 12:54 paulderscheid[m] biblioitem => Manifestation? 12:59 thd pauldersheid[m]: The WEMI RDA model does not map perfectly to Koha. The Koha bibliographic relationship was devised before FRBR and RDA. 13:01 cait MEETING NOW! 13:01 cait paulderscheid[m]: that's a topic for tomorrrow I think 13:02 cait #startmeeting Development IRC meeting 24 January 2024 13:02 huginn` Meeting started Wed Jan 24 13:02:52 2024 UTC. The chair is cait. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:02 huginn` Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:02 huginn` The meeting name has been set to 'development_irc_meeting_24_january_2024' 13:03 cait #topic Introductions 13:03 oleonard #info Owen Leonard, Athens County Public Libraries, Ohio, USA 13:03 Joubu #link https://meet.jit.si/KohaDevelopmentMeeting 13:03 cait Please introduce yourself with info and join us on Jitsi 13:03 cait #chair Joubu 13:03 huginn` Current chairs: Joubu cait 13:03 Joubu #info Jonathan Druart 13:03 cait #chair marcelr 13:03 huginn` Current chairs: Joubu cait marcelr 13:03 cait #info Katrin Fischer, BSZ, Germany 13:03 paulderscheid[m] #info Paul Derscheid, LMSCloud GmbH, Stuttgart, Germany 13:03 marcelr #info Marcel de Rooy 13:03 Joubu ashimema, tcohen https://meet.jit.si/KohaDevelopmentMeeting 13:04 Joubu paulderscheid[m]: join us 13:04 thd #info Thomas Dukleth, Agogme, New York City 13:04 cait #chair oleonard 13:04 huginn` Current chairs: Joubu cait marcelr oleonard 13:05 cait #topic Annoucements 13:06 cait #info oleonard reports progress on the Bootstrap 5 update 13:06 cait moving on to next topic 13:06 cait #topic Update from the Release Manager 13:07 emlam #info Emily Lamancusa, MCPL, USA 13:07 cait #topic Katrin plans to catch up on pushing patches for the rest of the week 13:07 cait #topic Updates from the Release Maintainers 13:07 cait #info No Rmaints present 13:08 ashimema Hi 13:08 ashimema Sorry, traffic after swim 13:08 ashimema #info Martin Renvoize, PTFS Europe 13:08 cait #info monthly release will be a little delayed 13:10 cait #topic Updates from the QA team 13:11 cait #info queue is quite full with 150, good news is that we have about the same number of sign-offs, the number of bugs is relatively small, but we have a large pile of older enhancements that need to be adressed 13:20 cait #info Some discussion about gamification, motivation for QA and testing happened 13:25 cait #topic Status of roadmap projects 13:25 cait #link https://wiki.koha-community.org/wiki/Road_map_24.05 road map 13:40 cait #info check the road map page for coming updateson status 13:41 cait #topic Actions from last meeting 13:41 cait #info no actions from last meeting! 13:41 cait #topic General development discussion 13:41 AshishKumar[m] hi 13:42 AshishKumar[m] my college want to implement koha library facility 13:43 cait #info RM will be on vacation from 8-23 February - RM assistants will take over 13:47 cait #info CSRF bug has been discussed needs more eyes - if you don#t have access get in touch with Release Team 13:48 cait #topic Review of coding guidelines 13:48 cait #info no items to discuss 13:48 cait #topic Set time of next meeting 13:50 Joubu #info Next meeting: 7 February 2024, 13 UTC 13:50 cait #endmeeting 13:50 huginn` Meeting ended Wed Jan 24 13:50:35 2024 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) 13:50 huginn` Minutes: https://meetings.koha-community.org/2024/development_irc_meeting_24_january_2024.2024-01-24-13.02.html 13:50 huginn` Minutes (text): https://meetings.koha-community.org/2024/development_irc_meeting_24_january_2024.2024-01-24-13.02.txt 13:50 huginn` Log: https://meetings.koha-community.org/2024/development_irc_meeting_24_january_2024.2024-01-24-13.02.log.html 13:53 cait thx all! 13:53 oleonard cait++ 13:53 thd pauldersheid[m]: Before the meeting started I was about to say something about MARC Koha and WEMI. 13:54 Joubu cait: done. If you want the jitsi link, etc. you need to edit the template 13:55 Joubu https://wiki.koha-community.org/wiki/Development_IRC_meeting_Template 13:55 Joubu this is what is used to generate the next meeting 13:56 paulderscheid[m] thd I saw 13:56 thd pauldersheid[m]: Koha had some sort of half-reasonable WEMI model prior to MARC Koha which was an adaptation of the the relational database model as was FRBR and explicitly stated in the original FRBR publications. 14:00 thd pauldersheid[m]: When Paul Poulain was developing MARC Koha, he had not recognised the WEMI like model in Koha and some levels became flattened such that every record was a manifestation record as with traditional MARC bibliographic systems. 14:02 thd pauldersheid[m]: Some subsequent work has at least partly unflattened Koha such that the common keys at the different levels are not necessarily redundant but the code may otherwise still imply the redundancy. 14:05 paulderscheid[m] Yeah, but it's still not a one-to-one mapping to the terminology. That's what threw me off (although it shouldn't have). 14:05 paulderscheid[m] joubu, there's a remote branch w/ the changes for bug 34478? 14:05 huginn` 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34478 is not accessible. 14:05 thd pauldersheid[m]: Ultimately to implement WEMI we need a new data model into which MARC records feed data and act as an exchange format but not the representation and indexing format. One of the goals of BIBFRAME was to be a relationship model, not a record model. 14:06 Joubu marcelr: about your translation problem, did you see bug 35567? seems related 14:06 huginn` 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35567 minor, P5 - low, ---, kevin.carnes, Pushed to oldstable , Host-item in "Show analytics" link can be translated 14:06 marcelr will have a look, thx 14:08 marcelr they solved it inline, just hoping for a smart solution :) 14:08 thd pauldersheid[m]: Yes, there is an identify of number of elements originally for the same purpose as WEMI without an identity to WEMI. 14:14 thd pauldersheid[m]: A good model would be a hyper model combining many different record formats into some super data format with also fine granularity to avoid semantic loss which could ingest MARC 21, UNIMARC, Dublin Core, ERMS, WikiData, etc. 14:14 cait Joubu: I'll put it on my todo... but not sad if someone does it before me 14:19 thd pauldersheid[m]: The University of California Union Catalog, MELVYL, had MARC based super records in the 1980s which combined data from all the records in the system. The US academic libraries system RLIN, subsequently absorbed by OCLC, sometimes used super records. 14:22 NikolayGospodinov[m] Hello. I have a question. Do you have scanned newspapers that you are viewing in Koha. If you have can you give me access to see what they look like? 14:23 cait we would only have links to some external repository for digitzied things 14:23 cait not something stored or viewed in Koha 14:24 NikolayGospodinov[m] Can I look into those? 14:25 cait as I said it#s only a link 14:25 NikolayGospodinov[m] okey 14:25 cait I'll find an example still sec 14:26 cait [off] https://bibliothekskatalog.bbf.dipf.de/cgi-bin/koha/opac-detail.pl?biblionumber=242224&query_desc=kw%2Cwrdl%3A%20digitalisierung 14:26 cait the "Digitalisat" links should be the right ones 14:26 NikolayGospodinov[m] okey 14:26 NikolayGospodinov[m] thank ypu 14:27 NikolayGospodinov[m] you 14:27 marcelr thx emlam++ 14:27 emlam np :) 14:32 cait got to run - will try to entangle things tomorrow again 14:32 cait bye all! 14:34 thd Joubu: You should change the configuration of the other BibLibre managed mailing lists to support DMARC to minimise mail going unseen in spam boxes for Gmail, etc. in February. I have 28 pages of comments about configuring Discourse migrating users and data etc. There is no simple route to a good inclusive configuration of Discourse for the Koha community even with a blank slate approach with no migration of data or users, there is much to 14:34 thd set up, configure, and test. 14:35 thd Joubu: is_list set to "Munge From". 14:35 thd dmarc_moderation_action set to "Munge From" for the rest of the BibLibre lists. 14:36 Joubu please open a bug report 14:36 thd Joubu, there is one open. 14:37 * thd finds it. 14:38 thd https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34927 14:38 huginn` 04Bug 34927: enhancement, P5 - low, ---, wizzyrea, NEW , Adding DMARC compatibility to mailing lists 14:38 thd I will add a new comment. 14:40 Joubu yes, please add a comment, as small as possible, with what needs to be done. 15:16 lukeg hi 15:17 caroline Hi lukeg! 15:18 blawlor[m] lukeg: hi 17:08 reiveune bye 18:14 tcohen Joubu: what has changed in Vue-land regarding flatpikr 20:36 aleisha hello all 20:44 caroline mtj around? 20:50 caroline well, bad news, restarting my computer did not fix the docker problem :( 20:50 caroline It still stops at "Inserting /kohadevbox/koha/installer/data/mysql/mandatory/account_offset_types.sql" 20:51 caroline A little bit above that, there is an error message from mysql 20:51 pastebot "caroline" at 127.0.0.1 pasted "ktd error message" (44 lines) at https://paste.koha-community.org/36495 20:55 caroline Are those files the ones in my main koha git? I can't find the kohadevbox directory, but I know where the installer/data/mysql/etc is in the git 20:56 emlam I think kohadevbox is the virtual directory docker creates when it starts up, but it does mostly lead to the "real" files in the git 20:57 caroline ok thanks emlam! 20:57 emlam no problem! good luck! 20:58 caroline I see a lot of crap when I do `git status` so I will try cleaning that up. Hopefully it's the source of *all* my problems (lol!) 21:05 paulderscheid[m] That's a strange error :D 21:06 caroline I cleaned everything, and redid ktd up.... 21:06 * caroline croses fingers 21:06 caroline *crosses 21:09 caroline oh I think it went past the point where it usually stopped! 21:09 paulderscheid[m] That's good! 21:09 caroline koha-testing-docker has started up and is ready to be enjoyed! 21:09 emlam hooray! 21:09 paulderscheid[m] 🎊 21:14 davidnind excellent! 21:16 caroline since wahanui is not here to say it: darn tootin' it is! 21:17 davidnind I miss that! 21:17 davidnind I'm a bit late in starting today, so good to see you managed to solve it! 21:26 davidnind My KTD work flow process for bug testing is normally:... (full message at <https://matrix.org/_matrix/media/v3/download/matrix.org/uuXKFumIHFESMSdHmKhjcekF>) 21:56 aleisha caroline, a good chance those ktd problems are because of leftover files! 21:57 aleisha a clean git checkout should work much better 21:57 caroline it surely points to that. I'm not sure what I did to have so many untracked files, probably a reset or something 22:07 caroline Is this order correct? If left empty, it will fall back to the first defined address in the following list: library reply-to, library email, ReplytoDefault, KohaAdminEmailAddress. 22:07 caroline (For AcquisitionsReplytoDefault) 22:07 caroline I thought it was library reply-to, ReplytoDefault, library email, KohaAdminEmailAddress. 22:08 caroline (ReplytoDefault before the library email) 22:16 caroline In the library form, it says the library reply-to falls back to ReplytoDefault, not the library's email... I find this confusing 22:32 davidnind I find that I get left over files when the CSS is update (yarn builds, etc), and with translations 22:33 davidnind No experience with the order of the reply to addresses, seems confusing to me (as you described!) 22:47 aleisha <caroline> I thought it was library reply-to, ReplytoDefault, library email, KohaAdminEmailAddress. 22:47 aleisha i think youre right that it should probably be this!