IRC log for #koha, 2024-02-29

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

All times shown according to UTC.

Time Nick Message
02:21 thd JasonGreene[m]: I do not know of a script for batch printing Koha patron cards but one may exist and I have never looked.  Batch printing spine labels for material I would expect.
02:24 JasonGreene[m]: I expect that the card printing function creates PDF files for printing.  You could save the patron card PDF files in succession and print them as a batch.
05:18 saa joined #koha
05:19 saa what are the steps needed to do on server side so that admin and opac works faster we have observed that it takes time to load data when searched either on opac or koha admin page
07:12 MarkHofstetter joined #koha
07:39 dolf_ joined #koha
07:41 Joubu @later tell caroline ping me when you have a minute :)
07:41 huginn` Joubu: The operation succeeded.
07:45 Joubu mtj: around? Are the packages ready?
07:49 reiveune joined #koha
07:49 reiveune hello
07:53 lds joined #koha
07:57 cait joined #koha
08:02 alohabot joined #koha
08:09 mtj hi joubu
08:13 cait joined #koha
08:20 cait joined #koha
08:47 krimsonkharne[m] morning all
08:55 paulderscheid[m] Morning #koha
09:02 Joubu @later tell fridolin can you ask someone at BibLibre to confirm the changes from 34663 please?
09:02 huginn` Joubu: The operation succeeded.
09:36 saa what are the steps needed to do on server side so that admin and opac works faster we have observed that it takes time to load data when searched either on opac or koha admin page
09:40 cait @later tell kidclamp ping!
09:40 huginn` cait: The operation succeeded.
09:41 cait saa: i believe your question is too general - performance issus are a complex topic. You might just be missing resources (DBMS like to have enough memory for example)
09:45 saa our server is running virtually and we need to know what excactly can be done to improve performance of kohaadmin and opac
09:45 cait give it more resources to start with
09:45 check the db has enough RAM
09:46 mysqltuner is a tool that can help with that
09:47 saa is there any configuration needed for apache or zebra to change for quick results loading in opac
09:48 cait if you are using packages the standard configuration should be ok
09:48 you can check on the about page > first and system information tab if everything is green and running
09:49 your intance should be using Plack - but if you don#t have a manual old setup, that shoudl all be taken care of
09:54 Joubu saa: do you have use_zebra_facets set to 1 in koha config file? If so, try 0 and restart the services
09:54 saa yes it is 1 in use_zebra_facets
09:55 yes using plack
09:56 when i click on system information it gave Database row format incorrect  Database tables with a row format other than 'DYNAMIC': 233  You may experience problems upgrading to newer versions of Koha unless you update the row format for your database tables.  To know how to avoid this problem see the related wiki page: Database row format Warnings regarding the system configuration Preferences and parameters Warning There is no "Fast add" (FA) framework define
09:57 XML configuration file Warning You are missing the <encryption_key> entry in your koha-conf.xml file. Please generate a key. We recommend one of at least 32 bytes. (You might use 'pwgen 32' to do so.)
09:57 how to correct this row format issue
10:06 cait have you checked the wiki page?
10:09 Joubu' suggestion about use_zebra_facets is good, it will definitely have an impact on performance do deactivate (you stil get facets, they are generated differently)
10:14 saa i have already made change as suggested by joubu
10:14 shall i run above script on wiki hope there wont be any issue on livekoha
10:15 is it neceesary to create encryption key
10:15 i installed mysqltuner but what further i need to do
10:20 https://wiki.koha-community.or[…]tabase_row_format in this script what all i need to change replace instancce name only right
10:50 Joubu @later tell mtj ping 35614
10:50 huginn` Joubu: The operation succeeded.
11:17 RamiKaram[m] Hello
11:18 i have a question if someone can help me with
11:21 can i install koha on one server, and install the database on another server? and change the database connection xml file under /etc/koha/sites/koha-db/kofa-conf.xml to point to the remote database ip?
11:26 ashimema do we have a way to remove the 'clear date' cross for flatpickrs when the date is required?
11:29 oleonard ashimema: Shouldn't form validation take care of that?
11:29 ashimema well.. it does mean you can't submit it empty
11:29 I just find it a little odd exposing a 'clear' button when the field is required.. but I suppose it's consistent
11:30 I'm not too worried
11:30 oleonard Maybe they're clearing the date because it's wrong and they want to start over? I don't know, I made that up.
11:34 ashimema indeed
11:35 I already came around
11:35 what I don't like however is the format of the forms I'm looking at
11:35 * ashimema uploaded an image: (22KiB) < https://matrix.org/_matrix/med[…]IdIXKfv/image.png >
11:36 ashimema the buttons feel like they're placed wrong.. but I get why they are where they are.. it would just be nice to make that warning more modal like.
11:36 I'm looking at bug 36175 for reference.
11:36 huginn` 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=36175 blocker, P5 - low, ---, martin.renvoize, NEW , Checking out items that are booked doesn't quite work
11:45 kidclamp joined #koha
11:47 tcohen hola #koha \o/
11:50 oleonard ashimema: I agree
11:50 Hi tcohen
11:51 ashimema it would entail a bit of a refactor to make it nicer though I think
11:51 not something I have time for right now alas ☹️
11:55 RamiKaram[m] Hello everyone, any idea of both koha app and database should be on same server? or can we split them?
11:55 * kidclamp waves
12:14 oleonard RamiKaram[m]: I know you can split them, yes.
12:19 tcohen oleonard: hi
12:30 thd joined #koha
12:42 oleonard Bug 36200... I kinda forgot Zotero existed
12:42 huginn` 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=36200 enhancement, P5 - low, ---, oleonard, NEW , Adding Zotero in SocialNetworks
12:49 thd Joubu: If you add my user back onto the Taiga koha-ils team, or whatever is necessary, I would be able to post the update from yesterday for the several variables changed in LocalSettings.php to turn Koha wiki caching back on for https://tree.taiga.io/project/koha-ils/us/250 as well as other information which people have been expecting me to post.  My Taiga user is Thomas Dukleth subscribed using td-koha-taiga AT agogme.com .  I may not pay muc
12:49 h attention to Taiga from my difficult past experience with the heavy JavaScript framework consuming almost all the resources on a netbook but I do give it some attention.
12:50 Joubu I didn't remove you
12:51 done
12:51 thd I cannot seem to post or see no link to do so.
12:51 lds joined #koha
12:53 thd Now I do.  I had not been at all engaged with Taiga for a very long time so it was fine for whomever to have removed me.
12:54 Joubu nobody removed you, it's another board
12:55 tcohen Joubu++
12:55 thd Now I understand.  There had not previously been a reason to add me to the new board.
13:23 Dyrcona joined #koha
13:47 caroline joined #koha
13:55 Joubu tcohen, ashimema: I don't know who created it, but I removed the "CSRF" team on gitea, we already have a "security" team.
13:56 and I have added the tags visibility to all our teams (people didn't see the list of the tags for the security repo)
13:59 tcohen Joubu: I remember adding someone to the CSRF group
13:59 Pedro
14:00 the security group contained the release maintainers and the RM
14:02 Joubu the security group contains people who needs access to the security repo
14:03 (I took care of adding people from CSRF to security if they weren't already)
14:03 tcohen https://tree.taiga.io/project/koha-ils/task/242
14:04 that's what I did a month ago
14:04 I agree we can just add people to the security repo
14:05 Joubu not the security repo, the security *group*
14:05 and the security group has access to the security repo
14:05 write access
14:05 tcohen I'm aware of all that
14:05 +1
14:05 * cait sends cookies
14:06 cait security group will be used
14:08 tcohen Joubu++ # tags visibility fixed
14:12 Joubu @later tell dcook seen 34478 comment 174? opinions?
14:12 huginn` Joubu: The operation succeeded.
14:18 khall joined #koha
14:19 khall_ joined #koha
14:30 tcohen thd++
14:39 Joubu cait: does it still make sense to allow empty descriptions for AVs?
14:39 should not we default to the code when we save the AV, and have NOT NULL in DB?
14:39 otherwise we have blank entry in dropdown lists
14:39 tcohen you might have a description for OPAC/staff only?
14:40 (thinking of NOT NULL)
14:40 Joubu we have a fallback if opac description does not exist, yes
14:40 but what if staff dscription does not exist?
14:40 do you mean we have some AVs for OPAC only and so it does not make sense to require a description for 'lib'/staff?
14:40 tcohen I mean, are you suggesting that if some is let unfilled, the other one is picked and stored?
14:41 Joubu I mean we should require a description for staff
14:41 tcohen I'd agree
14:41 Joubu the form wouldn't validate
14:42 and DBMS will reject the insert if attribute is empty
14:42 tcohen or would put a confirmation dialog telling the 'value' will be stored as description
14:42 Joubu PedroAmorim[m] is currently fixing a 500 for ERM because the rest api spec does not allow null, and the spec validation explodes
14:43 tcohen so to_api() is returning something that doesn't validate with the spec
14:43 Joubu I know we allowed empty at some point because the sample data had an empty value to display it in the dropdown list. But it was silly and we removed it
14:44 and now we always display the empty option
14:44 PedroAmorim[m] no, api/v1/swagger/definitions/authorised_value.yaml has description as not NULL but it is NULLABLE in DB
14:44 khall joined #koha
14:44 PedroAmorim[m] https://bugs.koha-community.or[…]_bug.cgi?id=34920
14:44 huginn` 04Bug 34920: enhancement, P5 - low, ---, jonathan.druart+koha, Failed QA , ERM breaks if an ERM authorized value is missing a description
14:44 tcohen PedroAmorim[m]: you can fix it in to_api() or on the DB
14:45 PedroAmorim[m] I assumed description==lib was NULLABLE in the DB for a reason, so I approached the problem from a different angle
14:45 i.e. defaulting to showing code==authorised_value when description==lib is null in VueJS dropdown options populated by AV list values
14:46 tcohen you can mitigate this by tweaking the response in Koha::AuthorisedValue::to_api()
14:46 Joubu which is not correct because a different behaviour of what we have in other places of Koha: just show the dscription (ie. empty string if null)
14:46 tcohen: yes, there are 10 places to deal with
14:46 tcohen but I agree if there's general consensus, the right fix is to 'fix the DB
14:46 Joubu that's exactly the question :D
14:47 that's why I am questioning the root of the constraint! do we really need to accept null in DB?
14:48 tcohen I'd fix the DB
14:48 Joubu otoh it looks like too much for a quick fix to backport
14:48 yes, me too
14:48 tcohen I think we all got sick of amending our DB design problems in the code everywher
14:48 Joubu so maybe fallback at to_api level as a temporary fix (and no need to fix client-api and REST API specs)
14:49 then on a separate bug report and fix the existing data in an atomic update and make the description mandatory
14:49 tcohen Joubu: that's exactly what I'm suggesting. Though I didn't ponder if it implies a lot of work on the front-end
14:49 as per Pedro's comment, things are designed this way so no big change
14:50 +1
14:50 Joubu I would not backport the DB changes anyway
14:50 tcohen totally
14:51 short-term backportable fix, and proper fix and revert of the tweak for the next release
14:51 Joubu are you happy with that PedroAmorim[m]? Looks like the fix will even be shorter
14:52 lukeg joined #koha
14:52 tcohen hola lukeg!
14:55 PedroAmorim[m] I'm always happy =D
14:55 can you please update the FQA reasons at bug 34920 with what the new direction should be then? I'll pick it up when possible
14:55 huginn` 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=34920 enhancement, P5 - low, ---, jonathan.druart+koha, Failed QA , ERM breaks if an ERM authorized value is missing a description
14:55 PedroAmorim[m] and open whatever new, follow-up, bug is required
14:57 Joubu++
14:57 tcohen++
14:58 Joubu done
14:59 bug 36203
14:59 huginn` 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=36203 enhancement, P5 - low, ---, koha-bugs, In Discussion , Authorised value's descriptions should not be NULL
15:10 wizzyrea joined #koha
15:16 cait hi wizzyrea!
15:17 fredericd: around maybe?
15:18 huberto joined #koha
15:18 huberto Hello everyone
15:21 oleonard Hi huberto
15:21 huberto I recently reopened bug #34755, which was confirmed by other koha users. My colleague patched it but Jonathan mentioned that this might be the same fix as bug #34478. The problem is, I don't have access to bug #34478. Is there any way I can at least see the bug's description?
15:21 huginn` 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=34755 critical, P5 - low, ---, maryse.simard, Signed Off , Error authenticating to external OpenID Connect (OIDC) identity provider : wrong_csrf_token
15:21 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=34478 is not accessible.
15:21 Joubu huberto: it will be pushed tomorrow
15:22 huberto Excellent. I'll see if it fixes our issue then.
15:24 Joubu huberto: I have isolated the patch that could fix your problem and pushed it there: https://gitlab.com/joubu/Koha/[…]9c29e04fa6fe01e13
15:24 if you want to try before tomorrow
15:25 huberto Thanks! I'll get to testing it as soon as I can.
15:25 Joubu I am sorry I don't have time to test but what you described on the bug (the token generated with a user then check with anonymous) is what this patch is addressing
15:46 bag joined #koha
15:47 lukeg1 joined #koha
15:58 lukeg1 cait: i am working to fix my release notes. I generated them without the release team, had to fix my user.yaml. Will have those up soon
16:00 bag joined #koha
16:00 khall_ joined #koha
16:06 khall joined #koha
16:11 reiveune bye
16:11 reiveune left #koha
16:26 cait lukeg1: thanks!
16:26 lukeg++
17:07 JasonGreene[m] anyone have a video on "as a librarian, how to check out books for someone else" or does each patron need to be logged in to check out?
17:08 oleonard JasonGreene[m]: A staff member must be logged in to the staff interface to check out to a patron
17:08 But I'm not sure I really understand your question
17:11 JasonGreene[m] ok, your answer is what I'm looking for.  I'm just a sys-admin so I'm learning more about libraries and how they function.
17:30 Instead of checking out physical books, does Koha have the ability to check out a PDF and only have the PDF usable for so-many days so it can't be kept or emailed to the someone else? Or is this just a dream?  :-)
17:31 oleonard It's only a dream at this time
17:31 JasonGreene[m] bummer
17:36 lukeg joined #koha
17:59 cait joined #koha
18:29 JasonGreene[m] After I built the system and changed 2 library's info and I deleted a few.  Once they are removed, are they gone or can I recover one of them?
18:38 cait JasonGreene[m]: the patron card tool can create patron card sin batch - but the patrons have to exist already
18:38 if you import patrons you can create patron cards for the full batch of imported patrons quite easily
18:39 JasonGreene[m] great, I'll look at it.. I just imported 250 patrons
18:40 create patron cards for the full batch of imported patrons  at the same time of the import?  i looked and didn't see that option... now they are already in the system
18:41 and gave about 75 a card number by hand
18:44 where do I find this option create patron cards for the full batch
18:49 lukeg joined #koha
18:55 cait hm
18:55 if you can, I would re-import them and add the cardnumber
18:55 there is a feature to automatically assign cardnumbers (autocardnumber I think), but I am not sure if it works on import
18:55 ... but you can't match them as they don't have a cardnumber, oh tricky
18:56 JasonGreene[m] hmm.. seeing that I did 75 by hand, I'll just do the rest by hand... not that many
19:01 cait ok
19:01 maybe have a look at the Autobarcode feature anyway
19:01 it assigns a cardnumber on saving, looking up the last one used in the database
19:02 JasonGreene[m] Thanks
20:45 khall joined #koha
21:07 JasonGreene[m] ok strange thing... I was give card numbers to patrons... did about 230 and the web pages gave "Internal Server Error"
21:07 I restarted Koha and I get the same... strange
21:11 Koha-library:/var/log/koha/library-new$ cat worker-error.log
21:11 20240229 15:07:55 library-new-koha-worker-long_tasks: client (pid 266984) killed by signal 15, stopping
21:11 going to reboot server
21:17 ok, rebooted and apache is running because I get port 80 however port 8000 and port 8001  give "Internal Server Error"
21:17 any idea what could have cause this? Koha? or ??
21:19 cat worker-output.log
21:19 Cannot connect to the message broker, the jobs will be processed anyway (Failed to connect: Error connecting to localhost:61613: Connection refused at /usr/share/perl5/Net/Stomp.pm line 27.; giving up at /usr/share/perl5/Net/Stomp.pm line 27.
21:19 ) at /usr/share/koha/bin/workers​/background_jobs_worker.pl line 92.
21:21 The drive has plenty of space... (full message at <https://matrix.org/_matrix/med[…]ZFLMSHqOQGPFtZyCx>)
21:33 maintenance@Koha-library:/var/log/apache2$ cat error.log... (full message at <https://matrix.org/_matrix/med[…]LOOxzDTPjALUwvTWx>)
21:47 nevermind... it is up and running and the server's local browser sees Koha... it was my a Desktop firefox.. Edge works
22:01 khall joined #koha
22:09 alohabot joined #koha
22:40 * dcook looks at scrollback
22:43 paulderscheid[m] gettext is a crime against humanity -_-
22:44 khall joined #koha
22:54 dcook @later tell Joubu I thought you'd gone ahead with that one. I've added a comment replying to 34478 comment 174
22:54 huginn` dcook: The operation succeeded.
23:52 mtj Hi folks.. Packages are built.
23:53 bag awesome!
23:53 heya mtj
23:56 mtj Hiya bag
23:57 1am in Europe, let's push in EU morning

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

koha1