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

Koha Error
by Abdou Youssef 21 Aug '08

21 Aug '08

Hello, plz i want a solution tothis problem that appeared when trying to run koha 3.00.00 Koha error The following fatal error has occurred:Access denied for user 'ukoha'@'localhost' to database 'kohadb' at /usr/share/perl/5.8/CGI/Carp.pm line 314. Compilation failed in require at C4/Circulation.pm line 25. BEGIN failed--compilation aborted at C4/Circulation.pm line 25. Compilation failed in require at C4/Overdues.pm line 24. BEGIN failed--compilation aborted at C4/Overdues.pm line 24. Compilation failed in require at C4/Members.pm line 27. BEGIN failed--compilation aborted at C4/Members.pm line 27. Compilation failed in require at C4/Auth.pm line 31. BEGIN failed--compilation aborted at C4/Auth.pm line 31. Compilation failed in require at /usr/lib/cgi-bin/koha/mainpage.pl line 24. BEGIN failed--compilation aborted at /usr/lib/cgi-bin/koha/mainpage.pl line 24.

2 1

Koha import problem
by Jason Macki 20 Aug '08

20 Aug '08

Hello, I've been able to import data from our old library system to Koha by uploading directly into the underlying mysql tables. That includes the marc data as well as the regular data tables. However, something about the ordering (I'm assuming) of the marc tags causes the search functions to not work properly. When I go into a record for editing and resave it through the web interface, the problem is corrected and the search functionality works. Does anyone know if there is a way to programmatically correct disordered Marc records, through a perl script or otherwise? Or do you have any other suggestions? My version of Koha is 2.2.9 running on Linux. Thanks for your time, Jason

1 0

Koha 3.00.00 debian install - a few minor observations
by Rick Welykochy 19 Aug '08

19 Aug '08

Hi all, I have completed a successful install of Koha/3.00.00 on Linux Deb (etch) running as a Linux vserver guest. My thanks and appreciation to all who contributed to making the installation process much easier and far more fool-proof than previous versions of Koha. I appreciated the final web-based configuration step. That allowed me (the sys admin) to hand over a completed install to the librarian and let her configure library thingies the way she wanted. My guess is that the deb-based install will be the easiest for the Linux crowd. Here are a few notes I made during the installation process. Note that the install was done on a *very* barebones instance of debian linux, with only a minimal number of packages installed to get the guest host to boot up. This is why there may have been some environmental differences from what one would normally expect in the base system. * debian package install is a good start and worked well, except libgd was not installed on my system: would be good to detect this and alert the sysadmin SOLUTION: sudo apt-get install libgd2-xpm-dev * cpan Perl package install worked except for 7 missing packages: SOLN: sudo cpan Email::Date GD HTML::Scrubber SMS::Send Text::CSV_XS Text::CSV Text::Iconv Of course, the GD problem was related to my not having libgb2 installed. * several attempts were made by debian apt to install and startup mysql 5 server, which we ignored since we already have a mysql 5 server that we can connect to * for the Koha install itself, the Perl method of make; make test seems wasteful: it copies some 145 MB of perl sources unnecessarily into blib then to /usr/share, and it takes a looooooong time. I suppose the upside is reproduceability and the ease of redoing parts of the make if required. * the instructions did not mention when to create the user 'koha': sudo adduser koha * we opt for having two domains (one for OPAC and one for admin) instead of using ports 80 and 8080. It was trivial to affect this change in the koha-httpd.conf file. Kudos on the Apache side of things :) All in all, a very good show. No hair pulling and minor issues easily resolved. thanks again, rickw -- ________________________________________________________________ Rick Welykochy || Praxis Services || Internet Driving Instructor The manual said Windows XP/SP2 or better so I installed Linux.

1 0

RFC 3.2: AJAX in the staff interface
by Jesse Weaver 18 Aug '08

18 Aug '08

(Full RFC at http://wiki.koha.org/doku.php?id=en:development:rfcs3.2:rfc32_ajax_in_the_s… ) Currently, in the svc/ directory and tagging tools, there are some cautious forays into using AJAX. However, many more areas of the staff (and possibly patron) interface could be improved using AJAX and well-structured web services. Towards this end, LibLime has made patches for AJAX usage on the circulation and issuing rules editor page. These patches make use of new Perl modules, and are based as much as possible on REST principles. MJ: Yes, the AJAX degrades. It even has its own system preference for the circulation screen.

1 0

Looking for KOHA Solution provider
by Noppadol Weerakitti 18 Aug '08

18 Aug '08

Hi, We have a KOHA project in Thailand and looking for an experienced KOHA solution provider who can spend time and resource here assisting us from planing, design, implement and train KOHA ILS. For more detail please contact directly to noppadol(a)tcdc.or.th Regards, Noppadol W. -- View this message in context: http://www.nabble.com/Looking-for-KOHA-Solution-provider-tp19027040p1902704… Sent from the Koha - Dev mailing list archive at Nabble.com.

1 0

RFC: setting up a test server
by Andrew Moore 15 Aug '08

15 Aug '08

Hi Koha Developers - I'm interested in setting up a system to run our test suite regularly and alert us of the results. You may know this as a smoke tester or a continuous integration server, but essentially, it's a thing that runs the test suite regularly and lets us know when things pass and fail. Here's how I picture it working, and please let me know if you have any suggestions or questions about it. I have set up a smolder server at <http://arwen.metavore.com:8000/app/public_projects/smoke_reports/1> that will accept test reports and display them with pretty red, yellow, and green boxes and other information. I expect my nightly test results to go in there, and if you or others would like to send test results there, that would be great. That's where we can look to make sure that stuff we added yesterday didn't break other features in other places in the code. To get the reports there, I just submitted a patch <http://markmail.org/message/upa6j34f6rwegsgr> for review that adds a few targets to the t/Makefile and a perl program to the t/ directory. These are so that you can run "make submit" from the t/ directory in the distribution to send your test results to the smolder server. I'll set up a cronjob to run the test suite on the latest git repository each night and submit the results to the smolder server. Based on any discussion that this email opens up, I may modify that patch and submit it intending for it to get applied. I've opened up bug 2498 <http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2498> to discuss this. There's also a page on the wiki that I started to describe these tools and how they can be used. <http://wiki.koha.org/doku.php?id=en:development:smoke_reports> You'll notice that none of this actually requires you or any other developers to change their behavior in any way. If you don't like this or have some kind of moral or religious objection to it, you can just ignore all of this smolder and smoke stuff and do just fine. So, let me know what you think, and expect the smoke test results to start showing up in smolder soon. Thanks, -Andy

1 1

RFC 3.2 - hold request targeting
by Galen Charlton 15 Aug '08

15 Aug '08

Hi, For 3.2, LibLime proposes to add a feature to target specific items to fill hold requests. This targeting, which would be done in conjunction with use of the holds queue batch job (build_holds_queue.pl) and its report, would allocate items that are sitting on the shelf to fill specific hold requests. The idea is that the library would run the holds queue report periodically, then use the report to pull items off the shelf in order to fill hold requests. When the report is generated, the batch job would also populate a new table (to be called hold_fill_targets) that recommends that specific items be used to fill specific hold requests. As items from the picklist are checked in, if the item is targeted to a specific hold, it would be used to fill that hold first instead of filling the request that happens to be at the top of the priority queue. Why do that? Suppose that a bib has two items, itemA and itemB, and suppose patron1 has a title-level request on the bib, and patron2 has an item-level request on itemB. Further, suppose that both items are available, meaning that both requests could be filled. At present, whether both requests are actually filled depends on the order in which the items are checked in. If itemA is checked in first, then patron1 gets it, and when itemB is checked in, patron2 gets it. Everybody is happy. However, if itemB is checked in first, patron1's request is filled, but patron2 is left waiting for the item. With the new targeting feature, the batch job will allocate items to fill particular requests, thus allowing all of the available items to be used to fill as many holds as possible, in priority order. The mechanism does assume that the library's workflow is to run the batch job, then *quickly* pull the items to put on the hold shelf or transfer to other branches. This mechanism will also be used to minimize the number of transfers by allocating items located at a branch to fill requests for that same branch. Regards, Galen -- Galen Charlton VP, Research & Development, LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709 skype: gmcharlt

1 1

Email::Date module
by Clay Fouts 14 Aug '08

14 Aug '08

Hello, all. Can anyone tell me what sort of terrible events will transpire if I install libemail-date-perl version 1.101-1 Etch package instead of the 1.103 version recently specified as a Koha dependency? I like to avoid installing modules directly from CPAN, but of course avoiding breakage is a higher priority. Thanks, Clay

2 1

Missing results when searching OPAC
by Daniel Alejandro Benavides D. 14 Aug '08

14 Aug '08

Dear members: We have installed here Koha 3.0 RC1 and after succesful using we have encountered that when searching through OPAC or Intranet interface, we don't get any results that we have seen before. We have made some imports of MARC records but then we can search either those imported too. Looking at mysql server, database koha, table biblio, we have the saved records. The url of the OPCA interface is at: http://168.176.86.15 and the given url when searching for "pascal" the browser url is: http://168.176.86.15/cgi-bin/koha/opac-search.pl?q=pascal Is there any way of altering the database or the system to have direct access to the Database, or better, what could be wrong? Thanks in advance ______________________________________________ Enviado desde Correo Yahoo! La bandeja de entrada más inteligente.

4 3

Koha 3 en español por favoe
by Christian Calle Jahuira 13 Aug '08

13 Aug '08

Estimados Amigos Agradesco muchisimo la cooperacion y la respuesta a este mensaje, no comprendo muy bien, solicite la version Koha-3.0.0 estable en Español, la traduccion completa al español. Si es este por favor necesito comprender y confirmar. Si alguien me comprende por favor estare muy agradecido Un abrazo Coordialmente ChristianJCJ 2008/8/13 Homero Almeida <homero1958(a)yahoo.com> Estimado Christian > Esta es la dirección entregada por el duro de Liblime sobre donde puedes > encontrar la version estable y ultima de KOHA > espero que te ayude > hasta pronto > homero > > --- El *dom 10-ago-08, Joshua Ferraro <jmf(a)liblime.com>* escribió: > > De: Joshua Ferraro <jmf(a)liblime.com> > Asunto: [Koha] Announcing Koha 3.00.00 > A: "koha-devel(a)lists.koha.org" <koha-devel(a)lists.koha.org>, > koha(a)lists.katipo.co.nz, koha-translate(a)nongnu.org > Fecha: domingo, 10 agosto, 2008, 5:15 pm > > 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 > _______________________________________________ > Koha mailing list > Koha(a)lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha > > > ------------------------------ > > Yahoo! MTV Blog & Rock > ¡Cuéntanos tu historia, inspira una canción y gánate un viaje a los Premios > MTV! > Participa aquí http://mtvla.yahoo.com/ >

1 0