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

3.0 zebra database creation on rel_3_0
by Paul POULAIN 28 Nov '06

28 Nov '06

As suggested & discussed with joshua, i've worked on zebra database creation today. I still have some tests to do, but it begins to be useable... I summarize : - All config files are now located in misc/zebra directory. PLEASE, if a .att, a .abs ... has to be improved, do it here, in the correspounding file. - All tools to migrate from a 2.2 to a 3.0 are now located in misc/migration_tools/22_to_30 directory - in misc/migration_tools, the rebuild_zebra.pl script will : * read your koha.xml file * create all directories needed, for both authorities & biblios * copy the needed files from misc/zebra, depending on your marc flavour * create the *-config.cfg files, with the correct directories * dump the authorities & create the zebra DB for them * dump the biblio & create the zebra DB for them I tried to put many informations while doing the job, let me know if it works for you, and, if not, pls let me know where it fails. Eventually, fix the script your self, you'll be welcomed. WARNINGS : - for instance, the script dumps only 100 biblios & 100 authorities. - there are many parameters to this script, they are not all working. - authorities zebraidx don't work atm, i'm sure i'm not far from the solution to the problem - Biblios zebraidx used to work in the previous commit, but, atm, as i've added authorities, i'm not sure they work. I'll try to fix this, not tomorrow (i'm not at office), but thusday, for sure) -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19

1 0

documentation for uploading to cvs repository
by Cindy Murdock 28 Nov '06

28 Nov '06

Hi all, Is there documentation anywhere on the proper way to upload files to the cvs repository? We want to upload updates to the ccfls templates, but Kyle informed me that he's having difficulty getting them uploaded, and asked me to drop you a line about it. Cheers, Cindy ______________________ Cindy Murdock Network Admin Meadville Public Library | CCFLS meadvillelibrary.org | ccfls.org

2 1

about virtual shelves
by Paul POULAIN 28 Nov '06

28 Nov '06

Owen & chris were speaking on the chat, last (my) night of virtual shelves. 2 notes on their discussion : - I agree it's strange to have virtual shelves based on items. Unless i'm mistaken, it's something Steve tonnesen wrote, and, as he disappeared, we will never know if it was a design mistake or a good idea. I still vote for "designe mistake". - about deletion of items/virtual shelves : I tried, in rel_3_0/updatedatabase, to define all SQL constraint to manage such things. So, virtual shelves entries should no more be connected to deleted items. However : nothing is done in 2.2 & it requires to have innoDB & not myIsam table structure (which updatedatabase also achieve) HTH -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19

1 0

Re: [Koha-devel] New Feature: Improved Z39.50 Client
by Waylon Robertson 28 Nov '06

28 Nov '06

On a piece of work i have completed.. i had to use mysql 3.23... Ubuntu, derivitive of debian, installs mysql 5 by default. It was an interesting challenge, uninstalling 5, and pinning it, then used mysql 3.23 from a redhat linux distro, using 'alien' to rpm2deb and install with scripts. uninstalled dbd::mysql, which under Ubuntu, was a matter of uninstalling a deb package.... installed via cpan the needed modules, that compled against mysql-devel-3.23. Went well. No problems. Waylon. ----- Original Message ---- From: José Parrella <joseparrella(a)gmail.com> To: Jerry Van Baren <gerald.vanbaren(a)smiths-aerospace.com> Cc: koha-devel(a)nongnu.org Sent: Saturday, 4 November, 2006 1:07:07 PM Subject: Re: [Koha-devel] New Feature: Improved Z39.50 Client Jerry Van Baren escribió: > FWIIW, you can "pin" versions using /etc/apt/preferences so you could > pin MySQL to 4.* with a more advanced Debian system. You can also > downgrade a MySQL 5.* installation to 4.*, but that might be tough > because of dependencies... it is probably better to install Debian > testing/Etch without MySQL, pin MySQL to 4.*, and then install MySQL > (which will install 4.x since it is pinned). Sure. However the dependencies on libmysqlclient varies, and DBD::MySQL and other already-packaged modules which depend on libmysqlclient might need to be purged and compiled using dh-make-perl or any other helper, or just installed manually. I planned to recompile Sarge's source package under Etch; I guess that's the nicest way. Of course it's possible to have Koha in Etch (I had it, just decided to fallback to Sarge) it's just quite more complicate to achieve, a little bit unmanageable and currently highly complex to do by means of an official Debian package. Jose -- José M. Parrella -> Debian Sid, k2.6.17.13 Escuela de Ingenieria Electrica Universidad Central de Venezuela -> ucvlug.info _______________________________________________ Koha-devel mailing list Koha-devel(a)nongnu.org http://lists.nongnu.org/mailman/listinfo/koha-devel Send instant messages to your online friends http://au.messenger.yahoo.com

1 0

Library-specific Code in rel_3_0
by Joshua Ferraro 27 Nov '06

27 Nov '06

Hi guys, This is a reminder that if you are committing something to Koha that is not universally useful, please create a system preference. I have come across several changes that are not universal and will need to be fixed in rel_3_0: * in member management, surname is all caps * titles are in french rather than english in english prog templates ?!?! * displaying "Branch: 1" instead of "Branch: Branchname" * use List::MoreUtils qw/uniq/; used in request.pl There are many other examples ... it's important to remember that the code you commit to rel_3_0 should not be library-specific. 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

3 3

Zebra and Directory Structures
by Joshua Ferraro 27 Nov '06

27 Nov '06

Hey guys, I'd like to propose that we reflect for a bit about how to structure the zebra components within rel_3_0 before we diverge too much. There are currently three zebra databases for a given rel_3_0 install, and it's likely there will be more in the future (if we have a metarecord bibliographic for instance), but for now we have: biblios (biblio records) authorities (authorities records ) public (for a publicly accessible Z39.50) Each of these needs its own 'tab' directory, as well as registry locations, etc (for the database files). We also have at least two MARC types to deal with, with more to follow if our plans for world domination succeed :-): usmarc and unimarc. Each flavor of MARC needs it's own tab files. I propose we create a standard for managing the zebra files as follows. The installer creates one directory 'zebra' with the following contents: $ ls zebra/ unimarc usmarc then, in each of these we'll have: $ ls zebra/usmarc/ authorities biblios public within each of these we'll have in turn: $ ls zebra/usmarc/biblios/ key lock recordDelete register shadow specialUpdate tab tmp This way, if I have one server with three disks, I can have the following distribution: Filesystem Mounted on /dev/sda1 / /dev/sda2 /koha/zebra/usmarc/biblios /dev/sda3 /koha/zebra/usmarc/authorities (ie, in this way, zebra biblios, authorities and mysql don't compete for disk usage). I also propose we attempt to keep unimarc and usmarc in as close sync as possible, using the same naming conventions, etc., to make sure we don't get confused. (I noticed that in the unimarc directory, there are directories with capital letters as the first letter of the dir ... which is different than in usmarc ... we should pick one method and stick with it ) All of the non-tab files (like koha.xml, ccl.properties, pqf.properties, zebra-biblios.cfg, zebra-authorities.cfg, zebra-public.cfg should IMO go into the koha etc directory, but in CVS we should have: misc/etc/usmarc/ misc/etc/unimarc/ because the files are different for each flavor of MARC. Or should we store these config files in the tab dir? Finally, once we decide on a method, lets clean up CVS by deleting all the extra directories and files (like zebraplugin and misc/zebra). Comments, suggestions? -- 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 3

New features commited in rel_3_0
by Paul POULAIN 27 Nov '06

27 Nov '06

Hello, a mail about new features added in CVS by us recently : In serials management : hdl did a lot of things : - he has updated serials management to have official scripts using the alt_ written by katipo : the previous "official" have been removed. - he added new screens to update serials status all at once : the list of waited/late serials is shown, the librarian can choose the one he want, and can update all of them in just 1 screen) - he improved a lot the SerialsAddItem : this feature let the library create an item on the fly when recieving a serial. now, the item form is exactly the same as in additems.pl, there is a lot of javascript (very web 2.0 ;-) ) - he added the branchname to the subscription description : this way, the librarian & the user can see the branch where the subscription is stored. This feature can still be a little bit improved I think In permissions, Antoine : - cleaned all permissions, by removing some (few) of them & cleaning all scripts to be sure they use the correct permission. - added "EditAuthorities", "Serials" and "Reports".They do what they are supposed to do ;-) In virtual shelves, I added a timestamp, to know the date/time where a book whas added in the shelf. It will then be easy to create a RSS feed for virtual shelves. In Suggestions : Antoine added a feature to select a reason why the suggestion has been accepted or rejected. The reason list is defined in Authorised values "suggest". In Tools, Antoine has added a script (tools/clean_borrowers.pl) that let the library : - remove all borrowers that did not issue anything since X days - anonymize all issues that have been returned more than Y days ago. X and Y being defined by the librarian before executing the script. In OPAC, i'll commit soon (it's written), a new script for the patron, that will show the X most issued items of a given itemtype (or all) for a given branch (or all), for materials acquired in the last 3/6/12/9999 months. Test & enjoy ;-) -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19

1 0

koha 2.2.7 is available for download
by Paul POULAIN 23 Nov '06

23 Nov '06

Koha 2.2.7 has been released & is available at : http://download.savannah.nongnu.org/releases/koha/koha-2.2.7.tar.gz RELEASE NOTES ============= Koha is the first Open-Source Integrated Library System. Koha is a full-featured open-source ILS. Developed initially in New Zealand by Katipo Communications Ltd and first deployed in January of 2000 for Horowhenua Library Trust, it is currently maintained by a team of software providers and library technology staff from around the globe. Koha 2.2.7 is more than 250,000 lines of code (see : http://bureau.paulpoulain.com/cvslog/) , contributed by about 50 different developers (46, +translators). The 2.2.7 version of Koha is a mature product, with a lot of nice features. More than 100 libraries are registered as users on wiki.koha.org, and we are sure that at least 300 libraries use the software. There are 2 projects derived from Koha. ======== WARNINGS ======== * The librarian interface is tested only with Mozilla/Firefox. Should work (partially) with IE. OPAC should work fine with any browser. * during install, you may get some warnings during package dependency checkings. Something like : "Too late to run INIT block at /usr/local/lib/perl/5.8.4/ZOOM.pm line 37." or "Subroutine PDF::API2::Resource::Font::Postscript::O_RDONLY redefined at /usr/share/perl/5.8/Exporter.pm line 65." You can ignore them. KNOWN BUGS ********** Critical/blocking : * mySQL5.0 : Koha is NOT compatible with mySQL 5.0 We plan to add 5.0 compatibility in Koha 3. If you want to give a try to 2.2.7 with mySQL5, you can have a look at http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1089, but it's untested & unofficial. * child card craziness, see http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1117 for details * Update child looses guarantor and address., see http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1065 for details * don't use spaces in currencies codes. Use USD, not US DOLLAR, for example. spaces breaks acquisition module. see bugs.koha.org for more information. Please report any problem in bugs.koha.org Apple users : it seems there is an annoying bug in Firefox, that you can have in librarian biblio search: only the first MARC field list is available and the others can't be opened. The problem is described and fixed at http://www.macfixit.com/article.php?story=20051226091140372 ======= CHANGES ======= Changes 2.2.6 => 2.2.7 ********************** - NEW z3950 client (for quick cataloguing) : it's based on ZOOM, and DOES NOT REQUIRE a daemon on the server. It has 2 majors consequences : it should work well on MS-windows servers platforms and it's much easier to install : just install Koha, and you have it. Another improvement is that you can select the servers you want to query. And, last but not least, it should be a little bit faster for single server searches. - some packages dependancy during install where missing - biblios without any title will show "no title" as title, in the result list, making them clickables - for libraries with IndependantBranche=YES, the biblio can be deleted only if it has no items attached or the librarian is a superlibrarian. This prevent a librarian from deleting a biblio with existing items in another branch. -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19

1 0

what does everyone use to indent/beautify their TMPL files?
by Mason James 21 Nov '06

21 Nov '06

hiya Everyone, ive been thinking (for a while) about a way to standardize the way we format/indent *.tmpl files in koha because... some of the *.tmpl files i create look awful, and they are just too complex for me to work out a consistant way of formatting them. ive been playing a little with 'tidy' recently (http://tidy.sourceforge.net/) and ive got 'tidy' to parse and indent a tmpl file without too much moaning, using a config .rc file like this... $ cat .tidyrc new-blocklevel-tags: tmpl_loop tmpl_if tmpl_else tmpl_unless new-inline-tags: tmpl_var tmpl_include indent: auto indent-spaces: 1 vertical-space: n wrap: 0 then, run tidy like so... $ tidy -c .tidyrc test.tmpl -- so, the question is...... - what tools does everyone use for their own *.tmpl indenting/formatting/beautifying? - are there better ones than 'tidy'? - is it a good idea for us to find a tool that formats our tmpl files in a standard way? any ideas folks? cheers, Mason. -- Mason James Katipo Communications www.katipo.co.nz +64 4 934 1285

5 4

The future of the prog templates
by Owen Leonard 21 Nov '06

21 Nov '06

Joshua and I have been discussing the future of the prog templates, and we'd like to get some input from the group. The prog templates were originally intended as minimal templates with only structural markup with no style information. They would be used only by programmers when develeloping new features. Because the templates would be minimal, it would be easier for designers of alternate templates to diff changes and incorporate them into their own templates. Now that 3.0 is starting to be used in production environments it's time to ask, are the prog templates still serving that purpose, or are they becoming the defacto default template? The issue is important to me because I believe that in order to provide the right amount of flexibility and detail for good design and usability the templates would have to be expanded: additional markup would have to be added to create the possiblity of one, two, and three-column designs, for instance. Divs would be added for the purpose of controlling layout--divs which have no semantic meaning. This kind of change is at odds with the original intention of the prog templates. If it is agreed that the prog templates should be expanded to allow more flexibility for more complex styling, some discussion would have to follow about the kind of layout scheme we should use. The system I chose for NPL's dev_week opac, for instance, is based on this one: http://www.positioniseverything.net/articles/onetruelayout/appendix/holygra… It has worked well for us, but includes some extra markup, as I said. If others have a tried-and-true layout that uses less extraneous markup please chime in. What does everyone think? Thanks, Owen -- Web Developer Nelsonville Public Library http://www.athenscounty.lib.oh.us

5 5