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

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

A few questions for French Team
by Joshua M. Ferraro 19 Mar '07

19 Mar '07

Hey gang, Just a few questions about some of the additions to 3.0 that I haven't been keeping tabs on. Could someone clarify the following: 1. what is a 'professional' borrower? 2. what is a 'department' (in overdues)? Is it a hard-coded authorized value for item.location? Should it be defined in the framework? 3. what is the function of z3950AuthorAuthFields and z3950NormalizeAuthor system preferences? 4. what is the function of expandedSearchOption syspref? 5. what is the nature of AutomaticItemReturn syspref? 6. ReservesMaxPickUpDelay syspref ... what's it for, is it years, days, months? 7. maxoutstanding, maxreserves, noissuescharge, shouldn't these be in issuingrules? 8. useDaysMode - shouldn't this also be in issuingrules? 9. borrowerRelationship - shouldn't this be configurable in the borrower categories? maybe a new authorized value? 10. memberofinstitution syspref? - what is the effect of this syspref? 11. SubscriptionHistory syspref? what is the effect of this syspref? 12. Would anyone object to me declaring bankruptcy on our sysprefs, and re-naming all of them for 3.0? It might be a bit inconvenient for a few libraries currently running Koha that want to upgrade, but long term I think it would make things a lot simpler ... 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

3 2

Diff and patch
by MJ Ray 17 Mar '07

17 Mar '07

I can't find the guide that I mentioned on IRC, but those looking for tips on better use of diff and patch may find them in this book "Comparing and Merging Files with GNU diff and patch" by David MacKenzie, Paul Eggert, and Richard Stallman http://www.network-theory.co.uk/docs/diff/Overview.html My most frequent commands are: 1. # generating a patch of changes to one file cp file file.orig edit file diff -u file.orig file | tee file.patch 2. # generating a patch of all changes in a directory diff -ruN dir.orig dir.mod > all-changes-in-dir.patch 3. # applying a patch to a file patch file < file.patch 4. # applying a patch to a directory cd dir patch -p1 < /tmp/all-changes-in-dir.patch 5. # reversing that patch out again when it doesn't work cd dir patch -Rp1 < /tmp/all-changes-in-dir.patch There are some handy cvs diff commands: 1. cvs diff -u file # changes since last commit 2. cvs diff -r1.1 -r1.2 -u file # changes between given revisions and with git: 1. git diff -u file # changes since last commit 2. git diff -u rel22 master file # changes between given branches This can also give a crude way to reverse a change: use diff to make a patch file and then feed it to patch -R... but there are usually better ways. cvs update's merge options and git revert. If you are using patch files without revision control much, you may find wiggle helpful: http://cgi.cse.unsw.edu.au/%7Eneilb/source/wiggle/ Ask questions and I'll try to answer. Mangling files is one thing I have had far too much practice at! Hope that helps someone, -- MJ Ray - see/vidu http://mjr.towers.org.uk/email.html Webmaster/web developer, statistician, sysadmin, online shop maker, developer of koha, debian, gobo, gnustep, various mail and web s/w. Workers co-op @ Weston-super-Mare, Somerset http://www.ttllp.co.uk/

2 1

Re: [Koha] Google Summer of Koha - thought on 1 idea you posted
by Joshua M. Ferraro 16 Mar '07

16 Mar '07

----- "Steven F. Baljkas" <baljkas(a)mts.net> wrote: > Friday, March 16, 2007 16:03 CDT > > Hi, Josh, et al. at LibLime, > > Congratulations on your selection as mentor for the Google Summer of > Code program! It looks to be an amazing thing. Thanks, we're pretty excited, as it turns out, 2/3 of applications weren't accepted. > I don't know if this'll be useful for you folks or not, but here goes > anyway ... > > I noticed in your list of ideas the following -- > > Improve Koha Cataloging Interface > Have had some customer feedback that theyd like to see a > more "traditional" cataloging interface; best way I can > describe this is a line interface like you would expect in > a text editor vs the tabularized interface we currently have. > > Could it be just a big <textarea> ? > > -- 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. Definitely something we've thought of, and in fact, I've spoken to Terry about this. We're in the middle of defining what would be involved in making MARCEdit capable of 'pushing' updates to Koha. I think it's a fantastic idea to add this to the list of Google Ideas. I'll write an email to Terry and add it to our list, thanks again for the idea! 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

1 0

Google Summer of Koha
by Joshua M. Ferraro 16 Mar '07

16 Mar '07

Hi all, Just a heads up to the Koha community that LibLime was selected as a mentor for the Google Summer of Code program. We've got a few ideas defined already, but are certainly open to additional suggestions: http://wiki.liblime.com/doku.php?id=googlesummerofcodeideas So if you've got a neat koha-related project that's doable in a three month period by a student or group of students, let us know. And of course, if you happen to be a student, we'd love to have you involved. You can select from one of the ideas above, or come up with something completely new ... More info about the program and the application process is available at the Google Summer of Code site: http://code.google.com/soc The deadline is fast approaching so get those applications in. 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

2 2

Status of Savannah
by Joshua M. Ferraro 16 Mar '07

16 Mar '07

Hi gang, I'll get back into the version control discussion shortly, just wanted to post a note saying where we're at with the recovery of Savannah. I was able to re-commit everything to the HEAD branch. However, if you have a working copy newer than Sunday March 10th, you may want to check out a fresh copy and diff your changes into the fresh copy to avoid conflicts. If you have any questions about this, let me know. 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

1 0