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

kohastructure.sql
by Simon Mitchell 16 Sep '09

16 Sep '09

Hi guy, am having a play with a script to convert the current mysql kohastructure.sql to postgresql etc. My thinking is that any updates to the mysql kohastructure.sql could be handled by automatically by a script. Firstly I have noticed that some table name and columns names are not quoted. Could some one fix that the next time an edit is done. Example DROP TABLE IF EXISTS `branch_transfer_limits`; CREATE TABLE branch_transfer_limits ( limitId int(8) NOT NULL auto_increment, toBranch varchar(10) NOT NULL, fromBranch varchar(10) NOT NULL, itemtype varchar(10) NULL, ccode varchar(10) NULL, PRIMARY KEY (limitId) ) ENGINE=InnoDB DEFAULT CHARSET=utf8; And My postgresql database complains that there is no unique key on aqbookfund bookfundid My thinking is this is cause by *REFERENCES `aqbookfund` (`bookfundid`)*which should be *REFERENCES `aqbookfund` (`bookfundid`,`branchcode`)* in table aqorderbreakdown. Does this need to be fixed or is bookfundid unique and justs needs a unique key? DROP TABLE IF EXISTS `aqbookfund`; CREATE TABLE `aqbookfund` ( `bookfundid` varchar(10) NOT NULL default '', `bookfundname` mediumtext, `bookfundgroup` varchar(5) default NULL, `branchcode` varchar(10) NOT NULL default '', PRIMARY KEY (`bookfundid`,`branchcode`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8; DROP TABLE IF EXISTS `aqorderbreakdown`; CREATE TABLE `aqorderbreakdown` ( `ordernumber` int(11) default NULL, `linenumber` int(11) default NULL, `branchcode` varchar(10) default NULL, `bookfundid` varchar(10) NOT NULL default '', `allocation` smallint(6) default NULL, KEY `ordernumber` (`ordernumber`), KEY `bookfundid` (`bookfundid`), CONSTRAINT `aqorderbreakdown_ibfk_1` FOREIGN KEY (`ordernumber`) REFERENCES `aqorders` (`ordernumber`) ON DELETE CASCADE ON UPDATE CASCADE, CONSTRAINT `aqorderbreakdown_ibfk_2` FOREIGN KEY (`bookfundid`) REFERENCES `aqbookfund` (`bookfundid`) ON DELETE CASCADE ON UPDATE CASCADE ) ENGINE=InnoDB DEFAULT CHARSET=utf8; ++++++++++++++++++++++++++++++++++++++++ some more ramblings follows I have been look at http://en.wikibooks.org/w/index.php?title=Programming:Converting_MySQL_to_P… and like the idea of using *SET sql_mode='ANSI_QUOTES' * at the top of the mysql sql files to get rid of the ` qoute and use ".* * The later versions of Postgresql has introduce new features that may make it possible koha to run on postgresql. Enum example - Mysql - CREATE TABLE `import_items` ( `import_items_id` int(11) NOT NULL auto_increment, `import_record_id` int(11) NOT NULL, `itemnumber` int(11) default NULL, `branchcode` varchar(10) default NULL, `status` enum('error', 'staged', 'imported', 'reverted', 'ignored') NOT NULL default 'staged', `marcxml` longtext NOT NULL, `import_error` mediumtext, PRIMARY KEY (`import_items_id`), CONSTRAINT `import_items_ibfk_1` FOREIGN KEY (`import_record_id`) REFERENCES `import_records` (`import_record_id`) ON DELETE CASCADE ON UPDATE CASCADE, KEY `itemnumber` (`itemnumber`), KEY `branchcode` (`branchcode`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8; Postgresql CREATE TYPE *enum_import_items_status* AS ENUM ('error', 'staged', 'imported', 'reverted', 'ignored'); DROP TABLE IF EXISTS "import_items"; CREATE TABLE "import_items" ( "import_items_id" serial, "import_record_id" integer NOT NULL, "itemnumber" integer default NULL, "branchcode" varchar(10) default NULL, "status" *enum_import_items_status* NOT NULL default 'staged', "marcxml" text NOT NULL, "import_error" text , PRIMARY KEY ("import_items_id") ); ALTER TABLE import_items ADD CONSTRAINT "import_items_ibfk_1" FOREIGN KEY ("import_record_id") REFERENCES "import_records" ("import_record_id") ON DELETE CASCADE ON UPDATE CASCADE; CREATE INDEX import_items_itemnumber_idx ON import_items ("itemnumber"); CREATE INDEX import_items_branchcode_idx ON import_items ("branchcode"); ++++++++++++++++++++++++++++ Regards Simon Sydney, Australia

2 1

Re: [Koha-devel] kohastructure.sql
by Zeno Tajoli 16 Sep '09

16 Sep '09

Dear Simon, At 08.26 16/09/2009, Simon Mitchell wrote: >Hi guy, am having a play with a script to convert the current mysql >kohastructure.sql to postgresql etc. >My thinking is that any updates to the mysql kohastructure.sql could >be handled by automatically by a script. i'm not sure this is the best path to have Koha on MySQL and on Postgresl. Chris Cormack is working on this topic (support Ps in Koha). I think he prefer to use a perl module as abstract layer (DBIx::Class). >Firstly I have noticed that some table name and columns names are not quoted. >Could some one fix that the next time an edit is done. > >And > >My postgresql database complains that there is no unique key on >aqbookfund bookfundid >My thinking is this is cause by REFERENCES `aqbookfund` >(`bookfundid`) which should be REFERENCES `aqbookfund` >(`bookfundid`,`branchcode`) >in table aqorderbreakdown. > >Does this need to be fixed or is bookfundid unique and justs needs a >unique key? In fact not all relations are present into .sql code. In fact to check to situation you need to see the code in the API (../C4 dirs). Documentation on DB level of Koha here: http://wiki.koha.org/doku.php?id=en:development:dbschema Attention on documentation about ver 3.0.3: Comments are correct, images not always. Bye Zeno Tajoli CILEA - Segrate (MI) tajoliAT_SPAM_no_prendiATcilea.it (Indirizzo mascherato anti-spam; sostituisci quanto tra AT con @)

1 0

Hiding search from users who haven't logged in
by Michael 16 Sep '09

16 Sep '09

Hi, I'm trying to make an adjustment on an OPAC. Is there a way to hide the 'search' form/buttons from users who have not logged in yet? Also, can it be done without editing the templates? Using jscript is fine or via any other method that can be done through System Preferences. Thanks!

2 1

Help for Koha and Fingerprint Reader
by Roxana Luz Fleipaz 16 Sep '09

16 Sep '09

Hello Friends. I'm sure there's someone here who has experience of working KOHA with Fingerprint Reader. My case is the following code readers have fingerprints SFR300 NEXT-S ver2 model, and I need to integrate with KOHA. Can anyone help me and tell me where to start? Thank you very much, Be aware of any please reply. Tanks. Roxana Luz

2 1

Koha error diagnosed, new question
by Chadwick, John, DCA 15 Sep '09

15 Sep '09

Okay, I diagnosed the cause of the error, but now I have a new question. In the koha-conf.xml file I commented out the last two lines concerning the memory caching, memcached_servers and memcached_namespace. That took care of the issue concerning being able to go to the web installer via the full url and getting the fatal error message when I use the just localhost:8080. Now, the question is, how important, or unimportant, is the memcached commands? Thanks, John +----------------------------------------------------------------------- -----+ John Chadwick, Ed.D. Information Technology Manager New Mexico State Library 1209 Camino Carlos Rey Santa Fe, NM 87507 Phone: 505-476-9740 Cell: 505-629-8116 Fax: 505-476-9761 john.chadwick(a)state.nm.us http://www.nmstatelibrary.org Confidentiality Notice: This e-mail, including all attachments is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited unless specifically provided under the New Mexico Inspection of Public Records Act. If you are not the intended recipient, please contact the sender and destroy all copies of this message. -- This email has been scanned by the Sybari - Antigen Email System. Confidentiality Notice: This e-mail,including all attachments is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review,use,disclosure or distribution is prohibited unless specifically provided under the New Mexico Inspection of Public Records Act. If you are not the intended recipient, please contact the sender and destroy all copies of this message. -- This email has been scanned by the MessageLabs Email Security System.

2 2

New install error.
by Chadwick, John, DCA 15 Sep '09

15 Sep '09

We are finally staging our production server that will house a couple of Koha sites to begin with using apache virtual hosting. I downloaded and install the latest version from the git repository and I have done a clean install. I am now getting something a bit strange and any help would be appreciated. When I use the following URL, we get to the Installer with no problem: http://localhost/cgi-bin/koha/installer/install.pl However, when we use the standard http://localhost:8080 <http://localhost:8080/> I get the following: production mode - trapped fatal error +----------------------------------------------------------------------- -----+ John Chadwick, Ed.D. Information Technology Manager New Mexico State Library 1209 Camino Carlos Rey Santa Fe, NM 87507 Phone: 505-476-9740 Cell: 505-629-8116 Fax: 505-476-9761 john.chadwick(a)state.nm.us http://www.nmstatelibrary.org Confidentiality Notice: This e-mail, including all attachments is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited unless specifically provided under the New Mexico Inspection of Public Records Act. If you are not the intended recipient, please contact the sender and destroy all copies of this message. -- This email has been scanned by the Sybari - Antigen Email System. Confidentiality Notice: This e-mail,including all attachments is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review,use,disclosure or distribution is prohibited unless specifically provided under the New Mexico Inspection of Public Records Act. If you are not the intended recipient, please contact the sender and destroy all copies of this message. -- This email has been scanned by the MessageLabs Email Security System.

1 0

what about 3.2 improvements under AGPL ?
by paul POULAIN 15 Sep '09

15 Sep '09

Hello, What do you think about releasing all our 3.2 improvements under AGPL ? http://www.gnu.org/licenses/agpl.html Summary: the AGPL makes mandatory to release source code even if your software is an hosted one. The AGPL is compatible with Koha, as Koha is GPL v2 *or later* http://www.gnu.org/licenses/gpl-faq.html#AllCompatibility (AGPL is considered as a part of the GPL: http://www.gnu.org/licenses/gpl-faq.html#SeparateAffero ) Of course, everything already existing, that is under GPL would stay as it. I think it would be a good idea. Publishing the source code is not enough (we all know that getting 400 000 lines of code without hint, help and a git repo would be useless), but at least, that would clarify our motives. cheers -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

4 3

Re: [Koha-devel] [Koha-patches] [PATCH] include grace period when calculating overdue fine
by Steve Wills 15 Sep '09

15 Sep '09

no. I think the grace period helps to determine when the fine is applied but not the amount of the fine. The fine_amount should be based on the duration between the due date and today. (due_date - today) the grace_end_date is grace_days after due_date. (due_date + grace_days) if today is less than or equal to grace_end_date, no fine. if today is after grace_end_date, fine_amount is charged as defined above. On a human note: I think that unless you are a meanie, it is human nature to try and give the patron a break, but strictly speaking, the grace period has nothing to do with the amount of the fine. At our library, there is no grace period but fines are never collected! Bringing the book back is always "good enough". LOL! Stev3 -----Original Message----- From: Galen Charlton [mailto:gmcharlt@gmail.com] Sent: Thursday, September 3, 2009 12:01 PM To: 'Steve Wills' Cc: 'Michael Hafen', koha-devel(a)lists.koha.org Subject: Re: [Koha-devel] [Koha-patches] [PATCH] include grace period when calculating overdue fine Hi,2009/9/3 Steve Wills :> If I understand this issue correctly, I would agree that the logic should> be:> item overdue = due_date - today.> Grace period calculations only come into play if the item is overdue to> discount the fine when applicable.> 2 cents.To clarify, are you saying that in your opinion the grace period*should* be subtracted when calculating the number of days to base theoverdue fine on?Regards,Galen-- Galen Charltongmcharlt(a)gmail.com

2 2

Re: [Koha-devel] Possible Feature
by Roche III, Edward 14 Sep '09

14 Sep '09

Thanks again Mike for all your help! Thanks! Ed Edward J. Roche Network Administrator Solanco School District 717.786.2151 x2437 "At the End of the Day, Did You Play to Win or Not to Lose?" -----Original Message----- From: Michael Hafen [mailto:mdhafen@tech.washk12.org] Sent: Monday, September 14, 2009 4:46 PM To: Roche III, Edward Subject: RE: [Koha-devel] Possible Feature Any page accessed by a barcode scanner will require that submit be pushed OR that the enter key be pressed. For this reason barcode scanners are commonly configured to add the enter key after any barcode scanned. That applies to this renew page, the enter sent by the scanner should do the job. On Mon, 2009-09-14 at 16:24 -0400, Roche III, Edward wrote: > Got it, looks good I will have the librarians test it out. > > I don't have a barcode scanner on hand but does it after scanning the > barcode automatically add it to the Renewed Items section at the bottom > or do have to hit submit? If you need to hit submit can code be added to > make that happen? > > Thanks! > Ed > > Edward J. Roche > Network Administrator > Solanco School District > 717.786.2151 x2437 > > "At the End of the Day, Did You Play to Win or Not to Lose?" > > > > -----Original Message----- > From: Michael Hafen [mailto:mdhafen@tech.washk12.org] > Sent: Monday, September 14, 2009 3:51 PM > To: Roche III, Edward > Subject: RE: [Koha-devel] Possible Feature > > I think patch can't handle these patches. It's because of the way git > shows the new file. You did good to put the renew.pl file in the > directory, please make sure the file has the executable permissions set. > A command like `chmod 755 renew.pl` should do the trick. That might fix > the Error 500 message. Let me know how that goes. There is a template > file for that page too, renew.tmpl, you will have to put that file in > the directory too I'm guessing. > > On Mon, 2009-09-14 at 15:17 -0400, Roche III, Edward wrote: > > I tried the Patch application and below is what I got.......Not sure > if > > I am doing it right. The renew.pl never gets put in the directory the > > link points to and if I put it there and I click the link on the > > Circulation page it gives me a...An Error has Occurred! > > Error 500 > > > > Can I do this manually? > > > > > > > > root@koha-vm1:/home/administrator/Desktop# patch < > > 0001-Add-page-in-circ-just-for-renewing.patch > > (Stripping trailing CRs from patch.) > > patching file renew.pl > > (Stripping trailing CRs from patch.) > > can't find file to patch at input line 251 > > Perhaps you should have used the -p or --strip option? > > The text leading up to this was: > > -------------------------- > > |diff --git > > a/koha-tmpl/intranet-tmpl/prog/en/includes/checkin-search.inc > > b/koha-tmpl/intranet-tmpl/prog/en/includes/checkin-search.inc > > |index d455649..5a23092 100644 > > |--- a/koha-tmpl/intranet-tmpl/prog/en/includes/checkin-search.inc > > |+++ b/koha-tmpl/intranet-tmpl/prog/en/includes/checkin-search.inc > > -------------------------- > > File to patch: > > > /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/includes/checkin-s > > earch.inc > > patching file > > > /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/includes/checkin-s > > earch.inc > > Reversed (or previously applied) patch detected! Assume -R? [n] > > Apply anyway? [n] y > > Hunk #1 FAILED at 2. > > Hunk #2 FAILED at 26. > > 2 out of 2 hunks FAILED -- saving rejects to file > > > /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/includes/checkin-s > > earch.inc.rej > > (Stripping trailing CRs from patch.) > > can't find file to patch at input line 283 > > Perhaps you should have used the -p or --strip option? > > The text leading up to this was: > > -------------------------- > > |diff --git a/koha-tmpl/intranet-tmpl/prog/en/includes/circ-search.inc > > b/koha-tmpl/intranet-tmpl/prog/en/includes/circ-search.inc > > |index 4b8841b..17f3841 100644 > > |--- a/koha-tmpl/intranet-tmpl/prog/en/includes/circ-search.inc > > |+++ b/koha-tmpl/intranet-tmpl/prog/en/includes/circ-search.inc > > -------------------------- > > File to patch: > > > /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/includes/circ-sear > > ch.inc > > patching file > > > /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/includes/circ-sear > > ch.inc > > Reversed (or previously applied) patch detected! Assume -R? [n] > > Apply anyway? [n] y > > Hunk #1 FAILED at 10. > > Hunk #2 FAILED at 35. > > 2 out of 2 hunks FAILED -- saving rejects to file > > > /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/includes/circ-sear > > ch.inc.rej > > (Stripping trailing CRs from patch.) > > can't find file to patch at input line 316 > > Perhaps you should have used the -p or --strip option? > > The text leading up to this was: > > -------------------------- > > |diff --git > a/koha-tmpl/intranet-tmpl/prog/en/includes/patron-search.inc > > b/koha-tmpl/intranet-tmpl/prog/en/includes/patron-search.inc > > |index a054829..f116316 100644 > > |--- a/koha-tmpl/intranet-tmpl/prog/en/includes/patron-search.inc > > |+++ b/koha-tmpl/intranet-tmpl/prog/en/includes/patron-search.inc > > -------------------------- > > File to patch: > > > /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/includes/patron-se > > arch.inc > > patching file > > > /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/includes/patron-se > > arch.inc > > Reversed (or previously applied) patch detected! Assume -R? [n] > > Apply anyway? [n] y > > Hunk #1 FAILED at 78. > > Hunk #2 FAILED at 102. > > 2 out of 2 hunks FAILED -- saving rejects to file > > > /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/includes/patron-se > > arch.inc.rej > > (Stripping trailing CRs from patch.) > > can't find file to patch at input line 351 > > Perhaps you should have used the -p or --strip option? > > The text leading up to this was: > > -------------------------- > > |diff --git > > a/koha-tmpl/intranet-tmpl/prog/en/modules/circ/circulation-home.tmpl > > b/koha-tmpl/intranet-tmpl/prog/en/modules/circ/circulation-home.tmpl > > |index 884b0dc..353c5b9 100644 > > |--- > > a/koha-tmpl/intranet-tmpl/prog/en/modules/circ/circulation-home.tmpl > > |+++ > > b/koha-tmpl/intranet-tmpl/prog/en/modules/circ/circulation-home.tmpl > > -------------------------- > > File to patch: > > > /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/modules/circ/circu > > lation-home.tmpl > > patching file > > > /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/modules/circ/circu > > lation-home.tmpl > > Reversed (or previously applied) patch detected! Assume -R? [n] > > Apply anyway? [n] y > > Hunk #1 FAILED at 19. > > 1 out of 1 hunk FAILED -- saving rejects to file > > > /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/modules/circ/circu > > lation-home.tmpl.rej > > (Stripping trailing CRs from patch.) > > patching file renew.tmpl > > > > Thanks! > > Ed > > > > Edward J. Roche > > Network Administrator > > Solanco School District > > 717.786.2151 x2437 > > > > "At the End of the Day, Did You Play to Win or Not to Lose?" > > > > > > > > -----Original Message----- > > From: Michael Hafen [mailto:mdhafen@tech.washk12.org] > > Sent: Monday, September 14, 2009 1:28 PM > > To: Roche III, Edward > > Subject: RE: [Koha-devel] Possible Feature > > > > You'll probably apply this patch on the command line. I'm not aware > of > > any other tools for handling patches. Assuming you save the > attachment > > I sent as 'attachment.patch': First option is the tool patch with a > > command like `patch < attachment.patch`. The second option is to use > > git. If you already have git working this is easiest, as you just > > change to the directory where the source code is and use the command > > `git am attachment.patch`. Git will handle it from there. > > > > On Mon, 2009-09-14 at 13:11 -0400, Roche III, Edward wrote: > > > Now I am going to be dump..I see there will be 6 file changes but I > > forget how to run the update. I know you told me this before but can't > > find the email. A little nudge would be good:) > > > > > > Thanks! > > > Ed > > > > > > Edward J. Roche > > > Network Administrator > > > Solanco School District > > > 717.786.2151 x2437 > > > > > > "At the End of the Day, Did You Play to Win or Not to Lose?" > > > > > > > > > > > > -----Original Message----- > > > From: Michael Hafen [mailto:mdhafen@tech.washk12.org] > > > Sent: Monday, September 14, 2009 11:43 AM > > > To: Roche III, Edward > > > Cc: patches(a)koha.org > > > Subject: RE: [Koha-devel] Possible Feature > > > > > > Attached is the patch file. > > > > > > On Mon, 2009-09-14 at 11:01 -0400, Roche III, Edward wrote: > > > > Cool, whenever you have a chance. > > > > > > > > Thanks! > > > > Ed > > > > > > > > Edward J. Roche > > > > Network Administrator > > > > Solanco School District > > > > 717.786.2151 x2437 > > > > > > > > "At the End of the Day, Did You Play to Win or Not to Lose?" > > > > > > > > > > > > > > > > -----Original Message----- > > > > From: Michael Hafen [mailto:mdhafen@tech.washk12.org] > > > > Sent: Monday, September 14, 2009 10:42 AM > > > > To: Roche III, Edward > > > > Subject: RE: [Koha-devel] Possible Feature > > > > > > > > Of course. It's Open Source :) > > > > > > > > On Mon, 2009-09-14 at 10:36 -0400, Roche III, Edward wrote: > > > > > Sweet...you always seem willing help! So you willing to share? > > > > > > > > > > Thanks! > > > > > Ed > > > > > > > > > > Edward J. Roche > > > > > Network Administrator > > > > > Solanco School District > > > > > 717.786.2151 x2437 > > > > > > > > > > "At the End of the Day, Did You Play to Win or Not to Lose?" > > > > > > > > > > > > > > > > > > > > -- 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

1 0

Koha LibraryThing Book Covers
by Kyle Hall 14 Sep '09

14 Sep '09

Hey All, We were thinking of switching from Amazon to LibraryThing for our book cover images. I know they have an API. When I googled 'librarything' and 'koha', I found this: http://www.librarything.com/thingology/2009/03/koha-support-introducing-chr… I searched the git repo and found no references to librarything. Does anyone know if Liblime ever released this code? If not, I'll just have to write a new module to take advantage of it. Thanks, Kyle http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org )

3 3