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

IndependantBranches features...
by Paul POULAIN 09 May '08

09 May '08

Hello, For libraries with IndependantBranches=ON, 1 question : Only the home library can edit an item. I think the holding library should be able to edit it as well. The use case : an item is returned after an issue, and the holding library sees that there is something bad on the item (page removed, DVD scratched... atm, the library can't update the item. I'll submit a patch for that, unless someone object. -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : 04 91 31 45 19

4 6

[Koha] Koha 3.0 beta on Kubuntu gutsy - "production mode - trapped fatal error"
by Mason James 08 May '08

08 May '08

> > Hi Robert, > > On a debian box, try installing the package 'libmysqlclient15-dev' > to resolve your missing 'mysql_config' file issue. > > $ which mysql_config > /usr/bin/mysql_config > > $ dpkg -S /usr/bin/mysql_config > libmysqlclient15-dev: /usr/bin/mysql_config > > Cheers, Mason. > Just a little update (on a debian box) The previous 'dpkg -S' example only works on packages that you *already* have installed Try apt-file to find out which package a file belongs to - that you *dont* have installed. $ sudo apt-get install apt-file $ apt-get update $ apt-file search 'mysql_config' libmysqlclient15-dev: usr/bin/mysql_config Mason. _______________________________________________ Koha-devel mailing list Koha-devel(a)nongnu.org http://lists.nongnu.org/mailman/listinfo/koha-devel

1 0

Re: [Koha-devel] QA process (was: "freezing" koha 3.0)
by Andrew Moore 07 May '08

07 May '08

On Wed, May 7, 2008 at 11:10 AM, Paul POULAIN <paul.poulain(a)free.fr> wrote: <snip> > For instance, the role of QA > manager means almost nothing in real life. I'm sorry about that, we > should speak of how to introduce the QA role in the git process. I'm interested in opening up this topic a little bit more. Specifically, I'd like to know what I can do as a developer to make the QA process more efficient and effective. Some of the things I can think of that I can do that may help us are: * ensure that I create test cases for new code that I add * try to create test cases for other code that I touch * Document and describe the recent changes to the test suite to make it easier for others to use and extend it * document my changes and the anticipated side effects more thoroughly in my git commit messages and on bugs.koha.org * triage my bugs and others so that bugs.koha.org is more accurate * set up a smoke bot to run the automated test suite after each commit and report the results What things do the rest of you see as being high-value contributions to the QA process? -Andy

3 2

RFC: alternate borrower IDs
by Galen Charlton 07 May '08

07 May '08

Hi, Various LibLime customers have requested the ability to have the borrower record store additional IDs beyond the barcode and OPAC user ID. To meet this requirement, we propose the following development, which barring a general escape of zombies from the sewers of Chicago, I could implement by the middle of next week. The concept of alternate (or additional) IDs would support the following use cases: [1] A (academic) library loads patron records for their students from CSV file extracted from a database run by the campus registrar. However, the registrar does not know or care about barcodes and userids assigned by the library; all they supply is a unique campus ID number that the library is expected to match against during patron imports. [2] A library has more than two identifiers for their patrons. Two types of identifiers can take passwords or PINs. [3] More broadly, and this is something that falls out of the specific implementation I'm about to propose, the library wants to add free-text attributes to the patron record that are not covered by the existing columns of the borrowers table. To implement this, two new database tables would be added: borrower_attribute_types (ID or attribute_types) * ID type code (e.g., INSTID) * ID type description (e.g., 'Campus student ID') * repeatable (whether or not a borrower record can have more than one ID of that type) * unique (whether or not the ID should be enforced as a unique identifier) * opac_display (whether or not the ID should display in the patron's account page) * password_allowed (whether or not a password can be associated with the ID and used for patron authentication) * staff_searchable (whether or not the ID can be searched in the staff interface) borrower_attributes * borrowernumber (foreign key) * ID type (foreign key) * attribute (text string containing the ID or attribute) * password (optional password associated with the ID) The primary functional changes would be 1. new Administration page to define borrower ID types 2. new patron editing page to add, delete, or edit borrower ID types 3. additional pane or box in patron account tab in OPAC to display additional IDs 4. in staff client, ability to include one or more ID types in search box 5. ability to load alternate IDs via the patron import tool. This would be done by adding an optional column in the CSV file that would contain ID types and IDs. Any unique ID would act as a matchpoint. For example, the column might contain: "INSTID:12345, MAJOR:Physics, ADDLOGIN:abcdef/passwd" The new feature would be guarded by a syspref - if the preference is off, no sign of the additional IDs would display in the Administration menu, the patron editor, or the OPAC. I would appreciate comments on this proposed functionality, the proposed implementation, and whether or not this would be of use to others. Regards, Galen -- Galen Charlton Koha Application Developer LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709 _______________________________________________ Koha-devel mailing list Koha-devel(a)nongnu.org http://lists.nongnu.org/mailman/listinfo/koha-devel

3 3

reserves.waitingdate & upgrade 22 => 30
by Paul POULAIN 07 May '08

07 May '08

Hello, in Koha 3.0, the reserves.waitingdate field is used in some places to check that a reserve has been filled & is waiting for pick up. It works fine. Except when migrating from 2.2 : the field is created empty, which a script like circ/waitingdate.pl disklike. That is a problem that can be solved by a single SQL statement : UPDATE `reserves` SET waitingdate=timestamp WHERE found='W' and waitingdate IS NULL Do you think we : - should ignore this transitionnal problem - should updatedatabase with a new DB dump - should do the SQL query when bumping to 062, that has some stuff related to reserves. (my preferred solution) Your opinion ? (feel free to confirm the SQL statement is correct. It was on the DB I just run it on, not 100% sure it's OK for any cases) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : 04 91 31 45 19

1 0

Standardised US English Translation
by russ＠russandsarah.gen.nz 07 May '08

07 May '08

Hi All, After a big fuss, I have gone a bit quiet. Working on Koha is not my day job anymore. Anyway, forgive the cross list posting, but my last email got forwarded to all the lists and I guess this topic is of interest to the devel list as well. I am happy to help out with standardising the language used in the default Koha install to that of the dictionary everyone agreed on. It would be easiest for me to do this using Kartouche at translate.koha.org, because then I can see how many strings still need to be translated and I can do it from anywhere. Any progress with getting a language code setup? Is Joshua the only person that can do this? Cheers, Russel

3 2

install problem postgres
by Roxana Luz Fleipaz 07 May '08

07 May '08

Dear colleagues .. I still long line of development of Koh .. I have a doubt, it is possible to make the installation of beta-koha3 with postgres, debian etch 4.0 at this time? Thank you. Atte. Roxana Luz _______________________________________________ Koha-devel mailing list Koha-devel(a)nongnu.org http://lists.nongnu.org/mailman/listinfo/koha-devel

3 2

circulation.pl and moremember.pl synching
by Henri-Damien LAURENT 06 May '08

06 May '08

Hi, there are some issues in synching moremember and circulation.pl : a) the branchname displayed near the user information is the issue branch and not the user homebranch. Is this the behavior expected or is it a bug ? b) the table for issued elements between moremember.pl and circulation.pl show different informations and both can be interesting ? We should choose one way to display and stick to it and allow the same functions OR have only one page to edit circulation information and fines. What should we do about that ? -- Henri-Damien LAURENT

1 0

Re: [Koha-devel] Koha-devel Digest, Vol 30, Issue 3
by Michael Sangoro 06 May '08

06 May '08

I just completed the installation of KOHA in Makerere University EPRC . Can some plz let me know of some Z servers i can test with that require no subscription. thanks Michael Okongo Sangoro Uganda - East Africa --- On Sat, 3/5/08, koha-devel-request(a)lists.koha.org <koha-devel-request(a)lists.koha.org> wrote: > From: koha-devel-request(a)lists.koha.org <koha-devel-request(a)lists.koha.org> > Subject: Koha-devel Digest, Vol 30, Issue 3 > To: koha-devel(a)lists.koha.org > Date: Saturday, 3 May, 2008, 11:00 AM > Send Koha-devel mailing list submissions to > koha-devel(a)lists.koha.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.koha.org/mailman/listinfo/koha-devel > or, via email, send a message with subject or body > 'help' to > koha-devel-request(a)lists.koha.org > > You can reach the person managing the list at > koha-devel-owner(a)lists.koha.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: Vote NOW for the Koha Community Website Theme > (Nicole Engard) > 2. Re: "freezing" koha 3.0 (Paul POULAIN) > 3. Re: "freezing" koha 3.0 (Paul POULAIN) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 2 May 2008 06:58:44 -0400 > From: "Nicole Engard" > <nicole.engard(a)liblime.com> > Subject: Re: [Koha-devel] Vote NOW for the Koha Community > Website > Theme > To: koha-devel(a)lists.koha.org > Message-ID: > <9128d7f00805020358y5235b155j7fd51549f22a103c(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > I know this discussion has sort of died, but I want to > bring it back > to everyone's attention. I'm working on the > documentation for Koha > and I'd love to be able to share it with everyone, but > it's on hold > until we get the new Plone site up and running. Is there > any way we > can come up with a way to push the site up and fix the > design after > the fact? Look & feel is secondary to content - and I > think it's > easier to decide how we want things to look once we're > actually using > the tool. > > I brought this up on #koha and was told that there was a > prize for > this design contest - I didn't realize that - and see > how that makes > things a bit more complicated - but I think we should come > up with > some sort of compromise to get the ball rolling. > > -- > Nicole C. Engard > Open Source Evangelist, LibLime > (888) Koha ILS (564-2457) ext. 714 > nce(a)liblime.com > AIM/Y!/Skype: nengard > > http://liblime.com > http://blogs.liblime.com/open-sesame/ > > On Fri, Apr 18, 2008 at 10:46 AM, Owen Leonard > <oleonard(a)myacpl.org> wrote: > > Paul is right, I agree with those who say the current > Koha.org design > > is preferable to the options we've been shown. > > > > > > > I'm sorry if my suggestion is out of place - > but wouldn't it be best > > > if we just got a site up and running that was > multi-lingual and then > > > worry about the design issues? > > > > I think Nicole makes an excellent point. I also think > that we need to > > consider the option of saying, "Sorry, there > were no winners this > > time." > > > > -- Owen > > > > > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel(a)lists.koha.org > > http://lists.koha.org/mailman/listinfo/koha-devel > > > > > ------------------------------ > > Message: 2 > Date: Fri, 02 May 2008 16:47:32 +0200 > From: Paul POULAIN <paul.poulain(a)free.fr> > Subject: Re: [Koha-devel] "freezing" koha 3.0 > To: koha-devel(a)lists.koha.org > Message-ID: <481B2984.6040604(a)free.fr> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > sorry, but 1 other example of "better enemy of > good" : the patches for > #2047 breaks scanindex searches, that badly fails : > Can't call method "field" on an undefined > value at > /home/paul/koha.dev/frantiq/C4/Biblio.pm line 3123. > > > -- > Paul POULAIN > http://www.biblibre.com > Expert en Logiciels Libres pour l'info-doc > Tel : 04 91 31 45 19 > > > ------------------------------ > > Message: 3 > Date: Fri, 02 May 2008 17:01:59 +0200 > From: Paul POULAIN <paul.poulain(a)free.fr> > Subject: Re: [Koha-devel] "freezing" koha 3.0 > To: koha-devel(a)lists.koha.org > Message-ID: <481B2CE7.8060601(a)free.fr> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Paul POULAIN a ?crit : > > sorry, but 1 other example of "better enemy of > good" : the patches for > > #2047 breaks scanindex searches, that badly fails : > > Can't call method "field" on an > undefined value at > > /home/paul/koha.dev/frantiq/C4/Biblio.pm line 3123. > > (patch on the way for this one, but mayber still another > side effect I > haven't seen...) > -- > Paul POULAIN > http://www.biblibre.com > Expert en Logiciels Libres pour l'info-doc > Tel : 04 91 31 45 19 > > > ------------------------------ > > _______________________________________________ > Koha-devel mailing list > Koha-devel(a)lists.koha.org > http://lists.koha.org/mailman/listinfo/koha-devel > > > End of Koha-devel Digest, Vol 30, Issue 3 > ***************************************** __________________________________________________________ Sent from Yahoo! Mail. A Smarter Email http://uk.docs.yahoo.com/nowyoucan.html

2 1

patches for #2047 broke scanindex searches (was: "freezing" koha 3.0)
by Andrew Moore 05 May '08

05 May '08

On Fri, May 2, 2008 at 9:47 AM, Paul POULAIN <paul.poulain(a)free.fr> wrote: > sorry, but 1 other example of "better enemy of good" : the patches for > #2047 breaks scanindex searches, that badly fails : > Can't call method "field" on an undefined value at > /home/paul/koha.dev/frantiq/C4/Biblio.pm line 3123. Hi Paul - Thanks for reporting this. I can't reproduce this problem, but I can guess a patch based on your description. Could you either help me try to reproduce it, or validate that a patch helps if I send you one, please? Thanks, -Andy

2 2