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

(no subject)
by Tümer Garip 27 Mar '07

27 Mar '07

Second part for rel_TG document. I will resend the first one in smaller chuncks if it does not go through Tumer

1 0

photos of borrowers
by Omar F. Silvestro 27 Mar '07

27 Mar '07

Since I make to put the photos of the borrowers in koha 2.2.8 Thanks Omar F. Silvestro Universidad Nacional de Córdoba

1 0

Waing moderator approval
by Tümer Garip 27 Mar '07

27 Mar '07

Hi moderator, The document i sent about rel_TG to this list is 49K and it is still marked as waiting for moderator approval. Wil it get through or should i resend smaller parts? Cheers Tümer

2 1

Re: [Koha-devel] bulkmarcimport and unicode data
by R Hariram Aatreya 27 Mar '07

27 Mar '07

missed sending to the lists. ---------- Forwarded message ---------- From: R Hariram Aatreya <rhariram(a)gmail.com> Date: Mar 27, 2007 4:36 PM Subject: Re: [Koha-devel] bulkmarcimport and unicode data To: "Joshua M. Ferraro" <jmf(a)liblime.com> hi Joshua, > 1. do you have MARC21 unicode records with LEADER / 09 set to 'a'? Not at first. Later, I hand edited the Leader and set the 9th to 'a'. Did not fix the issue. (I am assuming that one could hand edit the Leader) > 2. what are the exact errors you're getting with bulkmarcimport? No errors. > 3. can we get some samples of records that aren't importing correctly? Just filed a bug : http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1318 It has two attachments: 1. http://bugs.koha.org/cgi-bin/bugzilla/attachment.cgi?id=73 : contains two of problem chars in 245a (after "A") 2. http://bugs.koha.org/cgi-bin/bugzilla/attachment.cgi?id=74 : similar to 1, but with the two problem char removed. hari.

1 0

bulkmarcimport and unicode data
by R Hariram Aatreya 27 Mar '07

27 Mar '07

hi All, I am trying to import MARC data (in unicode Tamil) into koha using bulkmarcimport.pl However, bulkmarcimport.pl does not like 3 characters (U+0B88, U+0B89, U+0BC8). Whenever these 3 characters are encountered, the rest of the string (subfield value) is gobbled and is missing from the database. But, bulkmarcimport.pl imports correctly if these 3 characters do not occur in the MARC data to be imported. Any idea whats going on ? Thanks, hari.

2 1

Patch to catalogue by itemtypes report
by Nicholas van Rheede van Oudtshoorn 27 Mar '07

27 Mar '07

Hi all! I'm the IT guy for the Perth Bible College in Western Australia. We've been using Koha for the last 2 years or so, and are *very* happy with it. One thing that we required, however, was a report to show the value of the books in our library. This was necessary for all sorts of legal reasons. I patched the itemtypes report to include a third column for the price of each itemtype, and a grand total price at the bottom. A *very* simple patch. Would anyone be interested in this patch being submitted? I know that I've upgraded twice already (each time having to add the patch in manually :GRIN:) Once again, kudos to all the developers! Nicholas van Oudtshoorn Perth Bible College

3 3

Re: [Koha] Google Summer of Koha - thought on 1 idea you posted
by Jason Ronallo 23 Mar '07

23 Mar '07

On 3/16/07, Steven F. Baljkas <baljkas(a)mts.net> wrote: > -- and I have been wondering for a while if what Terry Reese had accomplished with MARCEdit's text-based editor might somehow be "incorporated"/"integrated" into Koha. In my experience, in order to run MARCEdit in Linux you need to use Mono (and even then I found it not stable). Some folks have reservations about using Mono because Microsoft may use any patents on C# against Mono and Linux, though after the patent agreement between Microsoft and Novell (where the lead developer of Mono works), Novell customers are protected. I don't know where to stand on the Mono controversy, but it's something to consider. I would not like to see a Mono app be the main MARC editor for Koha, though I'd be happy if other folks had it as an option, because it is a really good MARC editor. --Jason

1 0

Re: [Koha] bulkmarcimport and unicode data
by Steven F. Baljkas 21 Mar '07

21 Mar '07

Tuesday, March 20, 2007 17:35 CDT Hari, Wasn't there something in the past few months about an incompatibility in bulkmarcimport.pl with certain (?) parts of unicode? Would it be possible for you to do a global search and replace for those 3 problem characters (with whatever tools you have on hand) and recode them into MARC8? That might be a work-around for now. Just a thought. When you find your solution, do let the list know. Cheers, Steven F. Baljkas library tech at large Koha neophyte Winnipeg, MB, Canada ============================================================ From: "R Hariram Aatreya" <rhariram(a)gmail.com> Date: 2007/03/20 Tue AM 08:09:44 CDT To: koha <koha(a)lists.katipo.co.nz>, koha-devel <koha-devel(a)nongnu.org> Subject: [Koha] bulkmarcimport and unicode data hi All, I am trying to import MARC data (in unicode Tamil) into koha using bulkmarcimport.pl However, bulkmarcimport.pl does not like 3 characters (U+0B88, U+0B89, U+0BC8). Whenever these 3 characters are encountered, the rest of the string (subfield value) is gobbled and is missing from the database. But, bulkmarcimport.pl imports correctly if these 3 characters do not occur in the MARC data to be imported. Any idea whats going on ? Thanks, hari. _______________________________________________ Koha mailing list Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha ============================================================

2 1

[URGENT] Move away from Savannah/CVS
by Joshua M. Ferraro 19 Mar '07

19 Mar '07

Hi folks, This is the kind of email I hate to have to write. We're facing some urgency on a rather important issue: Savannah has been down for two days now, and we're going to have to make some quick decisions to avoid losing any more work time. This also comes at a point in time when we've decided to pick a new version control system to replace CVS. I caught paul/hdl this morning, and we feel a move to SVN with hosting from Google is the best solution: http://code.google.com/hosting/ Here are the likely questions, and our answers: Q: why SVN and not git, arch, etc.? A: while a distributed repository makes good sense in theory, we fear that it will be a barrier to entry for new library software developers and we'll end up spending a disproportionate amount of time teaching and managing version control Q: why not host a SVN repo at koha.org or koha-fr.org? A: we're software developers, not proper sys admins, and at this point in our community development it's not fair to place the burden of managing the repo on any one development team. Q: why google instead of gna.org, etc. A: hosting at a project like gna.org, could result in the same situation we're in now in a few months. With Google, we get a Subversion implementation backed by Google's massively scalable, highly available storage technology, and some of the best sys admins in the world. Q: what about licensing? A: Google is acting as a code repository, they are not assuming copyright on the code, or changing the license. We're sticking with GPL version 2 or greater. Any questions, see Google's Terms of Use: http://code.google.com/tos.html Q: What about losing all our version history? A: A move to Google will mean we'll lose our version history, that's true. Personally, I can't imagine we'd want to roll back any of the code in either rel_2_2, dev_week or head. I'd like to arrive at a concensus today about this issue if at all possible, so we can get back to work ... so please send your comments/suggestions/flames asap. Cheers, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf(a)liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS

15 39

Fixed Bug 612 : Renewal failure gives no feedback
by Kyle Hall 19 Mar '07

19 Mar '07

Hey All, I fixed bug 612 in dev_week. The files I needed to modify were renewscript.pl, moremember.pl, and moremember.tmpl. If anyone wants to pull this fix into other branches, please do so. For the template maintainers, I added this near the top of my moremember.tmpl:   Or More Items Were Unable To Be Renewed.  Later, in the issues loop I added this to the table headers: <th>Renew Attempt</th> and this to the issueloop <td>Renewal Failed</td> As dev_week is not even listed in bugs.koha.org, I have not touched the bug report for this issue. Kyle -- IT Tech Crawford County Federated Library System

1 0