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

Update translations for 3.0.5
by Chris Cormack 05 Nov '09

05 Nov '09

Hi All There were some strings that missed being translated for 3.0.4, these have been fixed now and I have updated all the .po files at translate.koha.org. 3.0.5 will be released shortly, mostly to fix the translations, so if you have time, please spend some time making sure your language is up to date. Thank you Chris Translation Manager

1 0

Koha Upgrading to 3.00.04 from 3.00.02
by Parthasarathi Mukhopadhyay 05 Nov '09

05 Nov '09

Dear all, I was running Koha 3.00.02 on Ubuntu 9.04 (Jaunty) for the last several months. Yesterday I upgraded the system to ubuntu 9.10. But Koha 3.00.03 was running properly. Today I upgraded from 3.00.02 to 3.00.04. Upgradation went on successfully. but when i tried to access koha, both interface reported the same error --- ------------------------------------------------------------------------------ The following fatal error has occurred: Can't locate YAML.pm in @INC (@INC contains: /usr/share/koha/lib /etc/perl /usr/local/lib/perl/5.10.0 /usr/local/share/perl/5.10.0 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10 /usr/local/lib/site_perl .) at /usr/share/koha/lib/C4/Search.pm line 31. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Search.pm line 31. Compilation failed in require at /usr/share/koha/lib/C4/Heading.pm line 25. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Heading.pm line 25. Compilation failed in require at /usr/share/koha/lib/C4/Biblio.pm line 36. Compilation failed in require at /usr/share/koha/lib/C4/Reserves.pm line 26. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Reserves.pm line 26. Compilation failed in require at /usr/share/koha/lib/C4/Circulation.pm line 25. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Circulation.pm line 25. Compilation failed in require at /usr/share/koha/lib/C4/Overdues.pm line 24. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Overdues.pm line 24. Compilation failed in require at /usr/share/koha/lib/C4/Members.pm line 27. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Members.pm line 27. Compilation failed in require at /usr/share/koha/lib/C4/Auth.pm line 27. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Auth.pm line 27. Compilation failed in require at /usr/share/koha/intranet/cgi-bin/mainpage.pl line 23. BEGIN failed--compilation aborted at /usr/share/koha/intranet/cgi-bin/mainpage.pl line 23. Apache Server version: Apache/2.2.12 (Ubuntu) Server built: Aug 18 2009 13:02:37 Koha 3.00.04.019 Koha DB 3.0002012 MySQL mysql Ver 14.14 Distrib 5.1.37, for debian-linux-gnu (i486) using EditLine wrapper OS Linux libra2 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686 Perl 5.010000 ------------------------------------------------------------------------------- What to do? Should I go for re installation of PERL modules? Parthasarathi Mukhopadhyay Department of Library and Information Science University of Burdwan, Burdwan, Rajbati - 713104, WB -- _______________________________________________ Search for products and services at: http://search.mail.com

2 1

General IRC meeting 4 November 2009
by Galen Charlton 04 Nov '09

04 Nov '09

Hi, Apologies for the lack of reminders. A general IRC meeting of the Koha project will be held tomorrow, 4 November 2009 at 19:00 UTC+0. The meeting will be held on the #koha IRC channel at irc.katipo.co.nz. The home page for the meeting, which includes links to time converters, is http://wiki.koha.org/doku.php?id=en:events:meetings:irc_meetings:meetingnot… The agenda for the meeting is: 1. Update on Roadmap to 3.2. 2. Update on Koha 3.0 Roadmap. 3. Follow-up on actions from General IRC Meeting 7 October 2009. 4. Agree times of next meetings. Regards, Galen -- Galen Charlton gmcharlt(a)gmail.com

1 0

data import question & 008 use in Koha
by Christopher Curry 03 Nov '09

03 Nov '09

Hello all, We're in the middle of migrating MARC data to Koha. We tried importing serials data into Koha and a record that had 1900+ items attached did not import. I found the record and tested importing it, removing items until it would import and found out that 1238 was the maximum number of items I could import with one MARC record. Can anyone tell me if there is a way to configure the import to accept more items? I used bulkmarcimport.pl on Koha 3.0.1, running on Debian Lenny. Also, our old ILS has a database issue that results in incomplete export of records created from original cataloging. These records are missing 008 fields. We're working out a method of exporting the data from the back end and splicing it back into the MARC before import, but the data imports into Koha without announced or noticeable errors. I wonder if we're wasting our time. Does Koha use the 008 field for anything? -- Cheers, Christopher Curry Assistant Technical Librarian / Assistant IT Officer American Philosophical Society 105 South Fifth Street Philadelphia, PA 19106-3386 Tel. (215) 599-4299 ccurry(a)amphilsoc.org <mailto:ccurry@amphilsoc.org> *For technical support, please use helpdesk(a)amphilsoc.org <mailto:helpdesk@amphilsoc.org>* Main Library number: (215)440-3400 APS website: http://www.amphilsoc.org

3 3

Default Koha to MARC Mappings on nonexistent table fields?
by Kyle Hall 03 Nov '09

03 Nov '09

Hey All, We have set up a plain Koha 3 install which we are using for import testing. I wrote a script to rebuild the biblio, biblioitems, and items tables from biblioitems.marcxml using the data stored in marc_subfield_structure. What I have found is that some of the framework code seems to reference table columns that do not exists. The columns referenced are: * bibliosubject.subject ( there is no bibliosubject table ) * biblioitems.cn_edition * biblioitems.cn_prefix Can anyone provide any insight to this situation? Are these dead columns, or columns that were never added, or just bugs? Thanks, Kyle http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org )

3 2

Migrating from Sirsi to Koha
by Lee Phillips 02 Nov '09

02 Nov '09

Hello all, I would like to hear from any libraries or consortia that migrated to Koha from Sirsi. I am most interested in the ease of gaining access to bibliographic and user records for conversion into Koha. I know of one school district in Montana that had trouble accessing their records and had to pay for extraction from Sirsi. If your library has made this migration and would share your experience with me I would be grateful. Best Lee Phillips Butte Silver Bow Public Library Butte, MT

1 0

Foundation forming #koha IRC meeting 29 October
by Thomas Dukleth 30 Oct '09

30 Oct '09

Please remember that the next Koha foundation forming IRC meeting will be held on #koha 29 October 2009 at 19:00 UTC+0. Time Converters: http://tinyurl.com/yjvlsam http://www.wolframalpha.com/input/?i=2009-10-29%2019:00%20UTC+0 Agenda: http://wiki.koha.org/doku.php?id=en:events:meetings:irc_meetings:meetingnot… It is a wiki. Fix any problems and write your own agenda items. Thomas Dukleth Agogme 109 E 9th Street, 3D New York, NY 10003 USA http://www.agogme.com +1 212-674-3783

3 3

version 3.0.4 on download.koha.org
by LAURENT Henri-Damien 29 Oct '09

29 Oct '09

Hi, I have just seen that the latest version for 3.0.4 had been uploaded on download.koha.org Thanks to LibLime for doing that. But for sake of not misleading people, I would find that great that people donot have the choice between 2 versions of 3.0.4 Would any liblimer be so kind as to remove the first 3.0.4 tarball since I cannot do it myself, please ? -- Henri-Damien LAURENT Release maintainer 3.0 branch

5 11

Searching with name=
by Marcel de Rooy 29 Oct '09

29 Oct '09

Hi all, When I search with name= in OPAC or staff, I have exactly the same results as with any=. I checked this with several expressions. When I check the results with yaz-client, I noted different results for a find with 1=1002 (name) and 1=1016 (any). Somehow the search with name= does not get mapped correctly to 1=1002 (somewhere in opac-search.pl or Search.pm or in ZOOM). Searching with personal-name= works correctly. Do you have the same results with name as with any on your Koha OPAC or staff? Can someone explain me how I can change the behavior of the searches with name= ? Thanks for responding! Marcel de Rooy

2 3

Document Availability Information API
by Jakob Voss 28 Oct '09

28 Oct '09

Hi, I just sent this mail to Code4Lib mailing list that not everyone may follow. I am not familiar with Koha source code and database internals so could you point me to where availability status and such (loan period and queue, call number, location...) is stored? I just wanted to announce that I finished a reference implementation of the Document Availability Information API (DAIA) as CPAN module at http://search.cpan.org/perldoc?DAIA. More information about DAIA can be found in the specification at http://purl.org/NET/DAIA and at http://www.gbv.de/wikis/cls/DAIA. The basic structure is: [Document] -- 1-to-n --> [Item] [Item ]-- 1-to-n --> [Service] (which is either [Available] or [Unavailable]) We created DAIA for German library networks as interchange format and API to encode information about the current availability of a specific document (or any copy of it) in a given library. There are numerous APIs for several tasks in library systems (SRU/SRW, Z39.50, OpenSearch, OAI-PMH, Atom, unAPI etc.) but no standard way to just query whether a copy of given - for instance book - is available in a library, in which department, whether you can loan it or only use it in the library (or even read it online) or if it is not available how long it will probably take until it is available again. Obviously such an API would be helpful not only to connect different library systems but to create mashups and services ("Show me on a map, where a given book is currently hold and available", "Send me a tweet if a given books in my library is available again" etc.). DAIA was createt to fill this gap. In the context of ILS Discovery Interface Task Force and its official recommendation (http://diglib.org/architectures/ilsdi/) DAIA fits to the GetAvailability method (section 6.3.1). At the moment the format and API are pretty stable so the main work is to create server and client components for several ILS software. Every library has its own special rules and schemas - Jonathan Rochkind already wrote about the problems to implement DAIA because of ILS complexity: http://bibwild.wordpress.com/2009/09/02/daia-and-ils-complexity/ . We cannot erase this complexity by magic (unless we refactor and clean the ILS) but at least we can try to map it to a common data model which DAIA provides. With the DAIA Perl package you can concentrate on writing the wrapper without dealing with DAIA parsing and serialization issues. Why should everyone write its own routines to grab for instance the HTML OPAC output to parse availability status? One mapping to DAIA should fit most needs, so others can build upon. A public DAIA converter/validator is available at http://ws.gbv.de/daia/validator Extensions to DAIA can be discussion in the Code4Lib Wiki http://wiki.code4lib.org/index.php/DAIA_extensions but I'd prefer no to start with the extensions but with basic services. If you have more cool ideas for client applications, just let me know! Cheers, Jakob P.S: Yes, there are some other awkward attemts to encode availability (Z39.50 Holdings, ISO 20775 Holdings, NCIP, SLNP...) but I found all of them underdefined and not publically documented or openly usable based on Web standards. -- Jakob Voß <jakob.voss(a)gbv.de>, skype: nichtich Verbundzentrale des GBV (VZG) / Common Library Network Platz der Goettinger Sieben 1, 37073 Göttingen, Germany +49 (0)551 39-10242, http://www.gbv.de

2 1