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

Why is itemtype a part of biblioitems ?
by Sylvain Machefert 20 Sep '05

20 Sep '05

Hi all, trying to configure koha for a library, I come across some problems. In its actual configuration the library has many itemtypes which help it to configure issuing rules. For example there is a type adult book and a type children book. Borrowers in an adult category can borrow items from children "branch" but children can't borrow from adult branch. My problem is that I have to check the total of "books" borrowed by a member to be sure it doesn't exceed the maximum he can borrow. In koha if I want to define a type children book and a type adult book, I get problems for some biblio like Harry Potter (grrrr) which are in both branches ! Up to now I have created four branches (Printed Children, Printed Adult, Multimedia Children, Multimedia adult) in which I'll configure the rights but I can't see how I'll be able to check the total easily (issuing rules are a little bit complicated). I must admit my mail must be unclear but I can't figure how to solve my problem, I'm getting angry after koha ! :) Sylvain

2 1

Install Meeting, 2005-07-05 21:00 +0000
by MJ Ray 16 Sep '05

16 Sep '05

Apologies for the late notice: I had trouble sending to this list last week. Tomorrow (Tuesday 5 July) at 21:00 +0000 (UTC), in #koha on irc.katipo.co.nz, there will be an IRC meeting to discuss installer and upgrader development for koha 2.3. All welcome. Possible topics: 1. General structure of the installer and upgrader; 2. auto-install features; 3. installer localisation (Locale::MakeText is in perl 5.8 core) Roughly the first 5 or 10 minutes will decide the timetable and I hope the meeting will be about an hour. If you can email any other topics or background reading links to this list beforehand, I'd appreciate it. -- MJ Ray (slef), K. Lynn, England, email see http://mjr.towers.org.uk/ http://www.ttllp.co.uk/koha/

5 4

Re: Koha OPAC error
by 毛�c�� 15 Sep '05

15 Sep '05

>(However, you MUST choose css as opactheme in systempreferences, in the librarian interface. Should solve your problem) I did it. Problem still there. Another other solution? 2005/9/15, Paul POULAIN <paul.poulain(a)free.fr>: > > ë�c�� a ��crit : > > Hi, Paul- > > > > > > I live in Taiwan. Installed Koha 2.2.3 with Fedora Core 4 recently. > > It is at: > > http://lit185.lacc.fju.edu.tw:8080 > > then redirected to > > http://lit185.lacc.fju.edu.tw:8080/cgi-bin/koha/opac-main.pl > > > > We keep encounter error while enter OPAC. We presume there might missing > > some template files, or something else. > > Please indicate the possible solution. > Please, do not send me mails directly. You must subscribe Koha mailing > lists to get help. > > (However, you MUST choose css as opactheme in systempreferences, in the > librarian interface. Should solve your problem) > > -- > Paul POULAIN > Consultant ind��pendant en logiciels libres > responsable francophone de koha (SIGB libre http://www.koha-fr.org) > -- Best regards ë�c��, Anthony Mao, mao at lins dot fju dot edu dot tw ICQ 30941847 Department of Library and Information Science http://www.lins.fju.edu.tw/mao/index.htm TEL +886 2 29052334, FAX +886 2 29017405 Fu-jen Catholic University, Taipei, Taiwan, R.O.C.

4 3

Re: Koha-devel digest, Vol 1 #1112 - 2 msgs
by Adam Nyaga 15 Sep '05

15 Sep '05

Hi, I downloaded TortoiseCVS so that i can get the latest files fron the koha cvs repository on sourceforge (cvs.sourceforge.net:/cvsroot/koha). However am unable to connect to the cvs, the application fetches the list of modules and gets debian; koha-tmpl; and CVSROOT, yet the modules one gets using the web browser (http://cvs.sourceforge.net/viewcvs.py/koha) are different. Even when i select one of the modules, e.g. debian, the application fails with the following message: In C:\DOCUME~1\anyaga\LOCALS~1\Temp\TortoiseCVS make new module temp\: "C:\Program Files\TortoiseCVS\cvs.exe" "import" "-m" "" "debian" "tcvs-vendor" "tcvs-release" CVSROOT=:pserver:anonymous@cvs.sourceforge.net:/cvsroot/koha Empty password used - try 'cvs login' with a real password cvs [server aborted]: "import" requires write access to the repository Error, CVS operation failed please help me cos i need the latest code urgently since the version i downloaded (koha 2.2.3 download) has errors/bugs and we are in the middle of a test installation before moving to production deployment. regards, Adam Nyaga On Wed, 14 Sep 2005 06:08:03 +0300, <koha-devel-request(a)lists.sourceforge.net> wrote: > Send Koha-devel mailing list submissions to > koha-devel(a)lists.sourceforge.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/koha-devel > or, via email, send a message with subject or body 'help' to > koha-devel-request(a)lists.sourceforge.net > > You can reach the person managing the list at > koha-devel-admin(a)lists.sourceforge.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Koha-devel digest..." > > > Today's Topics: > > 1. about leader management (Paul POULAIN) > 2. Re: about leader management (Joshua Ferraro) > > --__--__-- > > Message: 1 > Date: Tue, 13 Sep 2005 17:43:20 +0200 > From: Paul POULAIN <paul.poulain(a)free.fr> > To: koha-devel <koha-devel(a)lists.sourceforge.net> > Subject: [Koha-devel] about leader management > > hi, > > i've read on irc that joshua could not store leader in biblio modif=20 > (with cvs rel_2_2) > > It works for me, so i'm wondering if you didn't forgot to create a > field=20 > '000' with a subfield '@' and activate it in your framework ? > (I use 000 and @ to have a field and a subfield, as it's easier -from=20 > far- in the code, although it may be a little bit tricky to find > without=20 > help ;-) ) > > I also have seen the reservoir problem. That may be the same origin I=20 > suspect (but untested =3D> pls confirm or not) > --=20 > Paul POULAIN > Consultant ind=E9pendant en logiciels libres > responsable francophone de koha (SIGB libre http://www.koha-fr.org) > > > --__--__-- > > Message: 2 > Date: Tue, 13 Sep 2005 08:45:39 -0700 > From: Joshua Ferraro <jmf(a)liblime.com> > To: Paul POULAIN <paul.poulain(a)free.fr> > Cc: koha-devel <koha-devel(a)lists.sourceforge.net> > Subject: Re: [Koha-devel] about leader management > Organization: LibLime Library Solutions > > The leader problem was my fault -- I didn't have the latest > updated CVS. It works now for the reservoir as well. > > Thanks, -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

3 2

2.2 branch strategic question
by Paul POULAIN 15 Sep '05

15 Sep '05

Hi, 2.2.4 should be here soon, & i'm wondering what to do with releases. Let me explain my questions... I've released a new minor version every quarter. Each contains : - some bugfixes - some new features. Those new features didn't change the DB for 2.2.1, 2.2.2 and 2.2.3, and will change a little the DB for 2.2.4. With the 3.0 version announced for 2006Q1 (end of...), i'm not sure it would be the best solution to continue releasing 2.2.x with new features. Here is a list of pro and cons i've found. Feel free to add some of them. pro : - new features are always nice to have before next major release - some of them are very important and could be considered as bugfixes (like leader support in 2.2.4, for example) cons : - installing a new version every quarter is too much work - learning what is in a new version every quarter is too much work, libraries are missing new features ! - it's too much work to synch 2.2 and head with new feature. That won't be easier with new head work ! - new features means ... new bugs ! so, I suggest, after your reactions, feel free to say if we need a poll in koha & koha-fr mailing lists or decide. but i really have no preferred opinion. Maybe a little feeling that we could just release bugfixes in 2.2 branch. But not sure. Note that some features were requested by some customers and requires to be quickly written in order to deploy Koha, so i think I was right -from my point of view- until now ! -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

3 2

Koha 2.2.4 translations
by Paul POULAIN 15 Sep '05

15 Sep '05

Hi, i've uploaded uptodate version of the .po files for all languages available. You will find the updated files here : http://cvs.sourceforge.net/viewcvs.py/koha/koha/misc/translator/po/ (updated daily only, should appear tomorrow) The 2.2.4 should be released on Friday, 23. You can send me updated translation files directly if you can't commit them on CVS. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

about leader management
by Paul POULAIN 13 Sep '05

13 Sep '05

hi, i've read on irc that joshua could not store leader in biblio modif (with cvs rel_2_2) It works for me, so i'm wondering if you didn't forgot to create a field '000' with a subfield '@' and activate it in your framework ? (I use 000 and @ to have a field and a subfield, as it's easier -from far- in the code, although it may be a little bit tricky to find without help ;-) ) I also have seen the reservoir problem. That may be the same origin I suspect (but untested => pls confirm or not) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

2 1

question about
by Spencer Anspach 13 Sep '05

13 Sep '05

In C4::Biblio.pm, the subroutine MARCmarc2kohaOneField is passed the current statement handle ($sth) but never uses it. Can anyone tell me if this is a left-over artifact of an earlier functionality? Or an area of future development? The reason I ask is that I've implemented non-filing indicators locally (it is far from elegant, but it works, barely), but in order to do so I needed the database handle ($dbh) in that subroutine. The only subroutine that calls it (MARCmarc2koha) has $dbh, so it wasn't any problem to change the first parameter being passed from $sth to $dbh, but I wondered if that was something that was going to break future planned functionality. I tried to read through the revision notes and comments, but I didn't see anything that pertained. Also, that subroutine isn't exported and the comments indicate it should only be used by MARCmarc2koha (within Biblio.pm), so it seemed pretty self-contained and a managable modification. Thanks, Spencer -- Spencer M. Anspach, Library Systems Analyst/Programmer Library Information Technology, Indiana University Library E456 phone: (812) 856-5318 Bloomington, IN 47405 fax: (812) 856-4979 sanspach(a)indiana.edu pager: (812) 335-7403

2 3

Barcode Printing Problems
by Joshua Ferraro 13 Sep '05

13 Sep '05

Hi all, Is anyone using barcode printing on a production system? I recently tried to get them working and although I can get it to produce barcodes there are two problems: 1. The file that's exported has an extension of .pl ... this means that most OSes can't determine that it's a PDF by default. What's the best way to export it as a useful filename and extension? 2. The barcodes that are generated have leading zeros and one zero after the barcode. So they're almost right, but in their current form aren't really useful (don't scan correctly). Anyone else experiencing the same problems? Any solutions out there? Cheers, -- Joshua Ferraro VENDOR SERVICES 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

6 5

Koha Statuses and MARC?
by Joshua Ferraro 13 Sep '05

13 Sep '05

Paul et al, In Paul's proposed scheme for item statuses, the items.notforloan field is linked to MARC field 942$k and then an authorized value is set for that field (defined by the library). Before we invest too much development energy on this idea I'd like to question whether it's even a good idea to store status information in the MARC record, especially we we move toward using Zebra to store our textual (MARC) database. Stephen and I spoke earlier today and he's got me thinking that maybe it's not such a good idea to store statuses in MARC. MARC wasn't really designed for anything but the static record information. It's ill-suited for transactional based data such as statuses. I propose that for Koha 3.0 we create a new field in the Koha tables called 'items.status'. items.status can be a numeric value and have a set of library-defined authorized values. We can then add a framework for setting those values that a library must setup when they install the system. For instance, it should be possible to set Koha to automatically set an items status to 'in transit' when an item is on reserve to a patron in a branch other than the holdingbranch (when the item is returned) and 'waiting' when it arrives and is scanned. But the goal would be to make this a setting that the library could define when setting Koha up, a set of 'status rules'. Comments, suggestions, volunteers? Cheers, -- Joshua Ferraro VENDOR SERVICES 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