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

Request about a new table in Koha (MySQL level)
by tajoli 25 Jul '09

25 Jul '09

Dear Colin Campbell and all, I see your patch about a message system in Opac and Circulation. This patch add a MySQL table and clerly is for the version 3.2 I don't think RM of 3.0.x will insert it into into the official code. As CILEA we tring to complete the documentation of 3.0.x at MySQL level and to write a good documentation about MySQL level of 3.2. So could you send to Koha-devel list a description of this new table ? For example: --A brief description of the tables --A list of all implicit and explicit connection with others tables --A brief description of every field Thank you for every thing Cheers Zeno Tajoli

1 0

Hardcoding XSLT files to force opening URLs in new window (bug #3098)
by Wagner, Jane 24 Jul '09

24 Jul '09

If XSLT is turned on (for OPAC details and results), the syspref OPACURLOpenInNewWindow is not obeyed. For sites who want URLs to open in a new window, this is a problem ranging from mildly annoying to a serious concern. I reported it as a bug (#3098) some time ago, and revisited it again today for one of my sites. I have not yet been able to figure out how to pass the syspref into the XSLT files, but I have been able to hardcode those files to force opening a new window instead of the default same window. Following discussion on the IRC today, I'm not going to send this as a patch, but I thought I'd share it for other sites who want URLs to open in a new window and want an interim local fix until the larger problem of passing/obeying sysprefs is solved. Under koha-tmpl/opac-tmpl/prog/en/xslt, in MARC21slim2OPACDetail.xsl and MARC21slim2OPACResults.xsl, under the 856 section, search for the line <a><xsl:attribute name="href"><xsl:value-of select="marc:subfield[@code='u']"/></xsl:attribute> Change the beginning <a> as follows: <a target="_blank"> Jane Wagner Library Systems Analyst PTFS Inc. Content Management and Library Solutions 6400 Goldsboro Road, Suite 200 Bethesda, MD 20817 (301) 654-8088 x 151 jwagner(a)ptfs.com

3 3

Hints on reconciliation branch
by LAURENT Henri-Damien 24 Jul '09

24 Jul '09

Hi, Release Maintainer for 3.0.x speaking. I will be on holidays tonight for 2 weeks. But you can see some progress about reconciliation branch on koha-maintenance branch reconciliation. Be warned that it is for testing purposes and should not be used in production. Moreover, update database has not been updated yet. This work is in progress. There is already some bases for that. But dbversion numbering has some missing numbers. And you should have some hints about that quite soon. see http://git.koha.org/cgi-bin/gitweb.cgi?p=koha-maintenance.git;a=summary for the code. How can I test it ? if you have a dev version : git remote add maintenance git://git.koha.org/pub/scm/koha-maintenance.git git fetch maintenance git branch --track testing_3.0.2 remotes/maintenance/master git checkout testing_3.0.2 for those who are using HEAD already, either your version is 3.01.00.30 and you have nothing to do OR your version is before, and you may have to fix your kohaversion in your database to set it to 3.00.01.00 so that updatedatabase can update your database. You may have some duplicate warnings for all the transformations which has already been made. then login to intranet and updatedatabase will occur. And test and file any bug to me personnaly. What IS NOT in that version : Nothing from master and 3.0.x. Comments and bug reports welcome. Please, if you see some patches which have not made their way into that branch and which you use, be so kind as to resend them to me personnally. 3.0.x and koha master branch patches should all be there, but maybe some patches sent on list are not integrated. In the future, in order to be sure that patches can be smoothly integrated, I suggest that vendors could open up chosen git branches so that integration of patches can be more sure than simply making it via emails. See git.biblibre.com to see biblibre exposed branches for koha : master is our master branch 3.0.x is our 3.0.x branch official_3.0.x is a copy of official/3.0.x dom_wip is work in progress on dom configuration with git So highly unstable. If someone wants to test. It is the same thing as for koha-maintenance, git remote add biblibre git://git.biblibre.com/koha-biblibre git remote update you can rebase your branches over those remote branches, so that your devs can be on top and you can format-patch and send those patches to me for integration. I'll be back on 10th, August but will participate in IRC meeting. cheers. -- Henri-Damien LAURENT

1 0

Transition and continuity
by Galen Charlton 24 Jul '09

24 Jul '09

Hi folks, As some of you may have heard or been speculating about, I will be joining Equinox at the beginning of August. Although that of course means that I will start hacking on Evergreen, I am committed to seeing 3.2 to completion and release and will continue on as release manager. I also intend to start as release maintainer for 3.2, although as time passes, it may be necessary to find another RMaint. Regardless, I will continue to be involved in Koha. I look forward to continuing to work with you all. Regards, Galen Charlton Koha 3.2 Release Manager gmcharlt(a)gmail.com

10 9

Next project IRC meeting - 5 August 2009
by Galen Charlton 23 Jul '09

23 Jul '09

Hi, The next general IRC meeting of the Koha project will take place on 5 August 2009 at 10:00 UTC+0. The agenda currently includes the following items: 1. Update on Roadmap to 3.2 2. Update on Koha 3.0 Roadmap 3. Follow-up on actions from General IRC Meeting 1 July 2009 4. Management of KohaSocialNetworks To propose additional agenda items, please go to the wiki page for this meeting located at <http://wiki.koha.org/doku.php?id=meetingnotes09aug05>. As a reminder, the IRC meetings taken place on the #koha channel on the IRC server irc.katipo.co.nz. Regards, Galen -- Galen Charlton VP, Research & Development, LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709 skype: gmcharlt

2 1

to Garry Collum
by paul POULAIN 20 Jul '09

20 Jul '09

Hello Garry, I see your commits since a few months (april), but I don't remember seeing any introduction here, so I ask: could you pls introduce yourself, and tell us "why" you work on Koha ? You have now 58 patches accepted in Koha. Most of them are improving the overall quality of Koha (ie : inconsistencies fixes, like unused variables, html fixes ...) Do you plan to work on some features, or you'll just continue improving the quality? anyway, I want to express my thanks for the 58 previous patches, and my hopes there will be many many more ;-) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

5 5

zebra indexes are not working
by Z. Iqbal 20 Jul '09

20 Jul '09

hi i am working on koha3 with debian 5. i have imported about 68000 marc records through koha3 interface(staged,then import) with small files about 100 marc record in each file and zebra services have been working properly. the problem arises when i imported 69000 marc record the zebra service get stop and after 68000 record, no records have been search by zebra. can any one have the same problem. i donot know what to do? regards, z.iqbal -- View this message in context: http://www.nabble.com/zebra-indexes-are-not-working-tp24566721p24566721.html Sent from the Koha - Dev mailing list archive at Nabble.com.

1 0

koha doubts
by Sivasankari Muthuraja 20 Jul '09

20 Jul '09

1.how to configure to send mail when an item checkout/item checkin. I'm able to send mail , when a patron account is created. - hence it shows the mail functionality with my fedora linux machine/ with koha But while i do checkout/checkin , the mail should be sent, if the specify 0 in the delay, will the mail will be sent on today's date. 2.In circulation configuration - my system preference has only 28 attribute values to be changed , bu the liblime site has more features.(38 attribs). IS This is due to multiple branch modes. I'm using koha version 3.0002012. Is this addtional features available in latest versions greater tha 3.02. So, that i can enable certain features during circulation 3.I have selected Marc21 frameworks on, and selected addition for custom frameworks, like books,kits,binders,audiovisual materials etc - to limit the entry of marc21 contents - like book title,publisher,physical dimensions of book etc.(Since i'm a novice user, and have no knowledge in MARC21 fomats. I had added books successfully to it. But when i give a search - in a catalog with blank text(With out entering anthing and doing a search), no items are displayed. Is there anything related with zebra, to have this feature enabled. But if i give the keyword, the records are displayed , what may be problem Wont koha accepts blank search(on click of go with search textbox being blank), to display all the records. I saw some of the demo sites. it worked well some times. some times, i have select the specific item type to lists the available items in koha . But the catalog statistics in Report link gives results 0. But the stock/inventory management - shows the results of available books. kindly help me out to resolve this issues 4..suppose if each item has by default 2 weeks of loan period,from the date of checkout. - Last day in end of 2 weeks, is the due date to return. how to set the grace period for the extra days. How long i can set the grace period. if the days to return crossed the grace period. hope the fine will be levied. aftewards, the card will be debarred. Is this is a usual mechanism in library. Let me know the details about this -Sivasankari

1 0

DBD autocommitt error on Debian 5.0.1
by Sunita Barve 17 Jul '09

17 Jul '09

Dear All, We have selected debian 5.0.1 lenny for koha 3.00.03 installation. We have been getting the following error when we run admin/web opac page. we are following dselect command as mentioned for debian lenny installation. I would greatly appreciate if you could tell us how to come out of this error. I have also sent the same query on koha-digest page. We tried several times installing KOHA on Debian 501 Lenny system but on some machines it works and on some machines when machines are rebooted we get the following error. Does this error has anything to do with Debian 501 Lenny installation or any other error. Pl. let us know how to sort out this problem. Sunita Barve Koha error The following fatal error has occurred: DBD driver has not implemented the AutoCommit attribute at /usr/local/lib/perl/5.10.0/DBI.pm line 705. Compilation failed in require at /usr/share/koha/lib/C4/Circulation.pm line 25. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Circulation.pm line 25. Compilation failed in require at /usr/share/koha/lib/C4/Overdues.pm line 24. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Overdues.pm line 24. Compilation failed in require at /usr/share/koha/lib/C4/Members.pm line 27. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Members.pm line 27. Compilation failed in require at /usr/share/koha/lib/C4/Auth.pm line 31. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Auth.pm line 31. Compilation failed in require at /usr/share/koha/intranet/cgi-bin/mainpage.pl line 24. BEGIN failed--compilation aborted at /usr/share/koha/intranet/cgi-bin/mainpage.pl line 24. -- Sunita Barve, Ph. D. SIRC-In-Charge National Centre for Radio Astrophysics Post Bag No. 3, Pune Univ. Campus Pune 411 007, INDIA Phone : Office : 91-20-25719211 Residence : 91-020- 24470022 Mobile: 9922753827 Email : sunitab(a)ncra.tifr.res.in ; sunitabarve(a)gmail.com

1 0

Re: [Koha-devel] LDAP configuration in Koha3.0 on Linux
by Library Guy 17 Jul '09

17 Jul '09

I know very little perl, so I'm unsure of the syntax for single, double or no quotes for variables: Test 1: Either $userldapentry->exists("$uid_field"); or $userldapentry->exists($uid_field); Global symbol "$uid_field" requires explicit package name at /home/koha/kohaclone/C4/Auth_with_ldap.pm line 168, <DATA> line 253 Test 2: $userldapentry->exists('$uid_field'); Can't call method "exists" on an undefined value at /home/koha/kohaclone/C4/Auth_with_ldap.pm line 168, <DATA> line 253. James On Fri, Jul 17, 2009 at 12:24 PM, Michael Hafen<mdhafen(a)tech.washk12.org> wrote: > I'm not sure. Maybe if you changed the exists() call from 'uid' to > "$uid_field". Maybe that would still init the attrs hash. Can you try > that? > > On Fri, 2009-07-17 at 12:05 -0500, Library Guy wrote: >> I will check with our I.T. but I am not hopeful. What would it take >> for Auth_with_ldap.pm to be modified to circumvent this, such as using >> sAMAcountName? Is it that simple? >> >> James >> >> On Fri, Jul 17, 2009 at 11:47 AM, Michael Hafen<mdhafen(a)tech.washk12.org> wrote: >> > Of course, why didn't I see that before. Of course AD doesn't have the >> > uid attribute. >> > >> > There is a free download from Microsoft, Services For Unix, which adds >> > this and a few other attributes. Look into that. >> > >> > On Fri, 2009-07-17 at 11:41 -0500, Library Guy wrote: >> >> Ben, I'm testing the latest dev (3.01.00.037). LDAP authentication >> >> against our MS AD LDAP works properly using auth_by_bind, but if I >> >> enable either <replicate> or <update>, as soon as a new patron is >> >> authenticated Koha produces this error: >> >> >> >> Can't call method "exists" on an undefined value at >> >> /home/koha/kohaclone/C4/Auth_with_ldap.pm line 168, <DATA> line 253. >> >> >> >> The offending line 168 in Auth_with_ldap.pm is: >> >> >> >> $userldapentry->exists('uid'); # This is bad, but required! By >> >> side-effect, this initializes the attrs hash. >> >> >> >> I suspect it has something to do with uid not being a part of our >> >> schema, but I don't know where to go from here or how to help the >> >> developers address it. >> >> >> >> Thanks! >> >> >> >> James >> >> >> >> >> >> On Wed, Jul 15, 2009 at 8:06 PM, Ben Finney<ben+koha(a)benfinney.id.au> wrote: >> >> > Dobrica Pavlinusic <dpavlin(a)rot13.org> >> >> > writes: >> >> > >> >> >> Idea is simple: instead of having single administrative user which can >> >> >> do LDAP compare to check password, we just bind as user who is trying >> >> >> to login. >> >> > >> >> > Yes, this is the correct way to authenticate against an LDAP directory. >> >> > As you say, it requires no privileged access to the directory beyond >> >> > that granted to the authenticating user. >> >> > >> >> > This normal behaviour (bind as authenticating user) is available in the >> >> > current development tree of Koha 3.x, and is not yet in any stable >> >> > release TTBOMK. >> >> > >> >> > -- >> >> > \ Rommel: “Don't move, or I'll turn the key on this can of Spam!” | >> >> > `\ —The Goon Show, _Rommel's Treasure_ | >> >> > _o__) | >> >> > Ben Finney >> >> > >> >> > >> >> > >> >> > _______________________________________________ >> >> > Koha-devel mailing list >> >> > Koha-devel(a)nongnu.org >> >> > http://lists.nongnu.org/mailman/listinfo/koha-devel >> >> > _______________________________________________ >> >> > Koha-devel mailing list >> >> > Koha-devel(a)lists.koha.org >> >> > http://lists.koha.org/mailman/listinfo/koha-devel >> >> > >> >> _______________________________________________ >> >> Koha-devel mailing list >> >> Koha-devel(a)lists.koha.org >> >> http://lists.koha.org/mailman/listinfo/koha-devel >> > -- >> > Michael Hafen >> > Systems Analyst and Programmer >> > Washington County School District >> > Utah, USA >> > >> > for Koha checkout >> > http://development.washk12.org/gitweb/ >> > or >> > git://development.washk12.org/koha >> > >> > >> > > -- > Michael Hafen > Systems Analyst and Programmer > Washington County School District > Utah, USA > > for Koha checkout > http://development.washk12.org/gitweb/ > or > git://development.washk12.org/koha > > >

2 2