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

Size of Patron Pictures.
by Michael Hafen 07 Apr '08

07 Apr '08

There are two concerns I have with patron picture. First is whether they are scaled by the server when uploaded or displayed. Second is if they should have a specified size. On the (english) help for the member details page it says, "You should be aware that the Details page will display the image at 25% of the original pixel dimensions." It would seem that the details page scales the pictures when they are displayed. I see nothing the the html or css that does this. Are the pictures scaled by the server? One of my users, while testing Koha 3, uploaded a very large image for a patron. He can no longer access the form for changing the patron image as the picture has covered the form. This is inconvenient. I would like to see a restriction placed on the size of patron pictures to prevent this. What I would like is an addition to staff-global.css like this: img#patronimage { max-height : 180px; max-width : 145px; } That should do the trick. Thanks. _______________________________________________ Koha-devel mailing list Koha-devel(a)nongnu.org http://lists.nongnu.org/mailman/listinfo/koha-devel

2 3

HTML-Template-Expr
by James Weinheimer 07 Apr '08

07 Apr '08

Hello, I was wondering if anyone has used HTML:Template-Expr with Koha? Would there be any problems using this extension? It would be nice to be able to work with values in the HTML-Template without having to go into the perl coding. I haven't worked with Koha 3.0 yet (although I am currently having it installed). Perhaps 3.0 is completely new and doesn't need these functions? Thanks, Jim James Weinheimer j.weinheimer(a)aur.edu Director of Library and Information Services The American University of Rome via Pietro Roselli, 4 00153 Rome, Italy voice- 011 39 06 58330919 ext. 327 fax-011 39 06 58330992 _______________________________________________ Koha-devel mailing list Koha-devel(a)nongnu.org http://lists.nongnu.org/mailman/listinfo/koha-devel

3 2

Announcing Koha 3.0 (Beta 2)
by Joshua Ferraro 04 Apr '08

04 Apr '08

Hi folks, Due to oversight on my part, there were a few template display issues with the Koha 3.00.00-beta release on March 23, 2008. I had also neglected to pre-install the available translations. Both these issues have been cleared up and are now available in a Koha 3.0 Beta 2 release. You can download from the usual location: http://download.koha.org/koha-3.00.00-beta2.tar.gz http://download.koha.org/koha-3.00.00-beta2.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: e314123c824d37ca39b67436a2b0d874 koha-3.00.00-beta2.tar.gz I've also tagged this in Git as "version 3.00.00 beta2" v3.00.00-beta2 The release notes for this beta2 version haven't changed from the last one, so I won't reproduce them here. Cheers, -- Joshua Ferraro Koha 3.0 Release Manager -- 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

1 0

Koha 3.00Beta, language template provided (to joshua)
by Paul POULAIN 04 Apr '08

04 Apr '08

Hello Joshua, I just see that in the 3.00beta package, the templates are not provided in the different languages. Thus, to get Koha 3.00beta in French, you have to use tmpl_process3.pl and generate the french templates. This is not explained in the install notes, unless i'm mistaken Have I missed something ? why didn't you generate localized templates before releasing ? I think, at least for a stable version, we should provide localized templates, even at the prize of a .tar.gz growth cheers -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : 04 91 31 45 19

2 1

Itemtype mismatch
by Eric Bégin 04 Apr '08

04 Apr '08

Hi, After installing Koha 3.0-beta (nozebra) with all sample data imported. I did create a document (imported from z39.50) and set its item type to Books, Booklets, Workbooks. In the staff side, the item type is ok, but in the opac, it shows as Audio Cassettes, CDs. Anybody has the same behavior? Thanks, Eric

1 0

Why in the OPAC v3 code are reserves limited to items with an itemtype set
by Michael Hafen 03 Apr '08

03 Apr '08

I'm looking that the latest code for opac-reserve.pl and around line 143 the item list is limited to only those items that have an itemtype set, either in the biblioitems or items table depending on the syspref. I would like to know why this is when it is possible to have a record with no itemtype set. It is possible to have no itemtype set when staging/importing records, and additem.pl leaves the option of no itemtype when the syspref is set and that field is visible. So, why is it necessary in opac-reserve.pl to have an itemtype when it is possible that an itemtype will not be set. That is my question. I might think of this as a bug, and would prefer that all items be listed regardless of whether there is an itemtype set. Thanks.

1 0

question/problem with date
by Paul POULAIN 02 Apr '08

02 Apr '08

Hello, It seems that the C4::Dates::format_date function, has a small problem : if the incoming date is 0000-00-00, then the result is : 02/00/0, which is not really a date. I think we should get a '' (nothing) in this case. I tried to understand why this happend, but could not understand. Do you think it's a bug ? -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : 04 91 31 45 19

4 4

Table sorting and articles
by Owen Leonard 02 Apr '08

02 Apr '08

I've been adding a javascript-based table sorter to many tables in the 3.0 staff client and OPAC. It's a jquery plugin (http://tablesorter.com) and allows one to set custom parsers for dealing with specialized kinds of data. I implemented a special parser for English-language articles, so that titles could be ordered correctly while ignoring "a," "an," and "the." $.tablesorter.addParser({ id: 'articles', is: function(s) {return false; }, format: function(s) { return s.toLowerCase().replace(/^(the|an|a) /,''); }, type: 'text' }); I'm hoping the same can be done for other languages by implementing a system preference that contains the articles ("the|an|a") in the script above. I'm a little concerned about how well Javascript will handle non-English or non-Western characters, but I don't have the right data to test. Some searching turned up the statement, "The default sort algorithm in JavaScript is based purely on the Unicode code point." Which would indicate that as long as Unicode orders things correctly JavaScript will too. I'm not sure this is the case. I'd like to get some feedback. Does this sound workable for other languages? Can anyone run some tests with some "exotic" data? Thanks, Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org

2 2

Re: [Koha-devel] migrate from Koha-2.9 to koha-3-Beta
by Ricardo Dias Marques 02 Apr '08

02 Apr '08

Hi Roxana... and everyone else! :) On Mon, Mar 31, 2008, Roxana Luz Fleipaz <roxanaluz(a)gmail.com> wrote: > One of you can help me to migrate from Koha-2.9 to koha-3-Beta I think that you mean Koha 2.2.9 (and not Koha 2.9). There is a tutorial in the Koha Developer Wiki - http://wiki.koha.org - that walks through the migration process from Koha 2.2 to Koha 3.0. That tutorial (HOWTO / guide...) is located at: Upgrading from Koha 2.2 to Koha 3.0 http://wiki.koha.org/doku.php?id=22_to_30 I have NOT tried to follow those instructions yet, but I will probably have to do it later on: I have a development environment running Koha 2.2.8 and a production environment running Koha 2.2.9, which will need to be migrated. > The operating system I use is Red Hat Enterprice 5 licensed. Well, my development environment does run a RHEL (Red Hat Enterprise Linux) "clone"/rebuild distribution, but it's a clone of RHEL version 4 (not 5). Besides, that machine will probably be discontinued or "migrated" to openSUSE 10.3 (or SLES 10 - SUSE Linux Enterprise Server 10). Best wishes, Ricardo Dias Marques lists AT ricmarques DOT net

1 0

very nerdish geek onto the lazy git
by Ignacio Javier 02 Apr '08

02 Apr '08

Hi all: I'm trying to undo changes I've made on a lot (70) files in my kohaclone directory, so trash them and revert all since the last commit I've made to the origin branch, anyone has idea how using a git command or commands sequence? I've tried a: git fetch git rebase --continue origin but a *more or less lot* of messages appear: ...pl: needs update Etc... So I wanted to understand this error without being neither Linus Torvalds neither Junio Hamano, then I did notice was impossible. Have anyone idea of a alternative psicology for the problem, (...so I need only the command line... ;-)? I'll give a thanks in atomic unicode to the person who solves this. Ignacio Javier Gómez Rodríguez Tfno: 902905590 - Fax: 981571425 ignacio.gomez(a)coremain.com www.coremain.com _______________________________________________ Koha-devel mailing list Koha-devel(a)nongnu.org http://lists.nongnu.org/mailman/listinfo/koha-devel

2 1