Time Nick Message
00:22 rangi heh
00:22 rangi @wunder wellington nz
00:22 huginn rangi: The current temperature in Wellington, New Zealand is 14.0�C (1:00 PM NZDT on March 25, 2011). Conditions: Clear. Humidity: 82%. Dew Point: 11.0�C. Pressure: 30.06 in 1018 hPa (Falling).
00:35 brendan_ yup NZ and rangi win again
00:36 rangi :)
02:25 jcamins_away brendan/bg: around?
03:12 AmitG hi chris
03:18 gimireh hello
03:18 wahanui que tal, gimireh
03:23 kmkale Namaskar #koha
03:46 gimireh i have running koha 3.005 version on ubuntu 9.10 server, the system was working fine but now bib items are not recorded on db
03:47 gimireh i think this appeared after we had a bulk import of bibliographic items
03:49 gimireh items don't show in items tab of catalogue but when i click on edit item, there is list of items there
03:49 gimireh any idea what is happening
04:26 brendan_ hi AmitG
04:29 AmitG heya brendan_\
04:29 AmitG heya kmkale
04:37 kmkale hi AmitG
04:37 kmkale hi brendan_
04:38 brendan_ heya kmkale
04:38 AmitG heya kmkale india vs pakistan
04:38 AmitG you saw yesterday match
04:39 Oak hehe, Pakistan *can* win
04:39 kmkale AmitG: partially. only the last few overs
04:40 AmitG heya Oak
04:40 AmitG India wins
04:40 kmkale yup India pak gonna be tense match
04:40 Oak heya AmitG
04:40 AmitG yes
04:40 AmitG now most people on half day leave
04:40 AmitG on 30 march
04:40 AmitG india vs pakistan big match i m right kmkale
04:42 kmkale yup
04:42 kmkale currrent form pak 70:30
04:42 AmitG means kmkale
04:42 AmitG pak 70 india 30
04:43 kmkale IMHO
04:43 Oak Pakistan can't chase 300+ easily I fear... and Indian batting line up is looooong
04:43 kmkale Oak: Pak has about the best bowling attack currently
04:43 Oak I know :)
04:44 Oak so very interesting
04:44 Oak scenario
04:44 kmkale but India vs Pak brings out the best in everybody so hoping for the best :)
04:44 AmitG yes ur right Oak
04:44 AmitG Oak: r u from which country
04:44 Oak Pakistan
04:44 wahanui Pakistan is Nepal now, unless I missed something. Yes?
04:44 AmitG Oak r u from pakistan
04:44 Oak wahanui, you are mistaken
04:44 wahanui ...but wahanui is a bot...
04:44 Oak yes AmitG
04:44 AmitG your real name
04:45 Oak why would I do that AmitG ?
04:46 AmitG wahanui : u mean pakistan is nepal?
04:46 wahanui i don't know, amitg
06:51 cait hi #koha
06:52 brendan_ heya cait
06:53 cait hi brendan_
07:03 jransom heya Cait, Brendan
07:05 cait hi jransom
07:09 AmitG heya jrasnsom
07:09 AmitG heya cait
07:09 AmitG jransom: today SA vs NZ
07:10 cait hi AmitG
07:12 jransom hi Amit
07:22 rangi evening
07:22 jransom hey Chris
07:31 cait hi rangi
07:41 cait ok, time to go
07:50 AmitG heya sophie_m
07:51 sophie_m hello #koha
07:53 julian hi #koha
07:55 AmitG heya julian
08:13 kf hi #koha
08:19 AmitG heya kf
08:20 kf hi again AmitG :)
08:44 jransom Paul :)
08:50 kf hi paul_p and sophie_m
08:50 kf sophie_m++ for fixing the english message names :)
09:30 kmkale Namaskar #koha
09:32 kf hi kmkale :)
09:33 kmkale hi kf
09:35 kf rangi: still around?
10:37 * kmkale waves at druthb
10:37 druthb hi, kmkale. :)
10:38 * kf waves at druthb :)
10:40 druthb o/
12:14 AmitG heya nengard, jwagner
12:14 jwagner Hi AmitG
12:15 nengard hiya
12:16 AmitG heya nengard
12:25 kf wizzyrea: around?
12:26 kf @later tell wizzyrea http://git.koha-community.org/gitweb/?p=koha.git;a=commit;h=b7270536e42ced349fdbf72d63c795f4d4eb6384
12:26 huginn kf: The operation succeeded.
12:28 * druthb hands NateC the Velcro
12:28 NateC Why thank you
13:20 magnuse wanted: an example of a live opac with lots of branches
13:22 sekjal magnuse: does the dropdown for branch selection need to be on, or do the branches just need to be configured in the system?
13:22 magnuse sekjal: both would be interesting
13:25 sekjal http://catalog.nexpresslibrary.org/ has the dropdown
13:25 sekjal http://masscat.bywatersolutions.com/ does not
13:27 kf magnuse: nekls?
13:27 kf ah, I am too slow
13:27 magnuse yeah, should have thought about that - thanks sekjal!
13:28 danke i'm on koha 3.0, and when i genrate barcodes with low numbers... the width overruns the layout. is this bug fixed in later versions? i can't find anything
13:28 sekjal welcome, magnuse!
13:28 sekjal danke: Koha 3.2 has a significant rewrite of the label creator
13:29 danke excellent... how easy is the upgrade path?
13:29 sekjal very
13:29 danke how about moving onto a new machine? it's on a minitx box at the moment!
13:29 danke :)
13:30 sekjal danke: that would also be doable. dump your database on the old system, note your configurations, then do a fresh install on the new machine
13:30 sekjal upload the database, and the installer will update it's structure for you
13:30 danke wow, excellent. so literally everything i need is in the mysql db?
13:30 danke like... running mysqldump will be a good backup of the system?
13:31 sekjal yes
13:31 sekjal it's a very good backup
13:31 danke haha, yes. i love open source
13:31 danke thank you!
13:31 sekjal restoring from it, you'd need to rebuild the indexes, which takes time, but is all scripted
13:31 danke to be expected really
13:31 sekjal danke: you're very welcome. let us know if anything comes up in the process
13:32 danke will do, thank you
13:32 kf hi danke
13:32 kf are you from germany?
13:32 danke nope, the uk
13:32 kf ah, your name means thank you in German
13:33 danke yep. my actual name is dan keast, i've always liked that chopping the end off does that
13:33 kf :)
13:35 magnuse does anyone else have the left hand menu right at the bottom of this page - or is it just me? http://wiki.koha-community.org/wiki/Newbie_guide (FF 3.6.16 on OS X)
13:37 ebegin magnuse, I do have that too
13:37 ebegin FF4 on XP
13:38 magnuse hm, that menu is misbehving on some other pages too - i wonder why
13:43 nengard webinar time
13:43 nengard ttyl
13:55 wizzyrea ooo
13:56 wizzyrea one of my librarians just found a bug on additem.pl
13:56 sekjal wizzyrea: do tell!
13:57 * wizzyrea goes to file a bug
14:00 wizzyrea so if you have an item that is checked out
14:00 wizzyrea and you mark it lost on additem.pl
14:00 wizzyrea it will mark it lost, but not check it in (wrong)
14:01 wizzyrea if you do it from the moredetail.pl, when you mark an item lost it checks it in and puts the fee on the patron's account (right)
14:02 wizzyrea mind you, I've tested this on my production, not on my dev box... I"m going to go do that now.
14:05 danke would it be better to run the upgrade, then migrate to a new machine or vice versa?
14:06 sekjal wizzyrea: sounds familiar
14:06 danke ... i take it that the system wont detect the database is for an old version, and it's the upgrade which does the db modifications?
14:06 wizzyrea when you fire up your intranet for the first time it will detect you need a db update
14:06 sekjal danke: the Koha code itself checks to see if the DB version matches the code version
14:06 sekjal if the DB is out of date, it gets upgraded
14:06 wizzyrea ^^
14:07 danke so i can just put the database onto a new server, and install the latest version... everything is handled for me?
14:07 sekjal if the code is behind the data, though, there is nothing for that except to upgrade to match the DB
14:07 sekjal danke: yes
14:07 danke wow... that's really considerate programming
14:08 sekjal written by some really smart people
14:13 wizzyrea bug 5953
14:13 huginn 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5953 normal, P3, ---, gmcharlt, NEW, LOST status not behaving correctly from additem.pl
14:14 wizzyrea how big is your DB, danke?
14:17 wizzyrea (i ask because if it's largish, you might want to run updatedatabase.pl from the command line so it doesn't time out)
14:17 wizzyrea (especially if you're coming from 3.0)
14:22 sekjal danke: I'd recommend running it from the commandline, regardless of size, if you're doing that big an upgrade. Shows the update in real-time, which is more satisfying
14:22 sekjal to my mind, at least
14:23 wizzyrea hehe
14:23 wizzyrea that's a really good rason
14:23 wizzyrea reason, even
14:51 danke sorry, had to run off for a bit... i'm not sure how big it is now, the db was filled on the test machine without me... pretty small though i reckon
14:51 danke it's the toy library for the childrens center for a small town
14:52 danke ah, that's quite handy actually... was considering using the koha live cd to setup the new machine quickly. being able to do it from the commandline would be nice
14:52 rhcl नमसà¥à¤¤à¥‡ #koha
14:55 danke can i add images against items in the library?
14:55 wizzyrea I thought jcamins was working on something like that but it was ages ago... afaik that function isn't currently in koha
14:56 danke ah, okay. it's not important really
14:56 wizzyrea (you mean a la adding your own images for your records, right?)
14:56 wizzyrea (in place of say, amazon or google images)
14:57 danke yeah, that's it. a lot of them are toys, so an image would help cataloguing
14:57 wizzyrea I can definitely see how the images would be of use in a toy library
14:58 * wizzyrea imagines a terriffically complex batch import procedure for mapping bibnumbers to photos with filenames to correspond... brain melts down.
14:58 danke haha, yeah... there's the rub
14:58 danke it's that or blob fields. ech.
14:59 wizzyrea batch assigning the file names alone
15:00 wizzyrea that would be a big project.
15:00 wizzyrea if only toy manufacturers would agree on a standard set of metadata to assign to every toy...
15:00 danke sometimes they can be the most fun... i wish i had more spare time
15:01 danke "made in china"... haha, don't think that's going to happen
15:01 wizzyrea :)
15:01 wizzyrea with a unique identifying number!
15:01 wizzyrea 10 digits would be enough? right?
15:01 * wizzyrea repeats past foibles
15:02 wizzyrea sorry sorry, it's probably not clear that I'm in a snarktastic and sarcastic mode this morning
15:03 wizzyrea so don't take anything like the above ^^ seriously ;)
15:04 danke nah, i get it. it would be amazing though... maybe you could give them unique ipv6 addresses
15:04 wizzyrea well it would be nice, actually
15:05 wizzyrea for every toy
15:05 wizzyrea to have metadata regarding who made it, where it was made, what it's made of
15:06 wizzyrea some of that's on the package, but it's not formalized
15:06 danke yeah, i don't think any of these have any packaging left
15:06 * wizzyrea is thinking of the online stores who would benefit.
15:07 danke I'm geniunely wondering about what to do about children eating the barcodes off of them too
15:07 danke maybe just a folder with photos to store them instead of on the toys themselves
15:07 wizzyrea a bag with the barcode on it?
15:08 wizzyrea I think that' what our library that has a collection of cake pans
15:08 wizzyrea does
15:08 wizzyrea cuzn you can't bake the barcodes
15:08 danke these are babies to about 6 year olds... they'd probably eat the bag. haha
15:09 wizzyrea or suffocate :P
15:09 wizzyrea which would be worse
15:09 danke i'm just a parent, the libraries been requested as parents are erm... acquiring toys
15:09 danke yeah, debatable :p
15:09 danke haha
15:11 wizzyrea well, you could put a photo of the toy inside the bag, take the toy out of the bag at circ time, then keep the bag behind the desk until the toy comes back
15:12 wizzyrea i.e. don't give the bag to the patron
15:12 wizzyrea why yes, I might be hung up on bags.
15:12 danke haha, nah it's a good idea
15:12 danke though some of the toys are massive
15:12 wizzyrea wouldn't work for those obviously
15:12 danke like... toddler bikes etc
15:12 wizzyrea superglue?
15:12 wizzyrea epoxy over the barcode?
15:13 wizzyrea varnish?
15:13 danke yeah, that's a good idea
15:13 wizzyrea you didn't know you were going to be in for a deluge of how to fix your problem suggestions when you logged in this morning, did you :)
15:14 * wizzyrea also has a 3 year old, can imagine the challenges of circulating toys with anything even remotely removable on them
15:14 danke haha... so far my two year old has broken the tv, the oven, our speakers, and the wii
15:15 wizzyrea !!!!! your kid trumps my kid in the destructive department
15:15 danke some kind of nuclear defense strategy probably wont keep anything stuck to these toys
15:16 danke the oven was a genius one... when we weren't looking he'd shoved a teaspoon between the top of the oven and the worktop.... it's a fan oven and the teaspoon slowly got juddered back until it fell on two electrical contacts
15:17 wizzyrea !!! that stinks lol
15:17 danke haha, tell me about it. a replacement element is £50
15:18 wizzyrea (in our house the oven is a strict "don't go there" area. We make him stand on the carpet about 5 feet away when it's open, and he doesn't really go near it even when it's off because it might be hot... he learned that the not-damaging-but-hot-enough-to-sting way)
15:19 wizzyrea (he touched the outside of the oven one day when it was on)
15:19 danke haha, that's the ticket
15:19 wizzyrea ("oh!" lightbulb "It's HOT!"
15:20 danke i mean... the oven is left switched off at the wall whenever he's near it... never thought about the evil genius spoon tactic
15:20 wizzyrea yea, that's pretty ingenius, I have to say
15:21 kf magnuse?
15:24 * kf tries summoning magnus_away
15:30 * wizzyrea imagines kf doing some sort of norwegian summoning ritual, giggles
15:31 mib_ilomdd Does anyone know if there is a way to globally change the patron message settings? I need all Patrons to get overdue email!
15:31 mib_ilomdd For some reason they're all set to off
15:37 kf lol
15:37 kf wizzyrea: found the cause of my problem (auth value codes) but it's not in master :)
15:38 wizzyrea mib_ilomdd: we had the same problem, we ended up having to do a db level update to all patrons to turn it on
15:38 wizzyrea kf :) i saw your @later, i'm not sure why one would want the code *and* the description there.
15:38 wizzyrea someone obviously did
15:38 wizzyrea but to me
15:39 wizzyrea if you really want that... just put the code into the description, problem solved
15:40 kf yep
15:41 kf mib_ilomdd: I think there will be a script for doing this in 3.4
15:41 kf but not available in current version
15:41 kf wizzyrea: happy to know it will be gone soon :)
15:41 kf time for weekend now!
15:41 kf bye all :)
15:41 wizzyrea yay weekend!
15:45 mib_ilomdd Thanks - I will see if I can write something up...we can't upgrade just yet!
15:58 sekjal in a multiple branch setup with IndependentBranches enabled, should the homebranch always be able to update/edit/checkin the item, even if it's been sent to another branch (holdingbranch) to fill a hold?
16:00 wizzyrea sekjal: you would think so?
16:00 wizzyrea I mean, I would think so?
16:00 * wizzyrea tries to wrap her head about a setup where you wouldn't want that
16:01 sekjal I would think that the library that owns the item should always have permissions on it
16:01 wizzyrea that would be my assumption too
16:01 sekjal the library holding the item should have permissions, as well, since they have it, but those would go away once the item was transferred away
16:02 wizzyrea in nexpress, we have a 'gentlepeople's agreement' to 'not muck with other people's stuff, talk to them first'
16:02 sekjal In the event of a Floating Collections dev, the home library would just update to the holding branch upon initial receipt
16:02 sekjal (sorry, thinking ahead)
16:02 wizzyrea but we're not independent branches
16:12 sekjal bug 3203 is fun
16:12 huginn 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3203 normal, PATCH-Sent, ---, henridamien, ASSIGNED, Some Letters template variables are not available to certain notice types
16:12 sekjal for example, did you know that only borrower title, firstname, surname, userid and password can be parsed into an Account Details email?
16:23 cait yes
16:23 cait the worst thing is, this list does not include the cardnumer
16:23 cait so if you don't use the userid it's worthless
16:24 cait sekjal: and the item due / predue digest notices don't do branches
16:27 sekjal Account Details is pretty easy to fix, thankfully
16:28 cait sekjal: I tested them all recently for our first multi branch library
16:28 cait they are using all notices you can send to a patron
17:42 lavamind hello
17:42 wahanui hola, lavamind
17:43 lavamind I need to make some cronjobs quiet
17:43 lavamind for example, I dont want to receive this message every day : etud01: No branches with active overduerules at /usr/share/koha/bin/cronjobs/overdue_notices.pl line 296.
17:44 cait you should correct your configuration
17:44 cait this way the job is telling you it does nt work
17:44 magnus_away or filter out the messages in your mail client
17:45 lavamind they aren,t production instances, we use them to teach students
17:46 lavamind so until they get to setting that up, we *want* it to not work
17:46 cait comment out the conrjob
17:46 cait until you want it to run
17:46 lavamind yeah but that way it will never work
17:47 lavamind I have no clue when it will need to be run, I'm not the teacher :/
17:48 lavamind magnus_away: I think that's what I'll do, I was wondering if there was any way to make cron jobs quiet
17:49 cait there is a reason it's complaining
17:49 lavamind maybe there should be an option in koha-foreach
17:50 lavamind cait: I know there's a reason, and it's fine that way, but sometimes you do want to ignore some complaints
17:50 cait I prefer fixing things ;)
17:50 lavamind cait: you assume it's broken for everyone, in my case it's not
17:51 cait i understand that
17:51 lavamind broken is what we want, for teaching purposes
17:51 cait but your case is very special
17:51 lavamind maybe, but it's still pretty legitimate don't you think :p
17:51 cait of course :)
17:52 lavamind I suppose i'll just filter the cron message in my mail client
17:55 lavamind awh crap, can't do that with an imap account in thunderbird
17:55 magnuse oh wow, i'm a month behind with some of my google reader categories and didn't see this before now: http://googleblog.blogspot.com/2011/02/slice-and-dice-your-recipe-search.html
17:55 magnuse faceted search...
17:56 cait lavamind: perhaps using a different mail address would help?
17:59 fredericd lavamind: append to your cron entry: >/dev/null
18:00 cait hi fredericd
18:00 lavamind fredericd: tried that, doesn't work, seems like koha-foreach does its own redirections which arent overridable
18:02 fredericd lavamind: sorry, I responded too quickly. In fact, I don't know how koha-foreach works!
18:25 cait rangi++
18:52 rangi http://www.stuff.co.nz/sport/cricket/4812022/Black-Caps-shock-South-Africa-to-make-World-Cup-semifinals
18:52 rangi bam
18:58 bg wow
19:02 bg bit rough -- "confirming, it would seem, that their chokers tag is fairly fitting."
19:02 rangi heh
19:55 sekjal it's just an LDAP kind of day, it seems
20:39 schuster ooo sorry...
20:53 sekjal anyone know about a bug where holds pickup locations are messed up by updating the priority order?
20:57 wizzyrea what
20:57 wizzyrea whoa
20:57 wizzyrea but actually
20:57 wizzyrea this sounds familiar
20:57 wizzyrea sec
20:58 wizzyrea yeshttp://ticket.bywatersolutions.com/show_bug.cgi?id=804
20:58 huginn 04Bug 804: normal, P2, ---, chris, RESOLVED FIXED, Query form default submit action "or" instead of "submit"
20:58 wizzyrea sekjal
20:58 wizzyrea http://ticket.bywatersolutions.com/show_bug.cgi?id=804 (is what I meant)
20:58 huginn 04Bug 804: normal, P2, ---, chris, RESOLVED FIXED, Query form default submit action "or" instead of "submit"
20:58 wizzyrea shh huginn, that wasn't for you!
20:58 wizzyrea similar
20:59 sekjal bug 5805
20:59 huginn 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5805 critical, PATCH-Sent, ---, ruth, RESOLVED FIXED, Changing Pickup library on already queued holds causes havoc on all holds below it
20:59 wizzyrea but you're still seeing this?
20:59 wizzyrea on master?
21:03 sekjal wizzyrea: it's being reported on a version that doesn't have the patch for 5805
21:03 wizzyrea Aha
21:03 sekjal so I'll do an update, and see if that fixes the issue
21:03 wizzyrea :D
21:04 sekjal love it when the bugs are already solved
21:04 wizzyrea me too me too
21:04 wizzyrea and this one... it makes me feel fuzzy to know that because of us that got fixed :)
21:06 wizzyrea hmm I just closed my window that had all of my tabs open
21:06 wizzyrea oops.
21:42 pastebot "gmcharlt" at 68.101.78.67 pasted "for wizzyrea: and you can have random results as needed" (5 lines) at http://paste.koha-community.org/183
21:43 wizzyrea oooooo
21:43 wizzyrea gmcharlt++
21:48 pastebot "gmcharlt" at 68.101.78.67 pasted "wizzyrea: and grabbing the new book stuff is easy" (8 lines) at http://paste.koha-community.org/184
22:49 bg @wunder 93109
22:49 huginn bg: The current temperature in K6LCM - Westside / Mesa, Santa Barbara, California is 16.3�C (3:49 PM PDT on March 25, 2011). Conditions: Clear. Humidity: 62%. Dew Point: 9.0�C. Pressure: 29.96 in 1014.4 hPa (Steady).
22:50 bg @wunder wellington nz
22:50 huginn bg: The current temperature in Wellington, New Zealand is 17.0�C (11:00 AM NZDT on March 26, 2011). Conditions: Rain. Humidity: 100%. Dew Point: 17.0�C. Pressure: 29.89 in 1012 hPa (Steady).
22:50 bg ohhh rangi barely pulls out a win
23:10 gmcharlt @wunder 32605
23:10 huginn gmcharlt: The current temperature in Central Gainesville, Gainesville, Florida is 25.1�C (7:10 PM EDT on March 25, 2011). Conditions: Clear. Humidity: 27%. Dew Point: 5.0�C. Pressure: 29.89 in 1012.1 hPa (Steady).
23:12 sekjal Koha assumes that each branch will create it's own ACCTDETAILS notice (hence why <<branches.*>> tokens aren't parsed); shouldn't it, then, try to send from the Branch email, rather than KohaAdmin email?