- Koha - lists.katipo.co.nz

Windows OS -KOHA
by Julie Hulama 11 Jan '08

11 Jan '08

A consortium of legal libraries in Papua New Guinea are in the process to using KOHA as the preferred open source LMS and are i n the planning phase. Can someone advise if the only limitations for Windows OS is it does not allow for z39.50.... Is there another limitation in terms of library functionality and has anyone solve the ability to cater for z39.50 under windows? Happy to receive any comments. Julie Hulama Port Moresby

1 0

(no subject)
by M. Ram 11 Jan '08

11 Jan '08

I am new to Koha, we installed KOHA 2.2.9 and working on this. But when we add data (entry) simultaneously 3-4 peoples, system becames very slow.Kindly send me also ISBD format for AACR-2 and for accession No for rerieval form. How we control/protect duplicate entry on KOHA. At what level we make provision for this. Thanking you Mange Ram Incharge Central Library DEI(Deemed Univ), Dayalbagh, Agra-5

1 0

Katiaki
by BWS Johnson 11 Jan '08

11 Jan '08

Salvete! So, hypothetically speaking, when are elections for Katiaki? Cheers, Brooke

2 1

Migrating Data
by Lawrence Bean 10 Jan '08

10 Jan '08

We are in the process of migrating our data from Winnebago Circ/Cat to Koha 2.2.9. We exported the MARC records from Winnebago and imported them in to the Koha reservoir using the web interface, but now are unsure how to move those records into the active catalog other than doing it one-by-one by using the "add biblio" feature and searching by either title or ISBN. We're hoping that there is some way to batch process them all at once. It's unclear to us whether the bulkmarcimport.pl script will do this, or just import "complete" marc records also into the reservoire. Any guidance would be greatly appreciated.

1 0

Re: [Koha-translate] Translate Koha 3.0 into YOUR language
by Joshua Ferraro 09 Jan '08

09 Jan '08

On 1/9/08, Axel Bojer <axelb(a)skolelinux.no> wrote: > Joshua Ferraro wrote: > > Hi folks, > > > > Now that the alpha release of Koha 3.0 is out, we need to start lining up > > commitments from folks who want to translate Koha into their language. > > If you want your translation to be accepted for the 3.0 release, you MUST > > submit it before February 1st, 2008, which is the date that the Beta is > > released! Note: even partial submissions will be accepted. > > Good to know! > Does this mean it is a string freeze too, or will there be new strings? There will be a few new strings, the string freeze will happen after the Beta is released, everyone will get a chance to do a file update to their translation at that point ... > > So, what is the procedure for submitting a translation? You can, of course, > > roll your own, but if you want your translation to be included in the > > main release > > of Koha 3.0, we'd best have a bit of a formal procedure ... so here's my crack > > at an overview of the process: > > > > 1. Please take a look at http://translate.koha.org. Some translations already > > exist; please consider taking over an existing translation rather than starting > > a fresh one, unless the existing one is un-usably poor :-) > > > > 2. Please post your intent to translate Koha to the koha-translate list: > > > > http://lists.nongnu.org/mailman/listinfo/koha-translate > > > > In your email, please specify your Language, Region, and Country (and > > if your language uses a non-latin script, please also indicate the Script). > > Koha uses RFC4646 for managing language subtags, so it's important > > that we know all of those aspects of the language you're providing. > > We will translate koha into Norwegian, that means two writing languages: > Nynorsk and bokmål. I am the team coordinator :-) > No previous translations exists. Cool ... > > 4. Obtain the Translation Files. (doesn't apply if you use translate.koha.org) > > You need to copy two files from the Koha 3.0 repository, one for the OPAC, > > and one for the Staff Client: > > > > http://git.koha.org/cgi-bin/gitweb.cgi?p=Koha;a=blob_plain;f=misc/translato… > > > > http://git.koha.org/cgi-bin/gitweb.cgi?p=Koha;a=blob_plain;f=misc/translato… > > Ok. But I see this staff-file is bigger than the one I previously > downloaded. Is there a way to merge the new strings into my po-file that > is already started? KDE etc. uses such methods I think, but I have never > done it myself, so if someone has a receipt it would be nice :-) There's a way to do that within Koha, and I'm sure within your KDE environment. FWIW, the Koha method is documented here: http://www.kohadocs.org/usersguide/apb.html I'd be happy to do it for you if that would help ... > > 5. Naming your files. (doesn't apply if you use translate.koha.org) > > Starting with Koha 3, we're using RFC4646 language subtag > > naming conventions, (have a look at > > > > http://www.w3.org/International/articles/language-tags/ for an intro). > > > > RFC4646 has a concept of 'extensions' that Koha uses to tag for the 'theme' (t) > > 'interface' (i) and 'version' (v). For example, if you're creating a > > French translation > > from France, for the staff interface, and version 3.00.00.00, the > > filename would be: > > > > fr-FR-i-staff-t-prog-v-3000000.po > > We have started nb_NO-i-staff-prog-v-30000.po and will want to start > nn_NO-i-staff-prog-v-30000.po as well -- probably we will all use Kbabel. Sounds great! > > 6. If you've used translate.koha.org to submit your translation, when you have > > finished, the system will have that indicated on the report (100%). Otherwise, > > you'll have to send the file to us somehow. You can do that via email to the > > list (in which case i recommend creating an archive of the completed files, > > rather than sending them through in raw format). Or, if you are reasonable > > comfortable with the command line, you can submit them via Git as a > > patch. Here are the basic instructions for how to contribute using Git: > > > > http://wiki.koha.org/doku.php?id=en:development:git_usage > > Hmm, will take a look. For now I have downloaded them using the provided > link :-) 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

Translate Koha 3.0 into YOUR language
by Joshua Ferraro 09 Jan '08

09 Jan '08

Hi folks, Now that the alpha release of Koha 3.0 is out, we need to start lining up commitments from folks who want to translate Koha into their language. If you want your translation to be accepted for the 3.0 release, you MUST submit it before February 1st, 2008, which is the date that the Beta is released! Note: even partial submissions will be accepted. So, what is the procedure for submitting a translation? You can, of course, roll your own, but if you want your translation to be included in the main release of Koha 3.0, we'd best have a bit of a formal procedure ... so here's my crack at an overview of the process: 1. Please take a look at http://translate.koha.org. Some translations already exist; please consider taking over an existing translation rather than starting a fresh one, unless the existing one is un-usably poor :-) 2. Please post your intent to translate Koha to the koha-translate list: http://lists.nongnu.org/mailman/listinfo/koha-translate In your email, please specify your Language, Region, and Country (and if your language uses a non-latin script, please also indicate the Script). Koha uses RFC4646 for managing language subtags, so it's important that we know all of those aspects of the language you're providing. It's important that you post your intent, this way we can avoid overlap and perhaps can even do some collaboration. Note: even if you've contributed a contribution previously, please announce your intent so we can have you on record for the 3.0 version. 3. Determine the application you intend to use to do the translation. You have a few options: a. http://translate.koha.org will allow you to add your translations via a web-based interface. If your language, region, country and script are not listed, please email me and I will add them. b. Desktop Application - there are a few: LocFactory Editor (for OSX), POEdit (for Windows), Kbabel (for Linux). If you use a desktop application, please ensure that your encoding is set either UTF-8 or UTF-16, depending on your language's script support in UTF-8. Most languages should use UTF-8. c. Text file -- yes, you can edit POT files directly in a text editor, but please make sure you have the proper encoding as with the Desktop application. 4. Obtain the Translation Files. (doesn't apply if you use translate.koha.org) You need to copy two files from the Koha 3.0 repository, one for the OPAC, and one for the Staff Client: http://git.koha.org/cgi-bin/gitweb.cgi?p=Koha;a=blob_plain;f=misc/translato… http://git.koha.org/cgi-bin/gitweb.cgi?p=Koha;a=blob_plain;f=misc/translato… 5. Naming your files. (doesn't apply if you use translate.koha.org) Starting with Koha 3, we're using RFC4646 language subtag naming conventions, (have a look at http://www.w3.org/International/articles/language-tags/ for an intro). RFC4646 has a concept of 'extensions' that Koha uses to tag for the 'theme' (t) 'interface' (i) and 'version' (v). For example, if you're creating a French translation from France, for the staff interface, and version 3.00.00.00, the filename would be: fr-FR-i-staff-t-prog-v-3000000.po 6. If you've used translate.koha.org to submit your translation, when you have finished, the system will have that indicated on the report (100%). Otherwise, you'll have to send the file to us somehow. You can do that via email to the list (in which case i recommend creating an archive of the completed files, rather than sending them through in raw format). Or, if you are reasonable comfortable with the command line, you can submit them via Git as a patch. Here are the basic instructions for how to contribute using Git: http://wiki.koha.org/doku.php?id=en:development:git_usage Translations go in the misc/translator/po file, and should utilize the standard naming conventions. If you have a question, don't hesitate to ask. So ... any takers? Feel free to post on-list or email directly to me, I'll try to coordinate the activity. 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

Entering records in Lao or Thai
by Davita Janto 09 Jan '08

09 Jan '08

We haven't started using KOHA but will install soon. Are we able to enter records in Lao or Thai? Thanks. --------------------------------- Make the switch to the world's best email. Get the new Yahoo!7 Mail now.

2 1

Re: Unable to add patrons
by Paul McBride 09 Jan '08

09 Jan '08

Kia ora Brooke, Thanks for your reply. Sadly this hasn't helped. In my case, the system does not time out, it happily moves on to moremember.pl, but none of the data has been recorded. Quite foolishly, I didn't mention my setup: Koha 2.2.8 running under win xp Perl 5.008008 MySQL Ver 14.12 Distrib 5.0.45, for Win32 I noticed several people have mentioned the same problem before (e.g. http://www.nabble.com/Cant-Add-a-Patron-tt12738117.html#a12738117) but no solution has been recorded. If anyone has encountered this and has a suggestion, I would love to hear it! Kia ora ra, Paul. >Tena koutou, > >>I have just started using koha and am having trouble adding patrons. >Although I am am able to add biblio >>entries, when I try to add members, the details are not recorded. Upon >saving, the membership record is >>completely blank. >> >>I couldn't find an answer to this problem in the old posts or in forums >elsewhere. If anyone can help I >>would be most grateful... >> > >A long time ago when animals could talk, that sort of thing would happen >to me if I tried to reuse the same Patron number. It would occur if I >didn't fill all the mandatory fields, and also if the system had timed >out. > >Hope that helped, >Brooke

1 0

Announcing Koha 3.0 (Alpha)
by Joshua Ferraro 08 Jan '08

08 Jan '08

Hi folks, I'm happy to announce that a packaged alpha release of Koha 3 is now available. You can download from the usual location: http://download.koha.org/koha-3.00.00-alpha.tar.gz http://download.koha.org/koha-3.00.00-alpha.tar.gz.sig You can check the integrity of the package; either by verifying the provided GPG signature (.sig) or by comparing the MD5 checksum: 4fbd715cc6cd197264bba12b53391e42 koha-3.00.00-alpha.tar.gz I've also tagged this in Git as "version 3.00.00 alpha" v3.00.00-alpha This is the first packaged release of Koha 3. Prior to the official stable release of Koha 3.0, software issues, bugs, and unimplemented features must be addressed. These are documented on Koha's Bugzilla: http://bugs.koha.org and organized on the 3.0 RM's QA notes Wiki page: http://wiki.koha.org/doku.php?id=en:development:qanotes3.0 The release notes for this alpha version are pasted in below, and will also on the koha.org website sometime over the weekend. Cheers, -- Joshua Ferraro Koha 3.0 Release Manager ============================================================================== RELEASE NOTES FOR KOHA 3.0 ALPHA ============================================================================== Koha 3 is the next-generation release of the award-winning Koha open-source integrated library system. You can obtain Koha 3.0 Alpha from the following URL: http://download.koha.org/koha-3.00.00-alpha.tar.gz These Release Notes cover What's New in Koha 3, information about the new Revision control system (Git), and Version-release process, pointers to Download, Installation, and Upgrade documentation, a brief introduction to the new Templates, a call to Translation and Documentation writers, and finally, Known Issues with this version. ============================================================================== WHAT'S NEW IN KOHA 3? ============================================================================== 1. Zebra plugin - Zebra is a high-performance, general-purpose structured text indexing and retrieval engine. It supports large data sets (tens of millions of records) and includes support for SRU, Z39.50 and several query languages: CCL, CQL, and PQF. For more information about Zebra, please see: http://indexdata.dk/zebra Koha's new search engine, built on top of Zebra, supports features such as relevance ranking, field weighting, truncation, stemming, use of fuzzy operators, language-specific indexing, sorting, etc. Indexes are updated in real-time with circulation transactions, enabling limits by availability and statuses. Faceted refine-by limits are available from both staff and opac interfaces. For libraries that don't want the overhead of maintaing Zebra, Koha 3 ships with a NoZebra option, in which bibliographic and authority data is indexed in the RDBMS. 2. New installer - based on the common Perl module ExtUtils::MakeMaker, the new installer makes it a snap to get Koha running on just about any platform. The installer comes complete with a Developer's Toolkit target ('dev') that can be used to get a development environment linked directly to revision control, to support rapid prototyping and an agile development process. 3. Standard APIs - Koha 3 supports a number of important library search and retrieval standards and microformats, such as SRU/W, Z39.50 (http://www.loc.gov/standards/sru/) UnAPI (http://unapi.info/) and COinS/OpenURL (http://ocoins.info; http://www.niso.org/committees/committee_ax.html) Also supported is the popular Internet standard: OpenSearch (http://opensearch.a9.com/) created by Amazon's A9. Records are stored internally in an SGML-like format and can be retrieved in MARCXML, Dublin Core, MODS, RSS, Atom, RDF-DC, SRW-DC, OAI-DC, and EndNote; and the OPAC can be used by citation tools such as Zotero. Creating new export formats is a trivial exercise in writing XSLT; records can be passed through XSLT transformations either directly out of the index, or via a separate parsing function. To retrieve and interact with Circulation and Patron data, Koha 3 includes support for 3M's Standard Interchange Protocol (SIP2), using the OpenNCIP libraries (http://openncip.org) There are also an ever-expanding set of native REST APIs to handle interoperability with external tools such as third-party cataloging clients. These APIs provide authentication as well as add/edit/delete control over bibliographic data within a Koha system. For more information, see: http://wiki.koha.org/doku.php?id=en:development:web_services Koha 3 also includes pluggable authentication - easy integration with LDAP and Active Directory via the Auth_with_ldap module. The Amazon.com module can be enabled to enrich bibliographic data with jacket covers, professional reviews, ratings and comments from Amazon users, as well as point to 'Similar Items' within the catalog. OCLC's xISBN, and LibraryThing's ThingISBN can likewise be enabled to provide an 'Editions' tab on item detail pages. New with Koha 3 is service throttling for these services, to keep within subscription limits. 4. Cross-platform, multi-RDBMS, Web-server agnostic - Run Koha on the platform of your choice: Linux, Windows, Mac OS X, FreeBSD, Solaris. Koha 3 also includes better support for multi-RDBMS (MySQL 5.0 and PostgreSQL), and runs under Apache2, IIS, or the web server of your choosing. 5. Multi-lingual support - Koha was designed from the ground up for multilingual libraries. Koha 3 can handle Chinese, Japanese, and even right-to-left languages such as Arabic and Hebrew with ease (BiDi). Koha's index engine (Zebra) can handle record formats containing any UNICODE compliant script, such as Arabic, Chinese, Hebrew, Japanese and Korean. Zebra has this support via the ICU libraries created and maintained by IBM. You can translate Koha into your language using the built-in translation tools, or by visiting http://translate.koha.org. 6. New templates - Koha's staff and patron interfaces are developed with a template system that's easy to theme. The default templates are composed of 100% valid XHTML and CSS. Koha aims to meet or exceed U.S. Government Section 508 and W3C's WAI-AA standards for sight and motor impaired individuals. All Javascript usage comes with fallback modes that work in any web browser. 7. Koha 3 has quite a few new modules, as well as enhancements to existing modules, including: news writer, label creator, calendar, OPAC comments, MARC staging and overlay, notices, transaction logs, guided reports with a data dictionary and task scheduler, classification sources/filing rules. ============================================================================== REVISION CONTROL ============================================================================== With Koha 3, we've started using a new distributed revision control system called Git; it's the same system in use by many other projects, including the Linux Kernel. To learn more about how to develop Koha using Git, please see the Wiki page: http://wiki.koha.org/doku.php?id=en:development:git_usage ============================================================================== VERSION NUMBERING ============================================================================== With Koha 3, version numbering has been changed to use a method similar to Perl's: major.minor[.revision[.build]] * major: one digit * minor: two-digit * revision: two-digit * build: three-digit This alpha release of Koha 3.0 is versioned 3.00.00.041. Every database change or significant enough code change requires an update to the 'build' number, and developers will be able to easily upgrade their systems using the built-in updater. Koha 3.0 Release Schedule: This alpha release of Koha 3.0 will be followed by a beta release on Feb 1, 2008, including fixes to the following components: * General Bugfixing (everyone) * New API for item management (gmcharlt) * MARC21 Authorities (gmcharlt) * Improved I18N/L10N, lang detection (kados) * OPAC Templates re-design (oleonard) * Documentation and Translations (everyone) The final stable release of Koha 3.0 is slated for March 1 2008 and will include bugfixes to 3.0 beta. Subsequent releases of 3.0 will be bugfix releases, and won't include any new features. New features will be available in Koha 3.2 and subsequent releases. ============================================================================== UPGRADING FROM A PREVIOUS VERSION OF KOHA ============================================================================== The upgrade process from a previous version of Koha is documented on the Wiki at the following page: http://wiki.koha.org/doku.php?id=22_to_30 ============================================================================== TEMPLATES ============================================================================== You may have heard that the templates for Koha 3 have been re-skinned; there is also the start of a template style guide on the Wiki: http://wiki.koha.org/doku.php?id=en:documentation:templates_style_guide Kudos to Owen Leonard and the Nelsonville Public Library for their contributions! ============================================================================== TRANSLATIONS ============================================================================== Koha 3 alpha (this release) currently has complete translations for en-GB (English) and fr-FR (French). 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.nongnu.org/mailman/listinfo/koha-translate ============================================================================== DOCUMENTATION ============================================================================== User-contributed documentation for Koha 3 is available on the Koha Wiki (http://wiki.koha.org) The Koha Team welcomes documentation contributions; please join the Koha-devel list to volunteer: http://lists.nongnu.org/mailman/listinfo/koha-devel ============================================================================== KNOWN ISSUES ============================================================================== Known bugs are documented on the Koha wiki: http://bugs.koha.org and at the 3.0 RM's QA notes Wiki page: http://wiki.koha.org/doku.php?id=en:development:qanotes3.0

4 4

Bulk import problems in 3.0 alpha
by Bünzli Daniel 08 Jan '08

08 Jan '08

Hello, I have problems in importing data with bulkmarkimport and fail to see were they actually come from. The file notices.marc (see http://erratique.ch/tmp/notices.marc) contains 12 record in utf-8 encoded UNIMARC. That is characters 26-29 of 100 $a are set to "50##" (where # is space) which should mean utf-8 encoded AFAIK. Here's what I get when I try to bulk import it : > > ./bulkmarcimport.pl -c UNIMARC -d -file notices.marc > deleting biblios > .attempting to use non-existent class sorting routine > ....no mapping found for [0x96] at position 2 in BÖSIGER > g0=ASCII_DEFAULT g1=EXTENDED_LATIN at /opt/local/lib/perl5/site_perl/ > 5.8.8/MARC/Charset.pm line 210. > ERROR: failed to perform character conversion for record 5 > .no mapping found for [0x85] at position 1 in Åren utan nåd > g0=ASCII_DEFAULT g1=EXTENDED_LATIN at /opt/local/lib/perl5/site_perl/ > 5.8.8/MARC/Charset.pm line 210. > ERROR: failed to perform character conversion for record 6 > ...... > 12 MARC records done in 2.88230204582214 seconds The thing is that I don't know if this is a problem of my records (though I know of one other ILS that imports them fine), of Koha, of MARC::Charset or of my perl installation. Besides when I do a rebuild_nozebra I get the following errors : > > ./rebuild_nozebra.pl > *********************************** > ***** building BIBLIO indexes ***** > *********************************** > 2Cannot decode string with wide characters at /opt/local/lib/ > perl5/5.8.8/darwin-2level/Encode.pm line 182. > 3Cannot decode string with wide characters at /opt/local/lib/ > perl5/5.8.8/darwin-2level/Encode.pm line 182. > 4Cannot decode string with wide characters at /opt/local/lib/ > perl5/5.8.8/darwin-2level/Encode.pm line 182. > 6Cannot decode string with wide characters at /opt/local/lib/ > perl5/5.8.8/darwin-2level/Encode.pm line 182. > 8Cannot decode string with wide characters at /opt/local/lib/ > perl5/5.8.8/darwin-2level/Encode.pm line 182. > 10Cannot decode string with wide characters at /opt/local/lib/ > perl5/5.8.8/darwin-2level/Encode.pm line 182. > > Inserting records... > 159 > biblios done > > *********************************** > ***** building AUTHORITIES indexes ***** > *********************************** > > Inserting... > > authorities done Can anyone provide a hint ? Another thing is that I find it quite hard to actually see the data I import besides trying to search it. Is there a way to get lists of the data I have (say browse my catalog by title), know the number of records I have, browse my thesaurus and authors alphabetically ? Thanks for your answers, Daniel

2 3