Time Nick Message 21:44 cait rangi++ 16:40 oleonard caroline++ 16:31 caroline it would allow to have more than one restricted page too 16:31 oleonard That would be cool 16:30 caroline I guess it could be moved to pages with a flag "logged in users only" or something like that, now that we have pages 16:30 caroline yes 16:29 oleonard So it's just a single page which you have to customize yourself and can be used to provide links to a logged-in user. 16:27 caroline Not specifically about your question, but this is how to add resources to the restricted page and add the restricted page link somewhere... https://inlibro.com/knowledge-base/ajouter-une-ressource-numerique/ I notice it must be updated... ugh, it never ends! 16:26 caroline oleonard, I think that is a page that is accessible only when you are logged in. It's not accessible by default, users have to add the link somewhere 16:05 oleonard Under what circumstances is opac-restrictedpage.pl shown to the OPAC user? 15:40 paulderscheid[m] Especially the tests 😜 15:39 ashimema 🙂 15:39 paulderscheid[m] Currently working on an api for a 3rd party integration and I just have to say: feels great to stand on the shoulders of giants :D So much work already done! community++ 15:35 Shane-NP[m] No one saw me using out dated documentation....no one 15:34 Shane-NP[m] crawls under a rock 15:34 Shane-NP[m] Well that explains it 15:33 Shane-NP[m] https://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages#Configuring_Apache if anyone is wondering, it says beyond scope...why I ask 15:32 Shane-NP[m] However, unless I missed it, I see nothing about the 000-default.conf, or is that a none-issue with a domain setup? I know I removed it from 18 as well, as it is not in sites-enabled on that old server. 15:31 Shane-NP[m] hmm...should I modify the document to have a note to remove the symlink to 000-default.conf in sites-enabled? The Appendix covers the ports changes...kinda...saying 8080 and 8081...while I left OPAC alone and changed Intra to 8080 15:17 reiveune bye 15:12 Shane-NP[m] hmm...I didn't setup a domain (since 18 is running and lives on the domain), when I use the IP I get apache default page, any URL trick I can do or should I just remove Apache default site from sites-enabled 15:07 Shane-NP[m] Guessing I should keep the instance names the same 15:03 Shane-NP[m] mmmm...native SSH in windows...how I will not miss you putty...but you are a great tool I will forever keep around 14:53 Shane-NP[m] cait: so ignore the drop/create/quit then how do I use the import carrot command, it will create it then right? IE if I do NEWDB < OLD_DB.sql NEWDB will be created as it imports? 14:48 cait ah - no problem, just checking in... and yes, finish installation and then do the migrate - not the line about dropping the db the new instance will have created. it has the new structure, so you need it gone before loading your old one. 14:43 Shane-NP[m] Sorry I have been on a support chat about a Clever integration and wanting our SIS to do a mid-day sync to fix student emails I changed...I haven't even continued with Koha 14:39 cait Shane-NP[m]: doing ok? 14:28 aw-bib[m] thx :) 14:28 cait oleonard: oh good point! I think I saw he was giving a presentation 14:28 cait there coudl be statistics/action_log entries - but nothing will explode if those are still there 14:27 oleonard cait: Is he at Koha-US conference? 14:27 cait aw-bib[m]: no I think you are ok with those 14:27 cait hm no kidclamp? 14:27 aw-bib[m] cait: btw cleaning the issues/old_issues is effectively dropping all loan events, right? or do I have to be careful with some other tables that are connected? 14:27 cait oleonard++ Joubu++ 14:26 Joubu Great, thanks a lot! Your feedback has been very helpful. 14:25 oleonard Joubu: I was going to take one more look to see if I could think of anything else I missed testing, and I can do that today 14:24 cait with the API there might be more options 14:24 huginn 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33568 enhancement, P5 - low, ---, jonathan.druart+koha, Needs Signoff , Use the REST API to display items on the biblio detail view 14:24 Joubu oleonard: do you think you are ready to add your signoff to bug 33568? 14:24 cait I am not sure what most people do, we usually migrate only the patrons with the koha tools, the rest is scripts loading the data into the DB 14:19 aw-bib[m] I was just wondering if there some default path as it seems to me like a pretty common question to migrate this stuff. and the koc-path looked a bit like what I did when I migrated aleph to our current system. (just that aleph had some amnesia and lost "a few" transactions in it's history.) 14:13 cait but yes 14:12 cait I was not feeling like it 14:12 cait that sounds lke I made sense :D 14:11 aw-bib[m] ok, I'll check the koc, and if I don't end up with something working I'll dive into isusses and old_issues. and I understand that the id in issues gets transfered to old_issues so I'll have to make sure they don't clash. 14:09 cait .koc might work for your purpose, you could give it a try with a simple file and see the outcome 14:09 cait but I ususally only spec the migrations, I don't have to write the scripts heh 14:08 cait i believe that's probably the 'hardest' bit 14:08 cait you can simply move the PK counter with a SQL statement - so migrate the old ones, set the cunter in issues to the max(issue_id) from old_issues 14:08 cait so a key existing in issues, should not exist in old_issues 14:08 cait when an issue is returned it's moved from issues to old_issues 14:08 cait the only thing to look out for is that your PK don't run into each other 14:07 Shane-NP[m] Just so I don't screw myself, finish the full install and then do the migrate article correct? So I am using: https://wiki.koha-community.org/wiki/Koha_on_Debian, I am just done the MariaDB 14:07 cait old_issues is like issues - it's not a bad table 14:07 aw-bib[m] for the sql path: do you have some pointer where I could start out? 14:07 cait i think it will, but it might end u being a 'today's' transaction 14:07 aw-bib[m] I can have a look at that. 14:07 aw-bib[m] ah, so you think if I replay a checkin from 2 years ago it will not accept it. 14:06 cait but easy to test 14:06 cait you coudl try it, I might be wrong 14:06 cait so you can't backdate 14:06 cait when Koha proceses the files, it will do the checkouts when you process (I think) 14:06 cait like the checkout/checkin dastes 14:05 aw-bib[m] tdates being what? 14:05 Shane-NP[m] Short story long, I tried to move to another state...failed, and moved back, and then the position opened back up, and now I know why! 14:05 cait so if you need for stats... I'd try and add entries to old_issues and statistics using SQL instead 14:04 aw-bib[m] cait: right that's why I thought I could missuse it to replay the co/ci-events. 14:04 cait you can't use them for historic so well (you'd need to issue and return...) and you can't set the tdates things happen 14:04 cait aw-bib[m]: koc is for offline circulation 14:04 Shane-NP[m] not sure if that is a choice on 23...just being funny...because I have about 100 broken / unfinish things left in the wake of the person I hired to replace me...who was let go...and they asked for me to comes back 14:04 cait you can still look at Elastic later when you are feeling like it 14:03 cait Shane-NP[m]: I'd say so 14:03 aw-bib[m] I am currently trying to find a way to migrate movement data (checkout/checkin so the stats are right in the end). now I stumbled upon koc-files that look promising to accomplish that. am I here on the right track? 14:02 Shane-NP[m] 18 is probably using Zebra 14:02 cait being a little dramatic? ;) 14:02 Shane-NP[m] terminal is just blinking at me...judging me...making me question my life choices...wanting to me to make a decision...but I am trapped in an infinite time loop of wanting someone else to do it all for me 14:01 cait a normal intallation will usually give you Zebra 14:01 cait I think you need to install Elasticsearch separately if you want to tuse it, because it could also live on another server/be a cluster somewhere else 14:01 Shane-NP[m] uhh....I haven't built it all the way yet, I just installed MariaDB on the new Ubuntu VM 14:00 cait system preference SearchEngine can tell oyu 14:00 cait if you don't know it's probably zebra and correct :D 14:00 cait are you using zebra or elastic? 14:00 Shane-NP[m] I know Library will be my instance name 14:00 Shane-NP[m] This still valid?: sudo koha-rebuild-zebra -v -f library 13:58 cait I hope :) know... is hard 13:57 caroline you know I don't mean it in a negative way 13:57 caroline youu always have the knowledge people need 13:57 caroline nah! 13:56 cait caroline: that makes me feel like a terrible know-it-all 13:56 caroline cait++ #once again proves she has all the answers ;) 13:55 cait if you didn't change indexing etc. it should have all you need 13:55 Shane-NP[m] Yeah that sounds perfect if the DB hold most of the settings 13:55 cait and the koha ones look correct to me 13:55 cait the mysql commands don't really change that much 13:54 Shane-NP[m] Thanks..I was reading that but cringed at the dat 13:54 cait Shane-NP[m]: this is old, but accurate: http://kohageek.blogspot.com/2015/08/move-old-koha-database-to-new.html 13:53 cait if you really want to export your records, I'd use the tools in Koha to get them out in MARC with the items and than reimport 13:53 cait if you try to migrate with SQL you'll run into problems more likely 13:53 cait so you can have a brand new server and all your data 13:52 cait that#s all you need to do realyl and Koha takes care of the rest 13:52 cait don't want to interrupt... but maybe it woudl be really easier to install fresh, but add your existing database 13:40 Shane-NP[m] omg was just typing in the Windows search bar...my brain is toast. I almost typed 18.05.11, since you asked the version and it has both #s 13:37 Shane-NP[m] Well that was little dyslexia 18.11.05 13:36 caroline Shane-NP[m], do you have 18.05 or 18.11? the circulation_rules table was introduced in 18.11 it seems 13:35 aw-bib[m] Shane-NP: I think no config files all in the database, but you can create yml-files that define those and load it from there. 13:34 caroline I know the circulation rules table changed drastically, I don't remember which version 13:33 Shane-NP[m] are the library rules in a conf file I can import so I am not recreating all the patron types, check out rules, or am I just better off trying a fill mygration 13:30 Shane-NP[m] I just want to try and export the all the IT asset records I created. I can run a few lines of SQL....wish I had my skills back when I was an aspiring web-developer I can spit out basic SQL in my sleep with left, inner, outter joins...oh 20 years...ago..so far away 13:28 Shane-NP[m] I think I want to start fresh, and then I can mirror the other library on our server 13:27 caroline But if you know your way around databases, updatedatabase is a good option I think 13:27 caroline yeah, if you think it's too much, you can definitely create a new instance and simply migrate all the data into it. That's probably what I would do because as previously mentioned i am not a developer lol 13:27 Shane-NP[m] All the google results are from '15-18 so if there is a current guide moving server A to B that would be awesome. 13:25 caroline rofl 13:25 Shane-NP[m] IT person is a stretch these day...more road kill being run over by semi-trucks :P 13:25 oleonard Now we know why you don't call yourself a developer ;) 13:24 caroline lol!! I'm not that bad! XD 13:24 oleonard caroline: At first I thought you asked "Are you a dev or a person?" XD 13:24 caroline are you a dev or an it person? 13:23 caroline I mean, you could do a data migration as if you were moving from another product, but I'm pretty sure updatedatabase will take care of most things 13:23 Shane-NP[m] Plus 4 jobs in between my brain is worse then scrambled eggs haha 13:22 Shane-NP[m] been what 5 years since I touch this...18 to 23 :P I don't even remember what the instances are :) let alone what/how to move this stuff...im pulling a Dory here...just keep swimming...just keep swimming 13:21 caroline doesn't the updatedatabase script usually take care of schema schanges? 13:20 Shane-NP[m] Hmm...thinking the DB schema has likely changes a lot wonder if I can just migrate the materials I have an forget the history...just keep items records? 13:05 paulderscheid[m] Thanks oleonard, I havn't. 12:50 Shane-NP[m] Guessing I need /koha/koha-sites.conf from old server and the backup folder contents? 12:48 Shane-NP[m] I am doing a fresh install of 23, just got to the MariaDB section 12:47 huginn 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22436 enhancement, P5 - low, ---, koha-bugs, NEW , add move or copy control field from or to subfield in MARC modification templates 12:47 cait bug 22436 ? 12:47 Shane-NP[m] Can I backup an 18 server and move to 23? 12:46 cait like a filed one 12:46 cait I thin it#s a standing bug 12:37 oleonard Damned if I do and damned if I don't: https://snipboard.io/wzPHeu.jpg 12:36 tcohen[m] do you need to use @ for the subfield? 12:33 oleonard Why can't we copy the contents of a control field to a non-control field in a MARC modification template? 12:32 tcohen[m] thanks, if I find somethign I'll post somewhere 12:31 Joubu no idea right now, but drop me a note and I will have a look later 12:30 tcohen[m] I was having fun with cypress until I hit this heh 12:28 tcohen[m] the 3 12:28 Joubu do you want the 3 entries or just one? 12:28 tcohen[m] patron 12:28 tcohen[m] I noticed I was missing the x-koha-embed 12:28 Joubu sorry, I thought it was something else 12:28 tcohen[m] indeed 12:28 Joubu ok, so the 2 queries are not the same 12:27 tcohen[m] not returned by the API 12:27 tcohen[m] and now the record sources without a patron linked are 12:27 tcohen[m] and tried deleting the linked patron 12:27 tcohen[m] No, I'm trying to list record sources 12:26 Joubu you are adding a filtering, right? 12:26 tcohen[m] ? 12:26 Joubu you need a dedicated route 12:26 Joubu we talked about that already 12:24 tcohen[m] and not a Vue one 12:24 tcohen[m] this is a bigger problem 12:23 tcohen[m] if I ask to embed the (non existent patrons) then it returns only one row 12:22 tcohen[m] oh 12:21 ashimema does it now come from there 12:21 ashimema exactly 12:21 ashimema it's bugged me a few times too.. places where the whole point of the table is to never ever show certain things.. yet we still highlight it's a filtered set 12:21 tcohen[m] yes, the X-Total-Count 12:20 ashimema or something like that 12:20 ashimema as in, the response header returns a full count of all rows of the table.. no matter what? 12:20 ashimema is it not in the headers 12:20 ashimema haha 12:20 tcohen[m] haha 12:20 tcohen[m] I'm new to Vue, and this got my nerves high 12:19 * tcohen[m] uploaded an image: (252KiB) < https://matrix.org/_matrix/media/v3/download/matrix.org/mwDFDhPMZXOhvPZmmNxvvQGV/image.png > 12:19 tcohen[m] The exact same request in postman returns the 3 rows 12:19 tcohen[m] 'filtered from 3 total entries' 12:19 * tcohen[m] uploaded an image: (41KiB) < https://matrix.org/_matrix/media/v3/download/matrix.org/nayCVOMoZGYAITdhbjMXVKAR/image.png > 12:18 tcohen[m] Joubu, Pedro Amorim is there a trick on hte Kohatable component preventing display of some rows 12:11 oleonard That sounds similar 12:11 huginn 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8628 new feature, P5 - low, ---, aleisha, Failed QA , Add digital signs to the OPAC 12:11 oleonard paulderscheid[m]: Have you seen Bug 8628? 12:09 huginn Joubu: The operation succeeded. 12:09 Joubu @later tell PedroAmorim[m] please have a look at 34842 11:51 Joubu all the awesome stuffs are on the roadmap ;) 11:47 ashimema I should look at that again 11:47 huginn 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31383 enhancement, P5 - low, ---, jonathan.druart+koha, Signed Off , Additional contents: We need a parent and child table 11:47 * ashimema had forgotten about bug 31383 11:44 paulderscheid[m] Thanks for the heads up joubu, wasn't going to jump on it immediately anyway. 11:39 huginn 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31383 enhancement, P5 - low, ---, jonathan.druart+koha, Signed Off , Additional contents: We need a parent and child table 11:39 Joubu paulderscheid[m]: I don't, but keep in mind that there is a redesign of the DB structure going on: bug 31383 11:35 tcohen[m] hola #koha o/ 11:28 paulderscheid[m] News meaning Koha-News 11:28 paulderscheid[m] Anyone ever worked on an endpoint for news? 11:28 paulderscheid[m] Just in: Interesting customer request: Accessing news via URL (which could be realised via the API) for "Poster" Screens in the Lobby. 11:04 oleonard Which is it?? https://snipboard.io/wzPHeu.jpg 10:46 ashimema lol 10:45 oleonard [off] MarcEdit is powerful and indispensable but the interface is so so so terrible 10:32 magnuse kia ora oleonard 10:19 oleonard Hi all 09:47 cait but I would not make it a pref, maybe a setting on the circulation conditions somehow 09:46 cait I feel like it is possible... but I had not the right idea yet maybe? 09:43 krimsonkharne[m] cait++ 09:43 krimsonkharne[m] we'll talk more about it LMSCloud-internally.. might be worth thinking about a new syspref "Allow / Disallow checkouts if the item homebranch is different from the logged in branch" 09:42 krimsonkharne[m] yeah 09:38 cait using itemtypes is probably the most transparent option too 09:38 cait circulation conditions can be hard 09:38 cait hm or not 09:37 cait I thin it would probably work without that if you had CircControl to: library the patron is from 09:36 cait depending on how you select your rules 09:36 cait branch specific patron categories would probabl work too 09:33 krimsonkharne[m] yeah, we solved it with different, "homebranch-specific" item types in the end 09:28 cait or by using differnt itemtypes, but that's probably a last resort 09:28 cait maybe with CircControl... and circulation conditions 09:27 cait not a pref 08:47 krimsonkharne[m] for holds, it's clear.. but for checkouts I'm not sure 08:47 krimsonkharne[m] anybody know if there's a syspref for "only allow checkouts from the homebranch of the item"? 08:47 krimsonkharne[m] morning #koha 08:12 ashimema looks like jajm took it over 08:10 ashimema having said that.. as the send stuff pro-actively updates to address anyway I think.. it may well not have worked that way for a while anyway 08:10 ashimema I kinda liked that they set at the last minute so a retry of sending may pick up new addresses and things 08:09 ashimema I'm also not entirely sure about the move from setting addresses at the last minute to always setting them at enqueue 08:09 ashimema it probably massively predates the move to Email::Stuffer and friends 08:07 ashimema pass 07:53 Joubu ashimema: I really cannot remember. Didn't we have a problem in previous versions with that? Was it possible to have several email addresses in the to/cc fields? 07:49 Joubu it was working perfectly and was used in production by the customer 07:49 ashimema Yup 07:48 Joubu this should have been pushed years ago, really 07:48 ashimema OK.. I'll try to dig out whoever was rebasing then 07:48 ashimema Indeed 07:48 ashimema Lol 07:48 Joubu written 9 years ago... 07:48 Joubu I am no longer involved in this one ;) 07:48 ashimema Maybe it wasn't yours 07:47 Joubu Date: Thu, 21 Aug 2014 13:15:36 +0200 07:47 Joubu From: Jonathan Druart <jonathan.druart@biblibre.com> 07:47 ashimema Yes 07:47 ashimema Bug 12802 07:47 huginn 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12802 enhancement, P5 - low, ---, julian.maurice, Patch doesn't apply , Send notices using several email addresses 07:47 Joubu bug 12802? 07:47 ashimema The guarantee copy but takes that approach instead. We send an array of addresses to the cc header and email::sender handles the rest 07:46 Joubu can you remind me the bug/context of that? 07:46 ashimema But with multiple to addresses? 07:46 ashimema Why bit queue the notice once 07:46 ashimema You enqueue a copy of the notice for each address.. filling the message queue 07:45 Joubu sorry I don't understand the question :D 07:43 ashimema Practically running and phone typing 07:43 ashimema School run 07:42 Joubu Do you have a cat walking on your keyboard? 07:42 ashimema I wondered why the choice to multi enqueue as apposed 5i just send an array of addresses 8n the To? 07:41 ashimema Witt the multi-address email stuff 07:40 Joubu yes 07:40 ashimema Joubu about? 07:39 magnuse \o 07:37 MatthewBlenkinsop[m] o/ 06:37 ashimema Lol 06:34 dcook allo reiveune 06:34 dcook #hotproblems 06:33 dcook "I always find I'm in hot demand". I may have laughed out loud reading that hehe 06:32 reiveune hello 06:19 ashimema I always find I'm in hot demand at hackfest.. which is lovely and I want to help everyone with everything... But I so often don't actually achieve many, if any, of my goals 06:18 ashimema Maybe at the next hackfest I try to push for a more focused small room of Devs with a focused goal 06:18 ashimema Lol 06:15 * magnuse hands out lots of tuits 06:09 magnuse \o/ 06:05 dcook I feel the same way though. It's easy to see the flaws when you know where to look. 06:05 dcook Familiarity breeds contempt hehe 06:04 ashimema Kohas great and marches forward.. but I feel all the pain points really keenly at the moment. Maybe I just know them all too well.. 06:03 dcook Yeah, inertia ends up winning 06:02 ashimema Noone has time to concentrate on polishing 06:02 dcook Pretty much 06:02 ashimema It's all blocked by time 06:02 dcook Absolutely. It is tough :( 06:01 ashimema Pedro loves WordPress 06:01 ashimema Yeah, we should let some of those best of breed systems inspire us more 06:00 ashimema The editor does support all that.. but because we mix interfaces, news, pages and blocks all in one big mess, it's very difficult to actually apply the right stuff at the right time 06:00 dcook Of course, that's the whole point of Wordpress, but they go in some good directions for a few things 06:00 dcook Ahh yes yes. I gotcha. I was thinking about that a lot lately, especially compared to the Wordpress CMS functionality 05:59 ashimema We could do so much better with TinyMCE. Our WYSIWYG isn't at all WYG.. haha.. because we don't apply our stylesheets to it and we don't expose the Koha block components and things 05:58 dcook Ah yes relatable 05:58 ashimema Haha 05:58 ashimema I've submitted a bunch of tickets, but as soon as I tried doing any work on any of them I quickly found myself deeply tangled in the mess of mingled code paths 05:57 ashimema The additional content stuff trying to be too many things in my opinion. I'd like to see it split up more... Or at least the different concerns made much clearer in the code 05:57 dcook I like you guys but not that much :p 05:56 dcook Well I do want to be able to sleep and go to the bathroom... 05:56 dcook Yass so much 05:56 ashimema Like, 5 or 6 core Devs with some really clear goals locked in a room for a week 05:56 ashimema I'd like to see a second sort of hackfest. I love the existing one, but I'd like to see a more technical, smaller group focused event too 05:56 dcook I'd be curious to hear more about that 05:55 ashimema The additional content stuff is getting me down a bit honestly. There are so many little issues with that area of code.. the interest in polishing it just went away and the followups never came 05:55 dcook shindig* 05:55 dcook Tomas and I need to come to Europe and have a KohaSec shingdig 05:54 dcook Agreed 05:54 ashimema The big csrf one to try and catch all is interesting. I really don't think it shouldn't be too painful if we could actually get a group of us to concentrate on it for a few days together... But that just doesn't ever happen 05:53 dcook I appreciated your comment on the editor one 05:53 ashimema I tried to work through a few this week to keep them moving 05:53 dcook Trying <3 05:53 ashimema You've done a great job there mate 05:52 dcook As the author of every security patch in the next security release haha 05:52 dcook Agreed 05:52 ashimema It's a real hidden work too 05:52 dcook <3 ^ 05:52 ashimema Much like the security bugs of late.. we should really be prioritising them as a community but I'm struggling to have the motivation when it feels like it's such a small few who care about it 05:52 dcook Actually Jonathan has pointed out how the middleware thing is already a problem with the Mojolicious API 05:51 ashimema I've dabbled in that area over the years but never had time to really focus on it 05:51 dcook If only I could clone myself. What could go wrong... 05:51 dcook haha too true 05:51 ashimema There's just too many interesting projects to look at haha 05:50 ashimema We have a bunch of plack middlewares though that would need consideration. It's not an area I've deeply delved into so I don't know which of those would need mojo alternatives 05:50 dcook I've done a lot of work to move us in that direction, but I don't think it's been on anyone's radar 05:50 ashimema Hypnotoad 05:50 dcook ^ 05:49 ashimema I'd love to see us go native mojo 05:48 ashimema Oh, kivilahtio, long time no see 05:47 ashimema Morning 03:20 TripathiDP[m] kivilahtio: Thanks a lot. I will see the mapping. It is happening with all the records while issuing the book to the users. 03:18 kivilahtio TripathiDP[m]: because the issueing/holding is done via the Item-record (koha.items) and the searches are done by the indexes MARC21 records from the koha.biblio and koha.biblio_metadata tables. 03:16 TripathiDP[m] If there was any error with record, then why is it issuing? It shows the error but when check the report, it shows that book has been issued to the user. 03:16 TripathiDP[m] Thanks for quick response. 03:15 kivilahtio Fiza: Some of those fields are not visible in the intranet typical cataloguing views. 03:14 kivilahtio Fiza: If you know the biblionumber, you can check the Koha database biblio_metadata-table for how the MARC21 XML looks like. 03:13 kivilahtio correctly populated. 03:13 kivilahtio Fiza: If I understood correctly, you have this problem with only one record? Then it might be easier to just pull the record again from an external source using Z39.50/SRU. There is probably something wrong with the frameworkcode, or some of the KohaToMARC-mapping fields within the MARC21 record, such as the field 999$b (if I remmeber correctly) for biblionumber or 942$c for default itemtype. You might want to check the record if the Koha-fields are 03:04 * TripathiDP[m] uploaded an image: (94KiB) < https://matrix.org/_matrix/media/v3/download/matrix.org/ySJTtyQOTWYoJgEXCEbIjpwR/error500.jpg > 03:04 TripathiDP[m] Dear All,... (full message at <https://matrix.org/_matrix/media/v3/download/matrix.org/hXOkKLjRQflxKMRxyjqYgbIU>) 02:45 Fiza this what i found in opac-error.log AH01215: Use of uninitialized value $branch_limit in concatenation (.) or string at /usr/share/koha/lib/C4/Koha.pm line 493.: /usr/share/koha/opac/cgi-bin/opac/opac-search.pl, referer: https://../cgi-bin/koha/opac-search.pl?idx=&q=The+malayan+law+journal&branch_group_limit=&weight_search=1 02:40 Fiza These are new records that have been migrated from the symphony workflow to KOHA from direct database, table-to-table migration. all data transferred before is no problem, only this record. I and the team installed Koha version: 21.05.01.003. and we maintain the application including the server and database. 02:11 kivilahtio Who is maintaining Koha for you? 02:10 kivilahtio How did you install Koha? 02:10 kivilahtio Have the searches worked previously? 02:10 kivilahtio Fiza: There are so many reasons why the searches can go wrong. 02:09 kivilahtio Also you can tweak what is logged with the /etc/koha/sites/koha-name/log4perl.conf to maybe get more help. But probably not in this case. 02:09 kivilahtio I have no idea, there are so many. They often give more help. 02:06 Fiza may i know which logs file? 02:06 kivilahtio Fiza: can you take a look at Koha's server-side logs? 02:03 Fiza hello, im fiza, i have problem with my bib records, records has been added and can search in cataloging module, but it is not searchable in OPAC/catalog. the error promted is Error: Can't call method "raw" on an undefined value at /usr/share/koha/lib/C4/Search.pm line 763.