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

memcached and v3.2
by Paul POULAIN 01 Jul '08

01 Jul '08

Chris C. did some tests with memcached and it seems it's a great way to improve perfs of Koha. However, it requires some code changes. And an additionnal software installed on the server (memcached is provided on debian, and mandriva -contrib-, so it's probably not a true problem) I suggest that we add memcached option to Koha 3.2. Here could be a start for RFCs : - add a syspref usecached, to use or not memcached - memcache reference tables. I see the following reference things : context, sessions, userflags, permissions, language_*, systempreferences. Most of them are useed everytime a page is loaded in Koha (staff or opac) - memcache some other tables, that are often used : branches, itemtypes, auth_types, biblio_framework, categories, cities, ethnicity, opac_news "Memcaching" a reference table means modifying the GetTable() sub to check if the cache is already filled or not for this table : if ($usecache) { require Cache::Memcached; Cache::Memcached->import(); $memd = new Cache::Memcached( 'servers'=>['127.0.0.1:11211'], ); my $result = $memd->get("koha:reftable"); if ($result){ return $result; } else { $result = <retrieve result from SQL>; $memd->set("koha:reftable", $result, 300); # 300 : expire after 300 seconds. Can be set to more } } If you agree with this proposal, i'll add it to RFC for 3.2 pls comment. -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : 04 91 31 45 19 _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel

4 6

RFC: plan to reorganize cronjobs for overdues, notices, and fines
by Andrew Moore 01 Jul '08

01 Jul '08

Hi Koha Developers - After a brief audit of some of the code in misc/cronjobs it looks to me that the cronjobs that handle things like overdues, notices, and fines could use some work. There's a lot of overlapping functionality in the scripts in that directory, and not everything that we need for 3.0 is there yet. So, I'm hoping to find a reasonable way to get what we need easily. I'm looking for guidance here on developing a roadmap, so please speak up if you have recommendations. These are the scripts that I think we need: overdue_notices.pl - will prepare notices for items that are overdue. This increments the overdue notice counters. fines.pl - will calculate and update patron fines. This will NOT prepare notices. advance_notices.pl - will prepare notices for items that are not yet due, or have just become due. Patrons will have the option of receiving these or not. This is what will happen to many of the scripts that are there now: overduenotices-30.pl will get folded into overdue_notices.pl overduenotices-csv.pl will get folded into overdue_notices.pl overduenoties.pl will get replaced by overdue_notices.pl smsoverdues.pl will get replaced by overdue_notices.pl fines2.pl will get replaced by fines.pl fines-ll.pl will get folded into fines.pl. This script has good calculation stuff that should be salvaged. fines-sanop.pl will most likely be replaced by fines.pl. There are also some changes to the staff interface that will probably be done, as there is a similar disorganization there, but we can deal with that separately, I think. If we can agree on a general path like this, it will help us work together to reach a common goal. I can certainly get to much of this work myself in time, but there is some work going on in this directory by others and I want to make sure I'm not stepping on anyone's toes. If it looks like this path won't get us to where you think we should be, please speak up. If it looks like this is a reasonable way to proceed, please feel free to help out. Thanks! -Andy _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel

3 5

updates to patron messaging
by Andrew Moore 01 Jul '08

01 Jul '08

Hi Koha contributors - I've prepared a few patches to start reworking the patron messaging stuff that we have that's not quite working as we hoped in 3.0. The patches still have some parts that still need to be cleaned up or improved in them, and I don't expect them to be applied as is, but I want to get some feedback on the implementation. http://arwen.metavore.com/~acm/PatronMessaging/ I added a tab to the opac and to the patron management part of the staff interface. These allow users to edit preferences about how to receive the different types of messages sent to patrons. There is a new cronjob advance_notices.pl that prepares messages to be sent to patrons to let them know of items that are soon due or have just become due. I expect to eventually mimic this implementation in the overdues scripts as I outlined previously. <http://doiop.com/PatronMessaging> There is also a new cronjob, process_message_queue.pl, that is designed to actually send out messages of all kinds through SMS, email, or RSS and can be extended. I hope to be able to use this for other messaging besides just these. In order to send SMS messages, there is a new C4::SMS module that makes use of the SMS::Send module on CPAN. I'm hopeful that this will help us consolidate all of the different ways to send SMS messages. I'm hoping to get this polished up a bunch next week so that it can be applied, but I wanted to send this out today to make sure that it's not a surprise when it comes. Please let me know what suggestions or questions you have. Thanks! -Andy _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel

3 4

stats.pl/Stats.pm and Daily Reconciliation
by Chris Nighswonger 01 Jul '08

01 Jul '08

Hi all, I'm currently working on Bug 2008 involving the circulation report entitled "Daily Reconciliation." What I'm looking for is any kind of a specification outline for this report. The current code is quite broken. A little research in the wiki seems to indicate that the stats features in general were added in 2.2.2 ( http://wiki.koha.org/doku.php?id=en:development:roadmap2.2.x&s=stats) I'm particularly wondering what information we are looking for to be included in the Daily Reconciliation report. Should it include a line-by-line transactional summary or just entries for payments received, or simply some (which ones?) totals? Thanks, Chris Nighswonger _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel

2 1

Re: [Koha-devel] code formatting (was: [Koha-patches] [PATCH] Bug 2176: adding SMS::Send to list of dependencies)
by Andrew Moore 27 Jun '08

27 Jun '08

Hi MJ - On Mon, Jun 23, 2008 at 4:18 AM, MJ Ray <mjr(a)phonecoop.coop> wrote: >> > Why does this patch covertly reindent everything? >> >> I didn't intend for it to be covert. [...] > > OK. Please try to mention these things in comments. It'd be a bit of > a pain to cherry-pick a patch described as "adding SMS::Send ..." and > have the dep's rewritten without warning. Alright. If it helps you out, I'll add a comment about this to my growing commit template. I have started to try to bundle refactoring patches into a separate patch before functionality. I'll try to be a little more liberal on deciding what kinds of whitespace changes to pull out into a separate patch. >> I'd really like to be able to use perltidy to make the code that I >> edit and contribute more readable. Is there a particular indentation >> style that you think would be good to use on code that I change in >> Koha? I couldn't find much about this on the wiki. > > If my notes from 1.9 are accurate, we used to use > perltidy -bar -ce -pt=2 -vt=2 -en=4 > which is almost what is in the perlstyle manual, except cuddled elses. > However, it's not been enforced much and "more readable" depends on > what you're using to read it... Super, a step towards consensus! I've opened up bug 2269 to add a perltidyrc file with these options and will work to follow it. <http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2269> > The wiki really isn't in good shape and I find it too much of a pain > to edit. Searching the mailing list and IRC is usually more useful. > Should we create a HACKING file (which is what I think GNU software > calls the file) with the above sort of info in it? I agree that the wiki is tough to edit. I'm struggling to grow used to it, too. But, I think it could be a valuable resource, so I'm personally hesitant to abandon it. I was actually considering adding a "contributors checklist" or something similar on the wiki today. I think a HACKING file would be a great contribution, too. Perhaps you could also include some information about how to make your code translatable, too. That's an area that I'm struggling to find documentation on. Thanks! -Andy _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel

2 2

SMS::Send is mandatory now
by Zeno Tajoli 27 Jun '08

27 Jun '08

Hi to all, I'm testing a Koha 3.0 with the last update from git. I see that now SMS:Send is, praticaly, mandatory. It is used by catalogue/detail.pl, the pl that show the result of a search in the intranet interface. Not a problem, but now the module needs to be in the list of mandatory modules. I write down the error that I see in the browser. Bye Zeno Tajoli The following fatal error has occurred: Can't locate SMS/Send.pm in @INC (@INC contains: /var/donw/kohaclone/kohaclone2 /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .) at /var/donw/kohaclone/kohaclone2/C4/SMS.pm line 37. BEGIN failed--compilation aborted at /var/donw/kohaclone/kohaclone2/C4/SMS.pm line 37. Compilation failed in require at /var/donw/kohaclone/kohaclone2/C4/Letters.pm line 27. BEGIN failed--compilation aborted at /var/donw/kohaclone/kohaclone2/C4/Letters.pm line 27. Compilation failed in require at /var/donw/kohaclone/kohaclone2/C4/Serials.pm line 30. BEGIN failed--compilation aborted at /var/donw/kohaclone/kohaclone2/C4/Serials.pm line 30. Compilation failed in require at /var/donw/kohaclone/kohaclone2/catalogue/detail.pl line 25. BEGIN failed--compilation aborted at /var/donw/kohaclone/kohaclone2/catalogue/detail.pl line 25. Apache Server version: Apache/2.2.3 Server built: Jan 27 2008 18:13:21 Koha 3.00.00.096 Koha DB 3.0000096 MySQL mysql Ver 14.12 Distrib 5.0.32, for pc-linux-gnu (i486) using readline 5.2 OS Linux esx-fester 2.6.18-6-686 #1 SMP Thu May 8 07:34:27 UTC 2008 i686 GNU/Linux Perl 5.008008 Zeno Tajoli CILEA - Segrate (MI) tajoliAT_SPAM_no_prendiATcilea.it (Indirizzo mascherato anti-spam; sostituisci quanto tra AT con @) _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel

2 1

Re: [Koha-devel] Attending the ALA Conference Re: RFC for 3.2: Move items data from 952 to 949 by default
by MJ Ray 27 Jun '08

27 Jun '08

"Joshua Ferraro" <jmf(a)liblime.com> wrote: > I am out of my office from June 26th thru July 3rd attending the ALA > Annual Conference. [...] That's nice. Could you stop your auto-reply responding to list cc's please? Thanks, -- MJ Ray (slef) Webmaster for hire, statistician and online shop builder for a small worker cooperative http://www.ttllp.co.uk/ http://mjr.towers.org.uk/ (Notice http://mjr.towers.org.uk/email.html) tel:+44-844-4437-237 _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel

1 0

Re: [Koha-devel] [Koha-patches] [PATCH] Bug 2176: adding SMS::Send to list of dependencies
by MJ Ray 26 Jun '08

26 Jun '08

Warning: Reply-To set to koha-devel. "Andrew Moore" <andrew.moore(a)liblime.com> wrote: > I guess it should be optional. Good point. If it's an optional > dependency, how should I indicate that? Should I leave it out of > Makefile.PL altogether? I know no good way to indicate optional modules in Makefile.PL. Three choices that I think are better than total omission:- 1. put it in as a comment and POD string; 2. put it in as something like %CURRENT_PM like spamassassin does http://spamassassin.apache.org/full/3.0.x/dist/Makefile.PL 3. switch on META.yml generation and add a recommends line http://module-build.sourceforge.net/META-spec.html Which do people prefer? I'd lean towards doing (1 or 2) and 3. > > Why does this patch covertly reindent everything? > > I didn't intend for it to be covert. [...] OK. Please try to mention these things in comments. It'd be a bit of a pain to cherry-pick a patch described as "adding SMS::Send ..." and have the dep's rewritten without warning. > I'd really like to be able to use perltidy to make the code that I > edit and contribute more readable. Is there a particular indentation > style that you think would be good to use on code that I change in > Koha? I couldn't find much about this on the wiki. If my notes from 1.9 are accurate, we used to use perltidy -bar -ce -pt=2 -vt=2 -en=4 which is almost what is in the perlstyle manual, except cuddled elses. However, it's not been enforced much and "more readable" depends on what you're using to read it... The wiki really isn't in good shape and I find it too much of a pain to edit. Searching the mailing list and IRC is usually more useful. Should we create a HACKING file (which is what I think GNU software calls the file) with the above sort of info in it? Regards, -- MJ Ray (slef) Webmaster for hire, statistician and online shop builder for a small worker cooperative http://www.ttllp.co.uk/ http://mjr.towers.org.uk/ (Notice http://mjr.towers.org.uk/email.html) tel:+44-844-4437-237 _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel

6 11

RFC for 3.2: Move items data from 952 to 949 by default
by Joshua Ferraro 26 Jun '08

26 Jun '08

Hi folks, It's recently come to my attention that many ILSes store their items data in a 949 tag by default. Thusfar, we've stuck with the historical convention of 952 (which was our version of a 'localized' 852). 852, in the MARC21 standard, is reserved for 'holdings' data (holdings data is separate from items data, and there will be a future RFC addressing how Koha should handle holdings data). As Koha popularity expands, we should consider switching to the 'de facto' standard for items data (949). The need was brought to my attention recently on an OCLC list where it was discovered that OCLC uses 952 for internal codes, and therefore, it can't be exported. So libraries using OCLC for cataloging, who want to manually add their items data to their records, download them from OCLC, and them upload into Koha, will have to use another tag for items data. I'm thinking this would primarily consist of: 1. updating the default frameworks for MARC21 (UNIMARC too?) 2. updating the XSL stylesheets for MARC21 3. creating a script that moves stuff from 952 into 949 Thoughts? Cheers, -- 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 _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel

2 2

Announcing Koha 3.0 (RC1)
by Joshua Ferraro 26 Jun '08

26 Jun '08

Hi folks, I'm happy to announce that a packaged RC1 release of Koha 3 is now available. You can download from the usual location: http://download.koha.org/koha-3.00.00-stableRC1.tar.gz http://download.koha.org/koha-3.00.00-stableRC1.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: 5cc0914c5e8250c2491f4dbcf27d4301 koha-3.00.00-stableRC1.tar.gz I've also tagged this in Git as "version 3.00.00 stableRC1" v3.00.00-stableRC1 This is the third packaged release of Koha 3. Prior to the official stable release of Koha 3.0, translations will be updated; additional issues and bugs may be be addressed. A list of 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 RC1 version are pasted in below, and will also on the koha.org website sometime soon. Cheers, -- Joshua Ferraro Koha 3.0 Release Manager ============================================================================== RELEASE NOTES FOR KOHA 3.0 RC1 ============================================================================== Koha 3 is the next-generation release of the award-winning Koha open-source integrated library system. You can obtain Koha 3.0 RC1 from the following URL: http://download.koha.org/koha-3.00.00-stableRC1.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 release of Koha 3.0 is versioned 3.00.00.092. 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 (everyone) * New messaging enhancements (acmoore) * Lots of nomenclature cleanup * New testing suite (acmoore and gmcharlt) * SIP2 and LDAP fixes (atz) * Improved I18N/L10N, lang detection (kados) * Additional translations * Lots more, consult git.koha.org for the complete changelog This release candidate of Koha 3.0 will be followed by a stable release. 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-devel mailing list Koha-devel(a)lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel

2 1