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

Acquisition module
by paul POULAIN 19 Dec '08

19 Dec '08

Hello world, Some of you already know that BibLibre is working hard on a new acquisition module, that will be for koha 3.2 it's almost done & will be used in production soon by the SAN-Ouest Provence (based on a 3.0.x + new_acq) We plan to send the patches for main (3.2) branch in january. So : - librarian : you'll be invited to test features to see if we don't have lost something by mistake. - developpers (and those that work on code cleaning/strengthening atm), pls don't touch the acqui module, that will make the merge much more complex (and some of your stuff may be lost in the process) Many of the features announced in the wiki are done : http://wiki.koha.org/doku.php?id=en:development:rfcs3.2 The missing ones will be added quickly. -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

3 2

For 3.0.x update XML::LibXML and XML::SAX with cpan
by Zeno Tajoli 19 Dec '08

19 Dec '08

Hi to all, I have found same problems in the tree of 3.0.x I have update my installation of 3.0.x with git and I see on the splash page: Koha error The following fatal error has occurred: Can't locate object method "new" via package "XML::LibXML::SAX" at /usr/share/perl5/XML/SAX/ParserFactory.pm line 43. Compilation failed in require at /var/donw/kohaclone/kohaclone2/C4/Biblio.pm line 26. [...] To fix the problem I need to update the perl modules XML::LibXML and XML::SAX with cpan. In my installation those modules were installed using the debian stable versions (packages libxml-libxml-perl and libxml-sax-perl) I can't update them if I use etch packeges, probably lenny (unstable) packages are enough. But I have updated them with cpan and all is OK, now. I suggest to write into INSTALL.debian: 1.6.4 If you use debian stable (etch) you have two cpan modules not enough updated. So now update XML::LibXML and XML::SAX using cpan Bye Zeno Tajoli CILEA - Segrate (MI) tajoliAT_SPAM_no_prendiATcilea.it (Indirizzo mascherato anti-spam; sostituisci quanto tra AT con @)

2 1

RFC: Koha 3.2: Koha E-R diagrams and tables information
by Matteo Romanello 18 Dec '08

18 Dec '08

Dear all, I'm quite new to the list. A month ago I started working supervised by Zeno Tajoli (CILEA, Italy) on the task of providing some new documentation to Koha 3.0 DB. The main problem I'm facing now is how to ensure the persistence of descriptions and other information on tables and columns despite, for example, name changes over different releases of Koha. A likely solution is supposed to be the use of opaque identifiers along with a mechanism capable of parsing the perl script which updates the db and of capturing information concerned with changes of the db structure itself. I'll write hopefully soon to ask for some feedback and/or help! Thanks Matteo Romanello

1 0

Re: [Koha-devel] RFC Adding column to biblio for Remainder Of Title
by Michael Hafen 17 Dec '08

17 Dec '08

Thanks, that helps a lot. I think I understand now. Good link there. I was getting confused at step 2. I understood everything else pretty well though. I'd like to do something similar with call numbers. That is to only show the unique call numbers. Now I'm seeing how to do it, I wasn't so sure how it worked before. Just have to figure out the syntax needed to make a key of the 952$o now, and that shouldn't be to hard. I should be able to find a good example of that in the xsl. On the other hand maybe not, since the xslt processing isn't done on the staff interface. I don't think my librarians would be satisfied with the 245$b only showing up on the opac interface. On Tue, 2008-12-16 at 18:30 -0500, Galen Charlton wrote: > Hi, [snip] > That clause really does scan all of the available items and counts the > number of available items for each home branch. It uses the > Muenchian method to do the grouping; see > http://www.jenitennison.com/xslt/grouping/muenchian.html for an > explanation of the general technique. In this case, the XSLT is: > > [1] Putting a list of all available item nodes into the > $available_items variable by doing a lookup on the item-by-status key, > which is defined in line 10 of the stylesheet: > > <xsl:key name="item-by-status" match="items:item" use="items:status"/> > > [2] Selecting each node in $available_items that is the first > available item for each homebranch; this uses the > item-by-status-and-branch key. > > [3] Emitting the homebranch and a count of available items in that > homebranch, again using the item-by-status-and-branhc key. > [snip] > Regards, > > Galen -- Michael Hafen Systems Analyst and Programmer Washington County School District Utah, USA for Koha checkout http://koha-dev.washk12.org or git://koha-dev.washk12.org/koha

1 0

RFC: Koha : Merge biblio & biblioitems tables
by Ryan Higgins 17 Dec '08

17 Dec '08

Late entry, I know, but I would like to get rid of the clunky extra table, and merge the columns that we need from biblioitems into a new biblio table. I've listed the columns to keep on the wiki; please review and add any that are missing. http://wiki.koha.org/doku.php?id=en:development:rfcs3.2:rfc32_biblio_table -- Ryan Higgins LibLime * Open-Source Solutions for Libraries Featuring KohaZOOM ILS 888-564-2457 x704

10 34

French sysprefs file encoding
by Jesse Weaver 16 Dec '08

16 Dec '08

Hello, I noticed that various patches to the systempreferences creation SQL script for French have been in the Latin-1 encoding. The base encoding for the file is UTF-8. I'm not sure how tolerant MySQL is of this, but it's very visibly broken in a Vim editing session. Not out to chop off heads, just thought everyone would want to know. -- Jesse Weaver Software Developer, LibLime

3 3

Koha 3 on Ubuntu Gutsy (7.10)
by Partha Mukhopadhyay 14 Dec '08

14 Dec '08

Dear all Let me share with you a success story. Today we are able to run Koha 3 on Ubuntu 7.10 Gutsy Gibbon with Zebra server on. It's working nicely and all modules are functional. The extent of improvements in Koha 3 is simply amazing. Hats off to you genius developers of team Koha. The installation guide (although quite helpful) available at Koha wiki (http://wiki.koha.org/doku.php?id=ubuntu_gutsy) needs to be modified slightly. I wrote down the modifications we did during the installation time. The document will be submitted to wiki within a week. Thanks and regards again to developers. Dr. Parthasarathi Mukhopadhyay Department of Library and Information Science University of Burdwan, Burdwan, West Bengal, India -- _______________________________________________ Search for products and services at: http://search.mail.com

2 1

More encoding issues
by Chadwick, John, DCA 13 Dec '08

13 Dec '08

Quick question concerning the following wiki page on encoding: http://wiki.koha.org/doku.php?id=encodingscratchpad. Some of the information in the wiki seems to be more applicable to MySQL 4.1 instead of 5.x Also, some of the suggested changes to modify tables seem to refer to tables that are not in Koha 3.0.1. Specifically, there is no table called marc_subfield_table. There is a marc_subfield_structure. There is no abstract in the table biblioitems. -- Convert the database default encoding to UTF-8 and default collate to utf8 ALTER DATABASE kohawipofinal DEFAULT CHARACTER SET utf8 DEFAULT COLLATE utf8_general_ci; -- change the table encoding type (varchar -> binary -> varchar ) for MARC Data alter table marc_subfield_table modify subfieldvalue BINARY(255); alter table marc_subfield_table modify subfieldvalue VARCHAR(255) CHARACTER SET utf8; -- change the table encoding type (text -> blob -> text ) for Koha Tables alter table biblio modify title BLOB; alter table biblio modify title TEXT CHARACTER SET utf8; alter table biblio modify author BLOB; alter table biblio modify author TEXT CHARACTER SET utf8; alter table biblio modify unititle BLOB; alter table biblio modify unititle TEXT CHARACTER SET utf8; alter table biblio modify notes BLOB; alter table biblio modify notes TEXT CHARACTER SET utf8; alter table biblio modify seriestitle BLOB; alter table biblio modify seriestitle TEXT CHARACTER SET utf8; alter table biblio modify abstract BLOB; alter table biblio modify abstract TEXT CHARACTER SET utf8; alter table biblioitems modify abstract BLOB; alter table biblioitems modify abstract TEXT CHARACTER SET utf8; That should do it for now. John +----------------------------------------------------------------------- -----+ John Chadwick, Ed.D. Information Technology Manager New Mexico State Library 1209 Camino Carlos Rey Santa Fe, NM 87507 Phone: 505-476-9740 Cell: 505-629-8116 Fax: 505-476-9761 john.chadwick(a)state.nm.us http://www.nmstatelibrary.org Confidentiality Notice: This e-mail, including all attachments is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited unless specifically provided under the New Mexico Inspection of Public Records Act. If you are not the intended recipient, please contact the sender and destroy all copies of this message. -- This email has been scanned by the Sybari - Antigen Email System.

1 0

TMPL_VAR default
by Joe Atzberger 11 Dec '08

11 Dec '08

Nahuel's recent patch for "no title" reminded me of something. I don't think there is any problem with the patch, but I wanted to bring up the use of TMPL_VAR DEFAULT attribute, like:  I like the way that looks. But am I remembering correctly that there is some flaw in the translation system that impedes our use of this rather useful feature? If so, can anyone say more specifically what the problem is? That should be regarded as a bug worth fixing, and not some natural limitation that we just have to work around. I'm willing to attempt it if anybody can narrow the problem down. --Joe Atzberger

3 2

Koha 3.00.00 on Debian Sid - Install Report.
by Mahesh T. Pai 11 Dec '08

11 Dec '08

First, I am not subscribed, So any questions should be cc'ed to me. And apologies for cross posting - I cannot figure out which list this should be sent to. I got the system at around 6 PM last Saturday, and finished the job today (11th) morning - around 11 AM. OS install + Koha configuration took a mere 5 days. The OS installation was a battle, which ended only on Tuesday morning. I will not bother the list with details. Suffice it to say that the fault certainly was not Debian's. My ISP was corrupting the .iso files I was downloading. :-( The OS was Debian Sid/Unstable amd64 on a Intel D processor. That is all I needed to know about the hardware. Pristine install using debootstrap, and other packages added after rebooting from that install. Koha debian packages came from git.debian.org, (see the comments on http://blog.bigballofwax.co.nz/2008/08/05/koha-3-packaging/) "deb http://apt.workbuffer.org/ intrepid all" Is the line I had to add to /etc/apt/sources.lst. The packaging was buggy, but they got the dependencies right. Every dependency was fixed properly. The .debs failed to create sub directories under /etc/koha/ - a serious problem. I had to create the directories manually, and then do a "dpkg -i /var/cache/apt/archive/koha-<whatever>.deb" manually. Easy, eh?? It took me 3 days to sort out problems reaching the koha web-install page. I had the following lines in /etc/hosts 127.0.0.1 localhost library 127.0.0.2 librarian.koha 127.0.0.3 catalog.koha. "Catalog" is easier to remember than "OPAC", right? Since it was intended to be a stand alone system, I was tempted to leave out port 8080 part in apache2 configuration, but decided that the people who use it (there is a strong community of librarians here who are well aware of koha) may get confused with absence of 8080 in the URL. All the problems have been already reported on this (or -devel) lists, and googling was quick to give answers. But that it took 3 days means there were several problems. First was failure of the install scripts to put the table's names, user name, and password into the /etc/koha/koha-config.xml file. And there is some directive in koha-config.xml which put the "method to access the database as "sql". It ought to have been "mysql". Once this was sorted out, the catalog page would load, saying that the server is down for maintenance. But the web install refused to come up, complaining of some fatal error. This meant I had to manually install CGI::session from the tarball on cpan, as already mentioned in one of the lists. CGI::session I manually installed was same as the version in Debian. Guess this should go int INSTALL.debian file. Except the database configuration, I guess everything else in that file could be handled by debian installer, IMHO. Rounded off the install with a simple index page in /var/www/ with links to http://librarian.koha:8080 and http://catalog.koha. Further problems with the debian packages (snd some with koha itself). 1. Cid not create the cron jobs. (I did not realise it, till after I handed over the system. What are the consequences?) 2. I guess Debian packages does not create the appropriate files in /etc/init.d/ for the idzebra daemon. The koha-zebraqueue--ctl.sh is invoking the "daemon" binary, but debian uses start-stop-daemon binary. Hope things will run. I installed koha-idzebra-server package; not the koha-basic one. The work around was to NOT specify to use zebra for indexing. 3. What is the difference between marc21 and unimarc? Librarians would know it; but not poor souls like me, who would be doing the software installation. A description of both in the web installer would help; I chose marc21. 4. What happens if I abort the webinstaller? Some clues on the web installer pages would be nice. BTW, I did this free as in "free beer" for a friend of mine, at a law school with a mere 5K volumes. ;-) And I will write about the OS install elsewhere. -- Mahesh T. Pai || http://paivakil.blogspot.com REVOLUTION, n. An abrupt change in the form of misgovernment.

1 0