- Koha - lists.katipo.co.nz

Koha Upgradation
by Prasanth 25 Feb '11

25 Feb '11

Dear Professionals, We are now using Koha 2.2.5 version,but unable to generate barcode in this version ,we try to upgrade 3.2.2 version but some technical errors occured at this time.Any body help me to provide migration tools and details Regards Prasanth M.P. Librarian Chinmaya Institute Of Technology Kannur Kerala,India Ph:+91-9961858865

1 0

Proposal To Switch Koha's License to GPLv3 and AGPLv3 or AGPLv3
by Christopher Nighswonger 24 Feb '11

24 Feb '11

Greetings all, Some time ago the topic of changing the version/flavor of GPL license Koha is released under was discussed. In light of the momentum the community has built up in the area of change in recent months, now would be a good time to resume licensing discussions and bring them to a final resolve. Delaying them only means another round of disruptive changes at some point in the not too distant future. It would be nice to go ahead and have all the laundry cleaned and folded while we are about the task. As I see it, the advantage and rational for moving to GPLv3 are primarily that GPLv3 is compatible with AGPLv3. This allows us to accept work licensed under either of these two licenses. AGPLv3 carries the added advantage of the *additional* requirement that changes, etc. to the code be made available (at least) to those who access the changed code. This gives us quite a measure of protection more against Koha related code becoming locked up on a saas platform somewhere in the nebulous "cloud." Let's hash through this and come to a decision. Kind Regards, Chris

17 69

Question about cutter classification
by Marilen Corciovei 24 Feb '11

24 Feb '11

Hello everybody, We are trying to migrate an old proprietary software to Koha and one of the "requirements" of the librarians is something called "author sign" or "cutter number". The librarian manual I've consulted describes the process of creating this number using a table. This table contains for each letter 99 combinations of starting letters or syllables. For a bibliographic entry the starting letters of the name of the first author or the title is used to search in this table. Then the first letter and the resulting number is used as this code which has as purpose to simplify shelving. I was wondering if someone implemented such an algorithm in Koha in order to validate my assumptions for the requirements to implement such a field: - marc storage. Which marc field was used? (we are using unimarc) - formula. Was this implemented as a combo with all the values or as a value builder field plugin which calculates automatically the value? The algorithm is clear but there are some exceptions which are not quite obvious such as how this is calculated for a title starting with numbers. The manual states that for 1001 it uses "one thousand and one" as text. Thank you for any hints, Kind regards, Len www.len.ro

1 0

SOUL to Koha migration
by Vimal Kumar 24 Feb '11

24 Feb '11

Dear Friends, Anybody have tried data migration from SOUL software ( www.inflibnet.ac.in/soul/) to Koha? I exported the data as MARC from SOUL, but it does not open and edit using MarcEdit software. I request to share your experience in SOUL to KOHA migration. Regards, -- Vimal Kumar V. Mahatma Gandhi University Library Kottayam, Kerala- 686 560 Web: http://www.vimalkumar.co.nr Blog: http://vimalkumar.oksociety.in http://linuxhalwa.blogspot.com --------------------------------------------------------------------------- "I forget what I was taught. I only remember what I have learnt" -Patrick White

2 2

Re: [Koha] Batch import-updating of existing biblios
by hansbkk＠gmail.com 24 Feb '11

24 Feb '11

On Thu, Feb 24, 2011 at 4:09 AM, M. Brooke Helman <abesottedphoenix(a)yahoo.com> wrote: > Salve! >>> > And I would like to "add value" to them later on - say I find a MARC > source that assigns subject headings in a way that I like, or adds > links to cover images, etc. looking to selectively overlay/insert a > subset of the new records into my existing ones. > > How does Koha handle this? >>> > > Okay, that's a good question :) > > Koha pretty much doesn't right now, but folks are taking some hammers to > the code to make it try and manage that safely. PTFS kind of doesn't get that > you need a scalpel and not a caber for this job. (What else is new?) > >>> > Or would I be better off exporting my current records to MARC, using > an external MARC editing tool to handle the merge and then re-import? > Can anyone suggest tools for me to look at? I'm aware of biblios.net > and MarcEdit so far. >>> > > Currently yes, and I'd use the latter not the former, since the former > sucks. > > >>> > Or if it's really better to do this one record at a time, does that > change the recommendation as to using Koha for the process? >>> > > Mebbe. Sometimes Koha can put weird stuff into a MARC record, though > that's mostly over with by now. I used it as an editor since I was in the middle > of nowhere and no one would ever notice the aforementioned weird stuff anyhow. > >>> > And finally, what if there are certain field values that I do want > overwritten in addition to the new ones being brought in, but some > fields shouldn't be touched at all? >>> > > Hmph. I'd wait for Nicole's word on that. > > Cheers, > Brooke Thanks Brooke. I'm thinking I'll use Koha for one-at-a-time editing, and try to develop a sound workflow for bulk updating using external tools. Here are my current ideas - sanity check (from anyone) appreciated - and I realize it's a kludge, wish I were up to speed on text tools like Perl 8-( Unfortunately it seems that MARCedit is good for automating merges when you're merging in specific fields from consistent sources, matching control numbers etc, not for the kind of ad-hoc updating I'm doing. Note the below assumes I'm collecting a bunch of MARC records from a variety of sources, the goal being to cherry-pick the best quality data from each - some sources have good Subject headings, others more accurate imprint/collation data etc. 1 Export MARC records from Koha with a solid local control number (001) 2 Split these out into one-biblio-record per file named "koha.mrc", each in a folder named with the control number, drop item-level fields. 3 Bring in external MARC records, each file downloaded to the per-biblio folders, files named after the source. 4 Use MARCedit's to join all files per folder into one working multiple-record MARC file per title, then export as CSV and bring into a spreadsheet. One worksheet per title, one record per source MARC file. Column headers show the MARC fields used, everything's all in one place easy to scan. 5 Copy and paste, consolidate all into a single row (ensuring koha control number remains), delete the fields not used in Koha. Save/export the new master record back as MARC into the same folder named "new.mrc", 6 Join all the new.mrc's into a single file, stage into reservoir. 7 Use (one of the) Koha merge functions to update the existing biblios based on the control number matching - all existing data in each record overwritten by the incoming data. Obviously it would be great if either Koha or some other external tool allowed one to display multiple MARC records on screen in a GUI, allowing one to tick off the fields containing desired data, copying and pasting as needed and then one-button "merge" as specified to produce a new record. But it's a lot to ask I know, maybe one day Koha will have some of this. If I can help the developers at any stage from a motivated user's POV, someone please let me know how. And thanks in advance for any feedback on the above, especially suggestions on how to simplify a rather convoluted process, this just doesn't seem to be an area where one can KISS. I wish I could just say "eh good enough" and move on, but my OCD perfectionism won't let go 8-)

1 0

Koha 3.2.4 is now available
by Christopher Nighswonger 23 Feb '11

23 Feb '11

It is with pleasure that I announce the release of Koha 3.2.4. The package can be retrieved from: http://download.koha-community.org/koha-3.02.04.tar.gz You can use the following checksum and signature files to verify the download: http://download.koha-community.org/koha-3.02.04.tar.gz.MD5 http://download.koha-community.org/koha-3.02.04.tar.gz.MD5.asc http://download.koha-community.org/koha-3.02.04.tar.gz.sig Release notes for 3.2.3 are below the fold. Come and get it! RELEASE NOTES FOR KOHA 3.2.4 - 22 February 2011 ======================================================================== Koha is the first free and open source software library automation package (ILS). Development is sponsored by libraries of varying types and sizes, volunteers, and support companies from around the world. The website for the Koha project is http://koha-community.org/ Koha 3.2.4 can be downloaded from: http://download.koha-community.org/koha-3.02.04.tar.gz Installation instructions can be found at: http://wiki.koha-community.org/wiki/Installation_Documentation Koha 3.2.4 is a bugfix/maintenance release. Highlights of 3.2.4 ====================== Some of the higher profile bugs addressed in this release are: 2341 items marked 'On Order' (notforloan == -1) don't interact correctly with opac-reserve.tmpl 4263 repeatable subfields in items 5376 Batch Edit and Delete need Superlibrarian Permissions 5683 link_bibs_to_authorities.pl can corrupt records 5477 Test cases requiring database access fail 5681 Autobarcode using C4::Barcode has issues with leading zeros and large values 5731 If an item doesn't have a collection code set, moredetail.pl will error This release also contains a variety of minor enhancements improving Koha's interface and underlying scripts as well as updates to several translations. Bugs fixed in 3.2.4 ====================== 2742 Wrong language name in the preferences 3009 Change items.content field so it prints due date by default 3212 MARC21 leader plugins should force Leader/09 to 'a' 3319 Need a nicer error message when attempting to add a patron with no libraries defined 4160 Currency Conversion dosn't handle rates other than 100 5115 Tags JavaScript includes many untranslatable strings 5140 In Chrome, drop-down menus disappear after using pop-up calendar 5230 MARC export by call number range results in a zero byte file 5661 Authority search return an "Error 500" when "Sort by" is set to "No order" 5673 Incorrect Test of guarantorid 5689 System preference notifications are not translatable 5690 items.timestamp was not being updated when an item was edited 5691 If someone deletes all items, with independent branches on, it deletes all 5699 Don't ignore subfield 3 when building a new record (UNIMARC specfic) 5700 Statuses not being set properly 5718 Moveitem has the wrong permissions 5735 Expanding/collapsing cloned fields in editor takes original field 5736 Fixing some zebra configuration errors in marc21/biblios/record.abs 5741 Extra comma causes JavaScript error in Internet Explorer 5745 overdues with fines not showing titles 5777 System preferences Tab content title and Save button partially translatable 4306 Label manage batch listing should show item-level itemtype 5452 Overdue date color in borrower's today issues 5616 UTF-8 problem in Card View 5629 Adding anchor to holdings link in opac-detail.pl tabs 5665 Routing slip prints too wide for narrow printers 5702 Opac - Results : Highlight link need IF condition 5726 Fix a bug in the selection of biblios to merge 5727 Use of uninitialized value in concatenation (.) or string 5734 Fix column order in issue history 5751 Removing refetences to unused members quicksearch code/template 5759 When printing a borrowers information the secondary email address is not printed 5769 notice tab disappearing on edit patron 5776 menu on funds wraps when only 1 fund 5649 Change wording on review.tmpl from white/blacklists to approved/rejected 5654 misc/installer_devel_notes not needed 5716 Whitespace correction for browse shelf link 4931 Stocktaking must be based on holdingbranch instead of homebranch 5506 Translation Process Simplification 5532 "Saved" message for sysprefs editor should show names of saved prefs 5733 Empty cart in intranet when session is closed 5760 Add the jquery table sorter to borrowers reading record System requirements ====================== Changes since 3.0: * The minimum version of Perl required is now 5.8.8. * There are a number of new Perl module dependencies. Run ./koha_perl_deps.pl -u -m to get a list of any new modules to install during upgrade. Upgrades ====================== The structure of the acquisitions tables have changed significantly from 3.0.x. In particular, the budget hierarchy is quite different. During an upgrade, a new database table is created called fundmapping that contains a record of how budgets were mapped. It is strongly recommended that users of Koha 3.0.x acquisitions carefully review the results of the upgrade before resuming ordering in Koha 3.2.x. Documentation ====================== As of Koha 3.2, the Koha manual is now maintained in DocBook. The home page for Koha documentation is http://koha-community.org/documentation/ As of the date of these release notes, several translations of the Koha manual are available: English: http://koha-community.org/documentation/3-2-manual/ Spanish: http://koha-community.org/documentation/3-2-manual-es/ French: http://koha-community.org/documentation/3-2-manual-fr/ The Git repository for the Koha manual can be found at http://git.koha-community.org/gitweb/?p=kohadocs.git;a=summary Translations ====================== Complete or near-complete translations of the OPAC and staff interface are available in this release for the following languages: * Chinese * Danish * English (New Zealand) * English (USA) * French (France) * French (Canada) * German * Greek * Hindi * Italian * Norwegian * Portuguese * Spanish * Turkish Partial translations are available for various other languages. The Koha team welcomes additional translations; please see http://www.kohadocs.org/usersguide/apb.html for information about translating Koha, and join the koha-translate list to volunteer: http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-translate The most up-to-date translations can be found at: http://translate.koha-community.org/ Release Team ====================== The release team for Koha 3.2 is Release Manager: Galen Charlton <gmcharlt(a)gmail.com> Documentation Manager: Nicole Engard <nengard(a)gmail.com> Translation Manager: Chris Cormack <chris(a)bigallofwax.co.nz> Release Maintainer (3.0.x): Henri-Damien Laurent <henridamien.laurent(a)biblibre.com> Release Maintainer (3.2.x): Chris Nighswonger <cnighswonger(a)foundations.edu> Credits ====================== We thank the following individuals who contributed patches to Koha 3.2.4: D Ruth Bavousett Jared Camins-Esakov Colin Campbell Frédérick Capovilla Jerome Charaoui Galen Charlton Chris Cormack Frédéric Demians Magnus Enger Katrin Fischer Henri-Damien LAURENT Owen Leonard Chris Nighswonger Liz Rea Marcel de Rooy Paul Poulain Brice Sanchez David Schuster Robin Sheat Reed Wade Ian Walls We regret any omissions. If a contributor has been inadvertantly missed, please send patch against these release notes to koha-patches(a)lists.koha-community.org. The 3.2.x Release Maintainer especially thanks the 3.4 Release Team and all who participated in QA for their diligent labors in testing and pushing well over 330 patches since the 3.2.0 relese. Their continued work very much makes possible the release of 3.2.4 on its announced schedule. Revision control notes ====================== The Koha project uses Git for version control. The current development version of Koha can be retrieved by checking out the master branch of git://git.koha-community.org/koha.git The branch for Koha 3.2.x (i.e., this version of Koha and future bugfix releases) is 3.2.x. The next major feature release of Koha will be Koha 3.4.0. Bugs and feature requests ====================== Bug reports and feature requests can be filed at the Koha bug tracker at http://bugs.koha-community.org/ Naku te rourou, nau te rourou, ka ora ai te iwi.

8 11

Re: [Koha] help writing report
by ksckemperman＠chartermi.net 23 Feb '11

23 Feb '11

Found the anonymizer tool, which worked to clear circulation histories from the patron records; however the books in the history are still showing up in the report - I don't get it On Wed, Feb 23, 2011 at 11:20 AM, Nicole Engard wrote: > The report you shared was looking for collectiontitle and not book > title. So try this: > > > SELECT > borrowers.categorycode,borrowers.borrowernumber,borrowers.surname,borrowers.firstname,biblio.title,items.barcode,items.datelastborrowed > FROM borrowers LEFT JOIN statistics on > (statistics.borrowernumber=borrowers.borrowernumber) LEFT JOIN items > on (items.itemnumber = statistics.itemnumber) LEFT JOIN biblio on > (biblio.biblionumber = items.biblionumber) WHERE > borrowers.categorycode='3RD' > > As for clearing a patron's record there is a the anonymizer tool - but > I've heard mixed reviews of how it works. > > Nicole > > 2011/2/23 <ksckemperman(a)chartermi.net>: >> I am *trying* to create some reports for teacher/library use. What I >> need is >> a report that will list for each teacher the students names and the >> book(s) >> they have checked out today. I'd like it to read something like >> this: >> borrower category, borrower #, surname, first name, title of book, >> barcode, >> date checked out >> I have written this report, which is getting close to what I want, >> but the >> title of the book is not coming up (do I have the wrong value for >> that >> column?) and instead of reporting just the books that are currently >> checked >> out, the report lists every book in that student's history. Can >> someone >> help me to correct it? I am using the build new reports function >> because I >> don't really understand the whole SQL thing :) >> >> SELECT >> >> borrowers.categorycode,borrowers.borrowernumber,borrowers.surname,borrowers.firstname,biblioitems.collectiontitle,items.barcode,items.datelastborrowed >> FROM borrowers LEFT JOIN statistics on >> (statistics.borrowernumber=borrowers.borrowernumber) LEFT JOIN items >> on >> (items.itemnumber = statistics.itemnumber) LEFT JOIN biblioitems on >> (biblioitems.biblioitemnumber = items.biblioitemnumber) WHERE >> borrowers.categorycode='3RD' >> >> >> 2nd question - how do I clear a patron's circulation history? I have >> been >> using my daughter's # to practice/test different functions and now >> she has a >> history that is not accurate. >> Thank you, >> Shelley >> _______________________________________________ >> Koha mailing list http://koha-community.org >> Koha(a)lists.katipo.co.nz >> http://lists.katipo.co.nz/mailman/listinfo/koha >> >>

2 1

LibLime and Koha Community
by Tom Hanstra 23 Feb '11

23 Feb '11

I'm extremely new to the Koha Community and am trying to understand the relationship between the Koha Community developers and LibLime and its version of Koha. Based upon what I have read, LibLime forked off of the primary Koha community some time ago. Are the changes being developed there also being brought back into the open-source version of Koha? Is everybody working together so that database and software functionality is consistent? Or are these two versions slowly becoming more divergent over time? I hope I'm not kicking a hornet's nest here. I'm just trying to get a handle on how compatible these are and how to decide which version might best meet our local needs. Thanks, Tom Hanstra -- ----------------------------------------------------------------------------- Thomas A. Hanstra Systems Administrator Hesburgh Libraries of Notre Dame Phone: (574)631-4686 213 Hesburgh Library Email: hanstra(a)nd.edu Notre Dame, IN 46556 Welcome back my friends, to the show that never ends. We're so glad you could attend. Come inside, come inside... ELP -----------------------------------------------------------------------------

7 6

Re: [Koha] help writing report
by ksckemperman＠chartermi.net 23 Feb '11

23 Feb '11

Thank you, Nicole. That worked to report the book title, but I am still getting every book ever checked out on the report. Any thoughts on how to get only books *currently* checked out? On Wed, Feb 23, 2011 at 11:20 AM, Nicole Engard wrote: > The report you shared was looking for collectiontitle and not book > title. So try this: > > > SELECT > borrowers.categorycode,borrowers.borrowernumber,borrowers.surname,borrowers.firstname,biblio.title,items.barcode,items.datelastborrowed > FROM borrowers LEFT JOIN statistics on > (statistics.borrowernumber=borrowers.borrowernumber) LEFT JOIN items > on (items.itemnumber = statistics.itemnumber) LEFT JOIN biblio on > (biblio.biblionumber = items.biblionumber) WHERE > borrowers.categorycode='3RD' > > As for clearing a patron's record there is a the anonymizer tool - but > I've heard mixed reviews of how it works. > > Nicole > > 2011/2/23 <ksckemperman(a)chartermi.net>: >> I am *trying* to create some reports for teacher/library use. What I >> need is >> a report that will list for each teacher the students names and the >> book(s) >> they have checked out today. I'd like it to read something like >> this: >> borrower category, borrower #, surname, first name, title of book, >> barcode, >> date checked out >> I have written this report, which is getting close to what I want, >> but the >> title of the book is not coming up (do I have the wrong value for >> that >> column?) and instead of reporting just the books that are currently >> checked >> out, the report lists every book in that student's history. Can >> someone >> help me to correct it? I am using the build new reports function >> because I >> don't really understand the whole SQL thing :) >> >> SELECT >> >> borrowers.categorycode,borrowers.borrowernumber,borrowers.surname,borrowers.firstname,biblioitems.collectiontitle,items.barcode,items.datelastborrowed >> FROM borrowers LEFT JOIN statistics on >> (statistics.borrowernumber=borrowers.borrowernumber) LEFT JOIN items >> on >> (items.itemnumber = statistics.itemnumber) LEFT JOIN biblioitems on >> (biblioitems.biblioitemnumber = items.biblioitemnumber) WHERE >> borrowers.categorycode='3RD' >> >> >> 2nd question - how do I clear a patron's circulation history? I have >> been >> using my daughter's # to practice/test different functions and now >> she has a >> history that is not accurate. >> Thank you, >> Shelley >> _______________________________________________ >> Koha mailing list http://koha-community.org >> Koha(a)lists.katipo.co.nz >> http://lists.katipo.co.nz/mailman/listinfo/koha >> >>

1 0

KUDOS conference
by Buster 23 Feb '11

23 Feb '11

Hi, all. I read in another thread something about a Koha user group conference to be held in Madison, WI, in May. We are currently working on (or at least strongly considering) moving to Koha from Dynix Classic over the coming year. Could someone provide a link or other details about this conference? Thanks. --Jim Maroon -- ================================================== "The man, who, by his own and his family's labour, can provide a sufficiency of food and raiment and a comfortable dwelling place, is not a poor man."--William Cobbett, *Cottage Economy*, 1826.

3 2