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

LDAP configuration in Koha3.0 on Linux
by Sai bhalaji Dhinakaran 17 Jul '09

17 Jul '09

Hi, I am trying to configure Koha3.0 on Linux(Ubuntu) to use our LDAP server. I referred to the below link for configuration: http://wiki.koha.org/doku.php?id=en:development:ldap&s Our LDAP server does not provide any field name for password and hence I am not able to map in the koha_conf.xml file. Also, please let me know if there is any other file that I need to modify to succeed in configuring for this. Can someone please help me in resolving this issue since I am unable to understand the flow of this authentication process. Thanks and Regards, Sai. 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.

8 13

SQL schema of Koha 3.0.3
by Zeno Tajoli 17 Jul '09

17 Jul '09

Hi to all, as I say in previous post and on IRC, CILEA has sponsor writing documentation of Koha logical SQL schema. So CILEA has partial done the RFC <http://wiki.koha.org/doku.php?id=en:development:rfcs3.2:rfc32_koha_api_uml_…>Koha E-R diagrams and tables information If you go to http://wiki.koha.org/doku.php?id=en:development:dbschema you can see now two new links about Koha 3.0.3 logical schema In fact the SQL documentation is the same, the second has a proposal how to keep this documentation. From the README: Firstly, to automatize as much as possible the documentation task we used a tool called SchemaSpy <http://schemaspy.sourceforge.net/> which allows one to explore and produce a diagram representation of the MYSQL DB. Secondly, to store the produced documentation we leveraged the capability of MYSQL of associating comments to both tables and columns. Even though there are some (but not critical, in this case) drawbacks in using MYSQL comments to document the DB, such as limited length of table-level comments, the main benefit is that once entered they become part of the DB itself and thus they can be inherited, no matters if table or column definitions change with subsequent releases of the softwares. Documentation information is added by using an SQL script called "documentation patch". This patch has to be created dynamically, starting from an existing installation of KOHA because in order to add a comment is necessary to change the table/columns definition. Since the table/column definition can change at any time during the development process, we want to be able to "desume" this definition by looking at the DB structure. To do so, we leverage the XML file containing a representation the DB structure created by SchemaSpy when it runs on the DB of a Koha installation (note: the file will be called "koha.xml" if the DB name is "koha"). By transforming this XML file through an XSLT stylesheet we obtain dynamically an SQL patch. This SQL file can now be edited, for example to add new table/columns comments, and then it should be run again against the DB in order to update it. It's a good practice to re-generate the SQL patch every time we want to modify the documentation in order to avoid that in the meanwhile the DB structure changed. Example of commands needed to create the SQL patch: Step 1: Running SchemaSpy > java -jar schemaSpy_4.1.1.jar -dp <path_to_mysql_java_connector> -o <output_folder> -t mysql -host <host> -u <user> -p <password> -db <db_to_describe> Step 2: Creating the SQL patch: > java -jar saxon9.jar -s:<path_to_XML_file_generated_by_SchemaSpy> -xsl:generate_sql_dbdoc_patch.xsl -o:autogen_dbdoc_patch.sql Step 3: Update autogen_dbdoc_patch.sql vi autogen_dbdoc_patch.sql Insert the comments about new column, fix errors, etc. Step 4: Running the SQL script: > mysql -u <user> -p -h <host> < autogen_dbdoc_patch.sql So the work of Matteo Romanello is done. The questions are: -Do you like the selection of those tools ? -Do you think this is a good workflow to keep updated the documentation of MySQL level ? Bye to all Zeno Tajoli CILEA - Segrate (MI) tajoliAT_SPAM_no_prendiATcilea.it (Indirizzo mascherato anti-spam; sostituisci quanto tra AT con @)

1 0

[koha-devel]: 'syndetic' usage in koha
by Mason James 17 Jul '09

17 Jul '09

Bonjour peoples, Does anyone know if the 'syndetic' book-jackets/cover-images are free to use for "general" usage or is a payment required to use the service? is the service free-to-use , but throttled - for non-paying usage? I have had a look around, but i cant quite find any decent info regarding the TOC any clues? cheers, Mason

2 2

Koha dev install
by Library Guy 17 Jul '09

17 Jul '09

perl Makefile.PL creates a complete Makefile when run from the stable tar, but if instead I choose a dev install from kohaclone after git pull, the Makefile is incomplete. Hence my dev version of koha-httpd.conf contains only variable names: ## OPAC <VirtualHost __WEBSERVER_IP__:__WEBSERVER_PORT__> ServerAdmin __WEBMASTER_EMAIL__ DocumentRoot __OPAC_WWW_DIR__ ServerName __WEBSERVER_HOST__ # ServerAlias opac.mydomain.com ScriptAlias /cgi-bin/koha/ "__OPAC_CGI_DIR__/opac/" ScriptAlias /index.html "__OPAC_CGI_DIR__/opac/opac-main.pl" ScriptAlias /opac-search.pl "__OPAC_CGI_DIR__/opac/search" ScriptAlias /search "__OPAC_CGI_DIR__/opac/search" ErrorLog __LOG_DIR__/koha-opac-error_log # TransferLog __LOG_DIR__/koha-opac-access_log SetEnv KOHA_CONF "__KOHA_CONF_DIR__/koha-conf.xml" SetEnv PERL5LIB "__PERL_MODULE_DIR__" What am I missing? Thanks! James

3 2

Staff client keyboard shortcuts
by Owen Leonard 16 Jul '09

16 Jul '09

I'd like to start a discussion on how keyboard shortcuts are implemented in the staff client so that going forward developers can be working according to the same playbook. Right now there are two different kinds of keyboard shortcuts: - shortcuts via the accesskey attribute - shortcuts via a jQuery plugin, hotkeys (http://code.google.com/p/js-hotkeys/) (Please note that this was recently updated in HEAD and the syntax has changed). The advantage of the accesskey method is of course that it's not javascript-dependent. The disadvantage is that different browsers handle accesskeys differently, a combination of keys is usually required (Alt+ or Ctrl+Alt+), and not all keys or key combinations will be available (for instance, because of conflicts with built-in browser shortcuts). The advantage of the javascript method is that it is possible to configure single-key shortcuts, although I think different browsers will still retain their shortcuts. Try this demo page: http://jshotkeys.googlepages.com/test-static-01.html. Currently the core set of accesskeys are "u" for Check Out, "r" for Check In, and "q" for Search. The javascript-based match for these is "Alt-u," "Alt-r," and "Alt-q." Darrell Ulm just submitted a patch that would add "F12" to the list of js-based shortcuts, used for printing a circ slip. Ideally our goal would be to provide shortcuts via accesskeys wherever possible, and supplement the accesskey method with javascript-based shortcuts. However, this limits us to keys which are valid for the accesskey method. Going forward, how should we choose the default keyboard shortcuts? Should we attempt to fall back on accesskeys? If no, should we expand the use of js-based keyboard shortcuts? Eager for opinions, Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org

5 8

wiki.koha.org relicensing
by MJ Ray 16 Jul '09

16 Jul '09

I'd like to help us move forwards with http://wiki.koha.org/doku.php?id=relicensing Can I have dumps of the wiki and bugs databases to trawl through to determine the relicensing electorate, please? Thanks, -- MJ Ray (slef) LMS developer and webmaster at | software www.software.coop http://mjr.towers.org.uk | .... co Notice http://mjr.towers.org.uk/email.html | .... op

2 1

OCLC Connexion Gateway
by Walls, Ian 16 Jul '09

16 Jul '09

Developers, Currently, my catalogers use OCLC Connexion to search for and update bibliographic records. Upon completion of a record, they simply press F5, and the record is imported into our existing ILS. The window that pops up gives them the current status of the export, and a report back on the new bibliographic and item records that were created. We want to preserve this smooth workflow with Koha. I wanted to bring this to our community first, in case anyone might also be looking into this, or if anyone has pursued it in the past. It seems like something we could certainly make work, and perhaps it would lower the barrier of acceptance for some libraries, knowing they could preserve a workflow like this. I talked with OCLC at ALA 2009, and while they didn't have an answer for me right then and there, they indicated that I'd probably need to do some programming to build an OCLC Gateway client. I will be calling their direct support lines, and hope to get connected to someone on their end who can tell me what sort of configurations, protocols and the like I'll need to put in place. I'll keep everyone posted. Cheers, Ian Walls Systems Integration Librarian NYU Health Sciences Libraries 550 First Ave., New York, NY 10016 (212) 263-8687 </PRE> <html> <body> ------------------------------------------------------------<br /> This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain information that is proprietary, confidential, and exempt from disclosure under applicable law. Any unauthorized review, use, disclosure, or distribution is prohibited. If you have received this email in error please notify the sender by return email and delete the original message. Please note, the recipient should check this email and any attachments for the presence of viruses. The organization accepts no liability for any damage caused by any virus transmitted by this email.<br /> ================================= </body> </html> <PRE>

2 1

corrupt record in issues table
by Bob Birchall ＠ Calyx 16 Jul '09

16 Jul '09

We have an entry in the issues table with a NULL itemnumber. This is causing the 'holds to pull' report to fail. Is it safe to simply delete the corrupt row from the issues table? We're using Koha 3.00.01.005 on Debian. Bob Birchall CALYX

2 1

Marc framework test error
by Sivasankari 14 Jul '09

14 Jul '09

hi, THis is the error while running marc framework test, how should i resolve this Thanks Sivasankari

1 0

marc format error
by Sivasankari Muthuraja 14 Jul '09

14 Jul '09

hi, THis is the error while running marc framework test, how should i resolve this Thanks Sivasankari

1 0