- Koha-devel - lists.koha-community.org

Re: [Koha-devel] [Koha] callnumber.pl errors in koha-error_log
by Chris Nighswonger 17 Mar '11

17 Mar '11

Hi Pete, On Wed, Mar 16, 2011 at 2:37 PM, Peter Huerter <pete.huerter(a)gmail.com>wrote: > Hi Chris, > > I am invoking it as a callback. In order to get it to work I had to > respond > to the error in the koha-error_log, however I re-factored the code for our > purposes. > > Perhaps there is another issue then, but I am pretty sure I am using the > value_builder structure in the way it is intended. > I cannot duplicate this error on my sandbox. C4::Auth is loaded by callnumber.pl at line 22 (http://tinyurl.com/68kqmxq) so I'm not sure what might be causing the error on your system. There should be no need to import that sub as C4::Auth exports it by default. Kind Regards, Chris

2 2

DB dependant test-cases
by Paul Poulain 17 Mar '11

17 Mar '11

Hi, I don't remember if someone already suggested this, but I think we should have a "default database" for db dependant test cases. Julian is writing a test case for 5880, and we need some auth values to be able to test. Same think will happen for all db dependent test cases, and also for selenium test. So what about having a default database ? If one want/need to write a test that can be tested only with another setup, it could be : * modify default setting * do your test * restore default setting (ie: you want to test something for IndependantBranch=ON and the default is OFF : you set ON, do your test, you set OFF) Is it a good idea ? -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

2 1

Re: [Koha-devel] [Koha] callnumber.pl errors in koha-error_log
by Chris Cormack 16 Mar '11

16 Mar '11

Hiya Let's move this one to koha-devel too please Chris On 17 Mar 2011 07:38, "Peter Huerter" <pete.huerter(a)gmail.com> wrote: Hi Chris, I am invoking it as a callback. In order to get it to work I had to respond to the error in the koha-error_log, however I re-factored the code for our purposes. Perhaps there is another issue then, but I am pretty sure I am using the value_builder structure in the way it is intended. Thanks, Pete. -- View this message in context: http://koha.1045719.n5.nabble.com/callnumber-pl-errors-in-koha-error-log-tp… Sent from the Koha - Discuss mailing list archive at Nabble.com. ___________________________________... Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailm...

1 0

Re: [Koha-devel] [Koha] Barcodes - various thoughts and questions
by Chris Cormack 16 Mar '11

16 Mar '11

Hi Guys Good discussion below, but can we shift it to the koha-devel list please (cced in) Makes searching for these kind of development threads much easier if the are the development list Chris On 17 March 2011 06:09, Archives and Collections Society <paul.a(a)aandc.org> wrote: > Hi Chris, > > Many thanks... comments inserted into [snipped for relevency] text below" > > At 12:50 PM 3/16/2011 -0400, Chris Nighswonger wrote: >> > [snip] is either "not to be used", "deprecated" (e.g Â hbyymmincr.pm which >> > looked promising but "This format is deprecated and SHOULD NOT BE USED") or >> > has been relegated to "dead files" e.g. >> >>I am the one who is responsible for the hbyymmincr format. In >>hindsight it was a bit redundant as the homebranch can be included on >>the label without having to include it in the barcode. But at the >>time, it seemed a good thought. A critical limitation to this format >>is that it is only good for 9999 barcodes per month. While in >>production this might be ok, if one was doing a initial load of > 9999 >>items it would present a serious limitation on this format's >>usefulness. > > Yes, but we would modify it along the following lines (Note: we are not > necessarily following the "standard" CLSI 14 digit format[1], although I > think we would want to tend that way): > > <branch> replaced by 4 digit category (think sub-branch as in "navy", > "merchant marine", "oceanography"); then yymm; then increment based on > *separate* increment per sub-branch. No initial load or subsequent batch > would be > 9999. > > Q: we would prefer to use alpha for "sub-branch, but fear this breaks > industry standards. Yes? No? and can Code128 checksums be implemented? > >>I'm sure we could fix up the code to raise the limit, but it probably >>is not worth the effort, imho. > > If you wrote the original .pm, could we possibly prevail upon you to draft > a mod|fix as described above? We'd do testing and fine tuning and give the > results back to the community :) > >>[snip] >>Have you had a look at the POD for C4::Barcodes? >> >>http://perldoc.koha-community.org/v3.02.05/C4/Barcodes.html >> >>This includes some brief direction for adding other formats. > > Yes, as you say - brief. We're also somewhat confused on the background and > Koha use of $types hashref. Is there a more complete doc somewhere? (I > can't find it.) > >>[snip] >>The daemon has memory leak problems. You are well advised to run away >>from it as fast as possible. >> >>There should be no reason to totally reindex afaik. You can run >>rebuild_zebra.pl -b -a -z and just catch the new/modified records. > > Yes - we implemented that very early in our process; set to every minute, > overhead on incrementals seems very low. However, for batch jobs this has > to be done for *every* write to koha.db, hence our 12,000 records taking 10 > hours. > > Best regards - Paul > > [1] 14 digits: > 1:ItemType 2-5:[Sub]Branch|Category 6-9:YYMM 10-13:Increment 14:Checksum > > > --- > Archives and Collections (ACS) Society > 205, Main Street, Picton, Ontario, K0K 2T0, Canada > http://www.AandC.org > Canadian Charitable Organization 88721 9921 RR0001 > Dedicated to maritime conservation and education. > > _______________________________________________ > Koha mailing list http://koha-community.org > Koha(a)lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha >

1 0

Re: [Koha-devel] [Koha] library "categories" (=groups)?
by hansbkk＠gmail.com 15 Mar '11

15 Mar '11

Chris/Robin, If either or both of you could comment on the below I (and other future inquiring minds) would greatly appreciate it. On Tue, Mar 1, 2011 at 7:58 PM, <hansbkk(a)gmail.com> wrote: > Moving on to documentation issues, the section on libraries and groups here > > http://koha-community.org/documentation/3-2-manual/?ch=x3670#AEN3676 > > isn't clear on what the "properties" type of group could be used for. I never really got a clear definition of what that was for - hence the lack of clarity in the manual. Once you get an answer here I'll update the manual accordingly! My impression from my research is that it's perfectly clear that their purpose isn't clear 8-) I reckon they're an artifact of an intention for a future enhancement that never quite crystallized into released code. Let's make it easy - could "one who knows" please either confirm or deny that the below statement is "good enough for now" to add to the docs? Improvements (in style or content) would of course be welcome. 1.2.1.3.2. Library Property Groups The purpose of Property Groups is to allow you to categorize your Libraries in a way that makes sense to you. This could for example be "Main" as opposed to "Branch" or "Mobile", or by region, or perhaps status within a consortium. It is not necessary to assign Property Groups to your Libraries, as they are not currently used within Koha itself, but larger library systems may find them useful, e.g. as select criteria for custom reports.

2 1

Request for Patches that Update the Database
by Nicole Engard 14 Mar '11

14 Mar '11

Good morning all!! I have just updated my local Koha install to master so that I can update the manual with all of the new fixes and features added this weekend. I have a request to those who write new system preferences for Koha. When you update the updatedatabase.pl script, could you include the system preference name in your update note? That way it's easier for those upgrading to find the new preference that was added (and it's easier for the documentation manager to know which preferences she has to document still) :) A couple of updates this weekend mention new preferences, and I think I know which ones they are - but just a request for the future to make things a bit easier for all involved. Thanks a ton! Nicole C. Engard

1 0

3.2.6 Release Schedule
by Chris Nighswonger 14 Mar '11

14 Mar '11

It's hard to believe a month has nearly passed, but here we are again.... 3.2.6 is on track to be released on March 22, 2011, however, there is another important date between now and then which you should be aware of. On March 15, 2011, 3.2.6 will enter a string freeze to facilitate finalization of translation updates. After this date the only patches introducing string changes which will be pushed for 3.2.6 will be those addressing blocker bugs or security issues. All others will be pushed to 3.2.7. Patches not introducing string changes will be pushed up to the time of the release. Keep up the good work! Kind Regards, Chris Nighswonger 3.2 Release Maintainer

2 1

Hacker's corner, week 11 (challenge inside !)
by Paul Poulain 13 Mar '11

13 Mar '11

Hello, What happend this week on Koha source code? First of all, Frédéric Demian has written a page on the wiki to explain how our workflow works : http://wiki.koha-community.org/wiki/Bug-enhancement-patch_Workflow. Please refer to this page if you need to learn how it works. 1- bugs closed ========= 55 bugs were closed : that's a good news. Julian (newcomer, from BibLibre) closed most of them. Ian Wall closed two and Jared Camins and Katrin Fischer closed one. There are still 55 bugs waiting for being tested and closed. Julian will continue working on them this week as planned, so we can expect this number to reach "none" soon. 2- bugs pushed ========= Chris has pushed 12 bugs at the end of this week. They are now waiting for being closed. 55 bugs are in this status. They are related to all modules, the largest module having patches is the OPAC: 11 bugs. In the last 7 days, 22 bugs have been pushed. They fix 2 blocking bugs, and add a feature for quick adding a biblio on circulation (#3495) 3- bugs to sign-off =========== 26 bugs have been signed-off this week. Nicole Engard has signed the more, followed by Katrin and Julian. Accordingly, the total number of bugs to sign-off has been lowered to 122. 15 bugs to sign-off have been updated this week (either it's bugs to sign-off that have had a new comment, or new bugs to sign-off) 4- to discuss ======== Some Koha modules have many bugs waiting for sign-off: 16 bugs are related to cataloguing, 17 are related to OPAC and 19 are related to circulation & holds. It means there is a lot of work to do in the "to sign-off" part of Bugzilla. Everybody is welcomed to join. Signing some easy-patches requires only a few minuts. Some are very hard, but many are really easy. If each developer decided to sign-off 5 bugs next week (1 per day !), I'm sure the number would be lowered *a lot* ! See you next week, hoping the number of bugs to sign-off will have be lowered to less than 50 ! That's the challenge I give to all of us ! -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

1 0

KohaCon11 : Call for Papers
by Koustubha Kale 13 Mar '11

13 Mar '11

Call for Papers The 2011 Koha Conference committee is requesting proposals for papers and presentations. Presentations should cover topics of interest to current and future users of Koha. The conference is expected to have a wide variety of attendees, including - Library administrators - Librarians - Programmers and system administrators Presentations should be approximately 45 minutes in length and allow time for questions. Presenters can expect to have Interest access and a computer projector for slides and, if necessary, a laptop computer with standard presentation software. When submitting your proposal, please include - The name and institutional affiliation of each presenter - Contact information, particularly email address - The target audience for your presentation (e.g. introductory, technical, administrative, etc.) - The proposed title of your presentation - A brief description suitable for publishing in the conference program. Descriptions should be no longer than 250 words. Author Guidelines The process for submission is Abstract followed by proposal (2 rounds of review required; first for abstract, second for proposal) Please try to submit your papers as early as possible. *The deadline for submissions is 15th August 2011.* Start here to submit a paper to this conference. STEP ONE OF THE SUBMISSION PROCESS<http://kohacon11.vpmthane.org/ocs/index.php/k/k11/author/submit?requiresAut…> ( http://kohacon11.vpmthane.org/ocs/index.php/k/k11/author/submit?requiresAut…) Please feel free to contact me for any assistance, queries, offers of help, sponsorship, comments etc. My contact information is given below. Regards, Koustubha Kale Anant Corporation Contact Details : Address : 103, Armaan Residency, R. W Sawant Road, Nr. Golden Dyes Naka, Thane (w), Maharashtra, India, Pin : 400601. TeleFax : +91-22-21720108, +91-22-21720109 Mobile : +919820715876 Website : http://www.anantcorp.com Blog : http://www.anantcorp.com/blog/?author=2 PS : Forwarding to koha-devel again, as I had mistakenly sent the first post (sent to koha and devel lists both together) to wrong address for the devel list.

1 0

Re: [Koha-devel] [Koha] KohaCon11 : Call for Papers
by Koustubha Kale 13 Mar '11

13 Mar '11

On Sun, Mar 13, 2011 at 6:11 AM, Joann Ransom <jransom(a)library.org.nz> wrote: > Hi all, > > I wonder if anyone has a gut feeling on the possible 'size' and audience for > KohaCon11 in terms of numbers, interest and ability levels etc? > > Getting 100, 300, 500 or 1000 attendees participants will impact on the > speakers programme. For instance with 200 participants we could opt for 1 or > 2 streams of papers, but 500 or 1000 attendees could open up the possiblilty > of 4 - 5 streams. This could also mean different approaches. For instance > some quite specific or focussed papers could be delivered as well as some > high level. One stream could be high level, general, overview for newcomers > and decision makers/influencers, another stream could be focussed towards > librarians using it day in and day out, another at system administrators > (just for example). > > I ask this because it affects what kind of abstract to put together. Any > thoughts? > > Cheers Jo. > Hi Jo, Its difficult to estimate so early. As I see it, the purpose of Kohacon is twofold. Its for the community to meet, get to know each other, decide on future direction of the project etc. At the same time it is also to promote Koha in the region where its held. Apart from the usual Koha papers about features, development, perl, etc, one thing we can plan for is a stream for library science students. VPM, Thane runs BLIB and MLIB courses under the aegis of University of Mumbai, as do several colleges in the region. This is a fairly large number of students. Another stream I am quite keen on is for librarians new to Koha. This stream could be sub divided into "Installation, Set-up, Running Koha" & a second sub-stream addressing queries / difficulties faced by librarians using Koha may be through interactive sessions. Through its Granthalaya.org project VPM, Thane has enabled many Public Libraries to computerize their catalouges and operations using Koha. We will keep doing this for more and more libraries. The Public Libraries in India face unique challenges and have unique requirements in some ares such as accounting, reporting etc. I would love to see a interactive session between experienced librarians running Koha for many years and this set of librarians from Indian public libraries ( with some experience developers also sitting in the discussion panel to understand how Koha could be further develpoed to address the unique needs of these Indian public libraries ) One more idea I have in mind, is for a development stream for aspiring Koha developers from around the world. Or perhaps this could be addressed as a separate stream of the Hackfest as suggested by Paul. These are just some Ideas. Its for the community to decide. If we could reach an agreement on the kind of streams like the above suggested and some people volunteering to conduct these streams, contribute papers, sit in on discussion panels etc, we could promote the streams to the interest groups mentioned above. It will also help us in ground organization like additional halls / rooms etc. PS : posting this to koha-devel so see if we can spark some interest in my ramblings above ;) Regards, Koustubha Kale Anant Corporation Contact Details : Address : 103, Armaan Residency, R. W Sawant Road, Nr. Golden Dyes Naka, Thane (w), Maharashtra, India, Pin : 400601. TeleFax : +91-22-21720108, +91-22-21720109 Mobile : +919820715876 Website : http://www.anantcorp.com Blog : http://www.anantcorp.com/blog/?author=2

1 0