IRC Logs

Time Nick Message
00:44 rms hey
00:45 space_librarian hi
00:45 rms how do i install koha on debian ?
00:47 space_librarian which version?
00:47 wahanui1 which version are you upgraing from ?
00:48 rms im doing a clean installation
00:49 rms space_librarian: 3.2
00:49 mtj rms: start here...
00:49 mtj http://git.koha-community.org/cgi-bin/gitweb.cgi?p=koha.git;a=blob;f=INSTALL.debian
00:50 rms thanks
00:56 mtj rms there are some pretty .deb packages, but i havent used then yet
00:56 rms by the way, if you see a person with the nick schuster, tell him to contact me
00:56 mtj and dont know where that doco is
00:57 mtj later
00:59 rms my god, the git is large
01:00 mtj @later tell schuster rms wants you to contact him
01:00 huginn mtj: The operation succeeded.
01:01 mtj rms: yeah theres a big chunk of language translation dirs in the repo
02:18 kmkale Namaskar #koha
02:25 * kmkale waves at druthb
02:33 cathrsnz just testing this prior to going live next week.
02:33 cathrsnz @wunder hawera nz
02:33 huginn cathrsnz: The current temperature in Stratford, New Zealand is 21.3ï¿½C (3:41 PM NZDT on March 09, 2011). Conditions: . Humidity: 41%. Dew Point: 7.0ï¿½C. Pressure: 29.93 in 1013.4 hPa (Falling).
02:33 mtj cathrsnz: test awayâ€¦ ;)
02:34 wizzyrea oh are you training this week cathrsnz
02:35 mtj cathrsnz: and congratulations on your pro-activeness :)
02:35 wizzyrea :)
02:36 mtj â€¦ most folk arrive here *after* they have a problem
02:36 wizzyrea true enough :D
02:37 mtj @wunder wellington nz
02:37 huginn mtj: The current temperature in Wellington, New Zealand is 17.0ï¿½C (3:00 PM NZDT on March 09, 2011). Conditions: Partly Cloudy. Humidity: 63%. Dew Point: 10.0ï¿½C. Pressure: 30.21 in 1023 hPa (Steady).
02:37 wizzyrea @wunder lawrence, ks
02:37 huginn wizzyrea: The current temperature in Channel 6 Downtown, Lawrence, Kansas is 2.2ï¿½C (8:45 PM CST on March 08, 2011). Conditions: Overcast. Humidity: 93%. Dew Point: 1.0ï¿½C. Windchill: -2.0ï¿½C. Pressure: 29.86 in 1011.1 hPa (Steady).
02:37 wizzyrea brr
02:38 mtj eep, chilly in kansas :/
02:38 wizzyrea yes, it was snowing huge wet flakes earlier
02:38 wizzyrea not sticking but very pretty
02:42 mtj wizzyrea: are NEKLS using 3m self-checks?
02:42 wizzyrea yep
02:42 wizzyrea so far, on our 3.3 koha, there are no serious problems, only a couple of minor "our preference" issues
02:43 mtj ok, sounds good
02:43 kmkale wizzyrea: which tags are you using?
02:43 kmkale looking for a good rfid vendor in India
02:44 mtj sheesh, top-posters diaf
02:45 mtj top-posters, the bane of mailings-lists
02:46 wizzyrea just realized that I didn't send my response to you to the list
02:46 wizzyrea >.<
02:46 mtj np, ayre replied
02:47 wizzyrea ya I saw
02:47 wizzyrea kmkale, that's a good question, i don't know where they get their tags exactly
02:47 wizzyrea I can find out
02:47 wizzyrea if you like
02:47 kmkale I would like to know tag type, make, model if possible
02:47 kmkale then I can find a source here
02:48 eythian http://i.imgur.com/n64Z0.jpg
02:49 kmkale :)
02:53 kmkale wizzyrea: if an item can't be self checked out due to a hold, is there a physical barrier to prevent the patron from walking out with it? or are there alarms on the door?
03:10 kmkale_ bbl
03:13 gmcharlt rangi: datapoint - I've gotten around to testing using memcached for CGI::Session storage; definitely worth merging into 3.4
03:24 rangi sweet
03:24 rangi when I get back to more stable internets ill do so
05:44 cait hi #koha
05:51 eythian hi
05:56 cait hi eythian
05:56 cait mtj: still around?
06:22 cait morning magnuse
06:26 kmkale_ hi rangi
06:28 cait hi kmkale and rangi
07:11 magnuse good morning #koha
07:16 kmkale hi magnuse
07:16 magnuse good morning kmkale
07:34 magnuse bonjour paul_p
07:34 * eythian grumps at liberty allowing invalid data into its records.
07:36 paul_p hello magnuse
09:12 kmkale bbl
09:30 liw http://www.topatoco.com/merchant.mvc?Screen=PROD&Store_Code=TO&Product_Code=QC-LIBSCI-TOTE&Category_Code=QC
09:31 magnuse hehe
09:58 kf hi #koha
10:02 magnuse guten tag kf!
10:03 mtj heya magnuse kf
10:03 kf hi magnuse and mtj
10:03 magnuse hi mtj
10:03 kf mtj: we have 3M self checks for 5 branches in one of our newer projects here
10:04 mtj oooh, thanx for that info
10:04 mtj everything going okâ€¦ ?
10:05 kf mtj: they are not working yet
10:05 mtj â€¦ or still in testing phase
10:05 kf but can tell you in a few days more
10:05 mtj ah, gotcha
10:05 kf we asked them to test but i have no feedback
10:05 mtj cool, keep me posted
10:05 * magnuse wonders if it would be a good idea to collect experiences with self check machines on the wiki?
10:06 mtj yeah, i think so magnuse
10:06 kf mtj: we have very good experience with a German vendor
10:08 magnuse it would be good to show that "yes, koha does work with a lot of these machines"
12:33 jcamins @wunder 11375
12:33 huginn jcamins: The current temperature in Astoria, Astoria, New York is 1.9ï¿½C (7:40 AM EST on March 09, 2011). Conditions: Mostly Cloudy. Humidity: 75%. Dew Point: -2.0ï¿½C. Windchill: 2.0ï¿½C. Pressure: 30.63 in 1037.1 hPa (Steady).
12:39 magnuse @wunder bodo, norway
12:39 huginn magnuse: The current temperature in Bodo, Norway is 4.0ï¿½C (1:20 PM CET on March 09, 2011). Conditions: Scattered Clouds. Humidity: 61%. Dew Point: -3.0ï¿½C. Windchill: -1.0ï¿½C. Pressure: 28.97 in 981 hPa (Steady).
12:40 magnuse woohoo
12:40 druthb jcamins++
13:14 ebegin Anybody though about having a search result that we could navigate, for example, once we are displaying a detail record, we could have a next and previous button. Currently, we do not have the possibility to 'browse' the result. any thoughs?
13:15 druthb ebegin: I've had occasion to think about that. It would not, I think, be a huge thing to do.
13:19 ebegin druthb, Here my thoughts : the search would build a list of bib id based. We would need a SearchID (that could be the user sessions id) and a current index.
13:19 kmkale_a I had lots of trouble with patron card creator just now at a library. There are a number of small issues in there.
13:20 kmkale like the "Enter starting card number" refuses to work. It always start from 1st position
13:21 druthb ebegin: that'd be a nice way to do it, kind of stateful, which would save a lot of overhead over the stateless way I was thinking of it.
13:21 kmkale Also only code 39 type of barcode stays selected. All other types revert back to code 39
13:22 kmkale And there is no way to control the barcode print size
13:22 ebegin druthb, The next button display the next bib in the list and previous the previous one. The only probllem I see is to keep the search result when large amout of bib is involved.
13:22 druthb yeah, you'll need to expire those and toss them after a bit, or you'll end up with a lot of stray cruft.
13:23 ebegin druthb, I was wondering if we couldn't get zebra to keep this information for us. I know that there are ways to scan result of a z3950 server, based on a search id...
13:24 druthb hm...maybe.
13:30 ebegin Otherwise, the search index could be assigned to the user session id and a cron job takes care of removing the search indexes of dead session. I'll dig a little more to see.
13:30 jwagner kmkale, no one has responded to your label questions -- you really need to catch chris_n when he's online. He wrote the module so he'd be the best help.
13:31 kmkale jwagner: right. More observations really. But will chat with chris_n
13:39 tcohen hi #koha
13:40 tcohen anyone can explain briefly what quick slip is for (in checkout screen)
13:40 tcohen (i.e. quick slip vs. slip)
13:40 jwagner tcohen, if I remember correctly, quick slip is everything the patron checked out today, while slip is everything the patron has checked out in total
13:41 tcohen which is the most commonly needed?
13:41 tcohen I suppose quick slip...
13:42 jwagner Depends on the need. Quick slip is useful as a checkout receipt, but slip is best if the patron wants to know everything he/she currently has checked out.
13:42 tcohen of course
13:42 tcohen i'm resuming bug 4389, which was intended to help
13:42 huginn 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4389 enhancement, PATCH-Sent, ---, tomascohen, ASSIGNED, Trigger slip print on empty checkout submit
13:43 tcohen people working on circultaion
13:43 tcohen so I think i'll stick with qslip
13:43 tcohen thanks jwagner
14:42 * tcohen is happy as submited his remaining patches for his assigned bugs :-D
14:47 kf :)
14:47 kf tcohen++
15:27 sekjal anyone know of any data issues that would cause insanely high memory and CPU usage for opac-search.pl or opac-detail.pl?
15:50 gmcharlt sekjal: is it consistently reproduceable?
15:50 gmcharlt for a given bib or a given search?
15:50 sekjal gmcharlt: still working on confirming that
15:58 hdl sekjal: how many checkouts on one page ?
15:58 hdl sekjal: how many items for the biblio ?
15:59 sekjal this is happening on opac-search.pl and opac-detail.pl, for numerous searches and biblionumbers. most have around 1-2 items attached, and not too many checkouts
16:04 gmcharlt sekjal: so if we restrict it to the opac-detail.pl case for now, does it happen every time you display a particular bib?
16:08 sekjal haven't isolated a particular biblio yet; appears to happen on several
16:08 * magnus_lunch magnus_away
16:08 magnus_away oops ;-)
16:12 sekjal opac-search.pl is the real killer
16:12 sekjal 80-90% CPU usage with 13-15% memory usage for several seconds at a time
16:13 kmkale sekjal: how many records?
16:14 sekjal just under 50K titles
16:14 kmkale :(
16:15 kmkale not seen it on any of my install
16:17 paul_p sekjal, is there a biblio with maaaaaannnnnyyyyy items ?
16:17 paul_p like 500+ ?
16:17 paul_p (that could be an explanation)
16:18 sekjal biggest has 168
16:18 paul_p that's a lot, but I think it's not enough to have perf--
16:18 paul_p is opac-detail.pl?biblionumber=XXX on this biblio long to display ?
16:20 sekjal defaults to not displaying all the items (too many). Once I click the link, it take about 5 sec to show them all
16:20 sekjal wouldn't classify it as a abnormal
16:21 paul_p sekjal, even if they're not displayed, the xml is parsed. So if this step is not long, then it means your record is not long to xml-parse (displaying long is a firefox problem, not koha)
16:21 gmcharlt agree with paul_p - large XML blobs to parse would obviously slow things down, but it shouldn't be spiking CPU usage quite like that
16:22 sekjal I think there is something about the data that Zebra doesn't like
16:22 paul_p + it should not be in opac-search
16:22 gmcharlt sekjal: which process is spiking?
16:22 paul_p (I mean the problem should not arise in opac-search, only when displaying *one* biblio)
16:22 gmcharlt opac-search or zebrasrv?
16:22 sekjal opac-search.pl
16:23 hdl sekjal: even though you donot display items because too many, you are decoding the marcxml => it takes TIME
16:23 gmcharlt then I think that would rule out Zebra per se
16:23 paul_p is search on staff interface fast ?
16:24 sekjal no, staff-side search spikes similarly
16:26 sekjal memory and CPU grow as I watch on commandline top... at least 4 refreshes worth
16:27 sekjal I have a suspicion about whitespace... but I'm entirely clear why
16:27 sekjal err, not entirely clear
16:27 gmcharlt well, is the whitespace clear or not? if it's not, isn't it darkspace?
16:28 sekjal depends if you're viewing it as a .jpg or .png
16:28 gmcharlt heh
16:28 gmcharlt anytime, nytprof time, I think
16:30 sekjal yeah, I think perhaps so
16:38 kmkale bye all. Good night
16:39 paul_p bye all ! time to go back home for me ! (not to bed like kmkale_a though ;-) )
16:41 kf bye paul_p :)
16:41 druthb nekls++
16:41 druthb wizzyrea++
16:49 jcamins_away What's the minimum required version of Perl?
16:49 jcamins_away It's 5.10, isn't it?
16:50 sekjal 5.8.8 last I heard
16:50 sekjal talked of moving it to 5.10, but I don't think we agreed to do that yet
16:50 jcamins_away Good.
16:51 jcamins_away Any idea where ZOOM.pm comes from?
16:52 jcamins_away Ah. Net::Z3950::ZOOM
16:54 jcamins_away nekls++
17:01 kf nekls++
17:06 * jwagner gives jquery a swift kick
17:27 JesseM what is the default search field on Koha?
17:29 JesseM oh I got it relevance
17:30 jcamins_away JesseM: by default, Koha searches every single field that's been indexed.
17:30 JesseM THank you jcamins
17:34 wizzyrea :D bywater++
17:35 wizzyrea complicated_integration_of_missing_data--
17:44 * druthb waves to SharonNEKLS.
17:44 SharonNEKLS druthb The holds ratio report looks normal again - I am one happy (but still moody) person!
17:44 druthb Awesomeness!
17:45 SharonNEKLS Now we just need to get the old system to stop generating notices...
17:45 SharonNEKLS forgot to put that on our checklist...
17:45 wizzyrea (and yes, we filed a ticket)
17:45 SharonNEKLS and left a phone message, for good measure
18:32 sekjal NYTProf had some interesting lessons for my CPU/mem usage problem
18:33 sekjal quickest fix: reducing the number of search results per page from 100
18:34 wizzyrea 100 is an almost overwhelming number of resluts anyway
18:34 wizzyrea results* :P
18:34 sekjal a lot of processing time is being thrown at getting authorised_value_images for a biblio
18:42 sekjal yeah, Koha spends a lot of resources on get_authorised_value_images, but doesn't even necessarily use them
18:46 gmcharlt sekjal: the other factor is that it effectively runs through all of the items twice
18:50 sekjal NYTProf has the call to get_biblio_authorised_values (which is passed to the get images routine) with 5 seconds exclusive time and 13 seconds inclusive time (on my particular machine with 100 results returned)
18:50 sekjal a simple conditional to check to see if AuthorisedValueImages is even turned on first would save a lot
18:55 gmcharlt sekjal: yes, and presumably there's scope to make get_bib_auth_vals more efficient even when it is turned on
19:18 rms .
19:18 rms GAH.
19:24 Brooke_ kia ora
19:25 cait hi Brooke_
19:25 Brooke_ :)
20:13 Brooke_ stupid Journal of Library Innovation not having any stupid articles for me to read. Almost like I have to stupid contribute instead of stupid leech.
20:28 SharonNEKLS I love the reports library...
20:52 Brooke_ namaskar
21:56 rhcl raksaman
22:20 Jen_NCAR I have recently created a new MARC framework for catalogin archival collections. The MARC record looks good, but the frontend display leaves seomthing to be desired - very few relevant fields display. Is there a way within KOHA admin to dictate which MARC fields are displayed on the frontend and with what labels. Example: I might like the 545 to display with
22:21 gmcharlt Jen_NCAR: there's a server side XSLT file that we can edit for that
22:21 gmcharlt Jen_NCAR: you can drop me a line with what you want displayed and with what labels
22:23 gmcharlt files in question are ./koha-tmpl/opac-tmpl/prog/en/xslt/MARC21slim2OPACDetail.xsl and ./koha-tmpl/opac-tmpl/prog/en/xslt/MARC21slim2OPACResults.xsl, btw
22:25 Jen_NCAR gmcharlt: great! I will put that list together and get back to you. Actually, I should really ask our archivist what SHE wants displayed. Can I drop you a line tomorrow?
22:38 eythian Julian is doing really good work with getting bugs closed.
22:59 gmcharlt Jen_NCAR: sure, that's fine