Time Nick Message 22:44 gveranis thanks again 22:43 gveranis I read it but just seems not to work as expected 22:39 gveranis archive the www 22:39 gveranis ;) 22:39 gveranis no no 22:39 gveranis https://web.archive.org/web/20130808102525/http://bywatersolutions.com/2013/07/23/match-points-in-koha/ 22:38 cait bye all 22:37 cait sadly also down 22:37 cait https://bywatersolutions.com/2013/07/23/match-points-in-koha/ 22:37 cait gveranis: also might have been this 22:37 gveranis thanks for your support 22:37 gveranis good night 22:36 cait good night #koha 22:34 cait hm? 22:33 gveranis *below sorry 22:33 gveranis above the middle of the page has an explanation 22:32 gveranis https://bywatersolutions.com/tag/administration-tutorial/feed/index.xml 22:31 cait https://bywatersolutions.com/2012/10/22/basic-overview-of-match-points/2012-10-22_1239/ 22:31 cait hm 22:31 cait https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=3&cad=rja&uact=8&ved=0ahUKEwiAy62IsPLbAhWJb1AKHbm3BeYQFgg3MAI&url=http%3A%2F%2Fbywatersolutions.com%2F2012%2F10%2F22%2Fbasic-overview-of-match-points%2F2012-10-22_1239%2F&usg=AOvVaw0_Txj9N7JVsSErftdVsXRa 22:30 gveranis could you please send me the link ? maybe I can find it on archivewww 22:30 cait wher you need to check for a certain position 22:30 cait i would only fill that for control fields 22:29 gveranis offset and length for match check should be filled ? 22:28 cait i was looking for a blog post from bywater on it, but he link is broken 22:27 gveranis ok 22:27 cait let me look up something 22:27 cait sorry, about to fall asleep 22:23 gveranis I try only to use match check but without success also 22:22 gveranis Match Check , incoming 001 and target ( database ) record check field 942$x 22:21 gveranis but with Matchpoint i have 100% success , with and match check I have 0% success 22:21 gveranis I have set as match point the 001 as you told me and I try to use Match checks also. I want to check if 001 is the same as 942$x for the records I want to update I know is the same 22:19 gveranis cait something to ask again for matching rules. 22:07 cait gveranis++ 22:07 tcohen if someone had a budget to improve Koha's API faster… :-D 22:03 * MilkManzJourDaddy goes "AFK". 22:03 gveranis ok Vufind is only for OPAC 22:03 MilkManzJourDaddy Thanks. 22:02 MilkManzJourDaddy Well, I'll have a look at Vufind, and try to get them on an app' on F-Droid for patrons accessing the catalogue. I hate that Sierra uses the GET method!!! 22:02 gveranis and each solution depends on budget 22:01 gveranis 3. Koha - API - Sierra 22:01 gveranis 2. Koha - Vufind - Sierra - Encore 22:01 gveranis The options are 1. Koha - ILL - Sierra 22:01 gveranis you need to study them 22:01 gveranis it depends how you connect Koha , policies , Sierra 22:00 MilkManzJourDaddy gveranis: Ah, so Koha could work if the policies matched? But member libraries have their own rules, i.e. length of loan and number of renewals. 21:58 MilkManzJourDaddy I am a traveller, but try to leave a place in the same, or better state than when I arrived, including libraries. Proprietary software is unacceptable. 21:57 gveranis no I mean rules for loan , rules for patron, rules for access on collections etc.. policy is how a library is working under this union 21:55 MilkManzJourDaddy Well, surely there is restricted acccess, with passcodes" if that is what you mean by "policies". 21:54 cait where are you from MilkManzJourDaddy? 21:54 gveranis maybe 21:54 MilkManzJourDaddy Language barriers, perhaps. 21:53 * MilkManzJourDaddy is too. 21:53 gveranis with the union .. 21:53 gveranis Koha also has an API , you can retrieve and update etc records, patrons.. and other things from API. but again read policies.. under a union catalogue policies is the main key for all libraries to be engaged 21:51 gveranis the API is really good 21:51 gveranis *it 21:51 gveranis you can do iy 21:51 gveranis if you have a budget ;) 21:51 gveranis but you need development there for a bridge 21:51 gveranis Also Sierra has an API 21:50 MilkManzJourDaddy Ah. So they would have to detatch from the library system/union with patrons and materials, only communicating as ILL for loans. Not good. Thanks. 21:50 gveranis for the price.. 21:50 gveranis Encore can harvest data by OAI-PMH for other sources.. Koha has OAI-PMH for free.. Encore not be carefull ;) 21:49 gveranis but you should check policies 21:49 gveranis for loan and maybe patrons 21:49 gveranis so Koha and Sierra can communicate 21:48 gveranis Koha has ILL subsystem, Sierra has it also 21:48 gveranis not for loans.. patrons.. you must be informed for library policies 21:48 gveranis yes but only for the records 21:47 MilkManzJourDaddy > They can move to Koha as seperate ILS and provide records to Enocre 21:47 gveranis impossible 21:47 MilkManzJourDaddy So, how to use Koha as a ILS with a central database managed by Sierra? 21:46 gveranis Sierra use one postgresql database and each library has an instance of it as a scope.. 21:46 gveranis yes it is not ILS 21:46 cait yep 21:46 gveranis Vufind only for the OPAC 21:46 cait vufind is not an ILS 21:46 MilkManzJourDaddy This is what I mean. 21:45 gveranis *Encore 21:45 gveranis if they want to be connected some how.. 21:45 gveranis They can move to Koha as seperate ILS and provide records to Enocre 21:45 MilkManzJourDaddy Vufind for the library's I.L.S. Hmmm. Thanks. Well the union/system maintains the central database, but the library should be able to do it's own ILS, working with a DB. Thanks. 21:44 gveranis and believe me I search it a lot to move some way to Koha.. 21:43 gveranis my job is to be it administrator on a such a thing you described in Greece.. 26 academic libraries under a Sierra .. 21:43 gveranis If they want to use ILS then they cannot use Koha as a client it not the same thing 21:42 gveranis they are compatible 21:42 gveranis if they want only functionality for OPAC you can suggest Vufind fo the integration between Sierra and other sources 21:41 gveranis Sierra is a central systems which use scopes but the database is one 21:41 cait and koha is a full ILS, so you can't use 'just the OPAC' - if you are just looking for a different search interface 21:41 cait if they all have to use the same ILS koha might not fit in 21:41 cait or library uion 21:41 cait I guess it would dependon how hteir union catalog is organized 21:39 MilkManzJourDaddy Let's try this again… I want to recommend a F.(L.)O.S.S. I.L.S. to a library that is a member of a library union/system. The union/system uses a O.P.A.C. which is Innovative Interfaces, Inc.'s Sierra ILS & Encore Discovery Solution. Assuming that is M.A.R.C., could they use Koha as a client? 21:39 cait usually zebra based matching should be faster 21:39 cait match checks are using the db i think (from what i've read somewhere) 21:39 gveranis oh ok 21:38 cait and you can combine both 21:38 cait or you can add match checks 21:38 cait you can add either match points - they require an index 21:38 cait see at the bottom of the form? 21:38 gveranis with the same arguments as matchpoint ? 21:37 cait i haven't used it, but it shoudl be possible using the match check 21:37 gveranis it is something feasible ? or not ? 21:37 gveranis and if i would like to do a match record rule for a field/subfield that not have search-index 21:37 cait cool :) 21:36 gveranis cait it works now. with Local-number and match threshold = score = 100 21:35 cait what are you using there? 21:35 cait the important bit usually is the Search index 21:35 cait but htey can also be the same, it should work 21:34 cait match threshold 101 and score 100 would make no sense 21:34 cait it does 21:34 cait sorry 21:34 cait ah i tides 21:34 rangi cool :) 21:34 tcohen rangi: done! 21:34 cait yeah that makes no sense 21:34 gveranis a 21:34 gveranis score 101 21:34 cait score = 100 21:34 cait also if you are not using mulitple match points, the match threshold should match the score 21:34 gveranis Match Threshold -> 100 21:33 cait the example is very flawed 21:33 cait 001 has no subfields 21:33 cait leave it 21:33 cait and subfield 21:33 cait offset too 21:33 cait y 21:33 cait no you can leave that empt 21:33 gveranis length should have a value ? 21:33 gveranis I tried also with no success 21:32 cait gveranis: try Local-number 21:31 cait if you used Control-number that might not work for UNIMARC 21:30 cait can you share a screenshot? 21:30 cait what info did you enter? 21:27 gveranis I follow the documentation : https://koha-community.org/manual/18.11/en/html/administration.html and other guidelines from koha mail listing without success 21:26 gveranis hi #koha , I try to do a matching rule for field 001 but nothing worked. I have unimarc koha 17.11. Can someone help ? 21:15 tcohen hi wizzyrea 21:15 tcohen rangi, indeed! 21:15 wizzyrea hi tcohen 21:15 rangi https://wiki.koha-community.org/wiki/KohaCon18_Proposals#Arrivals_.26_Departures <-- tcohen you should add your details :) 21:14 tcohen hi rangi! 21:13 rangi hi tcohen 21:13 cait hi 21:12 tcohen hi 21:00 cait exciting even 21:00 cait not a very existing one 21:00 huginn Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21000 minor, P5 - low, ---, koha-bugs, NEW , debian/build-git-snapshot script ignores --distribution 21:00 cait bug 21000 17:08 cait sessions table 17:05 cait hm it's not a cookie... so where does it store that youchecked the checkbox 17:01 cait hm yep not getting rid of the special due date 16:58 cait when i switch to another user 16:58 cait i remove it weith delete and it comes back 16:58 cait hm they are right 16:57 cait so the cookie was just an additional catch... 16:57 cait so far we can't reproduce it - and the bug survived an update too 16:57 cait like it magically reappearing 16:57 cait we have a library rpeorting issues with the speciy due_date checkbox 16:54 cait i must finished the german translation today 16:52 cait hmm 16:52 oleonard Oh yeah, that one. 16:51 cait issues-table-load-immediately-circulation 16:51 cait change 16:51 cait ... and not hapyp about it for a chance 16:51 * cait found more cookies 15:49 Joubu ha yes 15:49 kidclamp pre-push should have saved me 15:48 kidclamp heh,testing irccloud so forget it steals my nicknameif I try to sign in elsewhere 15:48 Joubu kidclamp: hum? context please :) 15:48 huginn kidclamp: The operation succeeded. 15:48 kidclamp @later tell joubu it should have, apaprently didn't set it up right on my laptop, so my dekstop caught me on next push 15:48 tcohen hi kidclamp! 15:47 tcohen cait: I think it does 15:47 oleonard kidclamp: Thank goodness we got rid of that interloper 15:47 * kidclamp waves 15:46 tcohen Joubu: you are rihgt 15:46 * wmnickc waves 15:41 huginn Joubu: The operation succeeded. 15:41 Joubu @later tell tcohen: a ref to koha-plack is missing from the wiki install pages, right? 15:36 cait just not sure about syntax 15:36 cait i found a bug stating it was broken and fixed - so assume it should work 15:36 cait nm we will try it out 15:36 ashimema No idea I'm afraid cait 15:35 lavamind_ I would say, those are the best bugs because you get to learn something 15:33 * oleonard doesn't get excited about bugs he doesn't know how to fix 15:32 lavamind_ data loss bugs are exciting XD 15:32 lavamind_ oleonard: maybe not as exciting but hopefully valid ? :P 15:31 huginn Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=1000 enhancement, P2, ---, gmcharlt, CLOSED INVALID, installer: drop/suppress entries in mysql if re-launching installer script 15:31 oleonard lavamind_: Just as exciting as Bug 1000. 15:28 Joubu tcohen: a ref to koha-plack is missing from the wiki install pages, right? 15:27 huginn Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21000 minor, P5 - low, ---, koha-bugs, NEW , debian/build-git-snapshot script ignores --distribution 15:27 lavamind_ oleonard: there you go, filed bug 21000 :) 15:23 cait ashimema: do you happen to know if ldap can map extended patron attributes now? 15:23 tuxayo ^^ 15:20 huginn Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21000 could not be retrieved: InvalidBugId 15:20 * oleonard anxiously awaits the exciting turnover to Bug 21000 15:10 semarie so I will be able to check how upgrade using package is :) 15:09 Joubu packages will be available in the next few days 15:07 semarie I installed using debian packages for 'stable' 15:07 Joubu semarie: 18.05.01 has been released yesterday, it fixes several big issues of .00 15:04 semarie Joubu: thanks. now it see the right version 15:04 semarie ah yes :) 15:03 Joubu I would restart memcached 15:03 Joubu so you do not need this script 15:03 Joubu you have 3.6 15:03 Joubu hi semarie 15:03 semarie "Performs the necessary changes to upgrade a Koha system from 3.2 to 3.4" 15:03 semarie but I saw some command-line tools like: koha-upgrade-to-3.4 15:02 semarie which is wrong. the starting point isn't 18.05.00.000 15:02 semarie "Nous effectuons une mise à jour de Koha 18.05.00.000 à Koha 18.05.00.000" 15:01 semarie installer/install.pl doesn't see the "old" version 15:01 semarie for now, I have done it this way, but I am unsure about the upgrade process. 15:01 eythian a mysqldump and reload is pretty much the same as doing an upgrade 15:00 oleonard semarie: Yes 15:00 reiveune bye 15:00 semarie oleonard: about the "export". it is just a mysqldump ? 14:59 oleonard semarie: It's not my area of expertise, I'm just repeating what I've heard. 14:58 oleonard semarie: It is not recommended that you upgrade an installation which is that old. 14:58 oleonard semarie: The advice I've always heard about migrating old installations is to export your Koha database and import it into a fresh, up-to-date Koha installation. 14:57 caroline Hi oleonard! 14:57 oleonard Hi caroline 14:55 caroline hello everyone! 14:35 semarie hi. I have a quite old koha installation (3.06.12) I would like to upgrade to latest. what is the right way to do it ? 14:20 oleonard Hi cait 14:15 cait hi oleonard :) 13:48 ashimema oh.. thanks 13:46 Joubu ashimema: it's a new method (since 18.05 I think) of Koha::Plugins::Base 13:42 ashimema if i run under cgi there's no such error 13:42 ashimema I get `Can't locate object method "output_html" via package "Koha::Plugin::Com::...` 13:41 ashimema is there any magic that needs doing for a plugin to work under plack? 13:22 gveranis I would like to ask if community has a plugin for the field 000 creation on authorities in UNIMARC mode 13:21 gveranis hi koha# 12:58 tcohen that's returning 40-ish patrons that come with the sample data 12:57 AndrewIsh_ tcohen: Interesting, glad it's not something inherently wrong with the API :) I'm going to do some more testing, I've seen the problem on both Plack and non-Plack instances. I'll dig some more and report back. Thanks for that screenshot, very reassuring :D 12:52 tcohen I think you had plack disabled due to incompatibility with Shibboleth? 12:52 tcohen AndrewIsh_: https://snag.gy/YlVPKi.jpg 12:04 AndrewIsh_ Thanks eythian - I will try that! 11:53 oleonard Hi #koha 11:36 eythian AndrewIsh_: play around with something like this, and/or nytprof then perhaps https://metacpan.org/pod/Plack::Middleware::ServerTiming 11:33 josef_moravec i didn't notice the slow api nor in tests or using browser 11:31 cait something to discuss with tcohen maybe - for the limited testing I did with browser tools it didn't seem esepcially slow, but I might just not have noticed 11:28 AndrewIsh_ cait: Seeing it both with Plack and without 11:28 AndrewIsh_ eythian: I'm seeing the same problem across my dev server and a customer's test server, so not likely to be DNS 11:28 AndrewIsh_ ashimema: That was my thought, but no, I'm seeing the same on cities 11:21 cait AndrewIsh_: usng plack? 11:12 eythian For those sorts of delays, my first thought is often a failing DNS lookup. 11:10 ashimema but perhaps not 11:10 ashimema I thought it was ILL specific due to the complex nature of the db 11:02 AndrewIsh_ Hey all. Is anyone aware of any outstanding performance bugs on the REST API? I've been looking at poor response times on the ILL endpoint and discovered it actually appears to affect all endpoints. For example, a GET request to the /api/v1/cities endpoint, is taking 5.7s to respond with an empty response, similarly, a very simple GET on all ILL requests takes a similar time to response, with only 6 requests. Is anyone already aware of this? 09:45 cait josef_moravec: we still need qa, but some tiem to the next release now 09:36 josef_moravec that's absolutaly OK? we are planning to migrate to 18.05 during the summer (sometimes) ;) 09:36 fridolin until 17.05.16 09:35 fridolin oki I'll try to stabilise it 09:31 josef_moravec fridolin: you are doing great job on 17.05, we're still using it in production ;) 09:30 fridolin thanks ;) 09:29 josef_moravec cait++ 09:29 josef_moravec fridolin++ 09:13 jenkins * fridolin.somers: Update release notes for 17.05.13 release 09:13 jenkins * fridolin.somers: Increment version for 17.05.13 release 09:13 jenkins * unknown: Translation updates for Koha 17.05.13 09:13 jenkins Project Koha_17.05_D8 build #104: SUCCESS in 38 min: https://jenkins.koha-community.org/job/Koha_17.05_D8/104/ 08:34 huginn Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20922 critical, P5 - low, ---, jonathan.druart, Pushed to Stable , Koha::Number::Price must not be used in updatedatabase.pl 08:34 huginn Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18821 major, P5 - low, ---, kyle, Pushed to Stable , TrackLastPatronActivity is a performance killer 08:34 jenkins * Jonathan Druart: Bug 20922: Remove use of Koha::Number::Price in updatedatabase.pl 08:34 jenkins * m.de.rooy: Bug 18821: (QA follow-up) Last tweaks for performance 08:34 jenkins * kyle: Bug 18821: Convert to using cache with date checking 08:34 jenkins * kyle: Bug 18821: TrackLastPatronActivity is a performance killer 08:34 jenkins Project Koha_17.05_D8 build #103: SUCCESS in 38 min: https://jenkins.koha-community.org/job/Koha_17.05_D8/103/ 07:54 ashimema fridolin++ 07:54 ashimema :) 07:53 * fridolin releasing 17.05.13 07:40 fridolin hi there 07:33 gaetan_B hello 06:45 ashimema Morning 06:40 reiveune hello 06:32 josef_moravec morning alex_a 06:32 alex_a bonjour