Time Nick Message 11:59 |Lupin| I was just looking for a way to prevent some records to be displayed at OPAC, or to some user categories. Found a message where atz said this is not possible, but can hardly believe it. 11:54 |Lupin| hello everybody ! 11:50 Amit k 11:50 jwagner Maybe it's something for ALA this week -- we usually do sponsor a reception. 11:50 Amit jwagner: If you have any questions please feel free to contact John Rose at jrose@ptfs.com or Patrick Jones at pjones@ptfs.com. 11:49 Amit i have receive a mail from PTFS@mail.vresp.com 11:48 jwagner ?? 11:48 Amit PTFS organize a party 11:48 jwagner Hi Amit 11:39 Amit hi jwagner 09:44 kf hey :) 09:43 chris you europeans are quiet :-) 09:43 chris when the americans wake up 09:43 chris it gets busy in a couple of hours 09:39 paul_p channel very quiet those days... 09:39 paul_p hi kf 09:34 kf hi Kivutar and paul 07:54 Kivutar hi chris and #koha 07:53 paul_p hi chris 07:53 chris hi paul_p and Kivutar 07:28 nicomo 1910 : hum. My information seems a bit outdated, then 07:28 Amit hi paul 07:28 hdl_laptop In 1910 it made the wole tour. 07:28 paul_p hello world 07:28 hdl_laptop nicomo: yes it DID. 07:26 nicomo doesn't it used to actually make a tour of France? 07:25 nicomo then Paris 07:25 nicomo a bit in the south, a bit west, a bit in the alps 07:25 nicomo and actually I'm quite surprised, it's not a "tour" at all 07:24 nicomo just checking on the route : doesn't seem to be going through Lyon this year : ++ to that 07:24 hdl_laptop I had to park 1 mile from my home in order to be able to use my car ;) 07:23 hdl_laptop All the car traffic was a mess yesterday. 07:23 hdl_laptop It stopped yesterday right under my windows (in fact very very near) 07:22 hdl_laptop Yes. 07:22 nicomo yuk : city must have been invaded 07:22 nicomo hdl_laptop: the Tour was in Montpellier? 07:21 nicomo hi Amit 07:20 Amit hi kf, nicomo 07:08 chris hiya hdl, i looked for you on tv when watching le tour ... didn't see you :) 07:08 chris kf: hehe true :) 07:08 hdl_laptop hi all 07:08 kf chris: better keep your hair, its not worth tearing it out because of crontabs 07:07 chris signed off im afraid hdl_laptop 07:06 hdl_laptop jenish I think you might be willing to update your ubuntu system 07:05 nicomo hi chris and all 07:05 chris hi nicomo and anasha 06:50 ebegin he 06:50 ebegin he 06:50 chris nope, its not the only one, its open source, they can write their own :) but its the most maintained solution 06:49 chris hehe 06:48 ebegin chris, but are you sure the crontab is the only solution? ;) 06:46 chris i think they think if they keep asking questions somehow they will get a different answer :) 06:45 chris i count 7 times i have told the same 2 people to use cron to run rebuild_zebra 06:44 kf hi chris, why are you tearing your head out? 06:40 chris hi kf :) 06:30 kf good morning #koha :) 06:06 jenish can u tel me how to solve this 06:06 jenish this is the error wat am getting while installing Yaz in ubuntu8.10 06:05 jenish The following packages have unmet dependencies: yaz: Depends: libgnutls13 (>= 1.4.0-0) but it is not installable Depends: libyaz3 (>= 3.0.46) but it is not going to be installed E: Broken packages 06:05 jenish hi.......... 06:00 jenish The following packages have unmet dependencies: yaz: Depends: libgnutls13 (>= 1.4.0-0) but it is not installable Depends: libyaz3 (>= 3.0.46) but it is not going to be installed E: Broken packages 06:00 jenish But it return some error... 05:55 greenmang0 jenish: sudo aptitude install yaz 05:53 jenish How to install yaz in ubuntu 8.10 05:11 jenish error like this....... 05:11 jenish Has already been unwrapped into directory /root/.cpan/build/Net-Z3950-ZOOM-1.25-miaCYq '/usr/bin/perl Makefile.PL INSTALLDIRS=site' returned status 512, won't make Running make test Make had some problems, won't test 05:11 jenish it shows........... 05:10 jenish yes... i installed it 05:09 Amit have u install yaz 05:08 jenish i cant find ny solution.... can nybody help me... 05:07 jenish i cant install Net::Z3950::ZOOM.... 05:07 jenish i cant install Net::Z3950::ZOOM 05:07 jenish Amit.. 05:05 jenish in installing perl modules... 05:05 Amit what prblm? 05:04 jenish am new to koha and am installing it in ubuntu8.10.... but am facing sum prob.. 05:04 Amit hi jenish 05:03 jenish Hi.. 05:03 Amit hmm 05:03 brendan just doing some traveling 05:03 Amit http://lists.koha.org/pipermail/koha-patches/2009-July/003917.html 05:03 Amit my second patch 05:03 brendan how you doing -- 05:03 brendan heya Amit 05:03 Amit hi brendan 04:57 jenish am new to koha.... can nybody help... 04:57 jenish i cant install 'Net::Z3950::ZOOM' in ubuntu8.10 04:55 jenish hi 04:37 Amit hmmm 04:33 Jo but it is going well. 04:33 Jo busy testing our new koha 3 test site - micro testing :) 04:33 Jo very good. 04:29 Amit Jo: i m fine what about u 04:25 Jo how are you today? 04:25 Jo Hi AMit 03:23 Amit Hi Chris, Jo 03:23 Amit hi #koha good morning 21:35 pianohacker brb 20:54 richard hi chris 20:53 chris morning 20:36 richard hi 20:20 owen That seems to have worked fine 20:16 gmcharlt git pull ~gmc/koha/dev jquery 20:16 gmcharlt owen: ah, in that case try 20:15 gmcharlt owen: patch was prepared by beppu using 1.6.3.3 and appplied successfully by me in 1.5.6.5 20:15 owen I'm working on Arwen 20:15 gmcharlt owen: what version of git are you running? 20:12 owen gmcharlt: I get "error: No changes" when I try to apply jquery1.patch 20:12 schuster Yes - I wanted to ask about permissions and how that impacts the staff login vs opac. 20:11 Wizzyrea_ >.< 20:11 Wizzyrea_ er wiki 20:11 Wizzyrea_ http://wiki.koha.org/doku.php?id=en:development:ldap&rev=1246935665&do=diff 20:10 Wizzyrea_ schuster; did you see atz's blog post?/ 20:10 gmcharlt owen: ok, try this: http://arwen.metavore.com/~gmc/patches/jquery/ 20:08 owen gmcharlt: those patches don't apply for me. I'm not sure if it's the patches themselves or the path between my email and my git repo 20:05 owen Looks like John Beppu was reading the same article today on learningjquery.com that I was 20:04 schuster anybody here using LDAP for authentication? 19:55 gmcharlt owen: forwarded 19:08 owen gmcharlt: I've got some time now if you've got the patches 18:15 gmcharlt ok; I'll send you the patches in case you have a chance 18:12 owen I was just thinking about undertaking some upgrade tests myself! But I can't promise anything: I'm going out of town for a few days tomorrow 18:11 gmcharlt owen: would you have a chance to test some patches implementing a jQuery upgrade? 17:49 schuster Nobody seems to know how to fix it so that's why it is a "feature" that needs to have an "enhancement" ;) 17:43 owen Not that I know how to fix it :) 17:43 owen schuster: I'd classify that as a genuine bug, not an enhancement 17:21 schuster I feel an enhancement coming on... 17:21 schuster Does it drive anyone else crazy or just us that the facets in the opac for searching branches is in a "random" order? 17:11 |Lupin| thanks for your recommandation owen-away 17:09 owen |Lupin|: I think your only other choice is to look for a standard MARC field to store that information, and then to define the appropriate indexes in zebra (something which I don't really know anything about) 17:06 |Lupin| cause maybe one day a librarian working in our library may want to se item-types or ccodes for something more traditional, so maybe it is wiser to store information like format, public|private domain in a place where it won't bother anybody ? 17:05 |Lupin| owen: in fact, what I'm wondering is: is it wise to re-use existing koha concepts to capture things that are specific to ur library ? 17:04 |Lupin| I just discovered that there are also item-level i-types ! 17:04 |Lupin| now 17:04 |Lupin| owen: yes, I think this I understood 17:03 owen (I'm not sure why--seems like a poor choice to eliminate any options like that) 17:03 owen Although again, you can only offer your users one choice of limiters in the advanced search: either ccode or itemtype 17:02 owen |Lupin|: That certainly sounds workable 16:45 |Lupin| so maybe two item types (private domain and public domain) and one ccode for each available file format ? would that be okay ? 16:43 |Lupin| oh, ok 16:43 |Lupin| (in our model we pla to catalogue all the files we have for one book, with one item <=> one file) 16:43 owen No 16:42 |Lupin| so that one (at the biblio level) could be use for public / private domain books, and the other, at the item level, could be used to represent file formats ? 16:42 |Lupin| owen: is it possible to have item time at the biblio level and another series of item types at the item level ? 16:41 |Lupin| owen: okay. 16:39 owen So it might be appropriate to use itemtype or ccode, depending on what other categorization schemes you want to apply to your collection. Keep in mind that in the OPAC's advanced search you can display a filter by itemtype *OR* ccode but not both 16:38 |Lupin| owen: so the designation may be used as a search criteria, I think 16:37 |Lupin| owen: however books in the public doman can be downloaded freely wheres books in the private doamin can't 16:37 |Lupin| owen: in other words, there is no "circulation" per se 16:36 |Lupin| owen: well this time the question is for my job, so we handle electroni books 16:33 owen One question is how you would use the designation? As a means of isolating one or the other when searching? 16:33 owen Collection code might be an appropriate way to handle it, I probably wouldn't choose that because I'd want to be able to define a broader range of collection codes 16:32 owen Item types should probably be used for categories which affect circulation rules 16:31 |Lupin| would these be item-types ? 16:31 |Lupin| how would you guys represent the fact that a book is in the private / public domain ? 15:48 |Lupin| ebegin: right. Just display the content, not the @ label 15:47 ebegin But I think that we could prevent to display it to the user... 15:47 |Lupin| but it is then displayed in the staff client... 15:47 |Lupin| ebegin: ok 15:47 ebegin We need a place to store the value, that is the purpose of the @ 15:46 ebegin The @ is the koha's trick to say No subfield. 15:46 pianohacker |Lupin|: yes 15:46 |Lupin| or is the '@' interpreted as "does not have any subfield" ? 15:45 |Lupin| my 009 still has this @ subfield... 15:45 |Lupin| ebegin: how do you remove the subfields of one given field ? 15:43 |Lupin| ebegin: thanks 15:40 ebegin |Lupin|, I see. You can not change the default one, but this is a good suggestion though... 15:39 |Lupin| But now I think I understood things the wrong way 15:39 |Lupin| ebegin: So I waned to create a new framework, make this the default and make all my modifications there, so that the default framework installed by Koha remains untouched 15:39 |Lupin| ebegin: I thought there was a notion of which framework, among those proposed, is used by default, and I thought you can change this setting. 15:38 |Lupin| ebegin: actually I misunderstood the concept of default framework 15:36 ebegin you want to edit the default framework? or you want a record to use another one? 15:34 |Lupin| ebegin: the framework that is used by default 15:34 |Lupin| oh perhaps ou can't, actually, only choose one framework for each record you want to catalogue... 15:34 ebegin can you define "change"? 15:33 |Lupin| hmm how do you change the default cataloguing framework, pls ? 15:30 |Lupin| perhaps LDAP is the right thing actually 15:30 |Lupin| owen: me neither, just a vague idea of what it is used for 15:29 owen I'm not familiar with PAM 15:29 |Lupin| owen: couldn't they all use PAM or something similar ? 15:26 owen Unless each supported OpenID... 15:26 owen They're all separate software systems 15:26 |Lupin| would make things so mch easier... 15:25 |Lupin| would it be feasible that once yu have an account somewhere it also works for the rest ? 15:09 schuster Yep. 15:05 |Lupin| I guess wiki accounts, bugzilla acconts and koha.org accounts are different ? 15:05 |Lupin| hmm 14:59 |Lupin| ebegin: no I think the order of display does not match the one in the xml 14:54 |Lupin| ebegin: good question, let me see... 14:52 ebegin are the field in the same order that in marcxml? 14:49 |Lupin| yes 14:49 ebegin 101 is after 225?? 14:49 |Lupin| And also, there is an @sign just besides to it, as if @ was a subfield... I thought @means no subfield... 14:48 |Lupin| 009 appears between 225 and 101... 14:46 |Lupin| the only noying thing is that the fields are not sorted the right way 14:46 |Lupin| ah it's here !! 14:45 |Lupin| ebegin: yes, I saw it in the marcxml record 14:44 ebegin are you sure you have a 009 value for the record you are looking at? 14:43 |Lupin| after all: opac is not that important. The important is staff client 14:43 |Lupin| I can try again 14:43 |Lupin| well I didn't see it in the staff client either 14:41 ebegin so set its hidden to 0 then. I didn't know you want it to display in the OPAC also 14:40 |Lupin| ebegin: as said yesterday, I'd like the text to be displayed in the OPAC and in the staff client 14:40 |Lupin| ebegin: no, not in the editor because it uses javascript 14:36 ebegin do you look at it in the editor? The marc view only show fields/subfields with data. 14:36 |Lupin| ok, changed to 0 14:35 |Lupin| ebegin: it's -1 at the moment, let me change it 14:34 |Lupin| indeed returns 1 14:34 |Lupin| mysql> select hidden from marc_subfield_structure where tagfield='009' and frameworkcode=''; 14:32 ebegin |Lupin|, and make sure you also set the tab to 0 14:32 |Lupin| ebegin: thanks,let me see 14:32 |Lupin| owen: this certainly sounds wise, thanks 14:31 ebegin marc_subfield_structure 14:31 owen And if you don't plan on working on a particular bug it's there for others to see and try to fix 14:30 |Lupin| ebegin: could you remind me please in which table it was, so that I can check the curent value ? I think 1 was my last attempt 14:30 owen Then when you submit your patch you can attach a copy to the bug report. 14:30 owen |Lupin|: It's good practice to file a bug whether or not you plan to submit a patch. If you know you want to work on the bug yourself you can assign it to yourself. 14:30 ebegin s/value/hidden value/ 14:29 ebegin |Lupin|, I was able to see this field yesterday when I set its value to 1... 14:29 |Lupin| owen: I didn't do so so far because my hope was to be able to submit a patch 14:29 |Lupin| owen: ok 14:23 owen |Lupin|: I encourage you to file a bug report for each page/feature you find which you think should work without JavaScript. 14:19 |Lupin| tried different values for that field, no change 14:19 |Lupin| gmcharlt: if you mean the hidden column in a table I don't remember the name, yes 14:19 gmcharlt did you check the field visibility setting? 14:19 |Lupin| so I entered a description for it but it does not show up in OPAC or staff client 14:18 |Lupin| it's a coded field I'd like to use to store the old biblio numbers 14:18 |Lupin| gmcharlt: I was trying to tell koha to add unimarc field 009 to the current cataloguing framework 14:16 gmcharlt |Lupin|: please remind me what your question is 14:16 |Lupin| gmcharlt: did you se my message about unimarc field 009 ? Any idea who could help with that, pls ? 14:15 |Lupin| ebegin: and about links & co, they won't be very helpful because their javascript support is rudimentary... 14:15 |Lupin| ebegin: yeah, I know bulkmarcimport, but stage parc records may also be useful some time 14:14 |Lupin| hello gmcharlt 14:12 ebegin hi gmcharlt 14:10 gmcharlt hi folks 14:09 ebegin |Lupin|, you may want to try Links http://links.twibright.com/features.php 14:03 ebegin there is a bulkmarcimport.pl script that you could use. 13:56 |Lupin| any hint ? 13:56 |Lupin| but it does not work 13:56 |Lupin| so I replaced the button by <input type="submit"/> 13:56 |Lupin| tried t modify the html page, just to see whether canmake something usable with lynx 13:56 |Lupin| the submit button is again javascripted 13:55 |Lupin| trying to use the stage marc impor feature 13:55 |Lupin| folks 13:49 ebegin :) 13:49 owen I guess I'll have to look into the command line option when I *don't* want the 32-bit version! 13:48 owen I started to, and then realized Inkscape was exporting the 32-bit version by default. 13:48 ebegin owen, did you look at the command line option for exporting your svg file? 13:04 hdl_laptop hi owen . 13:02 owen What's new #koha?