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

Status of Debian and Koha
by Vincent Danjean 05 Aug '08

05 Aug '08

Hi, I'm pleased to announce that most of Koha dependencies (as listed in Makefile.PL) are present and up-to-date in Debian. The only exceptions are: * XML::RSS: the package libxml-rss-perl is outdated but its maintainer has just accepted that the package will be maintained by the Debian Perl Group. So it should be ok very soon. * Zebra [and Koha itself]: they will need more work According to a recent post on this list, zebra seems to require a more recent version of ZOOM (or at least of libyaz) than the one currently in Debian: Makefile.PL (from Koha) requires ZOOM >= 1.16 that works with libyaz2 2.1.48. Both ZOOM 1.16 and libyaz2 2.1.48 are on my webpage and in Debian experimental. But newer versions seem to be required. There is good hope here again that we will be able to upload an up-to-date yaz package in a few weeks. Next step: packaging zebra and Koha... Best regards, Vincent -- Vincent Danjean GPG key ID 0x9D025E87 vdanjean(a)debian.org GPG key fingerprint: FC95 08A6 854D DB48 4B9A 8A94 0BF7 7867 9D02 5E87 Unofficial pacakges: http://www-id.imag.fr/~danjean/deb.html#package APT repo: deb http://perso.debian.org/~vdanjean/debian unstable main

6 9

new sysprefs
by Paul POULAIN 20 Feb '08

20 Feb '08

Hello, i'm translating the syspref added this week, and have found some that are only defined, and not used in the code : - WebBasedSelfCheck - staffClientBaseURL - minPasswordLength - noItemTypeImages - noOPACHolds (+ kados said, and he was right, that setting "no" to a "noXXXX" parameter means "XXXX", so we should probably rename this syspref to something "positive") - emailLibrarianWhenHoldIsPlaced - holdCancelLength - libraryAddress - finesMode (this one is used, but only in C4/SIP/Patron.pm, which is, afaik, specific & not production ready - globalDueDate - itemBarcodeInputFilter - singleBranchMode - URLLinkText - noOPACUserLogin (which would be a duplicate of opacuserlogin iiuc + kados said, and he was right, that setting "no" to a "noXXXX" parameter means "XXXX", so we should probably rename this syspref to something "positive") - OPACDisplayExtendedSubInfo - OPACViewOthersSuggestions - OPACURLOpenInNewWindow - OPACUserCSS (what does this one mean ? We already have opacstylesheet, opaccolorstylesheet) - emailPurchaseSuggestions There are so many missing that I just checked my repo was uptodate !!! so, were they here by mistake ? it is some planned features ? something i've missed ? cheers -- Paul POULAIN BibLibre SARL Expert en Logiciels Libres pour l'info-doc Tel : 04 91 31 45 19

4 4

Koha 3.0 Staff Client Ready for Translation
by Joshua Ferraro 08 Jan '08

08 Jan '08

Hi all, Just a quick announcement for those of you interested in translating Koha 3.0 into your respective languages, the Staff Client POT file is ready for download and translation. I've created a generic POT that can be used, simply re-name the file to match your locale using RFC4646 conventions. Here's the link: http://git.koha.org/cgi-bin/gitweb.cgi?p=Koha;a=tree;f=misc/translator/po;h… (note that there is already a French translation written) The generic PO is called 'xx-XX-i-staff-prog-v-30000.pot'. You'll want to rename that file to match the language-script-region that you're translating. Starting with Koha 3.0, I'd like to propose a new naming convention for the PO/POT files in Koha that follows RFC4646 (have a look at http://www.w3.org/International/articles/language-tags/ for an intro). We can utilize RFC4646's concept of 'extensions' to tag for the 'theme' (t) and 'interface' (i) and 'version' (v). For example, if you're creating a French translation in France, the filename would be: fr-FR-i-staff-t-prog-v-30000.po Note that FR is a 'region' subtag ... but in some languages, such as Chinese, it's also useful to be able to distinguish between 'script's, such as 'Hans' (Simplified Han) or 'Hant' (Traditional Han). So you might, if you are translating Koha into Chinese, end up with a filename like: zh-Hans-i-staff-t-prog-v-30000.po RFC4646 gives us a lot of flexibility in how we distinguish between various translations. There are two excellent programs for doing your translation, depending on which platform you're running: LocFactory Editor (for OSX) POEdit (for Windows) Of course, you're free to simply use a text editor if that suites you, but please make sure you're in UTF-8 mode. Once you've got your PO file into a state where you're happy with it, you have a number of choies: 1. you can email it to the koha-translate list 2. you can email it to me 3. you can add it to Git yourself In the coming weeks I'll be updating translate.koha.org in preparation for the 3.0 cycle of releases, and improving the documentation on how to internationalize your Koha system, but if you prefer to work with local PO files, I wanted to make sure you had that opportunity. 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

2 1

updates to koha3 nozebra search indexing for MARC21
by Mason James 21 Dec '07

21 Dec '07

Hi koha-devel people, Ive been updating the marc index mapping for koha3-nozebra. The French team did a nice job on the UNIMARC stuff and ive had a go at padding out the currently pretty minimal MARC21 mapping. FYI: the *'s are wildcards, so, subject = '600*' means all 600 level subfields are used, when doing a 'subject' search any obvious errors or suggestions? thd, how does this look to your sharp arnd eagle-like gaze? ------------------------------------------------------------------------ ------------------------------------------------- 'title' => '210a,222a,240a,243a,245a,245b,246a,246b,247a,247b,250a, 250b,440a', 'author' => '100a,110a,245c,600a,610a,611a,700a710a,711a,800a,810a, 811a', 'isbn' => '020a', 'issn' => '022a', 'lccn' => '010a', 'biblionumber => '999c', 'itemtype' => '942c', 'publisher' => '260b', 'date' => '260c', 'note' => '500a, 501a,504a,505a,508a,511a,518a,520a,521a,522a,524a, 526a,530a,533a,538a,541a,546a,555a,556a,562a,563a,583a,585a,582a', 'subject' => '600*,610*,611*,630*,650*,651*,653*,654*,655*,662*,690*', 'dewey' => '082', 'bc' => '952p', 'host-item' => '952a,952c' ------------------------------------------------------------------------ ------------------------------------------------- Cheers, Mason -- Mason James mason.james(a)liblime.com Programmer www.liblime.com LibLime +64 21 542 117

5 5

C4 and date formats
by Ryan Higgins 21 Dec '07

21 Dec '07

Hey folks Just looking for a quick consensus on passing dates to C4 modules. Some expect iso, some expect local format. memberentry.pl is currently not working because the date is double iso'ed... I suggest the coding guideline that scripts maintain the date in local syspref-defined format, and that all public methods in C4::* should expect dates to be passed in local format. So format_date_in_iso should be rare at the script level. comments ? -- Ryan Higgins LibLime * Open-Source Solutions for Libraries Featuring KohaZOOM ILS 888-564-2457 x704

5 4

koha.org and kohadocs.org
by Bünzli Daniel 21 Dec '07

21 Dec '07

Both sites are routinely unavailable from this part of the world (europe). This is quite annoying (git.koha.org is, however, always up). Best, Daniel

5 8

Error message from bulkmarcimport.pl
by Bradley Peters 18 Dec '07

18 Dec '07

Hello, I was poking around the installation of koha that I made using the tarball linked earlier by Galen Charlton. Once I got the install done and entered some settings I tried to use the bulkmarcimport.pl command. Which failed with the following message: Undefined subroutine &main::GetMarcFromKohaField called at ./bulkmarcimport.pl line 219. I haven't figured out how to setup the Zebra index yet because the examples I've looked at so far all refer to there being records, but I don't have any yet. I was hoping that maybe running this command would give me some useful hints. Regards, Bradley Peters

6 13

RFC - installer changes
by Galen Charlton 18 Dec '07

18 Dec '07

Hi, I have made a number of changes to the installer and now have a version ready for general review. My git branch and the results can be accessed as follows: git repo: http://manage-gmc.dev.kohalibrary.com/koha-installer.git gitweb: http://manage-gmc.dev.kohalibrary.com/cgi-bin/gitweb.cgi?p=koha-installer.g… Tarball with the revised installer: http://manage-gmc.dev.kohalibrary.com/koha-3.00.00.032.tar.gz Changes include: * Prompting for more configuration information during perl Makefile.PL * Introduction of three installation modes: ** 'standard': typical install as root ** 'single': install everything under one subdirectory; meant for users who do not have root on their host but are allowed to install software. ** 'dev': run as much as possible from a git checkout * Improved conformance with FHS and Debian web application guidelines, particular in 'standard' mode. * Improved support for specifying where each logical installation target should go. * Replaced glob with a directory walk to identify files to be installed (thanks fbcit!). * Separation of Zebra configuration and data files in 'standard' mode. * Adjustment of Zebra configuration file layout. All Zebra config files in the Koha package are now installed and are available for use; the installer now simply sets profilePath to control which MARC and language options are in effect. * During 'standard' install, ownership of Koha's files can now be assigned to a non-root user (which should be different from the httpd user, of course). This allows most Koha server-side administration and web design tasks to be done without requiring root access. * Files are now installed with u+w. * By default the C4 Perl modules are bundled with the rest of Koha's files. * 'make test' now enabled * 'make' now just stages files in blib; nothing is actually installed until you do 'make install' * general bugfixes I should emphasize that by default the C4 modules are installed along with the rest of the Koha files, e.g. in /usr/share/koha/lib. They are not installed in any of the standard Perl module directories, although a packager could choose to put them there by setting PERL_MODULE_DIR when running perl Makefile.PL. As a consequence, this means that by default use of the PERL5LIB environment variable is necessary; 'make install' now prints a message suggesting the the user set KOHA_CONF and PERL5LIB in their profile. The default koha-httpd.conf now includes both of these variables. My main reason for doing this by default is that the C4 modules have at present no independent use outside of supporting Koha's CGI scripts and are intimately tied to the version of those scripts. Putting them in the default @INC will risk problems for users who need to run multiple versions of Koha on a box. Requiring use of PERL5LIB is not perfect, but it should be noted that we already have one required environment variable in the form of KOHA_CONF. If it is thought that this would cause too many problems, I would consider use of FindBin and use lib along with using rewrite-config.PL to set the correct module path in the command-line scripts. Related to this, I think it will be useful to consider specifying the version number when doing 'use C4::*' from the scripts, and possibly consider use of the 'only' pragma [1]. I would like to request that interested developers and users test the installer and provide feedback, debate, flames, etc. to koha-devel. My testing was done solely on Debian Etch, by the way. Also, please note that my repository was cloned from HEAD almost two weeks ago and I have not yet merged in current work, so please bear that in mind. Thanks to Henri-Damien Laurent, Chris Nighswonger, and Chris Cormack for contributing patches so far, and thanks to MJ Ray for creating the current installer on which my work was based. Regards, Galen -- Galen Charlton Koha Application Developer LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709 [1]: http://www.perl.com/pub/a/2003/03/18/only.html

6 19

Cannot search catalog
by Bünzli Daniel 14 Dec '07

14 Dec '07

Hello, I managed to import some records using bulkmarcimport. But when I try to search the catalog I get the following error (even though I did specify a search criteria). > No results found > You did not specify any search criteria. > > Error: Can't call method "size" on an undefined value at / > Applications/MAMP/htdocs/koha/lib/C4/Search.pm line 405. Any hint on what may be wrong ? This is on the latest master tree (with Galen's installer changes). Thanks for your answers, Daniel

1 0

Re: [Koha-devel] Internationalising Koha frameworks
by Thomas Dukleth 13 Dec '07

13 Dec '07

If you have any language specific or MARC variant specific Koha frameworks for sharing so that others may benefit from your frameworks in forthcoming Koha 3.0, the frameworks export script is now ready for multiple operating systems. Obtain the latest version of the Koha 2.2.X MARC Frameworks Export Script for your operating system. The export script should function from any system with mysqldump and access to the database as the Koha user given in koha.conf . The only essential requirement is having mysqldump included in the system $PATH when running the script. [A possible later version may allow specifying the path to mysqldump as a user option if someone thinks that is needed.] Koha does not need to be installed on the system running the script nor does it even need Perl. 2.1. OPERATING SYSTEM SPECIFIC SCRIPT VARIANTS. 2.1.2. UNIX BASED VERSION. For Unix based systems (Unix, GNU/Linux, Mac OS X, etc.) download the latest version of export_framework.sh. http://cvs.savannah.nongnu.org/viewvc/koha/misc/export_frameworks.sh?view=l… For installation requirements type: export_frameworks.sh -? i For help type: export_frameworks.sh -? For usage examples type: export_frameworks.sh -? e 2.1.2. MICROSOFT WINDOWS VERSION. For Microsoft Windows systems (Unix, GNU/Linux, Mac OS X, etc.) download the latest version of export_framework.bat for use as a script run from the command line console. http://cvs.savannah.nongnu.org/viewvc/koha/misc/export_frameworks.bat?view=… For installation requirements type: export_frameworks.bat -? i The installation requirements message explains how to obtain and install the bsdtar for Win32 dependency which is not needed for the Unix version of the script. For help type: export_frameworks.bat -? For usage examples type: export_frameworks.bat -? e 2.2. FINAL INSTRUCTIONS. Upon completion, after a few seconds, the script gives a specific message about where to send an email with the exported frameworks file attached so that it may be edited for inclusion as part of Koha 3.0 to share with everyone. If anything goes wrong, an appropriate error message is displayed. Please contact me on or off list if you have any questions or need assistance using the script. Thomas Dukleth Agogme 109 E 9th Street, 3D New York, NY 10003 USA http://www.agogme.com 212-674-3783 On Mon, November 26, 2007 4:07 am, Thomas Dukleth wrote: > Do you use MARC 21 in a language other than English? Do you use UNIMARC > in a language other than French or English? Do you use a MARC variant > other than MARC 21 or UNIMARC? > > If you have any language specific or MARC variant specific Koha frameworks > for sharing, please contact me on or off the list. LibLime has asked me > to prepare whatever MARC frameworks I can obtain for use in the > forthcoming version of Koha 3.0. Share yours so that others do not need > to do redundant work. > > [MARC frameworks are either bibliographic or authorities frameworks and go > by various names in Koha depending upon how you access them. In the > system administration intranet interface, they are identified as Biblio > framework (MARC structure) for bibliographic frameworks or Thesaurus > structure for authorities. In the installation directories, they have > names such as structure_def.sql for bibliographic frameworks or > authorities_normal_marc.sql for authorities.] > > I will supply very simple instructions for exporting your frameworks from > your SQL database if you need such assistance. > [...]

1 0