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

Re: [Koha-devel] Issuing Rules
by Petrus B. van Bork 19 Feb '08

19 Feb '08

Dear Jesse & Fellow List Members: This new script sounds great! We would - very much - like to see it deployed for 3.0, a version which we are committed to deploying as soon as the stable version is released. The old version is unwieldy and tricky, the fact that using defaults is broken is unhelpful too! One thing which we are specifically interested in knowing is if it will handle incrementing fines daily as opposed to lumpsums periodically? Best, Petrus Hanover koha-devel-request(a)nongnu.org wrote: > Send Koha-devel mailing list submissions to > koha-devel(a)nongnu.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.nongnu.org/mailman/listinfo/koha-devel > or, via email, send a message with subject or body 'help' to > koha-devel-request(a)nongnu.org > > You can reach the person managing the list at > koha-devel-owner(a)nongnu.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Koha-devel digest..." > > > Today's Topics: > > 1. Re: Issuing Rules (Galen Charlton) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 19 Feb 2008 10:18:19 -0600 > From: "Galen Charlton" <galen.charlton(a)liblime.com> > Subject: Re: [Koha-devel] Issuing Rules > To: Jesse <pianohacker(a)gmail.com> > Cc: Koha Development Mailing List <koha-devel(a)nongnu.org> > Message-ID: > <4659947d0802190818l47f9e189g1f5244ab9201ffe0(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi, > > On 2/18/08, Jesse <pianohacker(a)gmail.com> wrote: > >> My little script (attached, along with a template for the default set) >> is actually a replacement for issuingrules.pl. Instead of having a >> massive table with two cells for every combination of itemtype and >> category code, there is now just one row for each rule; if you have a >> default rule, and rules for DVDs and Nonfiction, you will have three >> rows, with a cell each for Fine Amount, First Remind, Amount Loanable, >> etc. This is a rather large change, but it makes defining issuing >> rules much simpler. >> > > I did a (very) quick port of this to 3.0 and took a look. I like the > idea of removing the big matrix, particularly for libraries that have > lots of item types and/or patron categories. I also like the fact > that it doesn't require the user to enter commas or remember what each > comma-delimited field means. I think this approach will make it much > easier to add additional fields to the issuing rules and manage them > in the UI. > > Some suggestions: > > * Add the ability to limit one's view by item type or patron category. > * Either sort the item types and patron categories by the description > or include the code so that it is clear how the entries are being > sorted. > * Somehow make clear what the default issuing rule is for a given > branch, item type, and patron category combination if it's not > explicitly specified -- perhaps by allowing for wildcard entries. > > I would be in favor of getting this into 3.0 or 3.x quickly, possibly > making it a parallel alternative to the existing issuingrules.pl for a > while. > > Regards, > > Galen >

3 2

Issuing Rules
by C W Nel 19 Feb '08

19 Feb '08

Thanks Jesse Did you perhaps fix the chargeperiod problem? If you enter 1,7,7 the last 7 disappears and is not written into the issuingrules table. (Ver2.2.9)

3 2

Question about 'Top Lists' reports
by Tina Burger 18 Feb '08

18 Feb '08

Hi all, I have a question about this report: 'Items not checked out' Can someone please describe the original intention of this report? It doesn't work as I expect it to work, so I'm trying to determine if there is a bug or I just misunderstand the intention. The resulting report has two columns: 'Num/Items' and 'Global' and under the 'Num/Items' column there is just row after row of sequential numbers. [i've attached a screenshot] I would expect there to be barcodes or titles or something. Does something need to be enabled for this to work? Am I misunderstanding this? Thanks!! --Tina -- Tina N. Burger VP Marketing, LibLime 449 East State St. PO Box 892 Athens, OH 45701 (888) Koha ILS (564-2457) ext. 705 tnb(a)liblime.com http://liblime.com

1 0

Issuing rules
by Jesse 16 Feb '08

16 Feb '08

I have been doing a lot of work recently on issuing rules in Koha; I have made a new, much nicer issuing rules screen am working on making issuingrules fallback better. I have working production code if anyone is interested, and templates for the default and NPL template sets. -- Jesse

1 0

Web installer, database, Darwin (maybe other BSDs?), qx(), mysql
by MJ Ray 16 Feb '08

16 Feb '08

This is just a short note to let the list know that I've found a couple of problems with the installation process which affect at least Darwin, MacOS X installations and I wouldn't be surprised if other BSD-like systems had similar problems. Anyone managed to install successfully on one? 1. MARC::File::XML won't install under sudo perl -MCPAN. The make test step fails. Running as root works. Not sure why this is and I've no plans to debug it further. This had me mystified for far too long. 2. the web installer can't invoke the mysql command-line client. The error is like "sh: line 1: -u: command not found" and appears once for each SQL file. I think this is the portability problem described in man perlop under the qx subheading. It's very similar to a problem in the 2.x installer. Galen has offered a few possible solutions (IPC::Open3, IPC::Cmd), I think I know some other possibles (DBIx modules and so on) and there's the solution I put in place last July that hdl rejected (pure DBI) if we get really stuck. I'll work through them until one works (starting with open3) unless anyone has a quick fix or sees a fatal flaw in any of them. I should have something coded in about 12 hours' time. Hope that helps someone, -- MJ Ray http://mjr.towers.org.uk/email.html tel:+44-844-4437-237 - Webmaster-developer, statistician, sysadmin, online shop builder, consumer and workers co-operative member http://www.ttllp.co.uk/ - Writing on koha, debian, sat TV, Kewstoke http://mjr.towers.org.uk/

4 6

Re: [Koha-devel] Itemtype and MARC21 Quandry
by Petrus B. van Bork 15 Feb '08

15 Feb '08

Dear Chris & List Colleagues: I believe that Sylvain is right, in this case, (....sorry Chris....), creating multiple records is not a good solution, when viewed from the perspective of a librarian, as opposed to a computer geek. Apart from issues of redundancy, a librarian wishes all the copies of one title to be listed in one place, even if the loan rules are different. Librarians spend time and effort eliminating duplication from their databases, and would not be comfortable with a system that forces duplication of identical MARC records. Let me note, that, to the best of my knowledge, MARC21 records while they MAY permit more than one 852 field, have no accommodation in the record for loan rules defining fines, borrower type or length of loan. See http://www.loc.gov/marc/holdings/echdintr.html - and I quote: "Field 852 (Location) is defined to contain information in as much detail as is needed to locate an item. It may include such information as a unique shelving designation, copy number, and the address for the current physical location of the item." Other systems hold the information stored in a separate record linked to the MARC record and this is the solution we favour. This should allow each copy to have its own borrowing rules including who may borrow, length of loan period etc. A single library may have one reference copy, one short loan copy and some normal loan copies of the same title in different areas of the library, and need to define different rules and limits for these copies being borrowed by different borrower types. Best, Petrus Hanover Public Library Ontario, Canada Sylvain Machefert wrote: Hi all, I sent a mail one week ago about this same problem for a library who has books for adults and books for children with different issuing rules but the same notice. I'm in favour of linking the itemptype to the item, not to the biblioitem. hope there'll be an elegant fix for that ... Hi All I honestly dont think this is the problem, whether the itemtype is on items, or biblioitems. The problem is that the import is only making 1 biblioitem. If you have a MARC record that contains multiple record types, you should get 1 biblio -> multiple biblioitems -> multiple items. This is not what is happening, and this is what is causing the problems. So we need to fix this. Chris

1 0

Offset & Creep Adjustment Feature for Label Creator Tool
by Chris Nighswonger 15 Feb '08

15 Feb '08

Hi all, I have just wrapped up what I call a Printer Profile feature for the Label Creator tool in Koha 3.0. This feature allows for the creation of printer profiles bound to printer/tray/template where 'printer' is the printer the profile applies to, 'tray' is the tray on that printer the profile applies to, and 'template' is the label template the profile applies to. Basically the profile allows the user to setup offset and creep adjustements (aka: printer callibration) specific to a given printer tray and label template. The printer referenced need not be one setup inside Koha itself. The template, however, must exist within Koha. This functionality is available in most label software I have used, and should keep the user from having to monkey with the template specs to get the text/barcode/etc. inside the label edges. I am wondering if there are any thoughts, considerations, objections, encouragements, etc. to this tool becoming a part of Koha before I submit the code? It works well here, but is beta. Regards, Chris -- Chris Nighswonger Faculty Member Network & Systems Director Foundations Bible College & Seminary www.foundations.edu www.fbcradio.org

2 1

Zebra fails to bind two sockets
by custard 13 Feb '08

13 Feb '08

Hi, Has anyone seen something like this, and is there a way around? $ sudo zebrasrv -f /etc/koha/koha-conf.xml Password: 21:13:44-13/02 [log] zebra_start 2.0.26 /etc/koha/zebradb/zebra-biblios.cfg 21:13:44-13/02 [log] zebra_start 2.0.26 /etc/koha/zebradb/zebra-authorities.cfg 21:13:44-13/02 [server] Adding dynamic listener on unix:/var/run/koha/zebradb/bibliosocket id=1 21:13:44-13/02 [fatal] Failed to bind to unix:/var/run/koha/zebradb/bibliosocket [No such file or directory] 21:13:44-13/02 [server] Adding dynamic listener on unix:/var/run/koha/zebradb/authoritysocket id=2 21:13:44-13/02 [fatal] Failed to bind to unix:/var/run/koha/zebradb/authoritysocket [No such file or directory] 21:13:44-13/02 [server] Adding dynamic listener on tcp:@:9999 id=0 21:13:44-13/02 [server] Starting server zebrasrv pid=434 The command is taken from the INSTALL file for Koha 3, and it's on Darwin 9.2.0 (OsX 10.5.2) thanks, custard. -- View this message in context: http://www.nabble.com/Zebra-fails-to-bind-two-sockets-tp15456847p15456847.h… Sent from the Koha - Dev mailing list archive at Nabble.com.

4 4

biblio search problem: 2.2.9 to 3.0 upgrade
by Matthew Metzger 13 Feb '08

13 Feb '08

Hello All, first, I want to thank the very helpful people who work on this project. I've come to appreciate how complicated libraries are. I started using Koha 2.2.4 in 2005 and have looked forward to 3.0 for some time. I have followed the instructions at http://wiki.koha.org/doku.php?id=22_to_30 I think that has been part of my problem, because I didn't realize that some of the instructions applied to unimarc, while I have marc21. I've added one Marc Record as a test and that is the only one that shows up in any search results, both on the intranet and the opac, even though I have over 5000 other items. That search result gets me to http://stam.library.admin.test/cgi-bin/koha/catalogue/MARCdetail.pl?biblion… I can view other items by manually changing the biblionumber in the address bar URL. However, it seems that only 100a shows up in the marc data for any other item except the one added after the upgrade. Also, the value of 100a seems to be incorrect as it is always the same "Personal name 20080208 frey50". I was browsing through the database tables using phpmyadmin and came across this warning: "PRIMARY and INDEX keys should not both be set for column `biblioitemnumber`" in Database: Koha > Table: biblioitems Is this something that should be changed? thanks for any help you can give me and for your time, Matthew Metzger

1 0

perl module problem - 2.2.9 -> 3.0 upgrade
by Matthew Metzger 13 Feb '08

13 Feb '08

Hello, I am attempting to move a 2.2.9 installation to 3.0 alpha. I'm almost there, but there seem to be a few problems. I have worked to install all the required perl modules and made sure that they were up to date. However, http://stam.library.admin.test/cgi-bin/koha/about.pl says that the XML::LibXSLT and YAML::Syck modules are missing. However, I know for sure that they are installed. cpan[6]> install YAML::Syck YAML::Syck is up to date (1.01). cpan[7]> install XML::LibXSLT XML::LibXSLT is up to date (1.66). The intranet makes me log back in after every link I click within it. I cannot yet search the OPAC, but it is probably an unrelated problem. thanks for any help you can give. -Matthew

1 1