Time  Nick        Message
00:12 * Francesca waves
06:27 cait        morning #koha
06:29 magnuse     kia ora cait
06:30 cait        morning magnuse!
06:50 reiveune    hello
06:54 alex_a      bonjour
07:26 magnuse     anyone got any experience with self checks that do offline circ? so if koha is offline the self check machine saves the circ operations and then communicates them to koha when koha is online again?
07:41 fridolin    hie alllllllll
07:42 fridolin    I'm back to work
08:12 cait        wb fridolin :)
08:23 fridolin    cait: hello how are u ?
08:24 cait        buuusy
08:24 cait        how are you and the family?
08:56 magnuse     welcome back fridolin
08:57 fridolin    magnuse: hie
08:57 fridolin    nice to see u again
08:57 fridolin    I'm a father now with a 3 years old little girl
08:58 fridolin    what a job, i'm happy to come back to work :D
09:02 magnuse     it can be a bit of a challenge, yeah :-)
09:02 * magnuse   has a son who is almost 4
09:27 fridolin    magnuse: a chance I have found a new passion : golf
09:27 fridolin    you must be zen to play 8-)
09:32 marcelr     hi #koha
10:32 Vinod       Hi All
10:33 Vinod       I have got some error in the web-opac near search field as like <<<<<<< HEAD======= >>>>>>> Bug 13144: Google transliteration does not work on bootstrap
10:34 huginn      04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13144 normal, P5 - low, ---, amitddng135, CLOSED FIXED, Google transliteration does not work on bootstrap
10:34 Vinod       Why this error might come can any one help me out?
10:35 Vinod       yes huginn This bug is closed but that is coming near the search field
10:35 Vinod       how can i fix that?
10:37 Vinod       can any body help?
10:55 magnuse     Vinod: that is a git thing. it means a patch was applied and there was some conflict
10:55 magnuse     how did you install koha?
10:56 magnuse     this looks like it might be helpful, if you have a git/gitified install and applied some patch(es) yourself: https://help.github.com/articles/resolving-a-merge-conflict-from-the-command-line/
10:57 cait        um
10:57 cait        opac news only visible when logged in... did i miss something there?
10:58 magnuse     yeah, we decided to keep the good news to ourselves ;-)
10:58 cait        oh? :)
11:00 magnuse     wasn't there some work on displaying news only from your library when you are logged in? sounds like it might be related to that
11:00 magnuse     just a hunch, though
11:00 magnuse     kia ora khall
11:02 magnuse     fridolin: you got time for that? :-O
11:08 cait        magnuse: hm good thinking - i will check if there is a library setting in this vresion
11:11 cait        magnuse++ thx!
11:40 magnuse     oleonard!
11:41 oleonard    magnuse!
11:44 druthb      oleonard! magnuse! cait!
11:45 oleonard    Was there not a meeting yesterday?
11:46 cait        oleonard: there would have been - but not enough participants
11:47 oleonard    Sorry, terrible time for me to try to make a meeting.
11:48 Vinod       magnuse: Thanks for the reply
11:52 oleonard    Hi Oak
11:52 Oak         hello oleonard :)
11:52 * Oak       waves
12:09 oleonard    Oh, a new German support company? cait were you aware of them?
12:15 cait        yes
12:16 cait        oleonard: where di you see it?
12:16 oleonard    On the mailing list
12:33 tcohen      bonjour
12:33 Oak         hello tcohen
12:43 magnuse     Oak
12:43 Oak         magnuse
12:43 Oak         \o/
12:45 magnuse     \o/
12:45 magnuse     Oak: you got yourself a company too?
12:45 Oak         Yes :) Working on it.
12:45 Oak         Working on the website at the moment.
12:45 magnuse     cool
12:45 magnuse     good place to start :-)
12:45 Oak         thanks!
13:14 cait        oleonard: thx!
14:03 Oak         later guys
14:28 kivilahtio  khall: Have you noticed that when you have definitions in log4perl.conf for opac, intranet, sip, commandline, ...  and opac.log is used by user www-data, and sip.log is used by koha, there is a problem with file permissions
14:29 kivilahtio  khall: looks like every time Log::Log4perl is instantiated, it tries to open filehandles for all the defined Appender
14:29 khall       no that in particular, but yeah, log permissions are a serious headache.
14:30 kivilahtio  khall: well I got it. I have a feature that is ran by www-data and koha
14:30 kivilahtio  khall: I was asking if you have any suggestions on how to fix it.
14:30 kivilahtio  khall: I was planning on splitting the log4perl.conf to each Koha subsystem
14:30 kivilahtio  like log4perl.opac.conf
14:31 kivilahtio  and load the config by the C4::Context->interface
14:31 kivilahtio  another option is to mae modifications to Log::Log4perl
14:31 kivilahtio  which might not be too difficult
14:32 khall       hmm, I worry that splitting the conf may lead to limited flexibility and more complication long term, but I've not real example
14:33 kivilahtio  khall: I completely agree
14:33 khall       maybe look at patching Log4perl first, and use that as a fallback
14:34 edveal      Has anyone in here come up with a good way to validate phone numbers. I have tried using the code that is in the jQuery library but have had issues with it. Any suggestions?
14:34 kivilahtio  edveal: we got such a validator from our ministry of something
14:34 kivilahtio  you could ask there. There must be a big authoritys handing out phone umbers in your country
14:35 kivilahtio  edveal: actually I think lari has a patch in bugzilla about validators
14:35 oleonard    edveal: What have you tried, and what didn't work?
14:35 kivilahtio  edveal: but afaik the phone number validator can be chosen and not implemented for your country
14:35 kivilahtio  I mean a validator implementation fitting your country is not there in Koha
14:36 oleonard    kivilahtio: Are you talking about finding actual valid numbers, or matching the correct format?
14:36 edveal      Sorry I mean just checking to verify that the number is in a specific structure when adding a patron.
14:36 kivilahtio  oleonard: matching a format
14:36 kivilahtio  oleonard: the regexp we got from the ministy is a monster
14:37 oleonard    edveal: One of the problems I've run into is the issue of how flexible you want it to be
14:37 edveal      oleonard, I have tried using what is in the Koha jQuery library and it seems to work unless the field is blank. Then the validation fails. I need something that is more flexible.
14:37 kivilahtio  edveal: https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=44705&action=diff
14:37 kivilahtio  line 101
14:38 oleonard    is both (555) 555-1212 and 555-555-1212 okay, for instance
14:38 edveal      No they want it to either be blank or 555-555-1212.
14:39 kivilahtio  the feature even has PageObject test coverage!!
14:39 kivilahtio  it is so cool :)
14:39 edveal      oleonard I tried the html phone validation and that didn’t work either.
14:40 edveal      pianohacker was not able to get the HTML5 validation to work either. Very puzzing.
14:40 edveal      I started with HTML5 validation
14:42 oleonard    edveal I use this regular expression in some SQL reports for finding bad phone numbers: ^([0-9]{3})\-([0-9]{3})\-([0-9]{4})$
14:42 edveal      Ah so you run a report to search for them and then they can be fixed...
14:43 kivilahtio  edveal: that is certainly what we did for a awhile
14:43 kivilahtio  edveal: it is much better to fix the problem at its root
14:43 edveal      I agree
14:43 oleonard    edveal: The trouble we have here is that staff want to put other text into the phone number field besides the phone number
14:43 kivilahtio  edveal: you dont need to do so much explaining to your patrons when they dont receive their sms'es
14:43 oleonard    like "555-555-1212 mom's phone"
14:43 kivilahtio  oleonard: validator blocks this. That is why we have custom borrower attrbiutes and notes
14:44 kivilahtio  oleonard: that crashed our prcoess_message_queue.pl
14:44 kivilahtio  well it is patched now :)
14:44 oleonard    kivilahtio: We don't have any automated notifications which use phone number, so we have some wiggle room.
14:45 kivilahtio  one of the biggest issues regarding the problems we have had with Koha are non-stnadard field usage. In database tables and in MARC Records
14:45 kivilahtio  mom's number being a prime example
14:46 kivilahtio  I guess we could implement a feture where only the valid matching part of the phone number would be used, and rest just ignored for automatic purposes?
14:46 kivilahtio  this would work well with the validator
14:46 kivilahtio  validator extracts matching parts
14:46 kivilahtio  everybody is happy
14:46 kivilahtio  if no matching part, phone number doesnt validate
15:00 reiveune    bye
15:09 tcohen      hi
16:02 kivilahtio  tcohen: hi
16:03 tcohen      hi kivilahtio
16:03 kivilahtio  khall: I fixed the multiuser scenario with Appender property create_at_logtime=true
16:03 khall       excellent!
16:03 kivilahtio  khall: but I have issues with making Koha::Logger work under apache2
16:03 kivilahtio  khall: wont log when ran from mod_perl
16:03 kivilahtio  khall: but works fine from the commandline when I try all interfaces
16:04 khall       odd, wonder why that is
16:04 kivilahtio  I mean jury-rig commandline to be interpreted as for ex. opac
16:04 kivilahtio  khall: Does it work for you?
16:04 kivilahtio  from apache2
16:05 khall       I haven't tested it any way except cgi
16:06 kivilahtio  khall: maybe I made a mistake, I thought mod_perl is the same as the mod_cgi
16:06 kivilahtio  I meant mod_cgi. The old and slow script-based solution
16:26 drojf       hi #koha
16:34 oleonard    Oh wow, I did not realize my follow-up for Bug 11565 got pushed.
16:34 huginn      04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11565 enhancement, P5 - low, ---, kyle, Pushed to Master , decreaseLoanHighHolds needs Override
16:34 oleonard    When I saw the "settings" link on the checkout page I thought I had my branches mixed up
16:35 drojf       so the meeting did not happen yesterday?
16:36 oleonard    No they cancelled it because you and I weren't there drojf.
16:36 drojf       heh good choice ;)
16:40 drojf       several people complained to me about relevance ranking in koha. is that a known something? never had to do with it because nobody complained before
16:42 oleonard    drojf: Yeah some people say it doesn't work and others don't have a problem with it. But the real issue seems to be no one really knows how it works.
16:42 drojf       yes that is what i imagined. lol
16:43 oleonard    http://irc.koha-community.org/koha/2016-05-09#i_1820535
16:43 drojf       i had somebody show me it does not work yesterday. so i know its a thing, at least for some. i would at least expect searchword-in-title to rank higher than searchword-somewhere-in-keywords
16:43 drojf       hahaha
16:43 drojf       thanks oleonard
16:45 drojf       bug 12431
16:45 huginn      04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12431 major, P5 - low, ---, gmcharlt, NEW , Relevance does not work properly when using QueryParser
16:45 drojf       bug 12430
16:45 huginn      04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12430 normal, P5 - low, ---, dcook, In Discussion , Truncation disables relevance ranking when not using QueryParser
16:46 drojf       so at least i intuitively changed the right sysprefs, did not help anyway
16:55 oleonard    It's an embarrassment, really, for Koha that we don't know how that works let alone make it better.
16:58 drojf       i was never aware that there is a problem. i dont cate about relevance because googl etold me nobody knows what is relevant for me
16:58 kivilahtio  khall: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16509
16:58 huginn      04Bug 16509: enhancement, P5 - low, ---, olli-antti.kivilahti, Needs Signoff , Koha::Logger dies when log4perl.conf has FileAppender files with different owners, also compatibility with logrotate
16:59 kivilahtio  khall: it has no issues with mod_cgi
16:59 kivilahtio  khall: that was my mistake confusig different dev environments
16:59 khall       cool, I'll check that out!
16:59 t4nk927     hello
16:59 kivilahtio  t4nk927: hi there
16:59 t4nk927     Can you help me with Koha installation
16:59 kivilahtio  t4nk927: Do you like t4nks?
17:00 kivilahtio  t4nk927: it depends
17:01 kivilahtio  t4nk927: I guess most of us here have installed Koha at some point
17:01 t4nk927     Can you tell me the latest 3.22 can be installed on Windows?
17:02 kivilahtio  t4nk927: I am sorry. I cannot help you with that. I am not very pro-Microsoft
17:02 oleonard    t4nk927: No, not directly.
17:02 kivilahtio  t4nk927: but I am sure somebody here has
17:02 kivilahtio  t4nk927: if you are starting to learn Koha, you hsould deploy it on Ubuntu 14.04. It is very straightforward
17:03 oleonard    t4nk927: You could install something like VirtualBox on Windows and run Koha inside that, but it would be suitable only for testing.
17:03 kivilahtio  t4nk927: It is very simple to install it from debian packages
17:03 t4nk927     why is it difficult to run on Windows
17:04 kivilahtio  t4nk927: because Koha is a community product, and nobody here runs it on Windows.
17:04 kivilahtio  t4nk927: so when programming Koha, nobody tests the developments against Windows
17:04 kivilahtio  and then most certainly it wont work on Windows, unless you invest a lot of time and effort to retrofit it to work there
17:05 t4nk927     if I run it on Windows will it be a problem?
17:05 kivilahtio  t4nk927: if you would do the effort, then somebody here would maintain the Windows version of Koha
17:05 kivilahtio  t4nk927: I don't think you can run it on Windows
17:05 t4nk927     As far as I know we can
17:05 kivilahtio  t4nk927: oleonard said you should run Linux on your Windwos machine
17:05 kivilahtio  t4nk927: then, like I said I cannot help you :)
17:06 pianohacker @later tell rangi what's the state of the ES browse code? (http://browse.koha.catalystdemo.net.nz/cgi-bin/koha/opac-browse.pl)
17:06 huginn      pianohacker: The operation succeeded.
17:06 t4nk927     Any one here
17:06 oleonard    t4nk927: As far as anyone knows it is not possible to install Koha on Windows.
17:07 t4nk927     As far as I know one can
17:07 oleonard    t4nk927: Who says?
17:07 t4nk927     I have done it previously
17:07 oleonard    t4nk927: If you think you can, you're welcome to try it.
17:08 kivilahtio  t4nk927: Yes. I would love to see how it goes :) While working at it you could write install instructions to our wiki
17:08 kivilahtio  t4nk927: here is one of hte many for Ubuntu
17:08 kivilahtio  https://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages
17:08 kivilahtio  t4nk927: also Redhat is not very popular system to run Koha on
17:08 kivilahtio  t4nk927: I recommend you use Ubuntu 14.04
17:09 t4nk927     I know
17:09 kivilahtio  t4nk927: You don't need to be a hard-core linux guyy. Just a regular dude will do ;)
17:09 t4nk927     but I can't change my home PC
17:09 t4nk927     OS
17:09 t4nk927     here is one example what I am talking about http://www.koha.rwjr.com/
17:09 kivilahtio  install Ubuntu 14.04 on a virtual machine on your Windows-PC
17:09 kivilahtio  there are a ton of guides online for that
17:09 kivilahtio  maybe you will even love Ubuntu!
17:10 kivilahtio  nowadays it is super great
17:10 kivilahtio  it even has Steam in it !
17:10 kivilahtio  Steam++++
17:10 t4nk927     I have worked on Ubuntu no uduntu its good
17:10 oleonard    t4nk927: That documentation is 10 years old
17:10 kivilahtio  oleonard: :)
17:10 kivilahtio  t4nk927: maybe you should ask those guys?
17:11 kivilahtio  t4nk927: not everybody who uses Koha hangs around here regularly, like me
17:11 t4nk927     I understand thats the reason I am asking if its possible as well
17:11 kivilahtio  can't help you with Windows sorry.
17:12 oleonard    t4nk927: You're asking if it's possible and we're saying no. You say yes. Try it and find out.
17:12 oleonard    t4nk927: None of us will be able to help you.
17:12 t4nk927     Any one else I hope may know
17:13 kivilahtio  t4nk927: ask those guys from the link you posted to us.
17:13 kivilahtio  email is cheap
17:14 oleonard    Be sure to send the email back in time 10 years.
17:15 kivilahtio  oleonard: :)
17:15 t4nk927     haha
17:15 t4nk927     Where do u work?
17:15 kivilahtio  Finland, Vaara-kirjastot
17:17 kivilahtio  t4nk927: and you?
17:17 t4nk927     nice to meet you Sir
17:17 t4nk927     I am from India
17:17 t4nk927     in a college library
17:18 kivilahtio  t4nk927: I have one thing to say to all public sector employees. Use linux, save your tax-payers money
17:18 t4nk927     because it is OSS?
17:18 kivilahtio  UK had a great idea for making OdenDocument standard mandatory in the public sector
17:18 kivilahtio  UK had a great idea for making OpenDocument standard mandatory in the public sector
17:19 kivilahtio  t4nk927: for starters
17:23 kivilahtio  then the public sector employs local people, and has more money to spend on, for ex developing Koha :)
17:25 jim_        any one here
17:29 jim_        hello
17:29 kivilahtio  jim_: hello?
17:30 kivilahtio  jim_: there are ~61 users online
17:32 jim_        I see
17:32 jim_        but I only see u
17:49 jim_        hello\
17:50 jim_        knock knock
17:50 oleonard    Hi jim_, do you have a question?
17:50 jim_        I have but you can't solve
17:51 jim_        What do u work as
17:51 oleonard    I work as a web developer for a public library in Ohio, USA.
17:52 jim_        Wow nice
17:52 jim_        honored to meet you
17:56 jim_        any one else here
18:59 oleonard    Bye #koha
20:16 rangi       pianohacker: i think the patches were all submitted
20:16 pianohacker hm.
20:19 cait        pianohacker: got your flights and all? :)
20:19 * andreashm waves
20:20 cait        hi andreashm :)
20:21 andreashm   hi cait
20:36 andreashm   reading the logs
20:36 andreashm   drojf: looking at relevance?
20:37 drojf       andreashm: a little
20:38 drojf       but it looks like i destroyed my dev vm. oops
20:38 andreashm   saw that there are two bugs regarding truncation and queryparser. seems relevance gets screwed any which way it is set.
20:38 andreashm   drojf: ouch
20:39 drojf       there is no relevance. relevance in the default zebra settings is order by biblionumber. i don't know about the queryparser, but without there is nothing relevant in relevance ranking at the moment
20:40 cait        hm
20:40 cait        there is some code to boost some fields i think
20:40 cait        but ... ok, i got no idea
20:41 drojf       that is about broader and narrower terms. if we mean the same thing
20:41 cait        just thought it used to work? in some ways at least?
20:41 drojf       in the way that it sorts by biblionumber i guess :)
20:41 cait        i think i wa sthinking field weighting
20:42 drojf       me too
20:42 andreashm   drojf: order by biblionumber? really?
20:42 drojf       andreashm: try it
20:43 * andreashm is scared too
20:45 drojf       maybe there is a magical combination of settings that gets something more relevant out of it
20:45 andreashm   hopefully
20:45 drojf       i have not found that part in the code thoug
20:45 drojf       though
20:46 drojf       (which does not mean much in the search module labyrinth)
20:46 andreashm   Regarding the OAI harvester thing that I asked about the other day, if was indeed a missing dependency.
20:50 andreashm   That sorted, I immediately run into another problem. 'bangs head against the wall'
20:51 liw         I want to sell a small cushion with a headband that you put on your forehead to make headbanging less painful
20:53 andreashm   liw: I'll buy one.
20:54 drojf       i'll buy shares of your startup!
20:56 liw         :)
21:08 drojf       i think a part of zebra rebuild is picking up the wrong koha-conf.xml in my dev vm
21:15 * cait      waves at kathryn
21:15 cait        drojf: did you check in? i still have to
21:15 kathryn     hi cait
21:16 drojf       no. i was waiting for you to try
21:16 cait        hm
21:16 drojf       23:16:03-12/05 zebraidx(1899) [warn] zebra_lock_create fail fname=__ZEBRA_LOCK_DIR__/biblios/norm..LCK [No such file or directory]
21:16 cait        it's too late tonight, tomorrow
21:17 drojf       i get that a thousand times. why would it look in __ZEBRA_LOCK_DIR__
21:17 drojf       unless it uses the wrong koha-conf.xml
21:32 drojf       good night #koha
22:09 huginn      New commit(s) kohagit: Bug 16489: ES code incorrectly refers to Moose <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=9d9f2efa941ba678d57a18718fedf752984dfee3>
22:20 huginn      New commit(s) kohagit: Bug 16474: Standardize spelling of EDIFACT <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=e3fa3a397845212d2030ff0a32256ec5bfd2964b> / Bug 16412: Cache undef in L1 only <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=7a452ac4149809c212d861ee8b08c3931f23234a> / Bug 16412: Make sure Koha::Cache->set_in_cache will not warn anymore <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;
22:30 huginn      New commit(s) kohagit: Bug 16473: Fix typo "an problem" vs "a problem" <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=3f0a1f0c7f5edebbaa5d61f0392e9ab67d201e00> / Bug 16480: Unclosed tag in shelves line 332 on intranet <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=9f5163cfcd1eb8becf48ae0861d8096720965c61>
22:46 oleonard    Hey anyone around to give me a sanity check? If I'm composing a notice and select multiple fields and insert them at once...
22:47 oleonard    I get this: <<branches.branchname, branches.branchaddress2, branches.branchzip>>
22:47 oleonard    That's not gonna work, right?
22:47 pianohacker oleonard: pretty certain no
23:37 dcook       Hey wizzyrea, are you around atm?
23:37 dcook       I have a koha-gitify question...
23:39 dcook       Or anyone who uses koha-gitify...
23:43 dan_        Hello everyone
23:43 dan_        In the zebra output log, what means the line "[warn] cs_listen failed [Too many open files]" (repeated a hundred times)? (log found after zebra srv process was dead)