- Koha - lists.katipo.co.nz

MARC display - subfield 0 - possible bug
by Janusz Kaczmarek 13 Aug '08

13 Aug '08

Dear Koha Developers, I have noticed that Koha (probably) never displays "0" subfields in librarian MARC view (of course the subfield is not empty nor hidden and it is active). It is probably because of the line: $subf[$i][0] = "@" unless $subf[$i][0]; (line 165 of MARCdetail.pl). (A similar situation in case of line 134 of opac-MARCdetail.pl.) Isn't it a bug? Shouldn't the line be like: $subf[$i][0] = "@" unless $subf[$i][0] ne ""; ? But even if, what is the line for? If the subfield code is changed then probably the subsequent line will cause a 'next'... Regards, Janusz Kaczmarek

1 0

Koha with a proprietary frontend?
by Jonas Karlsson 13 Aug '08

13 Aug '08

Hello, I ask on behalf of a a Swedish library that wants to replace it's current ILS with an open-source one as part of an open-source initiative and is considering Koha. The (potential) problem is that they have recently had a custom web-based frontend (opac) created that they are very happy with and do not want to replace with Koha. This frontend is a proprietary solution that neither they nor the company that helped them write it want to take open source. In other words, they want to use the Koha backend with their own frontend (they do realize that they will most likely have to change their frontend to interface properly with Koha.) Would this be a problem from either a legal standpoint (as Koha is GPL-licensed) or a technical standpoint (i.e. is Koha's frontend and backend so tightly integrated it would be difficult to do this)? Has anyone on this list done something like it? Yours, Jonas Karlsson

2 2

Error faced on Koha v.3 demo for academic libraries
by selma aslan 13 Aug '08

13 Aug '08

Hi While trying cataloging on demo for academic libraries, when I attempted to save a Turkish book (ISBN: 9753253710) imported from Library of Congress the following prompt appeared: The following fatal error has occurred: Wide character in null operation at /usr/local/share/perl/5.8.8/MARC/Charset/Table.pm line 96. Apache Server version: Apache/2.2.3 Server built: Jan 27 2008 18:09:58 Koha 3.00.00.099 Koha DB 3.0000099 MySQL mysql Ver 14.12 Distrib 5.0.32, for pc-linux-gnu (i486) using readline 5.2 OS Linux lapch04.ec2.liblime.com 2.6.21.7-2.fc8xen #1 SMP Fri Feb 15 12:39:36 EST 2008 i686 GNU/Linux Perl 5.008008 Could someone please explain the reason for this error, if there is a bug or what? Thanks Selma Aslan Kutuphane ve Dokumantasyon Muduru TOBB Ekonomi ve Teknoloji Üniversitesi Sogutozu Caddesi No.43 06560 Ankara Tel. 0 312 2924030 Faks. 0 312 2924095 http://www.kutuphane.etu.edu.tr

3 4

Announcing Koha 3.00.00
by Joshua Ferraro 12 Aug '08

12 Aug '08

Hi folks, I'm happy to announce that a packaged release of Koha 3.00.00 is now available. You can download from the usual location: http://download.koha.org/koha-3.00.00.tar.gz http://download.koha.org/koha-3.00.00.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: 0008f53d22333f7f2beb55d9a23b792a koha-3.00.00.tar.gz I've also tagged this in Git as "version 3.00.00" v3.00.00 The main difference between the packaged release and the Git tree is the existence of fully-built translations (over 31) and a statically defined VERSION string in the Makefile.PL of the packaged release. This is the fifth packaged release of Koha 3. Subsequent releases of 3.00 will be bugfix releases, and won't include any new features. New features will be available in Koha 3.2 and beyond. A list of current bugs are documented on Koha's Bugzilla: http://bugs.koha.org The release notes for this 3.00.00 version are pasted in below, and will also appear on the koha.org website sometime soon. Cheers, Joshua Ferraro Koha 3.0 Release Manager ============================================================================== RELEASE NOTES FOR KOHA 3.0 ============================================================================== Koha 3 is the next-generation release of the award-winning Koha open-source integrated library system. You can obtain Koha 3.0 from the following URL: http://download.koha.org/koha-3.00.00.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. Enriched content web services, such as those offered by Amazon.com, Baker and Taylor's Content Cafe, and the Google Book API can be enabled to enrich bibliographic content with jacket covers, professional reviews, ratings and comments from users, as well as point to 'Similar Items' within the catalog. OCLC's xISBN, and LibraryThing's ThingISBN an likewise be enabled to provide an 'Editions' tab, pulling together all the formats, languages, and editions of a work into the 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, and more! ============================================================================== 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 release of Koha 3.0 is versioned 3.00.00.107. 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 release of Koha 3.0 includes the following general improvements over the beta release: * General Bugfixing (over 150 bugs fixed since RC1!) * Nomenclature cleanup * Additional translations * Lots more, consult git.koha.org for the complete changelog 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: Upgrading from 2.2 or earlier version: http://wiki.koha.org/doku.php?id=22_to_30 Upgrading from a previous version of 3.0: Please consult INSTALL files for details on how to upgrade ============================================================================== 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.0 (this release) currently has complete translations for the following languages: OPAC: de-DE (German), el-GR (Greek), es-ES (Spanish), en (English), fr-FR (French) hu-HU (Hungarian), it-IT (Italian), pt-PT (Portuguese), tr-TR (Turkish), ru-RU (Russian), uk-UA (Ukranian) zh-Hans-CN (Simplified Chinese in China), zh-Hans-TW (Simplified Chinese in Taiwan) Staff Client fr-FR (French), en (English), hy-Armn (Armenian), ru-RU (Russian), uk-UA (Ukranian) zh-Hans-CN (Simplified Chinese in China), zh-Hans-TW (Simplified Chinese in Taiwan) Additionally, Koha 3 (this release) has partial translations for the following languages: OPAC: am-Ethi (Amharic), bg-Cyrl (Bulgarian), fa-Arab (Persian), fi-FI (Finnish) gl (Galego), he-Hebr (Hebrew), id-ID (Indonesian), ja-Japn (Japanese), kn-Knda (kannada), ko-Kore (Korean), mi-NZ (Maori), pl-PL (Polish), tet (Tetum) Staff Client: de-DE (German), el-EL (Greek), es-ES (Spanish), hu-HU (Hungarian), ja-Japn (Japanese), tr-TR (Turkish), 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 3

Re: [Koha] switching from 'standard' to 'dev'
by Brendan Gallagher 12 Aug '08

12 Aug '08

All - I have created the new symlink for the koha site (it appears in the / etc/apache2/sites-available)... I did not see a web-installer when navigating to the koha- intranet.... should I see one when I make the reinstall from standard to dev (I was already on Koha 3.00.00.107)... Made all my changes in the record.abs indexers and I am now rerunning the zebra-indexer. (the indexer is showing the correct directories in kohaclone like it did before) --I will let you all know what I see after the indexer completes. Further response in message below. Thanks, Brendan On Aug 11, 2008, at 4:45 PM, Joshua Ferraro wrote: > Hey Brendan, > > Can you please post your responses to the list, that way they are > archived for > others to see and others may spot stuff I don't. > > First off, are you on debian, and are you running apache2? Are you > familiar with > the apache2 sites-available and sites-enabled paradigm and with the > 'a2ensite' > and 'a2enmod' utilities? These are the best starting places :-) I have some kind of idea -- > > > Josh > > On Mon, Aug 11, 2008 at 4:33 PM, Brendan Gallagher > <gallabr(a)biblio.org> wrote: >> ln –s /root/koha-dev/etc/koha-httpd.conf /etc/apache2/sites- >> available/koha >> ln: target `/etc/apache2/sites-available/koha' is not a directory >> >> Stuck here... >> >> On Aug 11, 2008, at 4:26 PM, Joshua Ferraro wrote: >> >>> On Mon, Aug 11, 2008 at 4:21 PM, Brendan Gallagher <gallabr(a)biblio.org >>> > >>> wrote: >>>> >>>> Hi All -- >>>> >>>> I need a little help... >>>> >>>> I just recently tried to switch my Koha 3 install from a >>>> 'standard' to a >>>> 'dev' install... >>>> >>>> These are the steps that I completed... >>>> >>>> 1. cd kohaclone >>>> 2. git pull --> (to get the most recent release) >>>> 3. perl Makefile.PL >>> >>> Did you choose 'dev' at this point, and use the same database name, >>> database >>> user name, password, etc.? Yes - same for everything.... >>> >>> >>>> 4. make >>>> 5. make test >>>> 6. make install >>> >>> At this point you should have fines in /home/myuser/koha-dev. >>> Rather than >>> use >>> the koha-httpd.conf from before you want to symlink >>> home/myuser/koha-dev/etc/koha-httpd.conf >>> to /etc/apache2/sites-available/koha and then a2ensite koha. You >>> no longer >>> need that older installation's filesystem /user/share/koha or >>> wherever >>> else >>> the old install files are, everything's now in kohaclone, and >>> /home/myuser/koha-dev. >>> >>>> 7. make changes to the koha-httpd.conf (navigated to the intranet >>>> homepage >>>> and never got the web-installer screen like I did for all other >>>> upgrades/installs) >>>> 8. export KOHA_DIR and PERL5LIB Those are the directories that I identified.... >>>> >>> >>> Make sure PERL5LIB is kohaclone, and KOHA_CONF is >>> /home/myuser/koha-dev/etc/koha-conf.xml >>> >>> Hope that helps, >>> >>> Josh >>> >>>> 9.. rebuild_zebra.pl -b -r (from the kohaclone/misc/migration_tools >>>> directory) >>>> >>>> I originally made changes to my zebra indexer located here >>>> /etc/koha/zebradb/marc_defs/marc21/biblios/record.abs >>>> after all this I know that I must make changes to the zebra >>>> indexer >>>> /etc/zebradb/marc_defs/marc21/biblios/record.abs --> but I can >>>> not find >>>> that file... all I can find is this location --> >>>> /root/kohaclone/etc/zebradb/marc_defs/marc21/biblios/record.abs >>>> and I >>>> made >>>> the changes here plus ran my zebra indexer --> no luck >>>> >>>> >>>> All of the changes/configs that I made in the standard install have >>>> transferred to my new set up -- but none of my records or index's >>>> have >>>> changed. I realize that I need to reindex but I am stuck since >>>> rebuilding >>>> does not show my records... >>>> >>>> All of my item records are in the 949 field and not the 952 >>>> field(koha >>>> default). >>>> >>>> Any advice would be greatly appreciated. >>>> >>>> Cheers, >>>> Brendan >>>> >>>> >>>> ++++++++++++++++++++++++++++++++++++++++++++ >>>> Brendan A. Gallagher >>>> Software Services Coordinator >>>> Bibliomation, INC. >>>> Middlebury, CT 06762 >>>> http://www.biblio.org >>>> ++++++++++++++++++++++++++++++++++++++++++++ >>>> >>> >>> >>> >>> -- >>> Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE >>> CEO migration, training, maintenance, support >>> LibLime Featuring Koha Open-Source ILS >>> jmf(a)liblime.com |Full Demos at http://liblime.com/koha | >>> 1(888)KohaILS >> >> > > > > -- > Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE > CEO 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 5

OPAC language selection
by Tim McMahon 12 Aug '08

12 Aug '08

Is there any way to change the order of the languages in the opaclanguages system preference or set the default language for the OPAC? It says the top language will be tried first, but we'd like to have the OPAC open with a language that's lower on the list. I was able to change it by editing the value in the database, but was wondering how you could set it from the Koha staff interface. -- Tim McMahon Technical Services West Liberty Public Library

1 0

Re: [Koha] Import items (holdings)
by Jesse Weaver 12 Aug '08

12 Aug '08

On Mon, Aug 11, 2008 at 9:43 AM, Library Guy <library.guy.zero(a)gmail.com>wrote: > My current system exports the MARCs and the holdings into separate files. > The MARC export routine inserts a item unique number into the 910 field, and > the Item export includes this unique number in the item export file. I've > imported my MARCs into Koha just fine, but I cannot figure out how to bulk > import my holdings and then have them link properly to the MARCs. Can > anyone help? > > Thank you! > To the best of my knowledge, Koha can't deal with this automatically. Is the item export a CSV file, a marc record with holdings tags, ...? Señor Guy, I forgot to send this to the list.

1 0

Issue entering the member details from the member entry page
by Sai Bhalaji D. 12 Aug '08

12 Aug '08

Hi, I have an issue entering the personal details of the members from the page. The url that it points to is http://intranet/cgi-bin/koha/members/memberentry.pl. *Issue *After entering all the details in the page, when I click on the save button, it takes me to the next page which does not contain anything. Also I checked the database wherein there is record created in the *Borrowers*table. If someone can help me out in resolving this issue, it would be very kind. Please let me know if any more details are required. Thanks, Sai Bhalaji. Sri Sathya Sai University.

2 2

Re: [Koha] Circulation function
by Jesse Weaver 12 Aug '08

12 Aug '08

On Mon, Aug 11, 2008 at 6:58 PM, Zareena Mohamed Murtadza < zmurtadza(a)wwf.org.my> wrote: > We do have a unique number for each book that we called accession number. I > wonder if I can use that number to replace barcode number. > > Thanks > Most likely; just make sure that the right subfield of the item tag is mapped to items.barcode, and change the name. Koha is very loose when it comes to barcodes; if you put unique accession numbers in, it should be happy. > >>> "Jesse Weaver" < > > Unfortunately, no. The easiest thing to do in this case might be to give > the > books you want to circulate a temporary barcode, so you can test > circulation. Does your library require being able to circulate without > barcodes? > P.S. Please make sure to CC the list in your replies.

1 0

Koha 3.0.x Git branch created
by Galen Charlton 11 Aug '08

11 Aug '08

Hi, I have created a branch for maintaining Koha 3.0.x in the public Git repository located at git.koha.org. This branch and the master HEAD currently point to the same state of the Koha source tree, the 3.0-stable version, but this will change as patches are accepted for 3.1. Specifically, work destined for 3.1 will be added to the master HEAD, and patches for the 3.0.x maintenance versions will be cherry-picked from HEAD or added directly to the 3.0.x branch. The branch is called 3.0.x - I decided to use something shorter than "3.0-maintenance". For Git users, the next time you do a git fetch, a reference to the remote branch will be fetched automatically. If you want to make a local branch in your git repository that tracks the official 3.0.x branch, you can do git fetch git branch --track my3.0.x origin/3.0.x Here "my3.0.x" is the name of your local branch, and "origin/3.0x" is the name of the remote branch that is being tracked. To check out that tracking branch, do get checkout my3.0.x If you are running a dev-mode installation of Koha 3.0 and you *don't* want your installation to start following the 3.1 developments, you should fetch, create the tracking branch, and check out that branch BEFORE rebasing and going through the database update. Later tonight I will be pushing a patch to master's HEAD that updates the version number to 3.01.00.000. Regards, Galen -- Galen Charlton VP, Research & Development, LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709 skype: gmcharlt

1 0