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

koha 2.2.9 roadmap
by Paul POULAIN 27 Apr '07

27 Apr '07

Hello all, The rel_2_2 CVS branch is still very active (from LibLime). A lot of new features have been added (some backported from head). Those new features are a problem for stability, and a few major problems have been solved in this branch. Thus, i've ported to the rel_2_2_7 branch all bugfixes & could release a 2.2.9 with them. Here is the list : * MAJOR bug in addbiblio and additem (Bug 1330). Previously, if you added a field to a biblio it would save it with the same tagorder as one of the items, and then editing an item would result in it being deleted. * fixed some SQL queries (mySQL5 errors. That does not mean koha 2.2.x is mySQL5 compliant, but that's some errors identified & fixed. Just expect koha 2.2.9 to work with fewer problem under mySQL5) * fixed a SQL typo in overdues fixing on return (database was not properly updated) * Solved a problem where a plugin value(fixed fields...) would be lost when editing a record * fixed a bug in expiry date calculation * ENH in z3950 search : adding a test in search to avoid a system error if the server returns an invalid error (can happend, depending on z3950 server) * ENH: Added finer ISBD parsing to allow subfield values to contain {}. * ENH: removed an extra (& useless although harmless) call to MARChtml2xml * ENH: if branch unknown from Koha, take it from userenv, instead of first-defined. This will set branch to users registration branch if not explicitly set. TRANSLATORS : i've translations for french, and spanish that are uptodate. The templates are the same as for 2.2.7/2.2.8 Let me know if you have other templates to add/update. what is the status of ukrainian translation (should be OK I think) -- 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

(no subject)
by Chris Cormack 27 Apr '07

27 Apr '07

Hi All Paul Poulain reminded me on IRC the other night I hadn't done a post to the list about my recent change in work circumstances. For those of you who have been around Koha for a while you will know me as Chris from Katipo. Im now Chris from Liblime. Russel and Mason made the move with me as well. Heres the press release about it http://liblime.com/news-items/press-releases/liblime-to-acquire-katipo/ Just an explanation for any of you wondering who is this chris from liblime guy, I havent seen him on the lists before :) Chris -- Chris Cormack chris.cormack(a)liblime.com VP Research and Development www.liblime.com LibLime +64 21 542 131

1 0

Re: [Koha-cvs] koha/koha-tmpl/intranet-tmpl/npl/en/bull subscr... [rel_2_2]
by Paul POULAIN 26 Apr '07

26 Apr '07

Ryan Higgins a écrit : > CVSROOT: /sources/koha > Module name: koha > Branch: rel_2_2 > Changes by: Ryan Higgins <rych> 07/04/26 04:30:48 > > Modified files: > koha-tmpl/intranet-tmpl/npl/en/bull: subscription-detail.tmpl > serial-issues.tmpl > full-serial-issues.tmpl > > Log message: > small language changes >  > - Waited > + Waiting (cc: to koha-devel, anyone can give it's opinion) mmm... I won't argue on english quality, but : a "waited" serial means that it's not here, and is expected. A "waiting" item means (not serial) is here, but waiting for an event(being picked up by a patron, for a reserved item). Thus, in translations, it will be confusing to use "waiting" for 2 things. Could we choose a different word ? Is "expected" acceptable ? -- 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

Members : Code Cleaning
by Henri-Damien LAURENT 25 Apr '07

25 Apr '07

* Bornamesearch and GuarantornameSearch => SearchMember * GetMember, borrdata,getguarantordata => GetMember with a change in signature. * borrdata2 => GetBorrowerIssuesAndFines * GetMemberDetails No changes. * calcexpirydate =>GetExpiryDate * modmember => ModMember * newmember => AddMember * borrissues => GetPendingIssues * allissues => GetAllIssues * GetMembeReregistration => ExtendMemberSubscriptionTo * getboracctrecord =>GetMemberAccountRecords no longer takes env * GetBorrowersTitles => GetTitles * findguarantees => GetGuarantees * DeleteBorrower => MoveMemberToDeleted (move member data to deletedborrowers) And DelMember (delete member) * deletemembercompletely => DelMember * GetBorrowersFromSurname => GetMembersFromSurname * citycaracteristiques => GetCities * GetBorNotifyAcctRecord now takes borrnumber, and $notifyid and no longer env, param. * GetFlagsAndBranchFromBorrower is deleted.

1 0

code cleaning of Reserves.pm
by Paul POULAIN 24 Apr '07

24 Apr '07

* GlobalCancel : renammed to ModReserveCancelAll * OtherReserves : renamed to GetOtherReserves * MinusPriority : renamed to ModReserveMinusPriority and SQL improvement: 2 nested SQL read/update that could be done in 1 step * SetWaitingStatus : renamed to ModReserveStatus * GetReservations and FindReserves merged, API changed and resulting sub is GetReserves * GetFirstReserveDateFromItem removed (mered into GetReserves improved to return the branchcode that was the only field missing) * splitting GetReserves in 3 different sub : one for each parameter. Depending on the parameter (biblionumber / itemnumber / borrowernumber), the GetReserves sub returned differents things (2 var, 1 array ...) that is silly & hard to read. Splitting in 3 subs is not the most efficient, but it's more readable. Later, we could maybe merge them again by having a common returned result, but i'm not sure it would be possible * CountReservesFromBorrower renamed to GetReserveCount * CheckReserves : No change (see question below) * CancelReserve : name unchanged (it's not a reserve deletion, so I think DelReserve is wrong) * FillReserve renamed to ModReserveFill and variable names changed internally * FixPriority renamed to _FixPriority (internal sub) * WaitingReserves renamed to ModReserveAffect, POD & cleaned * GetWaitingReserves : removed (merged in BetReservesFromBorrowernumber) * CalcHLTReserveFee : removed (hardcoded specific rules for HLT. Don't ask me to reintroduce them, I will disagree : we can't have specific hardcoded code in Koha) * GetNextAccountNumber : removed (unused) * UpdateReserve : renamed to ModReserve * findgroupreserve : renamed to _findgroupreserve (internal sub) * CreateReserve : renamed to AddReserve (& opac-reserve call fixed : a undef parameter useless) * CalcReserveFee : renamed to GetReserveFee * GetReserveTitle : removed (useless) * FindReservesInQueue : removed (copy of GetReservesFromBiblionumber) * CheckReserves : removed $barcode parameter (never used) QUESTION 1 : what is reservecontraint table done for ? does it work ? It seems that the table is filled only in Reserves.pm, CreateReserve, only if constraint='o' or 'e' (dunno what it means). In the code, contraint seems to be possibly 'a', but I don't know how it can occur. QUESTION 2 : could someone explain exactly how reserves work (internally). I'm not sure i've got all cases. CONCLUSION : i'm not fully happy with this cleaning. I think a second tour could/should be done, mainly in Modxxx sub, as I think we could have a fewer number of subs. But I won't do it. -- 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

code cleaning of circulation
by Paul POULAIN 23 Apr '07

23 Apr '07

Hi, hdl & me start cleaning circulation module. The goal will be to have : - C4/Circulation.pm => to deal with issues, returns, transfers - C4/Overdues.pm => to deal with overdues and fines - C4/Reserves.pm => to deal with Reserves thus : - C4/Circulation/ will disappear - most subs will be renamed - some subs will be moved from a package to another - some subs will be dropped (merged into another one) comments welcomed ;-) -- 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

6 9

record into database from script?
by Jason Ronallo 20 Apr '07

20 Apr '07

Hi, I'm writing a command line script for rapid copy cataloging. At the moment it's very specific to my library, but I hope to make it more generic and useful for others. It adds on item level information, so I bulkmarcimport the saved files and the records are immediately active in the catalog. It also outputs a csv list that I use for printing labels in glabels. What I'm wondering is how I can get my script to push a MARC record into the active database or at least into the reservoir? I'm imagining that the script is being used by a copy cataloger and not the administrator of the machine, so calling bulkmarcimport won't work. Or would I be able to change group permissions on bulkmarcimport.pl, make the copy catalogers (who are on Linux boxes) members of the group, and then when they run the script their call to bulkmarcimport.pl will work? What other options are there? --Jason

1 0

Replace rel_2_2 with dev_week ?
by Bruffey, Mark 17 Apr '07

17 Apr '07

Reposting, because I think I made an error in the manner in which I posted it previously. Sorry. I'm trying to understand the relationship between the document "Updating KOHA" and the document "Installing and Configuring KOHA's Zebra Plugin." Following a fresh install of 2.2.8, I seem to have successfully implemented the instructions in "Updating KOHA." At least the interfaces come up. (I have inserted only one record into the database at this point; intranet db searching is fine, opac errors out in search iface but not a great concern at this point.) Comments: In "Updating KOHA" p.4, it would be helpful to clarify that $KOHA_WORKING_DIR ends up being $KOHA_WORKING_DIR/koha for the purpose of the symbolic links--or at least it did for me. Assuming I did get that right (I used MC to match contents of directories before executing ln -s in each case), I now want to "Install and Configure KOHA's Zebra Plugin." I've figured out the instructions up to _Prepare the Filesystem_, but now, stuck. I can't figure out if I am supposed to ditch all the symlinks I just created for cvs rel_2_2 in favor of dev_week. I have downloaded both into separate directories, but it looks like linking dev_week into /koha will overlap with rel_2_2 links. Should I just eliminate the rel_2_2 links and replace with the dev_week? Thanks, Mark L. Mark Bruffey Director Library Services Central Baptist Theological Seminary 900 Forestview Lane N Plymouth MN 55441 763 417 8264 (Tel) 763 417 8258 (Fax) mbruffey(a)centralseminary.edu Central Seminary www.centralseminary.edu <http://www.centralseminary.edu/> Fourth Baptist Church www.fourthbaptist.org <http://www.fourthbaptist.org/> WCTS Radio AM 1030 Online www.centralseminary.edu/wcts *************************************** Have you experienced the good news? "Every one who calls on the name of the Lord will be saved!" [Romans 10:13] ***************************************

2 1

where is opac-export.pl?
by Jason Ronallo 12 Apr '07

12 Apr '07

Hi, I'm wondering if anyone could direct me to opac-export.pl in cvs? I see from the live NPL opac-detail.pl pages that this is the script that runs when you select to save an individual record in various formats, but I can't find it in cvs. I'm trying to see if I can get this single record export to work in rel_2_2 (2.2.8 specifically). I know a little Perl, but still trying to find my way around cvs. A project I'm thinking about starting will rely on this functionality to succeed. --Jason

1 0

WebInstaller modification rel_30 [Important]
by Henri-Damien LAURENT 06 Apr '07

06 Apr '07

Adding Check for a systempreference Version Variable skips third party software check and mysql check to go to updatedatabase. Adding similar check to intranet and opac. BEWARE !!!!! You may be linked to install if you donot have Version variable set in your systempreferences table. If so, simply updatedatabase OR add Version 3.0 record to your systempreferences table. -- Henri-Damien LAURENT

1 0