Time Nick Message
21:21 JasonGreene[m] gotta leave work... I'll pick up later. thanks for the help
21:19 JasonGreene[m] I even tried changing the name of the pics after I removed the CSS . it stays blank
21:10 JasonGreene[m] I made the change and the area went blank and clickable... then I took it out and it stayed blank
19:35 caroline paulderscheid++
18:49 davidnind paulderscheid++
18:49 davidnind if you replace the Koha logo file with your own on the file system, it will most probably be overwritten with upgrades - so it is best to either have a separate file for your logo, or use a URL to your organisation's logo (for example, on the main site)
18:43 paulderscheid[m] You're welcome
18:42 JasonGreene[m] Thanks again
18:42 paulderscheid[m] Great!
18:42 JasonGreene[m] ok, I'll do it and let you know how it works
18:41 paulderscheid[m] Hereby I mean the path in the line of css.
18:41 JasonGreene[m] :-)
18:41 paulderscheid[m] Nah, you can do it. Just add the file and adjust the path to "../images/<YOUR_FILENAME>".
18:40 JasonGreene[m] maybe just leave the code and rename the files
18:39 paulderscheid[m] This is the path to that directory: /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/images
18:39 JasonGreene[m] ok, I'll look
18:38 paulderscheid[m] That should be where the koha-green-logo.svg lives.
18:38 paulderscheid[m] That will work
18:38 JasonGreene[m] or put it in "../images" folder
18:38 paulderscheid[m] You wouldn't want users to access your server configuration under /etc from the web, right :D
18:37 paulderscheid[m] It has to be accessible from the OPAC so this will not work.
18:37 JasonGreene[m] in the <YOUR_URL> can I use a local KOHA server .gif pic something like "/etc/apache2/sites-enabled/logo.gif>
18:30 paulderscheid[m] Anytime :D
18:30 JasonGreene[m] yes, I hope, I'll look ... thanks
18:29 paulderscheid[m] Have I made that clear enough? Or should I explain a bit more?
18:29 paulderscheid[m] Then you just have to replace <YOUR_URL> with a valid URL that points to an image.
18:28 paulderscheid[m] There you can just hit 'Click to edit' and enter this line `#logo { background: transparent url("<YOUR_URL>") no-repeat scroll 0%; }`
18:27 paulderscheid[m] It's not a file but rather a system preference. You'll find it under Administration -> System Preferences -> OPAC -> OPACUserCSS.
18:25 JasonGreene[m] ok, thanks. I'm not a code writer so I'll give that a try, where is that file?
18:24 paulderscheid[m] You can also use urls to your resources if they live somewhere else for example `https://<YOUR_DOMAIN>.<TLD>/<YOUR_IMAGE>.<YOUR_FORMAT>`
18:23 paulderscheid[m] What you could do is to override that line in OPACUserCSS with something like this: `#logo { background: transparent url("../images/<YOUR_LOGO_URL>.<YOUR_FORMAT>") no-repeat scroll 0%; }`
18:22 paulderscheid[m] The logo is set by css, specifically this line: background: transparent url("../images/koha-green-logo.svg") no-repeat scroll 0%;
18:18 paulderscheid[m] Let's take a look
18:18 paulderscheid[m] Ok
18:17 JasonGreene[m] nope... Koha 23.05.04
18:17 paulderscheid[m] Should show up in the lower right corner of the staff interface.
18:17 paulderscheid[m] 21.05 or 21.11?
18:17 JasonGreene[m] i thnk
18:17 JasonGreene[m] 21
18:17 paulderscheid[m] What version of koha are you running?
18:17 paulderscheid[m] Sorry, didn't want to ignore you there, was just doing something.
18:16 JasonGreene[m] yes
18:16 paulderscheid[m] Jason Greene you still there?
17:29 paulderscheid[m] Alright, seems to make no difference
17:25 paulderscheid[m] Will update
17:25 paulderscheid[m] I just noticed that my guide relies on an old version of koha-testing-docker (65 commits behind)
17:21 * JasonGreene[m] uploaded an image: (24KiB) < https://matrix.org/_matrix/media/v3/download/matrix.org/tWKBeZRwJhUDInYMTAySDuSn/koha-pic.PNG >
17:21 JasonGreene[m] that one
17:19 JasonGreene[m] hello all. is there a manual page that shows how the replace the upper left KOHA pic on the Library user page?
17:10 tcohen[m] You need --dev
17:10 PedroAmorim[m] thanks Paul, I probably need to pull ktd
17:09 paulderscheid[m] That's odd, koha-translate -l -a returns everything for me.
17:08 paulderscheid[m] Second run looks eerily similar.
17:07 pastebot "paulderscheid[m]" at 127.0.0.1 pasted "Test results of koha-testing-docker w/ podman, second run w/ no additional language installed and default sysprefs" (352 lines) at https://paste.koha-community.org/31934
17:05 paulderscheid[m] That's dubious.
17:05 paulderscheid[m] Ah, didn't read the second half of that sentence.
17:05 paulderscheid[m] Try de-DE, worked for me yesterday.
17:04 PedroAmorim[m] running koha-translate --install fr-FR says the selected language is not currently available and koha-translate --list --available returns empty
17:04 PedroAmorim[m] anyone able to confirm if koha-translate works on k-t-d?
17:02 paulderscheid[m] Noticed that I had a language and some sysprefs enabled, second run already looks better.
16:23 paulderscheid[m] Here are the test results. I have to double check if the setup is correct. Some of those might be false positives.
16:22 pastebot "paulderscheid[m]" at 127.0.0.1 pasted "Test results of koha-testing-docker w/ podman" (348 lines) at https://paste.koha-community.org/31929
16:20 reiveune bye
15:53 paulderscheid[m] Currently running all tests to check whether something is broken.
15:50 paulderscheid[m] Or rather signal 9s and -1s
15:49 paulderscheid[m] The issue w/ the random -9s was indeed related to memory, increasing the memory in the config file for qemu solved it.
15:49 tcohen[m] Ok!
15:49 paulderscheid[m] Hi tcohen, I just added a section on getting koha-testing-docker to work w/ podman if you want to try it out https://wiki.koha-community.org/wiki/Koha-testing-docker#How_to_use_koha-testing-docker_with_podman.
15:49 tcohen[m] at least that's what it looks like
15:48 tcohen[m] It is not on D11, it is on the full test suite
14:31 cait I need to leave in an hour or so - but will be bakc on it tomorrow morning
13:42 ashimema i have a meeting to head into shortly.. but can look at those tests after
13:41 cait it looks like all "hook" related tests are failing on D11 - also some random and a shibboleth one (35506 35507)
13:34 cait we do map 001 to ean in our installatons usually, for similar reasons
13:34 cait maybe we should have one
13:34 cait hm yeah, we don't have a koha-to-marc mapping for authorities
13:34 cait it looks like I broke D11...
13:34 domm[m] In that library we also added a nice hack to the auth-tables (actually when we first migrated it) to materialize the value of 024$a into a column (which also has an index, so lookups are very easy and fast)
13:32 cait makes sense
13:32 domm[m] I guess I'll start with hardcoding, and think about putting it into some kind of config later
13:32 cait I was wondering about hardcoding the lookup... but maybe one could also use something like field: index in a yaml style?
13:32 domm[m] Maybe 035$a would be an even better candidate (but it's repeatable, which makes the direct lookup a bit harder)
13:31 cait hm so other national libraries probably have their own field (loc at least)
13:31 domm[m] I think it's more or less the same in auths: https://www.loc.gov/marc/authority/ad024.html
13:31 cait hm i think that was 024 bibliographic, plz ignore
13:29 domm[m] So I guess we'll do an ad-hoc implementation for that customer and work from that to hopefully get it in a form that can be included in Koha :-)
13:29 huginn` cait: A standard number or code published on an item which cannot be accommodated in another field (e.g., field 020 (International Standard Book Number), 022 (International Standard Serial Number) , and 027 (Standard Technical Report Number)). The type of standard number or code is identified in the first indicator position or in subfield $2 (Source of number or code). (Repeatable) [a,c,
13:29 cait @marc 024
13:29 cait but itmight work for LOC data too?
13:29 cait I think you'd probably make some German libraries quite happy with this feature
13:29 domm[m] Yeah, it seems that this is not at all possible ATM.
13:28 cait as Koha doesn#t use $0, I am not sure if there is even a standard index on it
13:28 domm[m] yes
13:28 cait I think you are correct--- you are referring to the auto-linking feature?
13:27 domm[m] As far as I can see from the source code there is no option currently do this?
13:27 domm[m] Sorry, slightly complex question (if better suited for mailing list, please tell me): User creates new biblio via SRU from DNB (german national lib). This contains eg the author in 100, and contains the GND-ID in 100$0. Now we already have an auth_record which has that number in 024$a. So it would be preferable to do direct lookup for that number instead of doing a sligthly fuzzy search based on eg author name and date.
12:56 cait tcohen++
12:52 ashimema maybe a python change
12:52 krimsonkharne[m] just tested a git bz apply .... and it responded as usual for me, no "invalid escape sequences"...
12:42 ashimema I did update
12:42 ashimema maybe a system change my end
12:41 cait hm it didn't for me earlier at least
12:39 krimsonkharne[m] heyyy #koha
12:34 pastebot "ashimema" at 127.0.0.1 pasted "git-bz noise" (28 lines) at https://paste.koha-community.org/31902
12:33 ashimema anyone else find git-bz is spitting out a load of crap on apply?
12:23 cait tcohen[m]: pm? :)
12:21 ashimema I was really singing it's praises and trying to get people to adopt it.. but alas I'm down about it again now
12:21 ashimema I'm disappointing that the matrix bridge seems to have become more unreliable again of late..
12:20 ashimema mm
12:18 tcohen[m] Oh, matrix bridge is working today haha. Awesome
12:17 cait thanks tcohen and paulderscheid[m] :)
12:04 magnuse gah! shibboleth is driving me crazy! logging in at the idp looks ok, the shib logs on the koha server says a session is created and my username is there, but then koha doesn't think there is a session after all. and /Shibboleth.sso/Session also says there is no session either. so maybe the session is started ok, but then terminated immediately?
12:04 tcohen[m] I haven't used podman before. But I'm interested in looking at this
11:54 paulderscheid[m] I will document the process in the wiki of setting it up, you can try it sometime if you're interested and can find the time.
11:52 paulderscheid[m] The koha container basically works, it just kills plack seemingly at random.
11:51 paulderscheid[m] That was the first problem I had, but I didn't run into any actual permission errors anymore when switching to a rootful podman machine.
11:50 tcohen[m] Permissions?
11:47 paulderscheid[m] As 9 means kill, what could the reasons be? I also ran into killed webpack processes a bunch of times. Does that also sound like a problem w/ resource allocation to you?
11:46 paulderscheid[m] Did you ever run in to something like this?
11:45 paulderscheid[m] I was testing the docker compose files w/ podman yesterday and it basically works, but I got random failures of plack with exit 0 - signal was 9. Any idea tcohen?
11:43 paulderscheid[m] See cait, you got it!
11:43 paulderscheid[m] Hi #koha
11:40 tcohen[m] Your push looks great, cait
11:40 tcohen[m] Morning
11:13 cait ashimema++ # thanks for pointing me in the right direction for the bugzilla scripts
11:12 cait QA queue 42 > 30
10:43 cait working on the bugzilla updates
10:26 cait it did look slightly odd... just nervous here :)
10:26 cait https://git.koha-community.org/Koha-community/Koha/commits/branch/master
10:26 cait ok... wrong link
10:25 cait https://git.bsz-bw.de/koha/koha/-/commits/master/?ref_type=HEADS
10:25 cait hm I pushed, a git fetch origin git status now shows "up to date with master" - but gitea is not showing the commits
10:02 ashimema keeps it all very clean in your mind
10:01 ashimema it's nice
09:54 cait well not the password, but a separate remote to push
09:54 cait yep, I set it up like that yesterday, Joubu had pointed it out
09:54 ashimema basically.. it acted as an 'are you sure.. are you sure your sure' mechanism
09:54 ashimema so pull all worked fine as is.. but for push I had to explicitly state 'upstream'.. and I also stuck a password on it somehow at my end
09:53 ashimema then I tracked origin
09:53 ashimema I think I had two repo's set.. 'origin' which I set the read only http url and 'upstream' which i set to the keyed push url
09:52 ashimema though I can't entirely remember how I did it
09:52 ashimema I set myself some extra safeguards when i was doing it
09:51 ashimema it really does
09:51 ashimema hehe
09:43 cait working on the master branch feels SO weird
09:27 ashimema nice one
09:27 cait about to push some easier patches today - I'll go chronologically soon, but still practicing :)
09:26 * cait1 waves
09:25 PedroAmorim[m] \o
09:13 ashimema morning
08:26 cait1 good morning all!
06:48 reiveune hello