IRC log for #koha, 2011-03-12

All times shown according to UTC.

Time S Nick Message
00:11 jenkins_koha Project Koha_master build #31: SUCCESS in 33 mn: http://jenkins.koha-community.[…]b/Koha_master/31/
00:11 jenkins_koha Tomás Cohen Arazi: update INSTALL* to acknowledge the use of mod_deflate
00:12 jenkins_koha Starting build 32 for job Koha_master (previous build: SUCCESS)
00:29 cait left #koha
00:45 jenkins_koha Project Koha_master build #32: UNSTABLE in 33 mn: http://jenkins.koha-community.[…]b/Koha_master/32/
00:45 jenkins_koha * Colin Campbell: bug_5064 Rework data retrieval in
00:45 jenkins_koha * Stéphane Delaune: Bug 5595: (MT #5757)adding additional attributes support on patrons's search
00:45 jenkins_koha * Galen Charlton: bug 5846: fix detection of Javascript to compress by mod_gzip
00:45 jenkins_koha * Frédéric Demians: Bug 4072 Lost items aren't hidden on OPAC result page
00:45 huginn Bug[…]w_bug.cgi?id=5595 major, PATCH-Sent, ---, ian.walls, ASSIGNED, can't search 'searchable' patron attributes
00:45 huginn Bug[…]w_bug.cgi?id=5846 minor, PATCH-Sent, ---, gmcharlt, ASSIGNED, mod_gzip can missing compressing Javascript files
00:45 huginn Bug[…]w_bug.cgi?id=4072 normal, PATCH-Sent, ---, gmcharlt, NEW, hidelostitems hides all results when searching (nozebra)
00:50 rangi 5595 broke the tests
01:26 Ahmuck joined #koha
01:38 wizzyrea is now known as Guest324
01:38 wizzyrea joined #koha
02:18 druthb joined #koha
03:05 kmkale joined #koha
03:06 * druthb bows to kmkale, her hands before her palm-to-palm.
03:06 NateC left #koha
03:07 kmkale Namaskar #koha
03:07 kmkale druthb: why?
03:07 kmkale the traditional Namaskar?
03:08 druthb yes.  And also...I owe you a good 'un.  You had a bug description I bumped into that is spot-on--I've been trying to describe it but couldn't find a coherent way, if we can *solve* the darn thing..
03:09 druthb Bug 5847.
03:09 huginn Bug[…]w_bug.cgi?id=5847 critical, P1, ---, gmcharlt, NEW, Manage Staged MARC Records stuck at 0% if isbn matching rule selected.
03:09 kmkale The Namaskar is almost gone out of fashion now a days :( so its good
03:09 kmkale to have it. And I return the same to you with respect :)
03:09 druthb :)
03:10 druthb I think it's a beautiful thing, myself.  I'm just beginning to wrap my head around the depth of meaning there.
03:10 kmkale druthb: also if we can add to bulkmarcimport the facility to import items on isbn match, it will be great I think.
03:13 druthb i use bulkmarcimport for my migrations work, but I'm not completely happy with it, for several reasons.  Its' matching tools are way too limited, for one, so it's very easy to end up with duplicates and other problems.    I have similar frustrations with the patron import tool--works fine for single-owner libraries, but in consortia with reciprocal borrower agreements...can get messy.
03:14 kmkale yup
03:15 kmkale I tend to do a lot of data cleaning with google refine. You should see the pathetic state of catalouges I get for conversion in
03:16 druthb I'm sure.  I've handled some pretty filthy ones, too.
03:18 * kmkale is planning to send out Kohacon11 registrations open and call for papers today :)
03:18 druthb awesome!
03:19 kmkale so you can can start booking flights ;)
03:19 druthb I'm hopin' Brendan sends me!  Have to get on the hustle to get my passport and such.  :)
03:20 kmkale Also planning to go visiting hotels tomorrow to fill up accommodation information
03:20 druthb kmkale++
03:20 kmkale its great fun :)
03:23 theartful joined #koha
03:23 druthb yeah, I've enjoyed the conferences I've been involved with.
03:24 theartful Hi there...I am an Information Studies student and have a broad question about Koha in relation to Evergreen.
03:24 wizzyrea shoot
03:26 theartful As someone who is very familiar with Koha, what would you say are the top functionalities that Koha possesses...and Evergreen lacks?
03:26 eythian seriously, what kind of ILS uses borrower card numbers as a primary key into all its user data.
03:26 * eythian grumps about Liberty some more
03:27 wizzyrea oo wow that's a good question
03:27 theartful (too broad?)
03:27 wizzyrea gmcharlt would probably be the best to answer that
03:29 theartful I notice that Koha allows user contributions and web-based accoutrements...
03:30 ronald joined #koha
03:30 wizzyrea yes, that's one place where koha excels: we have tagging, user reviews, user lists, and our OPAC is generally more patron friendly than EG's
03:31 wizzyrea and, ahem, a bit prettier ^.^
03:31 theartful That was one of the major differences I noticed off the bat...but I'm looking for less obvious features
03:31 theartful How do I get in touch with this mysterious gmcharlt?
03:31 wizzyrea he's about the channel quite often
03:32 wizzyrea just not tonight, as it's friday night :)
03:32 theartful makes sense
03:32 wizzyrea but if you are in the US, pop by almost any weekday, or even during the day on the weekend
03:32 wizzyrea and you might catch him
03:32 druthb theartful: If you'd like to PM me your email address, I will be seeing him in person on Sunday, and will gladly pass a message.
03:32 wizzyrea druthb: lucky!
03:33 * wizzyrea has "seeing gmcharlt in person" envy
03:33 druthb yes, I think so, too.  He and his wife have invited me to their home for foodz.  And kitteh-greetings.
03:34 wizzyrea yay kittehs!
03:48 theartful left #koha
03:49 druthb :)
03:53 wizzyrea right. I'm out of top gear. suggestions for my next "i have a gimp foot and want to do nothing but watch the telly" show?
03:54 eythian wizzyrea: breaking bad, stargate atlantis, big bang theory, castle, flashpoint, firefly, being human.
03:54 wizzyrea ooo I like your style
03:54 eythian s/atlantis/universe/
03:55 wizzyrea Stargate Universe it is (1st two aren't on netflix instant)
03:56 wizzyrea thanks for the suggestions :)
03:56 eythian no problem :)
03:57 wizzyrea stupid sprained ankle
03:57 eythian :(
03:57 wizzyrea and it's not even a good story: i was bringing in the groceries!
03:58 eythian I heard you say "snowboarding down an untried slope."
03:58 wizzyrea <3
03:58 wizzyrea mhm
04:02 druthb "Doctor, it hurts when I do this."  "Then don't do that."
04:13 kmkale hey people Kohacon 11 registrations are open[…]Conf/registration :)
04:13 kmkale just sent out a mail to the lists. next comes the call for papers :)
04:17 eythian I guess I need to plan a talk.
04:27 kmkale eythian: that would be great :)
04:27 eythian It also makes it easier for me to convince work to send me over :)
04:33 kmkale druthb: ^^
04:33 druthb :)
04:37 kmkale just sent the call for papers  to the lists.[…]k11/schedConf/cfp :)
04:40 kmkale I would like some people to go through the website and point out any difficulties, errors and ommissions
04:52 kmkale need help here[…]chedConf/overview
05:00 brendan_ left #koha
05:00 bg left #koha
05:08 druthb left #koha
05:42 bencahill left #koha
05:47 brendan_ joined #koha
05:48 Oak joined #koha
06:25 indradg joined #koha
07:01 kmkale_ joined #koha
07:01 Oak left #koha
07:02 kmkale left #koha
07:02 kmkale_ is now known as kmkale
07:07 rangi evening
07:07 kmkale is now known as kmkale_
07:07 kmkale_ hi rangi
07:08 kmkale_ is now known as kmkale
07:11 eythian rangi: back in Wellington now?
07:12 rangi yep, need me to come in tomorrow?
07:12 eythian rangi: don't think so, almost finished here now, it all went pretty smoothly.
07:21 rangi sweet :)
07:23 kmkale left #koha
07:33 kmkale joined #koha
07:41 eythian rangi: OK, all done I hope. Home time :)
07:42 rangi sweet
07:42 cait joined #koha
07:42 rangi hi cait
07:42 cait hi rangi
07:43 cait I see you are still pushing patches :)
07:44 huginn New commit(s) kohagit: Bug 5569: Corrections to addbiblio.tmpl to be able to delete repetable mandatory... <[…]37454c7b6ab4c6110>
07:46 kmkale hi cait
07:46 cait hi kmkale :)
07:53 jenkins_koha Starting build 33 for job Koha_master (previous build: UNSTABLE -- last SUCCESS #31 8 h 15 mn ago)
07:55 wizzyrea left #koha
07:58 rangi yeah last one for today
08:11 cait koha om tis laptop is still really slow :(
08:12 cait hm a little better perhaps than yesterday
08:13 cait perhaps time to test the packages
08:15 rangi install the koha-common one
08:17 rangi[…]velopment_Version
08:18 cait ok
08:18 cait can you give me a hint what I have to do to make it a dev koha?
08:19 rangi install the package
08:19 rangi that will pull in all the dependencies
08:19 rangi then just install from git as usual
08:19 rangi (except you wont have to cpan or apt-get anything else on)
08:19 rangi OR
08:19 cait or? :)
08:20 rangi you can do a koha-create something
08:20 rangi then edit the /etc/koha/something/koha-conf.xml
08:20 cait hm but I need one for testing/writing patches
08:20 cait ah
08:20 rangi and /etc/apache2/sites-enabled/something
08:20 rangi to point to git
08:20 cait hm
08:21 rangi either will work
08:21 cait to the git clone folder I created before?
08:21 rangi *nod*
08:21 cait ok
08:21 cait will try :)
08:21 cait I have virtualbox on the other machine, so I can do a snapshot :)
08:21 rangi cool :)
08:26 jenkins_koha Project Koha_master build #33: STILL UNSTABLE in 33 mn: http://jenkins.koha-community.[…]b/Koha_master/33/
08:26 jenkins_koha Janusz Kaczmarek: Bug 5569: Corrections to addbiblio.tmpl to be able to delete repetable mandatory subfields
08:26 huginn Bug[…]w_bug.cgi?id=5569 trivial, PATCH-Sent, ---, januszop, ASSIGNED, addbiblio fails while editing and deleting mandatory repeatable subfields
08:50 fredericd rangi: who must close a bug? the one who open it, submit a patch, or sign it off?
08:51 rangi the one who opened it ideally
08:51 rangi next best would be someone else independent
08:51 rangi worst would be the person who signed off
08:52 rangi 2nd worst person who wrote the patch
08:52 fredericd yes, but ofter I open a bug and then I submit a patch. So generally I close it but I'm no so conforable with that...
08:53 cait so start closing other bugs first perhaps? provide information how to test things...?
08:54 rangi yep, because you are the one who wrote the patch, 2nd worst case
08:54 rangi writing a 'How to test'
08:54 rangi on the bug, and then bugging people to test and close it for you
08:54 rangi eg
08:55 rangi How To Test:
08:55 rangi * create a new report in the Koha Admin interface, select 'Save'
08:55 rangi * see the link to run the report appears after saving; select it and confirm the report is run
08:56 fredericd Your 'How to test' is often in the bug description
08:57 fredericd the question is who will try to reproduce it after patch has been pushed and decide to close it
08:58 rangi its often not
08:59 rangi very often the bug description is lacking a lot of information
09:00 rangi if you want to make it easier for people to test, then a how to test in that format with a step by step rule will make it a lot easier for someone else to test
09:01 kmkale bye all. have a nice weekend.
09:01 rangi then building relationships with people to get them to test yours and you test theirs is a good way to do it also
09:01 fredericd You know better know better than I
09:02 fredericd We should all try to describe accuratly bugs we fill with a 'how to reproduce this bug' section
09:02 kmkale left #koha
09:03 rangi yeah that would be excellent
09:03 rangi maybe a rule we can try to enforce for 3.6
09:03 fredericd I try to apply your suggestion about relationship but it take time
09:04 fredericd cait: Do you have any patch to test? :-)
09:04 rangi :)
09:04 rangi she does actually
09:05 rangi or did this morning :)
09:07 rangi[…]w_bug.cgi?id=5527
09:07 huginn Bug 5527: major, PATCH-Sent, ---, katrin.fischer, NEW, Reports: Patrons who haven't checked out misses active users from issues table
09:07 rangi its been signed off and pushed
09:08 fredericd I'm reading 5838 Katrin patch
09:08 fredericd ok, so I could close it? (5527)
09:09 rangi yep
09:09 rangi or at least resolved - fixed
09:09 rangi 5838 has been signed off, but i havent merged/pushed it yet
09:16 cait bug 5838
09:16 huginn Bug[…]w_bug.cgi?id=5838 enhancement, PATCH-Sent, ---, katrin.fischer, ASSIGNED, Don't show sql statement on guided reports result page
09:16 cait there is some disagreement about this one
09:17 cait I don't like to see the sql there, others do
09:17 cait I think the print out shoudl not show it, so you can hang it up somewhere, and most librarians don't know about the sql behind it
09:17 fredericd Does it mean it would help if I test it and sign it off if I agree with your point of view?
09:18 fredericd Bug workflow is not so clear for me...
09:18 fredericd A diagram show the different steps would help a lot
09:19 cait I think you could also note on the bug
09:19 cait I think the problem is we have no workflow for things like that - where people disagree
09:19 fredericd We don't knwo precisely who do what
09:19 cait normally it would be: file a bug - patch is written and attached, but status changed to needs sign-off
09:19 fredericd and who's who
09:20 cait someone else (not the patch writer) tests it
09:20 cait marks failed qa or signed of and resends it to the list
09:20 fredericd There are: bug reporter, patch writer, QA, commenter, RM, signoffer, and now patch closer
09:20 cait and if it's ok chris will probably push
09:20 cait hm yes
09:21 fredericd potentialy a lot of people with overlapping
09:21 rangi qa for 3.4 is being done by the sign offer
09:21 rangi for 3.6 id like a sign off, then signed off by qa
09:21 rangi before i look at it
09:22 rangi bug reporter and patch writer can be the same person
09:22 cait I like the idea - but I hope we find enough people
09:22 rangi we have ian for qa
09:22 cait at the moment we need more people testing, commenting, working on the bugs
09:22 fredericd rangi: Do you know if there is somewhere a diagram for such a workflow with various people roles?
09:22 rangi nope
09:22 fredericd for other projects?
09:23 cait hm, not sure, I think magnus did somethingin a presentation
09:23 rangi could be, but we do things a little differently to other projects
09:23 rangi the life cycle of a bug is fair simple
09:23 rangi bug is reported
09:23 rangi patch is sent
09:23 rangi patch is signed off
09:24 rangi patch is pushed
09:24 rangi bug is tested and marked resolved
09:24 rangi release happens
09:24 rangi bug is marked closed
09:24 rangi or
09:24 rangi patch is rejected
09:25 rangi obviously it is bad to have the patch writer, sign offer and bug resolver being the same person
09:25 cait hm, we need something on the wiki I think
09:25 rangi im not sure we do
09:25 rangi what we need is more people testing
09:25 fredericd A picture is worth a thousand words
09:26 fredericd but I understand!
09:26 rangi im not sure that the process is the problem
09:26 cait I think people on the chat know - but what about new committers and people mainly lurking on the lists?
09:26 rangi new committers are fine, they send a patch
09:26 rangi they have the easy bit
09:26 cait hm, will be back in 10 min
09:26 rangi ppl lurking on the list are hugely unlikely to get involved
09:27 rangi i wish that wasnt the case, but i feel that the people who find their way onto irc are the ones we can depend on
09:27 fredericd When you say 'patch is pushed', you mean push in a separate branch?
09:27 rangi that would be
09:27 rangi pushed for qa
09:28 fredericd Doen't it happen before sign-off?
09:28 rangi sometimes after too
09:28 rangi when there is one that i want another sign off on
09:28 rangi if it is straigh patch pushed, it will be in master
09:29 rangi (i do push almost everything to its own branch and merge anyway, but that is so i can remove them if they prove to be broken)
09:31 rangi[…]-worth-of-merges/
09:31 rangi and it makes the git log more useful
09:31 rangi[…]oha.git;a=summary
09:31 rangi as all those branch names are links
09:32 cait back
09:33 rangi it is always worth remembering we are getting better all the time
09:33 cait true :)
09:33 fredericd I can testify it is the case!
09:34 fredericd Would you agree on this worflow (this is rewording of yours)?
09:34 fredericd (1) A bug is submitted by the 'bug reporter'. It contains a description on how to reproduce it. This is required for testers or the person who will close the bug.
09:34 fredericd (2) A patch is submitted by the 'patch writer'.
09:34 fredericd (3) (optional) RM pushed it as a QA branch
09:34 fredericd (4) The patch is tested and sign-off by the 'patch signoffer'
09:34 fredericd (5) The patch is pushed by RM in HEAD
09:34 fredericd (6) The patch is closed by the 'patch closer'
09:34 fredericd Patch closer, signoffer, writer, and bug reporter must be different persons.
09:35 cait hm
09:35 rangi (6) marked resolved
09:35 cait writer and bug reporter might get difficult
09:35 rangi (7) the bug is closed when a release is made containing that patch
09:35 cait not sure it's necessary
09:35 cait if you find a bug and can fix it - it's a good thing
09:35 rangi yeah i think reporter and writer could be the same
09:36 rangi (i often do that when im reporting a bug that a client has reported)
09:36 cait same here
09:36 cait I think we all do
09:36 rangi ideally the client would report it .. maybe eventually :-)
09:37 cait your clients speak english
09:37 fredericd very unlikely
09:37 rangi (well i have a couple who do :))
09:38 cait I agree with fredericd - some can, but others not
09:38 rangi but yes for the majority very unlikely
09:43 fredericd There are several pages on the wiki about bugs/patches/git...
09:43 fredericd[…]eptance/Rejection
09:43 fredericd[…]gn_off_on_patches
09:43 rangi yep
09:44 fredericd Shouldn't we try to have a central page aggragating all this info?
09:44 cait +
09:44 cait 1
09:45 fredericd 'Bug/Patch Workflow'
09:46 rangi collecting them all would be good
09:46 cait have te workflow on a new page
09:46 cait link to pages from write patch and sign-off
09:48 fredericd cait: I'm not at all for spreading info on various pages, but I know it's generally not a shared point of view
09:48 cait if someone creates the page with the right categories I can try to work on that too - I am not very familiar with mediawiki yet
09:49 cait fredericd: I think as the other pages already exist it might be better
09:49 cait and the page might get very long and not give a good overview of the process if we put it all on one page
09:50 fredericd This is just a matter of organizing a document in sections, and to begin with a table of content
09:51 cait hm, I like that a tester can print out only the part about signing-off
09:51 cait but that can probably be solved on the wiki too
09:56 cait rangi: for installing the packages - stable or dev version?
09:56 cait going to replace it with git clone later - so it doesn't matter?
09:57 rangi go for dev
09:57 cait ok, thx
09:58 rangi people still print things out? :-)
09:58 cait I know some do
09:59 cait sighs
09:59 fredericd rangi: yes, people even do print from their iPhone
09:59 cait I have problems with my arrow keys in vi
09:59 cait and I know I had a solution for that before but can't find it
10:00 wahanui joined #koha
10:00 rangi i have a solution
10:00 rangi emacs
10:01 cait no, I will not start with another editor today
10:01 cait you want me to work on koha, right? ;)
10:04 rangi :)
10:06 cait found a solution :P
10:09 cait sudo apt-get install vim
10:14 fredericd[…]nt-patch_Workflow
10:23 cait fredericd++
10:35 fredericd I can't add a wiki page to a category
10:35 fredericd permission issue?
10:54 cait not usre, never tried it
11:07 druthb joined #koha
11:19 cait left #koha
11:20 druthb left #koha
11:57 braedon left #koha
12:15 jcamins_away is now known as jcamins
12:39 kmkale joined #koha
13:14 kmkale left #koha
13:17 indradg left #koha
13:25 kmkale joined #koha
13:43 kmkale left #koha
13:48 kmkale joined #koha
13:56 kmkale_ joined #koha
14:01 kmkale left #koha
14:01 kmkale_ is now known as kmkale
14:34 kmkale_ joined #koha
14:37 kmkale left #koha
14:37 kmkale_ is now known as kmkale
14:42 kmkale_ joined #koha
14:43 kmkale_ left #koha
14:46 kmkale_ joined #koha
14:47 kmkale left #koha
14:47 kmkale_ is now known as kmkale
15:09 kmkale left #koha
15:18 druthb joined #koha
16:18 kmkale joined #koha
16:56 kmkale left #koha
17:05 indradg joined #koha
18:48 wizzyrea joined #koha
19:01 jcamins @marc 583
19:01 huginn jcamins: Contains information about processing, reference, and preservation actions. (Repeatable) [a,b,c,d,e,f,h,i,j,k,l,n,o,u,x,z,2,3,5,6,8]
19:05 bg joined #koha
19:10 druthb left #koha
19:23 indradg left #koha
19:33 jcamins @later tell rangi I tested jwagner's revision to bug 5810. It worked properly so I signed off on it, and resent the patch to the list.
19:33 huginn jcamins: The operation succeeded.
19:36 bencahill joined #koha
19:38 jcamins @later tell nengard Could you please close bug 5723?
19:38 huginn jcamins: The operation succeeded.
19:46 cait joined #koha
19:46 cait hi #koha
19:46 jcamins hi cait.
19:47 cait hi jcamins :)
19:59 * jcamins gives cait a cinnamon roll.
19:59 cait mmh thx :)
20:00 jcamins They came out quite good, I think.
20:01 cait I lost the log with your description of the recipe :(
20:03 jcamins They're very easy: Combine 200 g milk (scalded and cooled), 25 g fresh yeast, 250 g bread flour; let stand until doubled; cream together 200 g butter, 100 g sugar, 6 g salt, 125 g eggs (~2 large eggs); mix together the sponge and butter/sugar/salt/eggs; add 250 g flour.
20:03 jcamins Bake at 190 deg C.
20:04 jcamins The instructions say to mix for three minutes after adding the flour at the end, but I found it takes a lot longer than that when doing it by hand.
20:05 jcamins To make cinnamon rolls, I roll it out thin, and sprinkle cinnamon & sugar on it, then roll it up into a log, and cut the log into 4-5 cm sections and bake with the swirly sides facing up.
20:05 jcamins Wait, 175 deg C.
20:05 jcamins Not 190.
20:07 cait ok
20:07 cait I only don't understand the part with the sponge?
20:08 jcamins That's what you call the milk/yeast/bread flour part.
20:08 jcamins It's like "levain". :)
20:08 jcamins Kind of.
20:08 cait levain?
20:08 cait you speak in riddles tonight :)
20:09 jcamins That's the French word.
20:09 jcamins I don't know the German.
20:10 jcamins Sauerteig?
20:10 cait not it's in koha logs - can't loose it now :)
20:10 jcamins No, that's only for sour starters.
20:10 cait yep
20:10 cait vorteig perhaps
20:11 * cait shares a piece of engadiner nusstorte with you
20:11 * jcamins looks up what that is.
20:11 jcamins Mmm.
20:13 cait caramel and walnuts
20:13 cait yummy :)
20:14 jcamins What do you think of bug 5276?
20:14 huginn Bug[…]w_bug.cgi?id=5276 enhancement, P5, ---, colin.campbell, NEW, subscription info shouldn't be required
20:14 jcamins No.
20:14 jcamins What do you think of bug 4276?
20:14 huginn Bug[…]w_bug.cgi?id=4276 critical, PATCH-Sent, ---, oleonard, REOPENED, "Related subjects" search doesn't work with XSLT on and chained subject terms
20:14 jcamins That's the one.
20:14 cait uh, let me check
20:14 cait but we have different structures
20:15 jcamins Oh right. You have working authorities.
20:15 * jcamins is jealous.
20:15 cait hehe
20:15 cait and different rules
20:15 cait rswk
20:15 cait regel zur schlagwortkatalogisierung
20:15 cait although we have some loc subjects too afaik
20:16 cait we have subject chains - but they are built from single subjects
20:16 cait at the moment we split them up into single subjects and that works quite good with koha - and have an authority for each of course
20:20 jcamins I guess you probably don't have an opinion about whether the chains need to work the way they do in Normal mode, or whether Owen's fix is sufficient.
20:21 cait it's hard to tell for me
20:21 cait I don't know the structure and subfields of those subjects
20:23 cait[…]wk_in_marc_21.pdf
20:25 cait hm
20:25 cait jcamins: I am not sure what the patch changes, but I think as we are only using $a most of the time it would not change much for rswk subjects?
20:25 jcamins I wonder if there's an easy way to do the chaining with jQuery.
20:26 jcamins cait: yeah, it wouldn't make any difference for you.
20:26 cait what are you trying to do ? search the subfields in one string?
20:27 jcamins Yeah.
20:29 cait hm
20:30 wizzyrea oh my gracious... I missed discussion of cinnamon rolls
20:30 * wizzyrea drools all over her computer
20:31 * jcamins offers one to wizzyrea.
20:32 * jcamins just realized why he has so little free diskspace.
20:32 jcamins He has his wife's entire computer backed up on his laptop.
20:32 jcamins Actually, every computer his wife has ever owned.
20:34 cait hehe
20:35 cait sorry to be of not much help with the subjects
20:35 jcamins No worries.
20:35 jcamins wizzyrea: thoughts on bug 4276?
20:35 huginn Bug[…]w_bug.cgi?id=4276 critical, PATCH-Sent, ---, oleonard, REOPENED, "Related subjects" search doesn't work with XSLT on and chained subject terms
20:36 jcamins Is owen's patch sufficient, or do we need the fancy linking that normal mode has?
20:37 Ahmuck left #koha
20:37 wizzyrea oh wow
20:39 jcamins Oh wow?
20:39 wizzyrea I'm thinking about this
20:39 wizzyrea bug
20:39 * wizzyrea has never had anyone comment on the subject search links
20:41 jcamins Really? Huh.
20:41 * jcamins has gotten roughly a gazillion complaints about this.
20:42 wizzyrea about how they aren't chained?
20:42 wizzyrea or just how they don't work?
20:42 jcamins How they don't work.
20:45 wizzyrea this bug is referring to where subjects are say "Vampires -- Juvenile Fiction"
20:45 wizzyrea right?
20:45 jcamins Right.
20:45 jcamins The search would only be on "Vampires."
20:45 wizzyrea not if you click the 2nd term
20:45 jcamins Ah, that's in normal mode.
20:45 wizzyrea hmmm
20:45 * wizzyrea doublechecks her sysprefs
20:46 jcamins So what I'm hearing from you is "yes, we're attached to the behavior in normal mode."
20:46 wizzyrea i'm not sure about that no
20:46 jcamins ("we" being the general "we")
20:47 wizzyrea Yes, I think it's a better behavior
20:47 wizzyrea normal mode
20:48 wizzyrea what I especially like, I think
20:48 wizzyrea well hm
20:48 wizzyrea in XSLT
20:48 wizzyrea the way the links are suggest that you're chaining
20:48 wizzyrea when you're not
20:49 wizzyrea and it's a little misleading, even in normal mode
20:49 wizzyrea because they're split
20:49 wizzyrea and you wouldn't know that you were chaining
20:49 wizzyrea so say you have vampires -- Juvenile Fiction
20:49 wizzyrea clicking vampires gives you a subject search for vampires
20:49 wizzyrea but weirdly
20:49 wizzyrea clicking Juv Fic doesn't do that, it does both
20:50 wizzyrea in my mind, I would see both of them as individuals, unless told to chain them... but that may be way too much to ask
20:50 wizzyrea and if not individuals, then the way that xslt shows them
20:51 wizzyrea where they appear obviously chained (but aren't) would be a better display
20:51 wizzyrea d
20:51 wizzyrea o
20:51 wizzyrea does this make sense, am I talking nonsense?
20:53 jcamins No, that makes sense.
20:53 jcamins And that means that owen's solution is good.
20:53 wizzyrea ok phew
21:05 wizzyrea left #koha
21:07 cait left #koha
21:08 cait joined #koha
21:10 Ahmuck joined #koha
21:19 thd-away` joined #koha
21:19 thd-away` is now known as thd
21:24 bencahill left #koha
21:25 bencahill joined #koha
21:26 thd-away left #koha
21:33 huginn New commit(s) kohagit32: Bug 5736: Fixing some zebra configuration errors in marc21/biblios/record.abs <[…]3d2fde043f9673e68> / Bug 5569: Corrections to addbiblio.tmpl to be able to delete repetable mandatory... <[…]2b4525cfa8fe1b796> / Bug 4072 Lost items aren't hidden on OPAC res
21:38 jenkins_koha Starting build 4 for job Koha_3.2.x (previous build: FIXED)
21:55 bg left #koha
21:55 bg joined #koha
22:11 jenkins_koha Project Koha_3.2.x build #4: UNSTABLE in 33 mn: http://jenkins.koha-community.[…]job/Koha_3.2.x/4/
22:11 jenkins_koha * Galen Charlton: bug 2975: fix calculation of due dates by offline circ
22:11 jenkins_koha * Galen Charlton: bug 2975: whitespace and formatting cleanup
22:11 jenkins_koha * Paul Poulain: BZ3624, proposed patch for kohastructure.sql rewritten
22:11 huginn Bug[…]w_bug.cgi?id=2975 critical, PATCH-Sent, ---, gmcharlt, ASSIGNED, Offline circ tries to circ on biblio-level "itemtype"
22:11 jenkins_koha * Chris Cormack: Bug 3624 : Follow up patch, to catch any installs that still have the missing columns
22:11 jenkins_koha * Frédérick Capovilla: Bug 5703: Hide the $9 subfield (linked authid) when showing series for a MARC record in normal view.
22:11 jenkins_koha * Katrin Fischer: Bug 5527: Fix some problems in inactive borrowers report
22:11 huginn Bug[…]w_bug.cgi?id=3624 blocker, PATCH-Sent, ---, paul.poulain, REOPENED, Basket group delivery place
22:11 jenkins_koha * Tomás Cohen Arazi: update INSTALL* to acknowledge the use of mod_deflate
22:11 huginn Bug[…]w_bug.cgi?id=5703 minor, PATCH-Sent, ---, fcapovilla, ASSIGNED, Content of the $9 subfield is shown for series when in Normal view.
22:11 jenkins_koha * Colin Campbell: bug_5064 Rework data retrieval in
22:11 jenkins_koha * Stéphane Delaune: Bug 5595: (MT #5757)adding additional attributes support on patrons's search
22:11 huginn Bug[…]w_bug.cgi?id=5527 major, PATCH-Sent, ---, katrin.fischer, NEW, Reports: Patrons who haven't checked out misses active users from issues table
22:11 jenkins_koha * Galen Charlton: bug 5846: fix detection of Javascript to compress by mod_gzip
22:11 jenkins_koha * Frédéric Demians: Bug 4072 Lost items aren't hidden on OPAC result page
22:11 huginn Bug[…]w_bug.cgi?id=5595 major, PATCH-Sent, ---, ian.walls, ASSIGNED, can't search 'searchable' patron attributes
22:12 jenkins_koha * Janusz Kaczmarek: Bug 5569: Corrections to addbiblio.tmpl to be able to delete repetable mandatory subfields
22:12 jenkins_koha * Marcel de Rooy: Bug 5736: Fixing some zebra configuration errors in marc21/biblios/record.abs
22:12 huginn Bug[…]w_bug.cgi?id=5846 minor, PATCH-Sent, ---, gmcharlt, ASSIGNED, mod_gzip can missing compressing Javascript files
22:12 huginn Bug[…]w_bug.cgi?id=4072 normal, PATCH-Sent, ---, gmcharlt, NEW, hidelostitems hides all results when searching (nozebra)
22:12 huginn Bug[…]w_bug.cgi?id=5569 trivial, PATCH-Sent, ---, januszop, ASSIGNED, addbiblio fails while editing and deleting mandatory repeatable subfields
22:12 huginn Bug[…]w_bug.cgi?id=5736 normal, PATCH-Sent, ---,, RESOLVED FIXED, Fixing some zebra configuration errors in marc21/biblios/record.abs
23:07 cait left #koha
23:29 druthb joined #koha
23:31 druthb left #koha
23:32 druthb joined #koha
23:32 * druthb reaches for the Velcro
23:39 druthb left #koha
23:39 jcamins is now known as jcamins_away

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