IRC log for #koha, 2023-08-23

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

All times shown according to UTC.

Time Nick Message
00:36 alohabot joined #koha
03:16 bag joined #koha
04:25 PriyanshuSoni[m] <rudyh> "Confirm that the item type you..." <- Yes, i have created a list of Books in public mode.
04:25 * public mode, still nothing is showing in crousel config.
05:40 fridolin joined #koha
06:03 alohabot` joined #koha
06:11 thibaud_g joined #koha
06:16 thibaud_g joined #koha
07:17 lds joined #koha
07:52 fridolin1 joined #koha
07:55 aw-bib[m] hello :) I'd have a small more bibliographic question. our catalouge currently holds a number of "not so common" ids. eg. pointers to inspirehep, arXiv in some cases even wos. I'd not want to loose them and at some later point in time even use them like we do now for uplinking to those sources. how do I preserve them in koha  properly?
08:54 Zahid[m] hi every one, need help in patrons
08:55 i am using koha 22.11 version i have imported all my patrons data into Koha 22.11
08:57 about 60000 patrons are imported successfully but when i see in koha the firstname of patron is not display on opening records, it searches correctly
08:58 fridolin1 left #koha
09:00 Zahid[m] the first name of some patrons are display correctly but some patron's firstname is not display
09:01 any suggestions ? am i missing some thing?
09:25 thibaud_g joined #koha
10:00 Annelisterman[m] Organizational patrons do not have first name. You can save/import it to the borrowers table but if you add organizational patron via staff interface it is not possible to add firstname. Also it is not shown on patron details page if there is one. Could that be the reason?
10:05 cait joined #koha
10:07 cait hello
10:27 oleonard joined #koha
10:28 oleonard o/
10:30 cait \o
10:34 khall joined #koha
10:49 Zahid[m] what is mean by organization identity vs patron identity ? how can i differentiate  ? and on what fields koha separates these two identity?
10:51 oleonard Zahid[m]: It's the same data, stored in the same place. It's just displayed differently based on the patron category
10:51 cait depending on the type you selected for a patron category, the name fields will display a little differently in the patron edit form
10:52 * cait nods
10:58 Zahid[m] thanks i got your point. my issue is resolved.
11:05 👍️cait oleonard Anneli Österman
11:32 khall_ joined #koha
11:52 PriyanshuSoni[m] Hey guys,... (full message at <https://matrix.org/_matrix/med[…]DwfkseFMvfvscMbmH>)
13:36 RudyHinojosa joined #koha
13:45 Dyrcona joined #koha
14:15 RudyHinojosa What could be causing the edit of an item to hang the interface for about 15-30 seconds? v23.05.02
14:16 using Mariadb
14:16 optimized.
14:24 https://drive.lightwavelibrary[…]iOj1f-k7Dgzt-GsQo
14:24 Current Config
14:31 cait RudyHinojosa: I am not sure, do you have many items on that record?
14:32 it's not 'normal' - it should be much quicker
14:32 RudyHinojosa just one. I am seeing a long wait time when triggering the drop down for item types. also seeing item type duplications in the dropdown. but they are not duplicated in admin item types.
14:33 cait that sounds all types of wrong
14:33 anything in the console? maybe some JS interfering?
14:33 also if you can have a look at the logs server side
14:33 RudyHinojosa https://drive.lightwavelibrary[…]YIqDJ-0LAAIvmHsQo
14:33 screen shot of duplicate item types
14:34 aroussos RudyHinojosa: any chance your MariaDB database is located on a host external to the system that hosts Koha?
14:36 RudyHinojosa no. mariadb is on the same server local
14:36 checking for JS interference in code blocks.
14:38 aroussos RudyHinojosa: OK then, the next thing I would do is create a very simple SQL report from within Koha (something along the lines of 'SELECT * FROM itemtypes') and run that to see if it returns quickly or hangs for 15-30 seconds
14:39 RudyHinojosa https://drive.lightwavelibrary[…]LBi3U-DbGgoqWIsQo
14:40 screen shot of only js in intranet block. I'm using the batch permissions plugin.
14:42 >aroussos: sql report came back instant.
14:42 cait just to make sure, I'd try to remove it and try again
14:42 just ruling it out as a source of the issue
14:43 RudyHinojosa cait: i'll do that right now. thank you. be right back w/ the verdict.
14:46 >cait: no effect. now I haven't restarted the server either after removing the codeblock. may not be required.
14:51 something goofy happening on the dropdown onstart routine.
14:51 onclick
14:52 going to try a different browser. was using edge.
14:53 uh oh. firefox does not have a problem. but the item types are still duplicated.
14:53 but it's fast.
14:56 cait super strange
14:56 I don't have edge to give it a try
14:56 RudyHinojosa I knew I hated microsoft for dozens of reasons, now it's for a bakers dozen reasons. ;)
14:57 cait is a baker's dozen more?
14:57 RudyHinojosa 13
14:57 lol
14:57 cait oh!
14:57 I am German so haven't come across that yet
14:57 if you give me 5 mins I can get my development up and check there at least for the duplication
14:58 RudyHinojosa I'm going to check advanced settings on edge and see if I can find some clues.
14:58 ok, I need to tell you that my client is using a consortium and sharing the itemtype across 3 other libraries.
14:59 cait ok so there is a library limitation going on
14:59 library groups also?
14:59 RudyHinojosa no groups
14:59 cait but it's showing up twice, not 3 times?
15:00 RudyHinojosa peek at my screenshot. it appears several times.
15:00 the main collection
15:01 cait that's a whole lot of main collection
15:01 RudyHinojosa https://drive.lightwavelibrary[…]YIqDJ-0LAAIvmHsQo
15:01 yeup.
15:01 cait only once in itemtypes I assume?
15:01 RudyHinojosa yes.
15:02 cait hm in master sample data the itemtypes are ok
15:02 I'll try to limit them to some libraries
15:03 hm still behaving nicely
15:03 RudyHinojosa https://drive.lightwavelibrary[…]jlpoW-XbHAuG-LsQo
15:04 my item type
15:05 using edge?
15:05 cait very similar to mine
15:05 I can't - on Linux
15:05 RudyHinojosa edge is available on linux
15:05 cait I am not sure I am willing to go there...
15:05 but didn't you say it also duplicated in firefox?
15:05 RudyHinojosa microsoft is your friend. let us in!
15:05 lol
15:06 yes, but at least there is no performance hit.
15:06 everything is almost instant.
15:06 cait very odd indeed
15:06 I am quickly running out of ideas here
15:07 you could try filing a report for the duplication at least - maybe someone else has seen it or an idea
15:07 RudyHinojosa I've seen echoes of dropdown data in coding projects that turned out to be a video driver issue.
15:08 cait that sounds hard to catch
15:09 RudyHinojosa https://answers.microsoft.com/[…]ac93-6569138807a9
15:14 cait can you confirm the newer version fixes it?
15:16 RudyHinojosa I'm on the latest on Pop-Os
15:16 i'll try on a windows machine shortly.
15:22 chrome has the same slow behaviour as well on the dropdown. firefox does not have this issue.
15:23 cait i guess most devs still touring Finland - so not many people around here today
15:28 oleonard No more touring for me...
15:28 cait me neither
15:28 but some more days of vacation at least
15:29 oleonard I'm having a weird permissions issue today... I can't see Recalls stuff even though I'm logged in as a superlibrarian
15:34 cait and turned it on too?
15:34 oleonard it must be some kind of data problem because it works with the sample data
15:35 cait where are you not seeing them?
15:35 oleonard The links on circulation home page
15:35 cait very odd
15:41 oleonard Using a slightly older version of my test data clears it up but I sure wish I knew what it was about.
15:53 eythian tcohen: https://gitlab.com/koha-commun[…]ocker/-/issues/19 I found the cause of your issue with docker swarm
16:35 Kolvir joined #koha
16:37 Kolvir I can not find this error from the MARC bibliographic framework test. Can someone please giveme some ideas on how to track it down? ALL items fields MUST : be mapped to the same tag, and they must all be in the 10 (items) tab
16:38 I've dug through the 952 field and compared it to the default framework, but can't see any differences
16:40 RudyHinojosa Kolvir->do you have everything in the 952 tag and subfields pointing to the 10 tab?
16:42 Kolvir yes
16:47 cait maybe you have an items field mapped to a field that is not a 952?
16:47 check the koha-to-marc mappings
16:48 Kolvir ok, will check that
16:57 That was it, thank you.
16:58 cait :)
17:02 Kolvir I was trying to get the DDC call number from 082a displayed in the holdings table instead of the one that shows up, they don't match exactly
17:02 cait yes, don't do that
17:03 have a look at the itemcallnumber system preference
17:03 it can help you with cataloguing, it will show the 082a if you add a new item, helping you with filling the callnumber in the item
17:04 also make sure to set up $2 cn_source with ddc (administration > classification sources)
17:04 it will help you get proper sorting for your callnumbers
17:09 Kolvir I've got 082a in the itemcallnumber system preference, but am not seeing where/how to set up $2 cn_source with ddc . I'm looking at Administration -> Classification Configuration
17:09 cait one moment
17:10 are you only using ddc?
17:10 Kolvir yes
17:10 cait ok
17:10 so in classification sources, make the "in use" only yes for dd
17:10 c
17:10 Kolvir ok
17:10 cait then set the DefaultClassificationSource system preference also to ddc
17:11 Kolvir ok
17:11 cait so now you are set up for any new items
17:11 do you have a lof ot items already?
17:11 Kolvir that's how it was already set
17:11 no
17:12 cait oh that's good then :)
17:12 Kolvir 50-60
17:12 cait ah, so what happens is when you catalog:
17:12 Kolvir cataloging starts this week
17:12 had to move to a new computer
17:12 cait the itemcallnumber is put in items.itemcallnumber
17:12 and then koha creates a sorting form of your itemcallnumber from cn_sort in cn_source
17:12 this is used for invnetory
17:12 or when sorting tables on callnumber
17:13 so good to have that set up correctly :)
17:13 fridolin joined #koha
17:13 Kolvir Ok, thank you!
17:13 cait hm from cn_source (classification type) in cn_sort (sortable form)
17:13 had them the wrong way
17:14 maybe have a look at those columsn in the items table sometime, it should be more easy to understand then
17:15 Kolvir ok
17:17 are the koha to mark mapping done after any record being modified by a template when it is saved? What I want to do is drop all 900 fields that come from say a z39.50 search when they are imported.
17:17 koha to marc I mean
17:19 cait the fields in biblio, biblioitems and filled/updated when you update/add a bibliographic record
17:19 the fields in items when you add/edit an item
17:19 not sure what you mean with the dropping
17:19 do you mean delete all 9xx from incoming records?
17:20 Kolvir yes
17:21 cait you can use an XSLT template for that
17:21 the mappings won't help with it
17:21 check the manual for the XSLT template setting in z39.50, we might have an existing one to do that alredy
17:21 Kolvir I didn't want a mod template to interfere with the fields koha adds to 952
17:21 cait ah no that won't happen
17:22 items work a bit different
17:22 the 952 is not part of your records
17:22 they are only added when you export
17:22 either to the search engine or when using the export tool
17:22 if you look at biblio_metadata.metadata at the sorted marcxml record, they are not there
17:23 Kolvir great. That's what I needed to know.
17:23 cait sorted = stored
18:16 KevinFurst[m] Is it ok to post a problem I'm having with importing Marc records here? I got the recommendation from the listserv.
18:17 bag yes please
18:18 cait always just ask, if someone around can help, they will :)
18:24 KevinFurst[m] Awesome. So here's the bg info. We're moving from Follett Destiny to a self hosted Koha instance. I've exported all my MARC records for my two libraries and am attempting to import them into Koha. We're talking around 23k records for one library and 11k for the other (2 branches I guess if I'm to use the correct terminology.) I noticed a couple of issues right away. 1. I had to make the branch codes match up to whats in Koha so I used
18:24 MarcEdit to do that and then 2. I noticed that Follett exported item info using 852 instead of 952 so I had to change that. Those two changes got me a step further so that when I staged the records for import, Koha was seeing BOTH, meaning on the managed staged imports screen, it gave me values in both the # Records AND # Items columns. Previous to those changes, I only got values in # Records column. However, when I go to import the
18:24 batch, it just immediately says it fails on the job screen. I've tried breaking it down using Marc split to files of 1000 and that didn't help. I've perused the logs in CLI and don't see anything immediately popping out as the issue.
18:25 cait let me get back to you in a moment
18:26 RudyHinojosa cait:resolved the 100's of repeating itemtypes in the dropdown.
18:28 bag KevinFurst[m]: sounds like maybe a bad record in there?
18:28 KevinFurst[m] Everything else seems to be ok in Koha and works. I'm using a server with 8GB of mem and it doesn't seemed pegged when I run the job. There's nothing else running on that machine. I did try a job of 10 or 11 records and it would import them but in scanning the fields between the two, I don't see anything really sticking out as materially different between the records that worked and those in the general file that fails every time on
18:28 import.
18:28 wahanui i think import is what I'm trying to figure out
18:28 bag can you valid the mrc format?
18:30 KevinFurst[m] I have run the validate marc records tool in marc edit and then used the "Clean" file it generated as the one I try in Koha. In the "error" file MarcEdit puts the bad records into, it's like 1 or 2 records, that's it.
18:31 If there is a bad record in there, am I correct that Koha wouldn't find it in the import/staging portion and would only find it on import? And it wouldn't just ignore that bad record, it would cause the entire job to error out?
18:31 cait hm it could be the items
18:31 do you have an example 952 you could share?
18:31 i might be able to tell you what's missing
18:31 but basically you want a b y to match exactly what you configured in Koha (homebranch, holdingbranch and itemtype)
18:31 case sensitive etc. exact match on the codes
18:31 I recommend to also add a $2 with your classification scheme - it will make Koha create a sortable form or your callnumber on import, which is used by inventory etc. - it can be done later, but it's easy that way
18:31 fi you are using ddc that woudl be $2ddc
18:31 KevinFurst[m]: ^any of that make sense to you?
18:31 KevinFurst[m] Yes. Give me a few minutes to work through that with my file.
18:32 cait I am not sure about how it deals with errors, but I remember we could do a little better there
18:32 are you aware that there are also command line scripts for the staged marc import?
18:32 and a bulkmarcimport tool
18:32 KevinFurst[m] One thing I noticed right away is that my file doesn't have a b for current library so I went in and deselected it as mandatory, leaving a home branch as both mandatory and made sure it matched correct values. Is b required no matter what?
18:33 cait yes
18:33 definitely
18:33 KevinFurst[m] No I wasn't aware of that.
18:33 cait make it mandatory again and set it in all your items
18:33 a and b can match, that#s no issue
18:33 KevinFurst[m] ok. Gonna try that.
18:33 cait so maybe you can just copy/shift with MARCEdit
18:33 koha doesn't like items with missing a b and y
18:33 so even if you got them in, they would give you some trouble
18:34 RudyHinojosa The default value "itemtypes" that doesn't exist in the table authorised_values is the culprit. The framework 952y points to this value called "itemtypes". I can't find it's source, so i can only assume it's pointing to some stored procedure to retrieve itemtypes. I had to create a new authorised value of "itemtype2" and recreate the itemtypes in here and reconfigure my custom framework 952y to point to this new authorised value.
18:34 works fine now.
18:35 cait not uqite
18:37 itemtypes are a pseudo-av
18:37 they are set not in authorised values but in administration > itemtypes
18:37 don't change the frameworks there, defualt is correct
18:37 and please undo that change
18:37 it is also set to give you tons of trouble
18:37 wahanui okay, cait.
18:37 cait same for a and b - pseudo-AV is set to branches, not found as an AV category but in administration > libraries
18:37 for both of you.. please be super careful about changing frameworks especially in the beginning
18:41 RudyHinojosa itemtypes is putting over 100 duplicate MAIN COLLECTION entries into the dropdown and the html source code proves that. My itemtypes are only 15 unique entries. So pseudo-av or not, it doesn't work.
18:42 cait i believe your problem might be more realted to the change
18:42 honestly, don't do that, if it's duplicateing, we need to fix that otherwise
18:42 changing the mapping will break things
18:44 RudyHinojosa it shouldn't break things. It's allowing me to choose from a valid authorised value. I'm not doubting you, but just stating it shouldn't break things. I didn't alter the default framework. I've been using a custom framework for sometime now with no problems.
18:45 cait itemtype in items is used for all kinds of stuff
18:45 and it expects valid itemtype codes
18:45 and might look at the mapping to figure out things
18:45 I can't tell you which side effects exactly, but I expect some or many in circulation
18:45 RudyHinojosa oh, then, i'm not worried. I pretty much duplicated my original administration->item types
18:46 cait well you didn#t change hte db field... but it's really just a band aid if that works
18:46 it would be better to get to the source of the duplicates
18:46 RudyHinojosa i agree, it's definitely a tail wagging the dog situation here.
18:47 I'm a seasoned 35 year developer and DBA. So i'm comfortable peeking anywhere anyone has a suggestion.
18:47 cait the code for building the item form is not super nice
18:48 well say it's a bit complex
18:48 RudyHinojosa additem.pl?
18:48 cait yeah, but it's a method in C4
18:49 the older part, I was just trying to spot it for you
18:49 RudyHinojosa ok.
18:50 cait Template file: https://git.koha-community.org[…]oguing/additem.tt
18:50 .pl: https://git.koha-community.org[…]oguing/additem.pl
18:53 i might have been thinking of the code that builds the item forms in serials/acq
18:53 it looks like the cod emight be all in additem.pl
18:54 RudyHinojosa <select name="item_group" id="item-group-add-or-create-form-select">
18:54 <optgroup label="Use existing item group">
18:54 [% FOREACH ig IN item_groups %]
18:54 <option value="[% ig.id | html %]">[% ig.description | html %]</option>
18:54 [% END %]
18:54 </optgroup>
18:54 <optgroup label="Other options">
18:54 <option id="item-group-add-or-create-form-no-add" value="">Do not add to item group</option>
18:54 <option value="create">Create new item group</option>
18:54 cait but htat's item groups
18:54 RudyHinojosa </optgroup>
18:54 cait not itemtypes
18:54 RudyHinojosa </select>
18:54 this is where the dropdown derives it's options.
18:54 cait nope
18:54 that#s a drop down below hte form
18:56 it appears below the item form
18:56 RudyHinojosa oh yeah. my bad.
19:05 cait it's probably in here:  [% PROCESS subfields_for_item subfields => subfields %]
19:07 RudyHinojosa in the additem.tt?
19:08 or pl
19:08 cait tempate code is here: https://git.koha-community.org[…]l_helpers.inc#L85
19:09 the additem.tt has the PROCESS line and the link above the template code for the form
19:13 RudyHinojosa they both look correct. I did see a JS reference to acquisitions, which is just in beta right now.
19:13 cait beta?
19:13 wahanui i guess beta is OK
19:13 RudyHinojosa but I think this issue has been happening since inception, just never went deep dive on the issue.
19:14 yeah, we have a test fund, test budget, edifact enabled, but not much further after that. test vendor. but no orders or baskets created. It was for generating a training video.
19:15 cait ah
19:19 RudyHinojosa not seeing anything special in procedures or functions in db level.
19:19 i am using mariadb, just to mention.
19:22 cait yeah, that's what most of us do
19:23 KevinFurst[m] cait: I rechecked with MARC validator in MARCedit again to be sure. There were no erroneous records to remove. I added both b and y subfields with data that matched the codes in the authorized values for each. Uploaded and results came up with 23k records and 19k items which is right. Went to import and it immediately failed again. Here is an example of a 952 I'm using =952  \\$p3222200006331O$aPRBE$g5.00USD$hFIC Bya$yBOOKS$bPRBE
19:25 cait hm
19:25 ah yes
19:25 $g
19:25 that is price eh?
19:25 KevinFurst[m] right
19:25 cait it's a datatype of decimal
19:25 KevinFurst[m] ahh
19:25 cait you can't use the USD there
19:25 KevinFurst[m] yep. will change now
19:26 cait your $h looks like it maybe is more a $o
19:26 KevinFurst[m] is location and call number. So h or o?
19:26 cait $o is the callnumber
19:27 $h is enumchron - used by serials to put the issue information in
19:27 or for volumes
19:27 KevinFurst[m] got it.
19:27 cait that would not prevent it from loading, but it would make sense to switch it
19:27 and you are not using DDC it looks like?
19:27 is that one of the other big classifications?
19:29 KevinFurst[m] FIC is just section + Auth name. Non fic is classified via DDC here
19:30 cait ah ok
19:30 I was wondering because of the $2 i told you about
19:31 that makes Koha create a sortable form of the callnumber
19:31 your FIC might work best with $2z = generic and the others with $2ddc
19:33 KevinFurst[m] ok good to know. I'm making changes now and will try another stage and import.
19:35 khall joined #koha
20:21 KevinFurst[m] Still failed. An example of what 952 looks like now
20:21 =952  \$p34517200027251$aPRBE$g8.99$yBOOKS$bPRBE$o597.3 Pop pb
20:21 I took out the USD and moved the h to o
20:28 jalway joined #koha
20:30 jalway We have two issues: #1 Trouble with Importing Patrons #2 Incorrect Koha to MARC mappings. Anyone around who wouldn't mind helping me get things figured out?
20:31 The #2 is more of a would I break anything, if I just changed the mapping to the correct form . . .
20:51 cait KevinFurst[m]: odd :( maybe try with a smaller sample to get format right first?
20:52 you could check the logs to see if something is there
20:52 it looks fine now to me
20:52 try without the item... try with it, try some combinations to limit it down a bit more
20:53 it's really late here so I am about to leave, but more people around in a few hours maybe
20:53 KevinFurst[m] Thanks for your help today
21:42 fridolin joined #koha
22:12 rudyh joined #koha
22:12 RudyHinojosa joined #koha

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

koha1