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

Fwd: Git users: bring out your bugbears!
by Chris Cormack 16 Oct '09

16 Oct '09

Hi Everyone One of my colleagues from work is off to a git get together, and Is asking if anyone has anything they really wish was different with git. I said I would ask the koha developers as we have used git for a while now. So any suggestions send them my way and I will pass them on to Sam. Chris ---------- Forwarded message ---------- Hi all, For some strange reason the Git project is again flying me over to Silly Valley for the Google Summer of Code Mentor Summit. And right after that I've got a thrilling 3 days of GitTogether™. This is a meeting with many core git developers to discuss direction for git - see http://git.or.cz/gitwiki/GitTogether09 What I'd appreciate is for people to drop me some notes about what you've found annoying in git or room for improvement - especially from those people who have had to teach it to new members in their team the most. One of the things I want to focus on are submodules - I hear from a lot of people that they suck and would like to hear from you why. If you have time to write, please do - otherwise if you'd prefer a face to face rant showing with example that's all good too. If there is sufficient interest in this I could schedule a brief workshop on it. I'm flying out in a week, so it needs to be between now and then. Cheers! Sam ----- End forwarded message -----

5 4

Label generator broken?
by Bernard Shiundu 15 Oct '09

15 Oct '09

Just upgraded my copy to 3.01.00.061 from 3.01.00.056 and get the following when trying to save any of my templates and layouts Can't bless non-reference value at /...C4/Profile.pm line 89. Apache Server version: Apache/2.2.9 (Debian) Server built: Jul 14 2009 20:03:28 Koha 3.01.00.061 Koha DB 3.0100061 MySQL mysql Ver 14.12 Distrib 5.0.51a, for debian-linux-gnu (i486) using readline 5.2 OS Linux laetitia 2.6.26-2-686 #1 SMP Wed Aug 19 06:06:52 UTC 2009 i686 Perl 5.010000 Before I file a bug report, anyone else got this?? ________________________________ Strathmore University provides all-round education in an atmosphere of freedom and responsibility. This email and any files transmitted with it are intended solely for use by the recipient(s) to whom it is addressed and may contain confidential information. If you have received this email in error please notify the sender immediately and permanently delete this email and/or any files attached to it from your computer. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Strathmore University. The University accepts no liability whatsoever for any loss or damages incurred, or suffered, resulting, or arising, from the use of this email and/or its attachments. The University warrants neither the integrity of the e-mail nor its freedom from errors, viruses, interception or any other form of interference. …………………………………………………………………. Website: www.strathmore.edu

3 10

[3.0.x] Errors in english system prefs
by Zeno Tajoli 15 Oct '09

15 Oct '09

Hi to all, I have found errors in standard english system prefs file, data/mysql/en/mandatory/sysprefs.sql I have write a bug about it http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=3712 This is valid on for 3.0.x I want to try to fix the bug. So I need info about some system preferences: -- FrameworksLoaded This preference is created and updated by web installer ? I think yes but i'm not sure at 100% -- ReceiveBackIssues -- maxItemsInSearchResults Those two preferences are present in the code, but not in cgi, templates or API files. Are they present now only for a future use ? Could you explain their use ? --- AmazonCoverImages, --- AuthDisplayHierarchy, --- OPACAmazonCoverImages --- ReadingHistory Those four preferences are present in the code and also in cgi, templates and API files. I think we need to insert them in data/mysql/en/mandatory/sysprefs.sql What do you think about it ? Bye Zeno Tajoli Zeno Tajoli CILEA - Segrate (MI) tajoliAT_SPAM_no_prendiATcilea.it (Indirizzo mascherato anti-spam; sostituisci quanto tra AT con @)

2 2

Question about bulkmarcimport.pl options
by Cindy Murdock Ames 14 Oct '09

14 Oct '09

Hi all, I have a question about these options in bulkmarcimport.pl: x source bib tag for reporting the source bib number y source subfield for reporting the source bib number idmap file for the koha bib and source id Can someone fill me in on what exactly they do? Thanks! Cindy -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Cindy Murdock Ames IT Services Director Meadville Public Library | CCFLS http://meadvillelibrary.org | http://ccfls.org

1 0

Can't call method "append_fields"
by constantine 13 Oct '09

13 Oct '09

Yes, the previous problem was solved, indeed... I do not understand why I have so many problems installing koha,.. maybe the last years I was too used to Joomla! installations :D So the challenging koha that its concept I so much admire and embrace makes me face another problem. Trying to add a MARC record, (I retrieved its data from a z30.50 server, but that does not matter, I think) and then I am getting an error page (http://localhost:8080/cgi-bin/koha/cataloguing/additem.pl) Its contents are: " Koha error The following fatal error has occurred: Can't call method "append_fields" on an undefined value at /usr/local/share/perl/5.10.0/MARC/File/SAX.pm line 95. at /usr/local/lib/perl/5.10.0/XML/LibXML/SAX.pm line 64 at /usr/local/share/perl/5.10.0/MARC/File/XML.pm line 443 Apache Server version: Apache/2.2.9 (Debian) Server built: Jun 21 2008 10:35:35 Koha 3.00.00.094 Koha DB 3.0000094 MySQL mysql Ver 14.12 Distrib 5.0.51a, for debian-linux-gnu (i486) using readline 5.2 OS Linux sangre 2.6.25.9xx6-costis07 #1 SMP PREEMPT Wed Jul 2 02:35:38 EEST 2008 i686 GNU/Linux Perl 5.010000 " The laste contens of /var/log/koha/koha-error_log are [...] [error] [...] [...] addbiblio.pl: INDEXING :orignew at /usr/share/koha/lib/C4/Biblio.pm line 2319., referer: http://localhost:8080/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=0&… [...] [error] [...] [...] addbiblio.pl: INDEXING :1 at /usr/share/koha/lib/C4/Biblio.pm line 2319., referer: http://localhost:8080/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=0&… [...] [error] [...] [...] addbiblio.pl: INDEXING :ocip at /usr/share/koha/lib/C4/Biblio.pm line 2319., referer: http://localhost:8080/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=0&… [...] [error] [...] [...] addbiblio.pl: INDEXING :20 at /usr/share/koha/lib/C4/Biblio.pm line 2319., referer: http://localhost:8080/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=0&… [...] [error] [...] [...] addbiblio.pl: INDEXING :y-gencatlg at /usr/share/koha/lib/C4/Biblio.pm line 2319., referer: http://localhost:8080/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=0&… [...] [error] [...] [...] addbiblio.pl: INDEXING :ddc at /usr/share/koha/lib/C4/Biblio.pm line 2319., referer: http://localhost:8080/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=0&… [...] [error] [...] [...] addbiblio.pl: INDEXING :SR at /usr/share/koha/lib/C4/Biblio.pm line 2319., referer: http://localhost:8080/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=0&… [...] [error] [...] [...] addbiblio.pl: INDEXING :pc15 2006-07-19 to SSCD at /usr/share/koha/lib/C4/Biblio.pm line 2319., referer: http://localhost:8080/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=0&… [...] [error] [...] [...] addbiblio.pl: INDEXING :jp00 2006-07-26 CIP recd at /usr/share/koha/lib/C4/Biblio.pm line 2319., referer: http://localhost:8080/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=0&… [...] [error] [...] [...] addbiblio.pl: INDEXING :jp20 2006-07-26 to subj at /usr/share/koha/lib/C4/Biblio.pm line 2319., referer: http://localhost:8080/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=0&… [...] [error] [...] [...] addbiblio.pl: INDEXING :jp03 2006-07-26 at /usr/share/koha/lib/C4/Biblio.pm line 2319., referer: http://localhost:8080/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=0&… [...] [error] [...] [...] addbiblio.pl: INDEXING :aa05 2006-07-27 at /usr/share/koha/lib/C4/Biblio.pm line 2319., referer: http://localhost:8080/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=0&… [...] [error] [...] [...] addbiblio.pl: INDEXING :1 at /usr/share/koha/lib/C4/Biblio.pm line 2319., referer: http://localhost:8080/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=0&… [...] [error] [...] [...] addbiblio.pl: INDEXING :1 at /usr/share/koha/lib/C4/Biblio.pm line 2319., referer: http://localhost:8080/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=0&… [...] [debug] mod_deflate.c(619): [...] Zlib: Compressed 37993 to 5966 : URL /cgi-bin/koha/cataloguing/additem.pl, referer: http://localhost:8080/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=0&… [...] [error] [...] [...] additem.pl: Can't call method "append_fields" on an undefined value at /usr/local/share/perl/5.10.0/MARC/File/SAX.pm line 95. at /usr/local/lib/perl/5.10.0/XML/LibXML/SAX.pm line 64, referer: http://localhost:8080/cgi-bin/koha/cataloguing/additem.pl?biblionumber=1&fr… [...] [error] [...] [...] additem.pl: at /usr/local/share/perl/5.10.0/MARC/File/XML.pm line 443, referer: http://localhost:8080/cgi-bin/koha/cataloguing/additem.pl?biblionumber=1&fr… What could I do to solve this problem? Tsardounis Constantine http://costis.name _______________________________________________ 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

2 1

Dear Developers... want help and how?
by David Schuster 12 Oct '09

12 Oct '09

I am more than willing to attempt to help in "testing" preparing for the next release. I just need some direction as to what I can do. I am unable to install an update locally - but am more than willing to test and do things on someone else' box. What can I do.... David Schuster -- View this message in context: http://www.nabble.com/Dear-Developers...-want-help-and-how--tp25664106p2566… Sent from the Koha - Dev mailing list archive at Nabble.com.

4 3

3 RFCs for Koha 3.4
by Nicolas Morin 12 Oct '09

12 Oct '09

Hello, There's a feature freeze for Koha 3.2, but BibLibre just won a development contract for Koha 3.4 with a university library here in France. I'll be updating the wiki during the next few days, with the details of the developments we plan to do as part of this contract. Most of them have to do with the Circulation module. The entry point for RFCs for Koha 3.4 is thus: http://wiki.koha.org/doku.php?id=en:development:rfcs3.4 I started out with 3 RFCs: Ergonomics of smart-rules and circulation parameters A lot of development is intended to allow for more refined parameters as far as circulation is concerned: see other RFCs for 3.4. There's going to be many more options and many more toggles / choices / more possibilities. It's doubtful this can be accommodated within the current smart-rules.pl page. So a new way to deal with the UI aspect of managing rules is in order. (to be continued with actual proposals: feel free to chime in) (http://wiki.koha.org/doku.php?id=en:development:ergonomics_of_smart-rules_a…) Flagged patrons: enhancements In 3.2 when a patron is manually flagged using gonenoaddress, lost or debarred, it's just managed as a toggle choice. Enhancements proposed are: * add a comment field to the current 3 choices: e.g. debarred_comment * add a hidden timestamp to the choices: e.g. debarred_timestamp * add a timestamp, entered through the UI, to put an end date to the flag: e.g. debarred_enddate or some such * add a script which lifts the flags based on the myflag_enddate * display the myflag_comment when the record is pulled in circulation.pl (http://wiki.koha.org/doku.php?id=en:development:enhancements_to_debarred_pa…) Enhancements to the display of extended patron attributes in circulation Extended patron attributes are a great tool, which provides nice flexibility in the information one wants to manage in the patron's record. But as of version 3.2 we don't have any way to manage how this information will be displayed once entered. For some extended attributes, it might be useful to have them display in circ/circulation.pl, in the Check Out tab, which is arguably the most important tab in this page. This RFC proposes: * to make the Check Out tab rather than Details the default tab called in the UI when the librarian scans the card's barcode and calls the patron's record from the checkout box at circulation-home.pl or at circulation.pl * to add a field to admin/patron-att-types.pl?op=edit|add_attribute_type → labeled “display in check out”, with a checkbox * manage the display of those selected attribute types in the display of the patron's information in the checkout tab on circulation.pl (http://wiki.koha.org/doku.php?id=en:development:enhancements_to_the_display…) Feel free to add your thoughts in the wiki. Again: more RFCs pertaining to circulation to be added in the coming days. Cheers, Nicolas -- Nicolas Morin Mobile: +33(0)633 19 11 36 http://www.biblibre.com

1 0

To mantain documentation on Mysql tables, indexess and relation
by Zeno Tajoli 12 Oct '09

12 Oct '09

Hi to all, as I said in the last IRC meeting, http://stats.workbuffer.org/irclog/koha/2009-09-02#i_295862, as CILEA we are working on mantain dcoumentation on Mysql tables, indexeses and relations. The work done until now is here: http://wiki.koha.org/doku.php?id=en:development:dbschema The instrument used is Schema Spy, http://schemaspy.sourceforge.net/. As I know is the better tool avaible for those works and open source. Well, to create a good documentation Schema Spy needs comments INSIDE definion of Mysql tables. So the SQL command of the table 'action_logs' now is : CREATE TABLE `action_logs` ( `action_id` int(11) NOT NULL auto_increment, `timestamp` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP, `user` int(11) NOT NULL default 0, `module` text, `action` text, `object` int(11) default NULL, `info` text, PRIMARY KEY (`action_id`), KEY (`timestamp`,`user`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8; For Schema Spy needs to be: CREATE TABLE `action_logs` ( `action_id` int(10) NOT NULL default '0' COMMENT 'Action ID', `timestamp` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP COMMENT 'Timestamp', `user` int(10) default NULL COMMENT 'User', `module` text COMMENT 'Module on which the action was performed', `action` text COMMENT 'Action (e.g., ADD,MODIFY,RETURN, etc.)', `object` int(11) default NULL, `info` text COMMENT 'Info about the action performed', PRIMARY KEY (`action_id`), KEY `timestamp` (`timestamp`,`user`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COMMENT='[sys] Log of actions performed on the system'; So Schema Spy need the command 'COMMENT' with useful information. So, the decision that we need to take: Do we insert the command 'COMMENT' in the basic definition SQL file, the file installer/data/mysql/kohastructure.sql ? Or do we insert the command 'COMMENT' in a specific file ? With the first option is very clear how to document a new develop on SQL, in the file installer/data/mysql/kohastructure.sql. With the second option we have a more standard installer/data/mysql/kohastructure.sql file [COMMENT is a command specific of MySQL] but it is easier to forget to document the new develop. I prefer the first option but there are differents opinion about it. So, please, tell what do you prefer. Bye Zeno Tajoli CILEA - Segrate (MI) tajoliAT_SPAM_no_prendiATcilea.it (Indirizzo mascherato anti-spam; sostituisci quanto tra AT con @)

5 6

Requests and Due Date Mail trigger
by Sai bhalaji Dhinakaran 12 Oct '09

12 Oct '09

Hi, I have Koha 3.0 running on Ubuntu. I would like to integrate it with our mail server. My requirements are: 1. User must be able to place request from OPAC page, which must drop into the Librarian's mail box. Is it configurable in the existing system or needs some code change? 2. User and the librarian must receive a mail whenever a book issued exceeds the due date. Please let me know if some more details are required to address this requirement. Thanks and Regards, Sai Bhalaji __________ Information from ESET NOD32 Antivirus, version of virus signature database 4498 (20091011) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com ________________________________ This email and any attachment(s) transmitted may contain confidential, proprietary or legally privileged information relating to D&B TransUnion Analytic and Decision Services Private Limited. The information is intended solely for the recipient. No part of this information may be disclosed, copied, reproduced, distributed or made available in any form whatsoever without prior authorization. If you have received this email in error please notify the sender electronically and delete all copies immediately. This email may contain viruses. D&B TransUnion Analytic and Decision Services Private Limited has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this email. We strongly advise you to ensure that the email and any attachment(s) are free of any virus.

1 0

OPAC Log-in
by Bob Birchall ＠ Calyx 12 Oct '09

12 Oct '09

Hi all, Is it possible to configure the opac so that a user can perform a search only if logged in? A special library wishes to expose its catalogue to internal eyes only. So the required sequence would be to enter the url, be directed to a log-in page (the way the staff client works) and then when logged in be directed to opac-user.pl (as happens now when you log in from opac-main.pl) How can that be achieved? Thanks, Bob Birchall Calyx

2 1