IRC log for #koha, 2013-12-09

All times shown according to UTC.

Time S Nick Message
00:00 cait1 hmthat's a weird thing
00:00 wizzyrea javascript disabled?
00:00 jcamins I can't reach my keyboard anymore.
00:00 wizzyrea how are you typing?
00:01 peggy With the handle of his spoon?
00:01 jcamins Hehe.
00:01 jcamins I was bending almost double.
00:01 * wizzyrea will be impressed if he's typing with his toes, or by thinking
00:01 jcamins The other 75cm exercise ball... not 75cm.
00:02 jcamins More like... 110cm.
00:02 jcamins My legs were on level with the keyboard.
00:03 onezero joined #koha
00:03 jcamins Okay, maybe I'll use a pyrex, and then cut the shortbread.
00:05 cait1 pyrex?
00:05 jcamins Glassware.
00:05 jcamins For baking.
00:08 NateC joined #koha
00:09 dcook Chemistry in general, no? ;)
00:09 cait1 oh
00:10 wizzyrea pyrex is oven/stovetop safe glassware. Tempered or some such.
00:11 peggy joined #koha
00:12 cait1 thx jcamins and wizzyrea
00:12 cait1 :)
00:16 cait1 good night all :)
00:16 cait1 left #koha
00:17 wizzyrea gnite cait
00:22 jcamins wizzyrea: when making shortbread, should you have a dough or a loosely mixed pile of crumbs?
00:23 wizzyrea are you going to roll it?
00:23 * wizzyrea has always had dough
00:23 wizzyrea but like, pie crust, if you squeeze it it comes together into dough
00:24 jcamins Yeah, I just wanted to confirm that I was supposed to squeeze it together.
00:24 wizzyrea so if yours does that, it's probably fine
00:24 wizzyrea yea, that seems right. you'd have shortbread crumbs otherwise. :)
00:24 jcamins Thanks.
00:29 peggy Does koha-remove work?
00:31 dcook Hmm, does anyone know if the default overdue triggers work if there are triggers for individual libraries set?
00:31 dcook peggy: As far as I know, but I don't think I've ever tried it
00:31 jcamins peggy: work for what?
00:31 jcamins If you mean in general, yes, I use it all the time.
00:32 peggy I think I need to uninstall Koha and the start again from the beginning.
00:33 dcook Ah, that command removes an instance, not the total program
00:33 jcamins dcook: right.
00:33 dcook jcamins: In terms of the deb command or the overdues? :p
00:33 jcamins The deb command.
00:34 jcamins I want to bake something else.
00:34 * dcook thinks that he should've asked his overdue question when cait was still arouhnd
00:35 dcook around*
00:35 dcook peggy: What are you trying to do?
00:36 peggy I have hosed my computer.  I've tried checking out the master, gitifying and whatever I type in Koha goes straight to the Search the Catalog tab.
00:36 peggy Something is seriously wrong.  I have nothing I want to save.  I just want it to work again so I can do some debugging
00:36 eythian this sounds like a browser issue, not a koha issue.
00:37 wizzyrea dcook my understanding is that the overdue triggers are default, unless there are branch triggers set
00:38 peggy I'm using iceweasel
00:39 wizzyrea do you have javascript disabled?
00:39 eythian what do you mean by "whatever you type"?
00:39 dcook And what's the "Search the catalog" tab? Staff client? OPAC?
00:39 eythian Can you explain in terrible gueling detail?
00:39 eythian *greuling
00:39 dcook hehee
00:39 eythian or however you spell that
00:39 wizzyrea grueling*
00:40 dcook wizzyrea: I get this message when I run the overdues "Found 7 branches with first message enabled:"
00:40 wizzyrea helping?
00:40 wahanui I'M HELPING!!!!!
00:40 dcook No reference at all to the default branch that I can see..
00:40 wizzyrea do you have 7 branches with first message enabled?
00:40 peggy I try to create a new patron.  My cursor is in the surname field.  I type a 'T'.  It appears in the top entry box in the search the catalog tab (the one that lets you choose between checkin, checkout, and search the catalog.
00:40 jcamins It's 7:40pm, and I really want to bake something.
00:41 wizzyrea brownies
00:41 wahanui brownies are a lie.
00:41 wizzyrea pft.
00:41 peggy If I choose the checkout tab and type a 'T' it switches to the search the catalog tab and puts the T in there.
00:41 wizzyrea clear your browser cache?
00:41 peggy jcamins, aren't you making cookies?
00:41 eythian that's pretty odd. Does this happen on all fields and pages? Have you restarted your browser, cleared cache, cookies, etc?
00:41 jcamins peggy: I am, yes.
00:42 jcamins I have a bit of buttermilk.
00:42 wizzyrea have you tried it in another browser on your machine besides iceweasel? (not that it should matter, but still)
00:42 dcook wizzyrea: I do. Here's the thing I'm wondering...Patron Category A has no notice defined for Branch A, but it does for Default. They receive no notices. This makes sense to me, since the branch should take precedence. However, if the branch takes precedence when notices are defined or not seems like default might only be used if there are no notices defined for any particular branch.
00:42 jcamins And yogurt...
00:42 jcamins I could make a quickbread. Maybe some coffeecake.
00:43 wizzyrea that seems right to me
00:43 wizzyrea well no, it will use the default if there are no notices defined for a particular branch
00:43 dcook Right. That makes sense
00:43 wizzyrea so if you have library A, with notices defined, and B with no notices
00:43 wizzyrea B will use the default
00:43 wizzyrea A will use the branch ones.
00:44 dcook Although...what happens if you don't want any notices for Branch B...
00:44 dcook I guess you could define a notice and have no delay...that could work
00:44 wizzyrea well you'd make the default no notices, and define notices for all branches?
00:44 eythian hmm, maybe peggy was using web-based IRC...
00:44 wizzyrea do note I haven't tried that.
00:46 dcook eythian: Good call
00:46 dcook wizzyrea: Makes sense to me in theory
00:46 dcook At the moment, I don't need true hard facts. Best guess is good enough.
00:48 peggy joined #koha
01:00 peggy I'm giving up for tonight.  jcamins, I hope you'll share your cookies!
01:00 peggy thanks, everyone for the help.
01:27 jcamins The shortbread looks beautiful.
01:28 dcook \o/
01:29 * dcook is debating whether to eat his packaged sandwiches or to grab laksa
01:29 dcook I could also do both...
01:29 onezero joined #koha
01:32 wizzyrea \o/
01:36 jcamins And, as per usual, the coffeecake has risen over the topping. :D
01:37 wizzyrea is that good?
01:38 jcamins Eh. It'd probably be more attractive if I could get the topping to stay on top, but it's delicious either way.
01:38 dcook All right. Gotta eat. brb
01:40 jcamins Oh dear.
01:40 jcamins In fact, it rose right over the pan.
01:41 dcook cakecano!
01:41 dcook fiery deliciousness
01:41 jcamins lol
01:46 dcook Mmm, yummy sammiches
01:50 mtompset joined #koha
01:50 mtompset Greetings, #koha.
01:51 mtompset Anyone here know how to trigger issung slips?
01:53 wizzyrea do a circ, click print button on toolbar
01:53 wizzyrea (not in firefox, in the circ toolbar)
01:59 mtompset Thanks.
01:59 mtompset Next question...
01:59 mtompset if I was generating news that goes on the slip based on branch...
01:59 mtompset would it be branch of the user logged in, or branch of the patron?
02:00 mtompset What do you think, wizzyrea?
02:01 wizzyrea oh branch of the circulating library
02:01 wizzyrea so logged in user
02:03 mtompset okay then... I think I can push up that patch then, amend the test plan, and go on my merry way. :)
02:03 mtompset Yes, the news by branch patch will affect slip printing. ;)
02:03 wizzyrea :) cool
02:40 mtompset :(
02:40 mtompset I hate finding other bugs as a result of testing.
02:50 eythian[…]page=22&zoom=auto,0,697 <-- they may want to update their docs a bit.
02:52 wizzyrea errrrrr
02:56 mtompset eythian: They've probably hired programmers who don't know how to write documentation. It is a skillset, you know. :)
02:56 eythian heh. I think it's more that it's just quite old and that aspect of it hasn't been updated.
03:08 mtompset Perhaps... oh shoot! If I have an opac_news items for a branch, and I have deleted the branch, what should I do? what should have been done?
03:09 eythian The news should have been deleted. If not, there's a constraint bug.
03:11 mtompset Hmm... how about warning on deletion of the branch?
03:11 wizzyrea why would you want to keep the news if you are deleting a branch/
03:13 dcook ^^
03:13 eythian yeah, that's why I figured just deleting the news is the best idea.
03:15 dcook @quote123
03:15 huginn dcook: I'll give you the answer as soon as RDA is ready
03:15 dcook @quote 123
03:15 wahanui @quote get 123
03:15 huginn dcook: downloading the Perl source
03:15 wizzyrea @quote get 123
03:15 wahanui
03:15 huginn wahanui: Quote #123: "rangi: #thingsihavelearnt if there is a mad scheme a library somewhere will be doing it ... except madder" (added by wizzyrea at 09:20 PM, March 30, 2011)
03:15 wahanui ...but quote #123: "rangi: #thingsihavelearnt if there is <reply>...
03:15 huginn wizzyrea: Quote #123: "rangi: #thingsihavelearnt if there is a mad scheme a library somewhere will be doing it ... except madder" (added by wizzyrea at 09:20 PM, March 30, 2011)
03:16 dcook So much this
03:16 dcook (Unrelated matter, perhaps)
03:16 wizzyrea we already ask for confirm on branch deletion
03:16 wizzyrea perhaps enumerating what will be deleted wouldn't hurt.
03:17 wizzyrea but... still don't see why if you go through all of that, why one would get mad about news going away that was defined for the branch you just deleted. Wouldn't one expect that?
03:17 eythian yeah, I'd think that'd be totally normal.
03:17 eythian Not deleting because there are items there, fair enough. You need to fix those.
03:17 eythian But news is no problem.
03:18 wizzyrea and if you start enumerating things that are to be deleted on branch deletion, people will get mad if something goes that wasn't warned about
03:18 wizzyrea so better to leave it vague I guess
03:18 eythian I reckon. Just make it do sensible things.
03:18 wizzyrea deleting the news is sensible.
03:19 mtompset Do constraints force deletes?
03:19 eythian depends on the constraint
03:20 eythian with ON DELETE CASCADE, yes
03:20 eythian without, no
03:20 mtompset So, I should have a ON DELETE CASCADE constraint on the opac_news branchcode that I'm adding.
03:20 mtompset right?
03:21 mtompset (less Koha code, more SQL smartness)
03:21 eythian well, it should have a foreign key reference to the branchcode
03:22 eythian that relationship have ON DELETE CASCADE attached to it.
03:22 eythian +should
03:25 KohaCanuck joined #koha
03:25 KohaCanuck Hi all
03:26 KohaCanuck Is there anyone on the channel with a technical background in Koha that might be able to help diagnose a weird issue?
03:26 eythian ask?
03:26 wahanui Don't ask to ask, just ask.
03:28 KohaCanuck Ok - The problem is this - I have a Koha installation that was working fine then I cleared the database and all seems to work except when I go to manage staged records after an import I have no buttons
03:29 KohaCanuck i.e. when viewing a batch in manage staged records I can see the list of records but no longer have the button to commit the load to the db
03:29 mtompset KohaCanuck: How did you clear the database?
03:30 KohaCanuck I have a script that I found online used by a Koha supplier - it just does a bunch of truncates
03:30 KohaCanuck I did a few loads after running this script and all was good
03:31 KohaCanuck This is a dev server so I can play around with this as necessary - I copied a working instance from the prod system too and still no change
03:31 KohaCanuck (using koha-restore)
03:32 KohaCanuck I can add items manually with no problem
03:32 wizzyrea http://koha.1045719.n5.nabble.[…]se-td3065836.html < this?
03:34 KohaCanuck no - it was a different script with all the tables specified individually
03:34 dcook I seem to remember having a similar issue but it was a while ago so I can't recall what happened in the end...
03:34 dcook KohaCanuck: Are you using a regular packages install or are you using koha-gitify?
03:35 wizzyrea[…]lean_database.sql < this?
03:35 KohaCanuck I saw the same issue posted by someone and they just reinstalled koha which I'd rather not do as I'd rather understand why it happened
03:35 dcook understanding++
03:35 KohaCanuck regular debian packages
03:36 KohaCanuck I'm a former system analyst/programmer/admin from many years ago - I'm just helping a local organisation getting their Koha system up as a favour
03:36 dcook Yeah, if you could paste a link to the script or paste the actual script using that would be helpful
03:36 mtompset If it is dev? why not drop the db and create it again, then go to the staff client and start from scratch that way?
03:37 KohaCanuck the script is here[…]lean_database.sql
03:37 KohaCanuck I've copied a working db from a production system which works fine and still have the same issue
03:38 KohaCanuck I've removed the dev instance altogether with koha-remove and restored from production using koha-restore - it came up and still the same issue
03:38 KohaCanuck I think its a Perl or Apache issue
03:38 * dcook doubts this
03:39 dcook Can you post some screenshots?
03:39 dcook You had it working at one point?
03:39 dcook Also, which version of Koha are you on? 3.14?
03:39 KohaCanuck yep - it was working fine after I ran the db clear script
03:39 wizzyrea are you using translations?
03:39 dcook After?
03:40 KohaCanuck Where can I post screenshots?
03:40 KohaCanuck Koha version:
03:41 wizzyrea (if the dev version is different from prod version, and you haven't updated the translations, it can cause wonkiness)
03:41 dcook KohaCanuck: Something like
03:41 dcook Interestingly enough, when I try to import on 3.15, I don't see any buttons either on my dev system
03:41 KohaCanuck I did wonder about that - they are different versions but I am struggling to get the older version on to the same version as prod
03:42 * dcook has played around with this DB way too much though
03:42 wizzyrea are you using translations?
03:42 eythian KohaCanuck: did you have buttons there before you did this?
03:42 KohaCanuck I don't think so - I'm not sure what translations are
03:42 eythian and: are you getting any javascript errors when you go to this page?
03:42 dcook ^^
03:42 dcook Also, KohaCanuck: What version is the prod system?
03:43 KohaCanuck yep the 'import this batch into the catalog' button is missing
03:43 dcook If you're trying to use a DB from different versions without upgrading your database, you'll run into problems
03:43 eythian dcook: you can't do that
03:43 eythian KohaCanuck: you can post screenshots to imgur
03:43 KohaCanuck Prod Koha version:
03:43 wizzyrea errr
03:43 dcook eythian: How do you mean?
03:44 wizzyrea you're importing a 3.12 db on a 3.09?
03:44 eythian you can't run with an old database. You don't have the option to.
03:44 eythian now going backwards is bad.
03:44 KohaCanuck ok I'm guessing this is the issue
03:44 * dcook bets so
03:44 wizzyrea ^^^^^^^
03:44 Dexas joined #koha
03:44 Dexas test
03:44 Dexas test
03:44 Dexas test
03:44 Dexas test
03:44 Dexas test
03:44 Dexas test
03:44 Dexas test
03:44 Dexas test
03:44 Dexas test
03:44 Dexas test
03:44 wizzyrea it works.
03:44 wahanui You should blog about it.
03:44 Dexas test
03:44 Dexas test
03:44 KohaCanuck so I tred apt-get update/apt-get upgrade to try and force and upgrade and it didnt work
03:44 Dexas test
03:44 Dexas test
03:44 Dexas test
03:44 Dexas test
03:44 Dexas was kicked by wizzyrea: User terminated!
03:45 eythian someone wann...
03:45 Dexas joined #koha
03:45 eythian ta
03:45 wizzyrea yw ;)
03:45 eythian KohaCanuck: what are your sources?
03:45 Dexas wizzyrea
03:45 wahanui wizzyrea is a Cylon, and they all have plans.
03:45 Dexas can u ban me for while
03:45 Dexas and unban
03:45 Dexas i check logger bot
03:45 wizzyrea Ah. I can. :)
03:45 Dexas wanna see something
03:45 Dexas thanks
03:45 eythian or: what's the whole output of apt-cache policy koha-common
03:46 wizzyrea Done (if you're checking the logs)
03:46 KohaCanuck koha-common:   Installed: 3.9-1~git+20120524174206.f9352e89   Candidate: 3.9-1~git+20120524174206.f9352e89   Version table:  *** 3.9-1~git+20120524174206.f9352e89 0         100 /var/lib/dpkg/status
03:47 mtompset 3.9?!
03:47 eythian You don't have an apt source configured
03:47 eythian so apt-get update won't work
03:47 KohaCanuck d'oh! Now I fell dumb
03:48 mtompset feel even. :P
03:48 mtompset It's okay. Obvious mistakes occur sometimes. :)
03:48 mtompset What is ibfk?
03:48 KohaCanuck indeed - my dumbness has affected my typing
03:49 wizzyrea oh did you install a package you built yourself?
03:49 mtompset I'm looking at constraints (reserves_ifbk_1 for example).
03:49 KohaCanuck I'm not that smart :) - I just grabbed a package online
03:49 eythian ifbk or ibfk?
03:49 wizzyrea oh you should use the official packages :)
03:49 wizzyrea packages?
03:49 wahanui rumour has it packages is at
03:49 eythian I think it's the name for a key anyway
03:49 wizzyrea ^^
03:50 mtompset I figure fk is shorthand for foreign key.
03:50 mtompset But what is ib?
03:50 eythian yeah, which is why I was confused because you didn't write that :)
03:50 dcook mtompset:[…]tand-for-in-mysql
03:50 dcook Search engines are rather rad
03:51 eythian lmgtfy++
03:51 KohaCanuck ok I'm going to add a source for the updates and see what happens
03:51 eythian you'll probably need to force-upgrade
03:51 wizzyrea it might be entertaining. :)
03:52 KohaCanuck ugh - if the server dies so be it - it'll free up the rest of my evening :)
03:52 wizzyrea you needed a night off. :)
03:52 dcook KohaCanuck: So I was just having the same problem as you
03:52 wizzyrea also, naah, it'll be fiiiiine
03:53 * wizzyrea couldn't replicate it
03:53 dcook (Actually, I was using a 3.15 database with 3.8 code...and had the same experience. It wasn't good.)
03:53 KohaCanuck the server is 10 miles away and its -30C out so I think I'll stay home :D
03:53 dcook hehe
03:53 wizzyrea ^ good plan
03:53 dcook What part of the country are you in, KohaCanuck?
03:53 KohaCanuck dcook did you just upgrade to fix?
03:53 eythian wahanui: could not reproduce is <reply>
03:53 wahanui OK, eythian.
03:53 Irma joined #koha
03:54 mtompset Silly me assumed it was some arcane Koha shortform, not in wide use.
03:54 dcook KohaCanuck: My situation is a bit different. I'm not using Debian/packages.
03:54 wizzyrea *snicker*
03:54 eythian bad dcook
03:54 eythian bad
03:54 dcook hehe
03:54 eythian no cookie
03:54 dcook :(
03:54 KohaCanuck Saskatchewan
03:54 dcook huh
03:54 wizzyrea what he said.
03:54 dcook That's where I'm from
03:54 mtompset Greetings, follow Canadian. :)
03:54 * dcook lives in Australia now though
03:54 mtompset FELLOW, even.
03:54 eythian wahanui: botsmack is <reply>Ow!
03:54 wahanui ...but botsmack is <reply>:(...
03:54 wizzyrea just not off a cliff.
03:54 eythian wahanui: botsmack is also <reply>Ow!
03:54 wahanui okay, eythian.
03:54 wizzyrea botsmack
03:54 wahanui Ow!
03:55 mtompset botsnack cookies
03:55 mtompset botsnack
03:55 KohaCanuck small world - which city dcook?
03:55 mtompset I thought there was a bot snack thing. :(
03:55 dcook Well, I lived in Saskatoon and Regina, but I'm a rural person
03:55 dcook Definitely a small world
03:56 dcook eythian: How do you manage multiple Koha instances using different versions?
03:56 eythian we very much try not to
03:56 wizzyrea @botsnack cookies
03:56 huginn wizzyrea: I've exhausted my database of quotes
03:56 * dcook is jealous
03:57 mtompset (it's a small world after all)
03:57 wizzyrea wahanui botsnack cookie
03:57 wahanui thanks wizzyrea :)
03:57 wizzyrea there it is
03:58 * wizzyrea corroborates eythian's story
03:58 pastebot "mtompset" at pasted "So is this my constraint clause to add?" (2 lines) at
03:59 eythian that seems like what you want
03:59 dcook I suppose a person could have a few Koha instances with a package install and then just make sure to use them with the right git tag...
03:59 wizzyrea hahahahahahahahahahahahaha
04:00 wizzyrea and as my final giggle for the day
04:00 wizzyrea
04:00 wizzyrea ^ just watched the deepsky video on the OLT
04:00 eythian dcook: yeah, we build all our packages with our own patches in them
04:00 eythian from a git repo, of course
04:00 dcook wizzyrea: lol
04:01 dcook eythian: That would be for production though, right? I'm thinking more in terms of dev work.
04:02 wizzyrea later kohan
04:02 wizzyrea s
04:02 wizzyrea let me try again
04:02 wizzyrea later kohans
04:02 dcook Kohans?
04:02 eythian Dev is in a VM on my machine. It doesn't use packages (because I built it before they existed)
04:03 eythian you can do that however you want, but staging and prod is package based.
04:04 dcook Makes sense
04:04 dcook I imagine you must have a company-specific and community-specific set up though, no?
04:04 eythian not really
04:04 eythian there's no need
04:04 eythian I have many git remotes though
04:05 dcook Do you use a fresh DB every time you're testing a patch in dev then?
04:05 eythian no, I usually just use whatever DB I have lying around.
04:06 eythian I may make changes to it for testing, or switch it out to another db if I'm not wanting the change the primary one.
04:06 dcook Wouldn't you run into issues like those above?
04:06 eythian No
04:06 dcook Of having newer code than your db?
04:06 eythian you can't have newer code than your db
04:06 eythian you can have newer db than code
04:06 dcook Sorry otherway around
04:06 dcook Yeah
04:06 eythian (but you shouldn't, it's bad.)
04:07 dcook Agreed. I'd like to avoid it in the future.
04:07 dcook But the only way I see it is to use a different DB each time
04:07 eythian It rarely causes issues, and if it does, then I change my db to an empty one.
04:07 bag well it's fine until you do a database call :P
04:07 eythian or an old one
04:07 dcook Mmm
04:07 eythian no, the schema doesn't change all that much
04:07 dcook In acquisitions and marc import it has
04:07 eythian I'm willing to be the missing buttons were totally unrelated to the database
04:07 dcook Those are the two main places I've noticed it
04:07 eythian sure, and in those places, I'll use a more appropriate database version.
04:08 eythian you know because it dies with an error about missing fields.
04:08 dcook Hmm, here's what happened with my missing buttons..
04:08 dcook I had a 3.15 database
04:08 dcook Staged the records as 3.8 and then had missing buttons
04:08 dcook Switched back to 3.15, staged a new batch of records, and had a fully functional interface
04:09 dcook No JS errors. But the code must've expected something and didn't get it
04:09 dcook Probably in relation to newer Koha handling importing for authority records
04:09 dcook But, that's just my guess
04:12 dcook Well, not in relation per se, but due to changes in data it expects now
04:12 dcook </ramble>
04:12 bag @monologue
04:12 huginn bag: Your current monologue is at least 1 line long.
04:12 wahanui i already had it that way, huginn.
04:13 bag @monologue dcook
04:13 huginn bag: (monologue [<channel>]) -- Returns the number of consecutive lines you've sent in <channel> without being interrupted by someone else (i.e. how long your current 'monologue' is). <channel> is only necessary if the message isn't sent in the channel itself.
04:14 dcook hehe
04:14 dcook I'll have to do that next time, bag ;)
04:26 mtompset are constraints up or down?
04:26 mtompset eg. branches and opac_news.
04:26 mtompset where do I add the constraint? opac_news, right?
04:27 dcook yarp
04:27 * dcook is fairly certain at least
04:28 eythian yeah
04:28 eythian you're saying "I depend on this other thing"
04:29 eythian you don't say "this other thing depends on me" because that would be hard to manage.
04:29 dcook ^^
04:30 dcook Just make sure that the field in opac_news has proper values in it already when adding the constraint
04:30 dcook Or else you'll get all manner of errors
04:30 dcook Well, warnings
04:30 wahanui warnings are nothing to worry about.
04:30 eythian they'll be errors and the contraint won't get applied
04:31 pastebot "mtompset" at pasted "Errors like this?!" (1 line) at
04:31 dcook That's what I was thinking, yep
04:31 mtompset But blank isn't a valid branch code. :(
04:32 eythian maybe...
04:32 wahanui i think maybe is a momentaneous error
04:32 eythian hmm
04:32 mtompset Guess I'll have to rethink how to do this.
04:32 eythian I think there might be a way to allow null
04:32 dcook Really?
04:32 eythian maybe
04:32 * dcook hasn't noticed one before but would be intrigued
04:32 eythian I'm not sure, I haven't ever done it that I know of
04:32 dcook If so, that could mean adding more constraints in Koha would be possible
04:32 dcook Which I can only think would be a good thing
04:33 eythian papa: do you know? you know these things often.
04:34 papa eh? which one in particular?
04:34 dcook Hmm
04:34 dcook mtompset: Is the opac_news column nullable?
04:34 papa not off top of my head
04:34 mtompset Not currently.
04:34 mtompset But it could be if that works. ;)
04:34 dcook Actually, what column in the opac_news table?
04:35 * dcook doesn't see a branchcode column
04:35 dcook I assume you're adding one?
04:35 mtompset Yes.
04:35 dcook If I read the interwebs correctly, that might do it mtompset
04:36 mtompset There's this "Match full/partial/simple" option.
04:36 eythian papa: I think you can, because "on delete set null" is a thing
04:37 eythian I think if the column is nullable, then you can have a null in there without breaking the relationship
04:37 eythian but a blank is not null
04:37 papa depends on the database
04:38 mtompset branches and opac_news with a branchcode column added.
04:38 eythian mysql in this case
04:38 mtompset you mean this wouldn't transfer across RDBMS well?!
04:38 mtompset Oh sucky.
04:39 eythian I dunno
04:39 dcook eythian: Good point about blank not being null..
04:39 eythian The easiest thing to do would be to test it
04:39 eythian then you know for sure.
04:39 papa postgres allows for foreign keys to be null, and does not check if it is null. mysql - I know I had some issues.
04:40 eythian well of course it had some issues, but did they affect this :)
04:41 mtompset I could always just delete matching branches, update matching branches in the C4::Branches, which is ugly.
04:41 eythian what?
04:41 eythian why not just set anything blank to null?
04:41 eythian and see if this works like that
04:42 mtompset I'll give it a go.
04:42 eythian and make sure that creating new items that would set it to blank instead set it to null.
04:42 eythian because if that works, that's the easy way that improves the health of the schema at the same time.
04:42 eythian but first, test it in mysql because that'll tell you in about 3 minutes if it's possible or not.
04:44 Oak joined #koha
04:44 * Oak waves
04:45 mtompset Greetings, Oak.
04:45 Oak hello mtompset
04:45 Oak how is it going?
04:46 pastebot "mtompset" at pasted "No errors! YAY!" (13 lines) at
04:49 eythian make sure it actually worked
04:49 eythian just to be safe :)
04:50 eythian you're also going to want to change any blank entries to null and make the logic understand that, etc etc.
04:51 papa do you want news that are not branch specific?
04:52 eythian I would expect so.
04:53 papa then all good
04:54 mtompset papa, yes.
04:54 mtompset NULL = every branch
04:54 papa ok, all good
04:56 mtompset well the upgrade gave me a column of NULLs.
04:56 mtompset how do I list constraints?
04:56 papa show create table
04:57 mtompset describe {table}?
04:57 papa show create table {table};
04:58 mtompset Ah... there we go. Constraint is shown. :)
04:58 mtompset Now to tweak the adding to not use '', but rather undef. :)
05:22 arunkumars3189 joined #koha
05:32 jenkins_koha joined #koha
05:32 liw joined #koha
05:32 ibeardslee joined #koha
05:32 halcyonCorsair joined #koha
05:32 mtj joined #koha
05:35 mtompset Woo hoo!
05:35 mtompset Thanks for the NULL idea guys.
05:35 mtompset This branch constraint is rather handy. :)
05:38 dcook contraints++
05:38 dcook constraints++
05:38 mtompset @karma contraints
05:38 huginn mtompset: Karma for "contraints" has been increased 1 time and decreased 0 times for a total karma of 1.
05:38 mtompset You're the first typo. ;)
05:39 mtompset Granted, I had to do ugly behind the scenes deleting to get a branch to delete, but when it did... news item went bye-bye. :)
05:40 dcook @karma constraints
05:40 huginn dcook: Karma for "constraints" has been increased 1 time and decreased 0 times for a total karma of 1.
05:41 mtompset Really?!
05:41 dcook Koha is lacking a bit in that department..
05:41 mtompset constraints++ # it should be way higher.
05:42 mtompset Okay... dumb question... I know the old way to add columns doing the and stuff...
05:42 mtompset How do I do it the DBIx way?
05:42 eythian if you're lucky, someone's put it in the wiki.
05:42 eythian You're probably not that lucky.
05:46 mtompset Nope. I don't think so.
05:47 dcook Someone might've done a write up about that from Kohacon
05:47 dcook Galen and Kyle talked a bit about that
05:47 dcook I'm trying to remember the discussion..
05:48 mtompset It's okay. I should have gone to bed an hour ago.
05:48 mtompset I'm just happy to have my code in a testable state for tomorrow.
05:48 mtompset (well later today)
05:48 mtompset Then I'll have a really nice News by Branch patch ready. :)
06:09 mtompset Have a great day (24 hour period), #koha.
06:09 mtompset Bye dcook eythian papa, etc.
06:09 papa bye
06:37 Oak mtompset++
06:38 Oak papa++
06:38 Oak eythian++
06:45 dcook night #koha
07:38 marcelr joined #koha
07:38 marcelr hi #koha
07:38 Oak hi marcelr
07:38 marcelr hi Oak
07:45 Sander joined #koha
07:45 Sander left #koha
07:46 Sander joined #koha
07:47 Sander Hi all!
07:47 Sander I have a question about Athority Control and Koha
07:48 Sander Is there a way to use an Automatic Authority Control Program to manage the Authorities in Koha?
07:49 reiveune joined #koha
07:49 reiveune hello
07:50 Sander hello
07:50 sophie_m joined #koha
07:52 Sander I mean: I need an Automation that when I add a not acceppted form to an authority search in all the biblio record and when it finds the not accepted form it replace with the accepted one
07:53 * Sander slaps bshum around a bit with a large fishbot
07:56 alex_a joined #koha
07:56 alex_a bonjour
08:19 gaetan_B joined #koha
08:19 gaetan_B hello
08:19 wahanui salut, gaetan_B
08:22 laurence joined #koha
09:01 nlegrand joined #koha
09:02 nlegrand Hello
09:14 paxed if i wanted to translate the marc21 field descriptions, would i copy installer/data/mysql/en/marcflavour/mar​c21/mandatory/marc21_framework_DEFAULT.sql and translate that?
09:15 paul_p joined #koha
09:15 cait joined #koha
09:19 busla joined #koha
09:24 paxed what's the '01e' tagfield in marc_tag_structure? (marc21_framework_DEFAULT.sql)
10:07 paxed ('243', 'a', 'Uniform title', 'Unifor title', ...
10:07 paxed ('943', 'a', 'Uniform title', 'Unifor title', ...
10:09 rangi ('243', 'COLLECTIVE UNIFORM TITLE', 'COLLECTIVE UNIFORM TITLE', 0, 0, '', ''),
10:09 paxed "Unifor title"
10:11 * paxed is pondering a way to automagically translate those texts.
10:11 samueld joined #koha
10:19 cait paxed: you are translating those on - right?
10:21 paxed cait: the marc field description names are not in po-files, afaik.
10:21 cait yes they are now
10:22 cait - you only have to drop bgkriegel a nice mail and ask for it to be added
10:26 paxed ah, ok. although i won't be using pootle, as i can grab the "official" translations from the national library's XML file, it'll be much easier for me to write a script to mangle them into the po-file.
10:31 paxed ....except it looks like the comments in the po-file aren't that useful in trying to match the text to a marc-field. *grmbl*
10:31 cait whatever you prefer
10:32 cait I am helping bgkriegel to make the po for marc files work and i think we are almost there now, one patch pending fixing some bad translations
10:32 paxed i prefer computers to automate tasks, not make me type more. :P
10:32 paxed ok, so you'd know about that...
10:32 paxed say... a comment like this:
10:32 paxed #: Bib Sub 100 f 110 111 130 240 243 400 410 411 600 610 611 630 696 697 698
10:32 cait bibliographic
10:33 cait field 100 f and others i think
10:33 paxed bibliographic data, sure, field 100f? 110? 111? is it the whole field, or some subfield?
10:33 cait i think 100f not sure about the others
10:33 cait i only looked up things with the first subfields, perhaps not ideal for atuomating yes
10:33 cait but it's easy to check with the sql file
10:35 paxed the comment really should list the exact subfield or just the field number if it's for the whole field.
10:36 cait it's a new thing
10:36 cait it works pretty well already, but I think patches will be accepted :)
10:36 paxed good thing you get comments on it before it gets put into action then... :P
10:37 cait it's still in a test phase
10:37 cait maybe try to take things offered with a bit more positivity?
10:39 cait it's a process and an alternative to translating the sql files
10:42 paxed sorry my positivity is a bit low - it just feels like Koha's translation process is nothing but fighting an uphill battle.
10:43 cait I have been translating it for years and there has been lots of process
10:43 cait it's  boring
10:43 cait especially the first time around
11:33 irctc949 joined #koha
11:33 irctc949 hi
11:33 wahanui hola, irctc949
11:33 irctc949 can you please suggest which envoirnment we have to use for customise koha
11:34 abhijit123 joined #koha
11:35 irctc808 joined #koha
11:36 abc123 joined #koha
11:37 irctc769 joined #koha
11:38 irctc769 left #koha
11:59 kivilahtio joined #koha
12:02 kivilahtio Hi there. I get cookies like this: 5o0pnktW: {"offset":61,"query":"idx=kw&q=rock","limit":"​","sort":"","pagelen":20,"results":[6804,6807,​6810,6811,6812,6815,6819,6825,6826,6840,6841,6​859,6861,6862,6864,6865,6866,6870,6871,6877]}
12:02 kivilahtio any idea where these come from? It is rather tricky as they overflow the browser cookie cache
12:02 kivilahtio and force the user to empty their cookies.
12:03 kivilahtio oh and I am browsing the catalogue/
12:03 kivilahtio so when we make repeated searches, we get more and more cookies in our browser history, named with this 8-character long hash
12:04 kivilahtio Heres another example.   8iT9mp2y: {"offset":1,"query":"idx=kw&q=rock","limit":""​,"sort":"","pagelen":20,"results":[1114,1178,1​363,1414,1444,1449,1480,1618,2365,2490,2512,27​79,2926,2999,3004,3005,3018,3197,3323,3507]}
12:07 kivilahtio hmm I think I got a lead from js/browser.js
12:15 cait kivilahtio: search history maybe
12:15 cait there is a bug for that
12:15 cait check bugzilla for cookie
12:15 cait bug 10952
12:16 huginn Bug[…]_bug.cgi?id=10952 major, P5 - low, ---, julian.maurice, Failed QA , Store anonymous search history in session
12:16 cait bug 10338
12:16 huginn Bug[…]_bug.cgi?id=10338 normal, P3, ---, oleonard, NEW , Search history can cause "Out of memory" errors
12:16 cait ok have to run, bbl
12:19 kivilahtio The problem we are encountering happens in the staff client. We encountered those ones in OPAC as well but disabling browsing history fixed it for us.
12:19 kivilahtio Still getting a cookie overflow from staff clients catalogue/
12:28 jwagner joined #koha
12:39 busla_ joined #koha
12:43 tomas_ joined #koha
12:44 tomas_ morning #koha!
12:48 collum joined #koha
12:58 francharb joined #koha
13:00 francharb Good morning Koha
13:02 busla joined #koha
13:02 meliss joined #koha
13:26 ebegin joined #koha
13:30 reiveune bye
13:30 reiveune left #koha
13:57 talljoy joined #koha
14:00 nengard joined #koha
14:11 NateC joined #koha
14:11 kivilahtio So no-one really is encountering this issue we are facing, where we get searchCookies from intranet-tmpl/js/browse.js? More specifically rows 32-40?
14:12 kivilahtio and these cookies fill up the browsers cookie jar and then our apache2 server fails to parse the query header?
14:12 kivilahtio This happens when multiple searches are conducted in the staff client
14:13 Dyrcona joined #koha
14:16 NateC left #koha
14:29 Dyrcona joined #koha
14:31 cait joined #koha
14:35 ashimema joined #koha
14:36 * cait waves
14:36 cait hi ashimema
14:36 ashimema Hello Cait
14:36 wahanui Hello Cait are you here?
14:36 ashimema wahanui never ceases to catch me out
14:36 wahanui ashimema: excuse me?
14:36 cait :)
14:36 ashimema fancy an easy QA cait.. but 6331
14:37 ashimema fancy an easy QA cait.. bug 6331
14:37 huginn Bug[…]w_bug.cgi?id=6331 minor, P5 - low, ---, fridolyn.somers, Signed Off , Obsolete marc column in deleteditems
14:37 cait not sure i will get to it
14:37 cait i am at my dad's
14:37 ashimema no worries.. hows the holiday going?
14:37 cait not sure how long i will be at the laptop :)
14:37 cait good :)
14:37 ashimema hope you've started relaxing now..
14:39 cait heh
14:39 cait i think i am starting to figure it out
14:39 ashimema good oh, I find it walways take's me a few days to wind down.. mostly I only have a few days off at a time so it doesn't work well.
14:40 ashimema either that, or I book myself something stupid to do to take my mind off work (think kayaking down crazy rivers in the alps, or hiking the inca trail.. I'de reccomend it)
14:40 * druthb waves to cait and ashimema.
14:40 ashimema good day druthb
14:41 cait hi druthb :)
14:41 cait ashimema: i think that's not the kind of thing that comes to my mind
14:41 cait I bought 2 new books :)
14:41 cait and visiting with friends and family... we went to a chocolate fair/market
14:41 ashimema such a library geek cait ;)
14:41 cait hehe
14:42 cait and played a ton of board games during the weekend
14:42 ashimema mmm. chocolate is always good however
14:42 kivilahtio which boardgames did you play?
14:42 kivilahtio cait?
14:42 wahanui cait: go to bed
14:42 ashimema the meeting I'm in is missing chocolate..
14:42 cait hm oddville
14:43 cait kugelfuhr (self published german game i think)
14:43 cait quirkle
14:43 cait carcassonne with various extensions
14:44 kivilahtio ok
14:44 * druthb suggests "Quelf."  Fun, silly game.
14:44 kivilahtio looks interesting
14:44 kivilahtio last I played was Resistance
14:44 kivilahtio maybe I could buy meself a new christmas present
14:44 kivilahtio :)
14:44 mrenvoize joined #koha
14:44 * druthb played "Cards Against Humanity" at the Thanksgiving party recently.  With five or six people in the game, that can be a *lot* of fun.
14:45 jcamins We played Munchkin on Saturday. That was also quite fun.
14:45 kivilahtio but seriously. Nobody is encountering searchCookie overdose when doing searches in hte staff client, namely catalog/
14:45 kivilahtio munchkin is!
14:45 mrenvoize I *love* ' Cards Against Humanity' druthb.. it's hilarious
14:45 kivilahtio jcamins: but with all the expansions... the card stacks are scary
14:46 druthb I have the first three expansions, and the Bigger, Blacker Box expansion.
14:46 mrenvoize
14:46 cait oddville is pretty nice
14:46 cait i haven't figured out the best strategy yet
14:46 jcamins Heh. We played with the original and one expansion.
14:46 cait it's probably the most 'advanced' of those 4
14:46 kivilahtio I could just progarm a small modification to periodically clean up extra searchCookies?
14:46 druthb I'm also becoming a Phase 10 fan, and have played Fluxx a couple of times, too.
14:46 kivilahtio I like Citadels
14:47 cait kivilahtio: the plan was to move them to the sessions
14:47 kivilahtio Also Dungeon Lords
14:47 cait did you see the bugs I posted earlier?
14:47 kivilahtio cait: inside OPAC
14:47 cait then the data in the cookies would be much smaller
14:47 kivilahtio cait: yes I did and I commented they are for the OPAC.
14:47 cait could be done in a next step - I don't think we have search history in staff yet?
14:47 kivilahtio we have no problems in opac, this is not a search history thing, I believe
14:48 kivilahtio every time we make a new search we get a new search cookie
14:48 jcamins This is the browser that allows you to page back and forth through results.
14:48 jcamins I never encountered a limit.
14:48 kivilahtio after 30+ searches apache fails to server
14:48 jcamins But I see no problem with making it so that it can be disabled.
14:48 kivilahtio jcamins: well it is pretty hard to break it but our head librarian is at my heels on this matter
14:49 kivilahtio and I guess when working you could easily make 30+ searches during one session
14:49 kivilahtio jcamins: I was thinking of removing all search cookies when a certain threshold is reached
14:49 jcamins kivilahtio: better would be to make it possible to disable it.
14:50 kivilahtio jcamins: to disable the cookie generation alltogether?
14:50 jcamins Right.
14:50 jcamins Make it optional with a system preference.
14:50 kivilahtio jcamins: I think it might prevent the next - previous buttons from working in the catalogue/
14:50 jcamins Of course it would.
14:50 kivilahtio jcamins: ah ok :) now I see your point
14:51 kivilahtio jcamins: So you think just removing extra searchCookies is a bad idea?
14:51 jcamins They won't show up if it's disabled, and you've maintained predictability.
14:51 jcamins Yes.
14:51 kivilahtio well I am not deleting hte cookie currently in use, but old cookies when a new one is created?
14:52 jcamins Because if you remove search cookies at unpredictable intervals, the user will encounter irregular, non-reproducible problems.
14:52 kivilahtio jcamins: yeah, that is horrible
14:52 jcamins The reason for the way the feature works is so that you can have multiple searches in different windows, and page through them all simultaneously.
14:53 kivilahtio jcamins: hmm, it's starting to make sense
14:53 kivilahtio jcamins: but I like that feature :)
14:53 kivilahtio jcamins: I wonder if there is a way to save that feature
14:53 kivilahtio jcamins: I guess we could increase our cookie limit in our apache2 config
14:54 kivilahtio jcamins: and our head librarian can have a automatic cookie cleaner plugin
14:54 kivilahtio :)
14:55 kivilahtio if we hit trooble then disable the cookie generation
14:55 kivilahtio jcamins: Any suggestions where I could document my finding regarding this searchCookie overflow?
14:56 jcamins Umm... we could maybe put it in the FAQ, not that it's a frequent question.
15:01 rocio joined #koha
15:06 kivilahtio I'll try to dokuwiki it after I get my account request approved.
15:09 tomas_ even when it is unlikely, if it is possible to build a cookie like that weneed to find a solution
15:09 cait kivilahtio: ah
15:09 cait give me a sec - i can approve
15:10 cait kivilahtio: approved
15:11 kivilahtio tomas_: well we could change the labeling of the searchCookie from "R3xkG3fT" to "sc<timestamp>" and then remove the last one?
15:12 kivilahtio jcamins: I guess this would preserve some predicatbility? Maybe you could set a system preference on how many cookies you want to sotre?
15:12 jcamins kivilahtio: that would make sense.
15:12 jcamins Or the timestamp.
15:13 kivilahtio jcamins: maybe both? It's not that hard to code
15:13 kivilahtio depedning on how easy it is to pull all cookies with jquery :)
15:13 kivilahtio but then it is yet another system preference, of which there are already too many
15:15 blou holà koha!
15:15 kivilahtio cait: Thanks for the verification!
15:15 kivilahtio blou: Hola!
15:16 blou too many system preferences?  That is a philosophical discussion.  I love those!
15:16 blou hi kivilahtio!
15:16 jcamins You could hardcode it at ten.
15:16 jcamins Or even three. The important thing is that the behavior be consistent.
15:16 kivilahtio jcamins: you think your multitasking librarians can settle for 10?
15:17 jcamins I think so, yeah.
15:17 kivilahtio jcamins: ok
15:17 jcamins The most common use cases are ~3.
15:17 kivilahtio jcamins: Thanks for your particiaption, I'll try to get it done tomorrow
15:19 blou Little question, before I send to it to the mailiing list: anyone has translation issue with the bootstrap theme?
15:20 tomas_ write to koha-translate directly
15:20 blou but the root issue is the programming (the .tt s)
15:21 blou but ok, I'll do that.
15:21 tcohen did u find untranslatable stuff?
15:21 blou A lot
15:22 drojf joined #koha
15:22 blou translate update doesn't catch stuff that is not between > < it seems, and there are a LOT of them now
15:23 blou the tts have been reformated (nicely), but that puts a lot of words not between > and < anymore, so they are not in the .po at all
15:23 francharb cait, hi!
15:23 francharb did you notice this as well?
15:23 francharb ^
15:25 kivilahtio Another day, another trial! Thanks #Koha for helping out!
15:33 jenkins_koha Starting build #143 for job Koha_3.12.x (previous build: SUCCESS)
15:52 meliss joined #koha
16:01 jenkins_koha Project Koha_3.12.x build #143: SUCCESS in 28 min: http://jenkins.koha-community.[…]/Koha_3.12.x/143/
16:05 rocio1 joined #koha
16:14 pablito joined #koha
16:18 pablito hi everyone
16:18 pablito Is it possible to checkout books by call number in Koha 3.14?
16:33 Oak joined #koha
16:48 cait blou: interesting - the <> not being on the same line should not be a problem- something not inside an html tag sometimes is
16:48 cait do you have an example?
16:48 Oak Guten abend cait
16:48 * Oak waves
16:49 cait Oak.
16:49 Oak :)
16:49 cait francharb: interested in the translation problem if you or blou are around
16:49 Oak it's abend there right?
16:50 Oak never mind.
16:50 wahanui Good, I'm glad you figured it out. I didn't understand, and probably never will, being a bot.
16:50 * Oak will annoy cait when she is free
16:52 ebegin cait, about the translation problem. I think we had a flow in our workflow and the problem is not in the translation itself
16:53 cait oh ok
16:53 ebegin s/flow/problem
16:53 druthb @quote random
16:53 huginn druthb: Quote #34: "<chris> oh except that time .. when katipo decided to write an ils just for fun, then forced HLT to use it" (added by gmcharlt at 06:23 PM, September 16, 2009)
16:53 ebegin s/flow/flaw :)
16:55 cait ebegin: so i can ignore the mail? :)
16:55 ebegin until further notice, yes :)
16:56 cait ah maybe sent ashort note?
16:56 cait :)
16:56 ebegin In progress :)
16:56 tcohen hi cait
17:00 cait hi tcohen :)
17:02 tcohen cait: what would you change on my patch for bug 10957?
17:02 huginn Bug[…]_bug.cgi?id=10957 trivial, P5 - low, ---, tomascohen, Failed QA , 710$a with 710$b (subordinate unit) present shows wrong (XSLT)
17:03 cait tcohen: sorry, I didn't have the time yet to get back to that
17:03 tcohen np, I'll try to remember what was it about
17:04 cait mostly irritating was that the logic for detail page and results seemed different
17:04 tcohen ok, and you mean it wasn't like that before
17:04 tcohen right :-) ?
17:05 cait no idea
17:05 cait probably it was - could you try the exampe you noted and see if you are happy with how it displys`
17:05 tcohen i will
17:17 cait hm
17:17 cait someone an idea for a good syspref name for not showing who managed a suggestion?
17:17 talljoy joined #koha
17:17 cait in theopac that is
17:18 cait OpacShowSuggestionManagedBy ?
17:18 cait OpacSuggestionShowManagedBy?
17:19 pianohacker joined #koha
17:19 cait OpacSuggestionManagedBy
17:22 maximep joined #koha
17:33 onezero joined #koha
17:36 tcohen bug 9114
17:36 huginn Bug[…]w_bug.cgi?id=9114 enhancement, P5 - low, ---, tomascohen, Needs Signoff , exported MARC frameworks encoding should be UTF-8
17:45 tomas_ joined #koha
17:45 cait bug 10907
17:45 huginn Bug[…]_bug.cgi?id=10907 enhancement, P5 - low, ---, oleonard, Needs Signoff , Showing the staff members name who managed a suggestion should be optional
18:01 gaetan_B hmm, why is the itemtype dropdown menu for suggesting a purchase not the list of itemtypes?
18:03 ebegin gaetan_B, good point. I think that was the case before, wasn't it ?
18:04 gaetan_B i remember it caused a debate not so long ago
18:05 gaetan_B but maybe not here
18:05 ebegin The only thing I can think of is to prevent user to be overwhelmed with too many choices...
18:06 gaetan_B in that case we should just hide the menu, but not show an empty menu
18:09 francharb gaetan_B, I guess it was a joke
18:09 francharb ;)
18:09 gaetan_B aaah irc jokes ;)
18:10 ebegin gaetan_B, I didn't look at it, but does it currently use a auth. value ?
18:13 cait gaetan_B: maybe check your advancedsearchtype setting
18:13 cait i think there is an unfixed bug in that area that also influences the suggestion from
18:13 gaetan_B aaah thanks cait
18:13 gaetan_B this is waht i was thinking of
18:13 gaetan_B advancedsearchtype
18:13 gaetan_B :)
18:14 cait i think we still have some weirdness happening since we changed that from being 2 choises to multi value
18:20 nengard joined #koha
18:25 laurence left #koha
18:25 Dyrcona joined #koha
18:34 gaetan_B it's bug 9223 if you were wondering
18:34 huginn Bug[…]w_bug.cgi?id=9223 normal, P5 - low, ---, fridolyn.somers, In Discussion , Multiple values of AdvancedSearchTypes in suggestions
18:36 cait @later tell Joubu - could you take another look at bug 11248?
18:36 huginn cait: The operation succeeded.
18:38 cait gaetan_B: btw - isn't it really late for us? :)
18:39 gaetan_B cait: it is :'(
18:39 francharb it is! Time to brush your teeth and go to bed!
18:39 francharb ;)
18:40 gaetan_B also today my soundsystem started making unwanted noise
18:40 gaetan_B which makes it a really bad day
18:40 gaetan_B !
18:41 cait :(
18:47 francharb :(
18:56 rangi morning
18:57 cait morning rangi
18:57 gmcharlt hi rangi
19:00 pianohacker yo rangi
19:01 rangi gah
19:01 rangi criticism_without_positive_suggestions--
19:09 NateC joined #koha
19:19 francharb hi rangi!
19:20 francharb I just read Joubu's email
19:21 francharb It sounds like he is trying to figure out how things works for other developer
19:21 francharb It's positive in a way
19:22 francharb questionning yourself to see if you can do better
19:22 francharb it's what I read between lines
19:23 francharb I hope other developers will share how they feel about developing in koha community
19:23 gmcharlt that's a charitable interpretation; however, there are more productive approaches for identifying and working on problems, IMO
19:23 francharb maybe that will lead to suggestions for better integration...
19:24 francharb gmcharlt, maybe
19:24 francharb gmcharlt, I would like just to remind that english is not our first langage
19:25 francharb and maybe, in french it wouldnt sounds this way
19:25 francharb I'm never sure if my english is understood the way I wanted tom for example
19:25 francharb ;)
19:25 gmcharlt francharb: it is difficult to know without seeing the original French, as it were
19:26 francharb for sure
19:26 gmcharlt of course, not that Joobu was necessarily composing in French, then translating ;)
19:26 francharb and there is also a cultural way of adressing problem that doesnt helop
19:28 gmcharlt well, that's potentially a large point -- there are circumstances where accompanying suggested solutions with the complaints is more likely to be better received
19:28 gmcharlt and, of course, circumstances (even within the same culture) where such a requirement is an undue burden
19:29 francharb I need to go back to work! But I hope we will have a time to talk about it later
19:29 francharb :)
19:34 rangi heres what i have been working on, to try and help
19:34 rangi
19:34 rangi all bugs needign signoff, in date order
19:34 rangi colour coded by severity
19:35 jcamins Nice!
19:35 rangi if you mouse over youshould get the description
19:35 rangi if you click it should claim
19:35 rangi what i need to do is make that claim stick
19:35 rangi (and then time out)
19:35 rangi so an easy way for people to see what bugs others are looking at, to stop double ups
19:35 rangi and and easy way to spot ones to sign off in general
19:37 rangi like bug 7376
19:37 huginn Bug[…]w_bug.cgi?id=7376 critical, P5 - low, ---, olli-antti.kivilahti, Needs Signoff , Transfer limits should be checked at check-in
19:37 rangi ill try to finish that off in my spare time, hopefully tonight
19:40 drojf oh that's nice!
19:41 rangi another thought i had
19:43 rangi is to do the same for signed off
19:43 rangi but colour code them by who in the qa team is eligible
19:44 rangi cos when i was doing qa, i used to click on things and then go, oh, thats a catalyst patch
19:44 rangi or oh a catalyst person signed that off
19:44 rangi and have to go look for another one
19:45 francharb ++
19:45 drojf regarding the email, i think it is ok to get things off your chest even if you do not have solutions. i see a little undertone of "let's complain together" instead of "find solutions" but i assume that is not how it is meant. i don't see how questioning gmcharlt in that context is ok or in any way helpful though, given that he donates his time to be RM.
19:46 francharb That's the awkward part. I agree. ;)
19:47 gmcharlt drojf: to be fair, the fact that I spend time on being RM, both with the support of my employer, and spending my own personal time on it, does not excuse me from criticism
19:48 gmcharlt but one thing I will say is this: I am intentionally taking stability of master as among my top concerns
19:48 rangi stability++
19:49 gmcharlt I will also say this as a general statement: I'm not at all a fan of overemphasizing expedience as opposed to coding a new feature thoroughly
19:50 gmcharlt and I also believe that a sufficiently bad implementation of a new feature, no matter how desirable the feature, should /not/ go into Koha if it would cause problems of severe technical debt down the road
19:50 gmcharlt I *am* a fan of small patches that implement large features in an iterative fashion (hey, tell the RM a story!)
19:51 gmcharlt but I do acknowledge that there is room for improvement -- and that includes in myself
19:54 rangi if there wasnt, we'd all be bored and leave :)
19:56 onezero joined #koha
20:00 bag :)
20:07 * cait just wants to state that she never got any cookies.
20:08 drojf gmcharlt: i did not mean you can't be criticised. :) but as RM you are in charge of making decisions, and the one not to push everything immediately that is in the queue has been communicated before, at least it was not news to me. and i think these questions should not have been part of this particular email.
20:09 * cait wonders if brendan has the right address and goes to read irc backlog
20:10 gmcharlt cait: maybe ask your next door neighbor? ;)
20:10 cait !
20:10 cait i might have to do that :)
20:10 cait did you get your coookies? :)
20:10 drojf "fe fif nof geff any cookief"
20:11 gmcharlt cait: sadly, they seem to be stuck at customs between the nation of California and the country of Upper Cascadia ;)
20:11 bag cait I perfer to hand deliver them
20:11 cait bag: I really have to get to go to marseille then... :)
20:12 * cait eyes drojf suspiciously
20:12 * drojf chews slowly
20:16 KohaCanuck joined #koha
20:18 KohaCanuck Hi all, I'm wondering if anyone can shed any light why my dev koha system has started to look like this after an upograde
20:18 wizzyrea you probably want to shift + refresh
20:18 wizzyrea clear your cache
20:18 wizzyrea ot
20:18 wizzyrea it is because the underlying framework for the javascript has changed, and you need new copies.
20:19 KohaCanuck it does it in all different browsers I have
20:19 wizzyrea yep, all browsers you've loaded koha in before?
20:20 gmcharlt KohaCanuck: I also suggest checking the javascript console of your web browser
20:20 wizzyrea ^ and that
20:20 KohaCanuck ok will try those suggestions - thanks!
20:24 jcamins KohaCanuck: alt-refresh is necessary on Chrome.
20:25 gaetan_B ok time to go brush my teeth and go to bed
20:25 gaetan_B bye !
20:25 cait sleep well gaetan_B :)
21:05 eythian hi
21:05 cait hi eythian :)
21:06 eythian hi ciat
21:19 ebegin A question I have since a long time and never dare (or had time) to ask
21:19 gmcharlt *drumroll*
21:20 wizzyrea ask?
21:20 wahanui Don't ask to ask, just ask.
21:20 ebegin Why do we use the MARC21 952 fields instead of852 for holdings ?
21:21 gmcharlt ebegin: one answer (besides potentially being just an accident of history): standard MARC21 852 fields aren't all that great at representing a full item record
21:21 cait hm i think because 852 don't have all the things we want to do could be one reason
21:21 cait gmcharlt++ # always having the better explanations :)
21:22 ebegin That what I expected. However, we could have use the standard 852 and add our additional custom subfields in 952... (don't think I want to change everything)
21:22 ebegin Just want to know the reason.
21:23 cait ebegin: i think splitting up on 2 fields would only confuse things
21:23 gmcharlt ebegin: doing that is not implausible, but would have made record processing more difficult
21:23 cait having one line for one item is much less error prone
21:23 gmcharlt since you'd have to keep track of pairs of fields for each item
21:23 * cait nods
21:23 gmcharlt also, I am in Germany today, and cait is in Seattle
21:23 gmcharlt apparently ;)
21:24 cait huh?
21:24 cait sorry, i didn't want to interrupt
21:25 gmcharlt cait: just that we seem to be occupying the same head at the moment :)
21:25 cait oh :)
21:27 kenan24 joined #koha
21:32 cait gmcharlt: if you are in the same head ... could you send some thoughts in my direction on how to fix the bug i am working on? :)
21:32 gmcharlt "Use the Source, Cait!"
21:33 wizzyrea *snicker*
21:33 wizzyrea <3
21:33 drojf joined #koha
21:33 gmcharlt cait: seriously, which bug?
21:33 cait ah, just something small actually
21:34 cait bug 5010
21:34 ebegin cait, change you == by eq in your comparison
21:34 huginn Bug[…]w_bug.cgi?id=5010 normal, P5 - low, ---, gmcharlt, NEW , Incomplete links in carts and lists sent from the staff client
21:34 cait ebegin: good one :)
21:34 * ebegin is guessing
21:34 cait some of the cart/list emails have incomplete urls
21:34 cait those have the opacbaseurl defined in the .pl file as well... but not the same it is in auth
21:36 cait i am just a bit confused i guess :)
21:39 gmcharlt cait: one issue re your last comment -- constructing a base URL using $ENV{'SERVER_NAME'} from the *staff* interface won't necessarily give the correct result
21:39 cait hm we acutally have links into the opac for the intranet mails as well
21:39 gmcharlt e.g., it's quite common for staff and OPAC interfaces to have different base names
21:40 cait but... it doesn't use the pref at all
21:40 cait which seems also bad
21:40 cait so i think neithe rof the currently implemented ways is correct
21:40 cait ew.
21:40 eythian yeah, there are complications with both.
21:41 gmcharlt especially since there's no guarantee that a given Koha catalog won't have a *bunch* of different OPAC and staff base URLs
21:42 cait ok, now it gets really ugly
21:42 eythian yep, we have one setup that has two for each.
21:42 cait ok, what can I do?
21:42 cait i think fixing for multiple opac interfaces... is too hard... couldn'tyou use the new apache sys pref rewrite thing in that case?
21:42 cait setting different OpacBaseURLs for each?
21:42 rangi[…]lay.html?id=91286
21:43 eythian probably, yeah.
21:43 rangi my first cpan patch in a while
21:43 cait yay :)
21:43 * rangi is using Catmandu to throw things into elasticsearch
21:43 gmcharlt cait: yeah, that would be a reasonable approach without having to write code
21:43 cait rangi++
21:44 cait so if I got it working... and using the pref
21:44 rangi its even actually working
21:44 cait rangi: elastic search? woohoo
21:44 rangi indexing
21:44 wahanui indexing is done by Zebra.
21:44 rangi and basic search anyway
21:44 cait wahanui: not necessarily ;)
21:44 wahanui cait: sorry...
21:44 cait sounds like a good start
21:46 cait would something like this work?             OPACBaseURL               => ($in->{'query'}->https() ? "https://" : "http://") . C4::Context->preference("OPACBaseURL");
21:46 cait assuming that a port would be added into the pref as well?
21:47 nengard left #koha
21:47 pastebot "rangi" at pasted "Now saving a biblio updates the index (if you have the syspref on)" (37 lines) at
21:47 rangi im happy in it's simplicity
21:49 cait and should I touch or better have it in the .pl files... and leave the line alone for now?
21:49 cait not sure what it#s used for
21:51 cait hm looks like it was added with the multiple PAC interface support
21:53 rangi[…]ds/elastic_search  <-- for people playing at home
21:53 gmcharlt rangi++
21:54 cait rangi++
21:54 cait will try to add it only to the .pl files
21:54 rangi im not utterly decided on the module names/layout .. and wont be at all offended of any suggestions of a better layout
22:05 cait grepping for OPACBaseURL we do harcode http a lot all over the place
22:08 rangi yeah
22:09 ebegin Couldn't we add the http or https in the syspref ?
22:09 cait i wonder if in a first step i could just make it all rely on what we have in
22:09 cait and then we could centrally fix that
22:09 cait that would make the list email link behave the same as the cart email link in opac... as the cart email already uses the way
22:10 cait ebegin: i thik we removed it from the pref in the past... but i have no idea why
22:10 papa joined #koha
22:11 ebegin we did that for a another product too. We just switch in adding the http/https in our settings
22:11 cait i don't exactly remembe why it was removed
22:11 cait maybe because some are using a mix?
22:11 cait like running the patron account with https but the normal opac pages not
22:12 gmcharlt cait: ebegin: I suspect the reasoning was to make it easier to tack on http or https if a catalog supported both
22:12 cait :)
22:16 BobB joined #koha
22:22 francharb bye all
22:55 dcook joined #koha
23:09 maximep aaaaaaaaaaaaaaah I hope out z39.50 search in OPAC isn't a duplicate :/
23:10 cait sorry maximep
23:10 maximep it's several years old, but we only just got to share it :/
23:11 cait it's the danger in doing that :(
23:11 maximep :'(
23:12 rangi maximep: it kinda is unfortunately
23:13 rangi hopefully there's bits of both that are useful
23:13 maximep pretty sure we did it differently
23:13 maximep fred will look at it friday
23:44 maximep left #koha

| Channels | #koha index | Today | | Search | Google Search | Plain-Text | plain, newest first | summary