tag:www.nabble.com,2006:forum-14380Nabble - Koha2008-10-11T15:11:37ZKoha is the first open-source Integrated Library System (ILS). In use worldwide, its development is steered by a growing community of libraries collaborating to achieve their technology goals. Koha home is <a href="http://www.koha.org/" target="_top" rel="nofollow">here</a>.tag:www.nabble.com,2006:post-19936910Re: RFC: Improvements to Koha security and privacy2008-10-11T15:11:37Z2008-10-11T15:11:37ZJesse Weaver-2<div dir="ltr"><br><br><div class="gmail_quote">On Wed, Oct 8, 2008 at 3:49 AM, Krishnan Mani <span dir="ltr"><<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19936910&i=0" target="_top" rel="nofollow">krishnanm75@...</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><span style="font-weight: bold; font-family: Courier New,courier,monaco,monospace,sans-serif;">Introduction</span><br style="font-weight: bold; font-family: Courier New,courier,monaco,monospace,sans-serif;">
<span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">With growing Koha usage at large public libraries and exposure of the OPAC (and in several cases, the Intranet interfaces) to audiences over the (big, bad) public Internet, the Koha community needs to be increasingly sensitive to security and data privacy. </span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
<br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">If not, it is possible that Koha
systems may present easy targets to unscrupulous people looking for potentially sensitive patron information that may be compromised and abused.</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
<br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">In this regard, Koha is not current with many commonly-accepted mechanisms to improve overall security. Moreover, these mechanisms (IMHO) can be easily added to Koha without disproportionate effort. The most cost-effective way of improving security of any system is to build the security into it upfront.</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
<br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif; font-weight: bold;">Suggested improvements</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
<br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif; text-decoration: underline;">S1. E-mail confirmation workflow</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
<span style="font-family: Courier New,courier,monaco,monospace,sans-serif; font-style: italic;">Background</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">At account creation, Koha now has the option (using a template) in 'Notification' to send e-mail to an e-mail field on the patron records. The default template even includes the login name and password (in cleartext). </span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
<br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif; font-style: italic;">Issue</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
<span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">Any errors in specifying or recording e-mail address will send account creation (or other) e-mail to the wrong person. With the default template, such errors will directly allow another person to login to the member's account.</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
<br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif; font-style: italic;">Improvements</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
<ol><li><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">To
introduce an e-mail workflow requiring patrons to confirm membership. Koha can send account details after confirmation of membership. (An example is the workflow for users signing up to Koha mailing lists)</span></li><li>
<span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">To change the default template to include only a one-time password (or one-time login facility) (to be described below)</span></li></ol><span style="font-family: Courier New,courier,monaco,monospace,sans-serif; text-decoration: underline;">S2. About passwords</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
<span style="font-family: Courier New,courier,monaco,monospace,sans-serif; font-style: italic;">Background</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">Login passwords are not temporary and there is no mechanism to
force users to change passwords. </span><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">While Koha suggests a password to be set at the time of account creation, this means that at least one staff member knows passwords or may set them to something that is trivially weak.</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
<br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">Currently, a system preference allows administrators to specify (only) a minimum character length for passwords.</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
<br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif; font-style: italic;">Issue</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
<span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">More than one person is involved and has knowledge about passwords being set/reset. This introduces potential human error in communicating passwords during account creation or password reset</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
<br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif; font-style: italic;">Suggested improvements</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
<ol><li><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">Introduce one-time passwords (or one-time login links) automatically generated and e-mailed by Koha <br></span></li><li><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">Change the default
account creation template shipped with Koha to include a one-time password/link allowing time-bound one-time login</span></li><li><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">Force users to change first-time passwords immediately on login</span></li>
<li><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;"></span><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">Staff to only request Koha to reset the passwords on accounts rather than set actual passwords.</span></li>
<li><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;"></span><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">Provide a self-service facility to users to request new passwords (or to reset passwords via a one-time login). Users are authenticated using a configurable piece of information from patron records that is used to construct 'challenge'
questions.</span></li><li><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">Disallow display of passwords in cleartext anywhere in Koha or in e-mail notification</span></li><li><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">Enhance checks for password strength by checking for, some combination of uppercase and lowercase characters, numerals, and special characters. Add system preferences for administrators to specify the particular mix.</span><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;"></span></li>
<li><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">Allow administrators to specify a lifetime for passwords (say, 90 days), and have Koha force users to change passwords older than the same.</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
</li></ol><span style="font-family: Courier New,courier,monaco,monospace,sans-serif; text-decoration: underline;">S3. Database access and 'super-librarian' login</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
<span style="font-family: Courier New,courier,monaco,monospace,sans-serif; font-style: italic;">Background</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">Koha stores the database user and password to (/etc/koha/)koha-conf.xml with the password in cleartext. This file is world-readable, and my own attempt to restrict access to this file breaks Koha. </span><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">The same login and password is used to login to the Intranet post-installation, with 'super-librarian' privileges</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
<br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif; font-style: italic;">Suggested improvements</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
<ol><li><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">Protect configuration files containing sensitive information and change Koha code to be able to read the same (This author is unaware of a suitable mechanism in Perl but recalls using the 'requires' facility in .php on products like Joomla)</span></li>
<li><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;"></span><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">Disallow logging into Koha using the database user and password</span></li>
<li><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;"></span><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">Create a one-time administrator login during installation to be used post-installation to create regular staff users.</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
</li></ol><span style="font-family: Courier New,courier,monaco,monospace,sans-serif; text-decoration: underline;">S4. Print "last login" information upon logging in</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
<span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">This alerts users to any logins they may not recall and help detect any compromise attempts.</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
<br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif; text-decoration: underline;">S5. Securing KOHA logins over SSL</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
<span style="font-family: Courier New,courier,monaco,monospace,sans-serif; font-style: italic;">Background</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">The OPAC login facility is available on most pages inline with other page content</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
<br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif; font-style: italic;">Issue</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
<span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">If a site wants to secure, say, just logins, by serving those pages over SSL, it is currently not possible to do so without serving all of
the site over SSL. This may not be acceptable considering potentially higher load and response times to serve content over SSL.</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
<span style="font-family: Courier New,courier,monaco,monospace,sans-serif; font-style: italic;">Suggested improvements</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><ol><li><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">Separate the login page (as in the Intranet), so as to secure the same over SSL, and once the user is authenticated, the user can be redirected to regular content served over HTTP.</span><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;"></span></li>
<li><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">Allow configuring at installation time the use
of SSL for some set of pages, including, for example, login, change password, patron profile pages, etc.</span><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;"></span></li><li><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">Simple instructions for admins to generate and use self-signed certificates for SSL may be included with the documentation.</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
</li></ol><span style="font-family: Courier New,courier,monaco,monospace,sans-serif; text-decoration: underline;">S6. Improvements to disabling/enabling OPAC and Intranet access</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
<span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">At the moment, it is unclear whether clearing out the login and password field on a member record disables their login, and whether non-staff patrons
have access to both OPAC and Intranet or just the OPAC. </span><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">(the author is researching these)</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
<span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">This can be remedied by simply providing an additional toggle to enable/disable login for a patron. </span><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">This may also be useful in the event that a stray patron posts abusive content in tags or book reviews.</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
<br><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">Thanks and regards,</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
<div style="font-family: Courier New,courier,monaco,monospace,sans-serif;">krishnan mani<br>Pune, India<div><br></div></div></div><br>
<hr size="1"> Share files, take polls, and make new friends - all under one roof. <a href="http://in.rd.yahoo.com/tagline_groups_8/*http://in.promos.yahoo.com/groups/" target="_blank" rel="nofollow"> Click here.</a></div><br>_______________________________________________<br>
Koha-devel mailing list<br>
<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19936910&i=1" target="_top" rel="nofollow">Koha-devel@...</a><br>
<a href="http://lists.koha.org/mailman/listinfo/koha-devel" target="_blank" rel="nofollow">http://lists.koha.org/mailman/listinfo/koha-devel</a><br>
<br></blockquote></div><br>These sound fairly reasonable. Could you put them on the wiki under <a href="http://wiki.koha.org/doku.php?do=login&id=en%3Adevelopment%3Arfcs3.2" target="_top" rel="nofollow">http://wiki.koha.org/doku.php?do=login&id=en%3Adevelopment%3Arfcs3.2</a> ?<br>
<br>(Together or separated, whichever seems best)<br clear="all"><br>-- <br>Jesse Weaver<br>Software Developer, LibLime<br>
</div>
<br />_______________________________________________
<br>Koha-devel mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19936910&i=2" target="_top" rel="nofollow">Koha-devel@...</a>
<br><a href="http://lists.koha.org/mailman/listinfo/koha-devel" target="_top" rel="nofollow">http://lists.koha.org/mailman/listinfo/koha-devel</a><br><p>From forum: <a href="http://www.nabble.com/Koha---Dev-f14381.html" embed="fixTarget[14381]" target="_top" >Koha - Dev</a></p>tag:www.nabble.com,2006:post-19930449Re: error when adding vendor2008-10-11T00:47:31Z2008-10-11T00:47:31ZCharleeDear All,
<br><br>I have installed Koha 3.0 on OpenSuse 11. I am also getting the same error while adding a vendor -
<br><br>Koha error
<br><br>The following fatal error has occurred:
<br><br>Undefined subroutine &main::AddBookseller called at /usr/share/koha/intranet/cgi-bin/acqui/updatesupplier.pl line 92.
<br><br>Apache Server version: Apache/2.2.8 (Linux/SUSE) Server built: Jun 6 2008 23:42:07
<br>Koha 3.00.00.107
<br>Koha DB 3.0000107
<br>MySQL mysql Ver 14.12 Distrib 5.0.51a, for suse-linux-gnu (i686) using readline 5.2
<br>OS Linux linux-fty1 2.6.25.5-1.1-pae #1 SMP 2008-06-07 01:55:22 +0200 i686 i686 i386 GNU/Linux
<br>Perl 5.010000
<br><br><br><br><blockquote class="quote light-black dark-border-color"><div class="quote light-border-color">
<div class="quote-author" style="font-weight: bold;">mallikarjun dora wrote:</div>
<div class="quote-message shrinkable-quote">Dear ALL
<br><br>Koha error
<br>The following fatal error has occurred:
<br><br>Undefined subroutine &main::AddBookseller called at
<br>/usr/share/koha/intranet/cgi-bin/acqui/updatesupplier.pl line 92.
<br>Apache Server version: Apache/2.2.8 (Linux/SUSE) Server built: Jun 6
<br>2008 23:42:07
<br>Koha 3.00.00.107
<br>Koha DB 3.0000107
<br>MySQL mysql Ver 14.12 Distrib 5.0.51a, for suse-linux-gnu (i686) using
<br>readline 5.2
<br>OS Linux susekoha 2.6.25.5-1.1-pae #1 SMP 2008-06-07 01:55:22 +0200
<br>i686 i686 i386 GNU/Linux
<br>Perl 5.010000
<br>_______________________________________________
<br>Koha-devel mailing list
<br>Koha-devel@lists.koha.org
<br><a href="http://lists.koha.org/mailman/listinfo/koha-devel" target="_top" rel="nofollow">http://lists.koha.org/mailman/listinfo/koha-devel</a></div>
</div></blockquote>
<p>From forum: <a href="http://www.nabble.com/Koha---Dev-f14381.html" embed="fixTarget[14381]" target="_top" >Koha - Dev</a></p>tag:www.nabble.com,2006:post-19929645Out of office2008-10-10T22:00:30Z2008-10-10T22:00:30Zhoward_dahdah<html><body>
<p>I will be out of the office starting 11/10/2008 and will not return until 20/10/2008.<br>
<br>
I wont be accessing this email account but if it is urgent send a message to <a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19929645&i=0" target="_top" rel="nofollow">howiedahdah@...</a>. Otherwise you can contact Andrew Hendry on 9902 2711.</body></html>
<br />_______________________________________________
<br>Koha mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19929645&i=1" target="_top" rel="nofollow">Koha@...</a>
<br><a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_top" rel="nofollow">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br><p>From forum: <a href="http://www.nabble.com/Koha---Discuss-f14390.html" embed="fixTarget[14390]" target="_top" >Koha - Discuss</a></p>tag:www.nabble.com,2006:post-19927228Re: Koha 3 on Ubuntu 8.04 - "trapped fatal error"2008-10-10T15:44:31Z2008-10-10T15:44:31ZBetsy LawThis error was discussed in another thread and the solution proposed
<br>was to install CGI::Session::yaml or CGI::Session::Serialize::yaml
<br>(two different answers were given).
<br><br><a href="http://www.nabble.com/Installing-3.0-on-FreeBSD---Web-Installer-Errors-td19684528.html" target="_top">http://www.nabble.com/Installing-3.0-on-FreeBSD---Web-Installer-Errors-td19684528.html</a><br><br>--Betsy
<br><br>On Fri, Oct 10, 2008 at 3:26 PM, ANDREW MICHAEL EFREM GIESLER
<br><<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19927228&i=0" target="_top" rel="nofollow">agiesler@...</a>> wrote:
<div class='shrinkable-quote'><br>> Hello,
<br>>
<br>> I've installed Koha 3 on Ubuntu 8.04 with all pre-run tests reporting success. When I visit <a href="http://127.0.1.1:8080/" target="_top" rel="nofollow">http://127.0.1.1:8080/</a>, Koha redirects me to <a href="http://127.0.1.1:8080/cgi-bin/koha/installer/install.pl" target="_top" rel="nofollow">http://127.0.1.1:8080/cgi-bin/koha/installer/install.pl</a> and gives this message:
<br>>
<br>> production mode - trapped fatal error
<br>>
<br>> The Koha error log (/var/log/koha/koha-error_log) shows this error followed by several others:
<br>>
<br>> [Fri Oct 10 16:03:40 2008] [error] [client 127.0.1.1] [Fri Oct 10 16:03:40 2008] install.pl: DBD::mysql::st execute failed: Table 'koha.language_subtag_registry' doesn't exist at /usr/share/koha/lib/C4/Languages.pm line 178.
<br>>
<br>> Languages.pm line 178 is trying to select * from table "language_subtag_registry". The 'koha' database has no such table; in fact, there it has no tables at all. I've confirmed that my 'kohaadmin' user exists, has the correct password, and owns the 'koha' database with all permissions enabled.
<br>>
<br>> Any ideas?
<br>>
<br>> …Andy Giesler
<br>> _______________________________________________
<br>> Koha mailing list
<br>> <a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19927228&i=1" target="_top" rel="nofollow">Koha@...</a>
<br>> <a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_top" rel="nofollow">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br>>
</div>_______________________________________________
<br>Koha mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19927228&i=2" target="_top" rel="nofollow">Koha@...</a>
<br><a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_top" rel="nofollow">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br><p>From forum: <a href="http://www.nabble.com/Koha---Discuss-f14390.html" embed="fixTarget[14390]" target="_top" >Koha - Discuss</a></p>tag:www.nabble.com,2006:post-19927091Koha 3 on Ubuntu 8.04 - "trapped fatal error"2008-10-10T15:26:35Z2008-10-10T15:26:35ZAndy GieslerHello,
<br><br>I’ve installed Koha 3 on Ubuntu 8.04 with all pre-run tests reporting success. When I visit <a href="http://127.0.1.1:8080/" target="_top" rel="nofollow">http://127.0.1.1:8080/</a>, Koha redirects me to <a href="http://127.0.1.1:8080/cgi-bin/koha/installer/install.pl" target="_top" rel="nofollow">http://127.0.1.1:8080/cgi-bin/koha/installer/install.pl</a> and gives this message:
<br><br>production mode - trapped fatal error
<br><br>The Koha error log (/var/log/koha/koha-error_log) shows this error followed by several others:
<br><br>[Fri Oct 10 16:03:40 2008] [error] [client 127.0.1.1] [Fri Oct 10 16:03:40 2008] install.pl: DBD::mysql::st execute failed: Table 'koha.language_subtag_registry' doesn't exist at /usr/share/koha/lib/C4/Languages.pm line 178.
<br><br>Languages.pm line 178 is trying to select * from table “language_subtag_registry”. The 'koha' database has no such table; in fact, there it has no tables at all. I’ve confirmed that my 'kohaadmin' user exists, has the correct password, and owns the 'koha' database with all permissions enabled.
<br><br>Any ideas?
<br><br>…Andy Giesler
<br>_______________________________________________
<br>Koha mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19927091&i=0" target="_top" rel="nofollow">Koha@...</a>
<br><a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_top" rel="nofollow">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br><p>From forum: <a href="http://www.nabble.com/Koha---Discuss-f14390.html" embed="fixTarget[14390]" target="_top" >Koha - Discuss</a></p>tag:www.nabble.com,2006:post-19925973Re: Login questions2008-10-10T13:55:27Z2008-10-10T13:55:27ZBradley Peters-2On Wed, Oct 8, 2008 at 12:31 PM, Bradley Peters <<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19925973&i=0" target="_top" rel="nofollow">koha@...</a>> wrote:
<br>> First I searched in the manual, but I could not find an explanation
<br>> there. (I may have missed it, but I looked through the Table of
<br>> Contents and did a search for "My Library".)
<br><br>After the fact, I found this question answered in the manual FAQ. It
<br>seems there might be something not right with the search index as
<br>there were some other terms that also did not return results (e.g.
<br>debar) but are present. Which is kind of weird considering its on a
<br>Google product.
<br><br>Sincerely,
<br>BDP.
<br>_______________________________________________
<br>Koha mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19925973&i=1" target="_top" rel="nofollow">Koha@...</a>
<br><a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_top" rel="nofollow">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br><p>From forum: <a href="http://www.nabble.com/Koha---Discuss-f14390.html" embed="fixTarget[14390]" target="_top" >Koha - Discuss</a></p>tag:www.nabble.com,2006:post-19924075Re: HELP ME WITH KOHA 3.0 INSTALATION2008-10-10T11:56:55Z2008-10-10T11:56:55ZAdalid OrtizThat's right I'm sucefully installed Koha serveral times on Windows XP
<br>SP 2 with the instructions at Rob Weir web site about Koha.
<br><br>----------------------------------------------------------------
<br>This message was sent using IMP, the Internet Messaging Program.
<br><br>_______________________________________________
<br>Koha-win32 mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19924075&i=0" target="_top" rel="nofollow">Koha-win32@...</a>
<br><a href="http://lists.koha.org/mailman/listinfo/koha-win32" target="_top" rel="nofollow">http://lists.koha.org/mailman/listinfo/koha-win32</a><br><p>From forum: <a href="http://www.nabble.com/Koha---Win32-f14384.html" embed="fixTarget[14384]" target="_top" >Koha - Win32</a></p>tag:www.nabble.com,2006:post-19923826Re: HELP ME WITH KOHA 3.0 INSTALATION2008-10-10T11:41:23Z2008-10-10T11:41:23ZBetsy LawSo far no one has reported success in installing Koha 3.0 on Windows.
<br>Version 2.2.9 is working well on Windows if you would like to try it.
<br>Here is the link to the Windows documentation and dependencies:
<br><br><a href="http://www.koha.rwjr.com/" target="_top" rel="nofollow">http://www.koha.rwjr.com/</a><br><br>Be sure to read the instructions linked from that page
<br>(<a href="http://www.koha.rwjr.com/Koha_on_Windows.html" target="_top" rel="nofollow">http://www.koha.rwjr.com/Koha_on_Windows.html</a>). They walk you
<br>through steps like getting your Perl directory right. Also note that
<br>you should use mysql 4 because mysql 5 is not compatible at this time.
<br> Here is where mysql 4 downloads are archived:
<br><br><a href="http://dev.mysql.com/downloads/mysql/4.1.html#win32" target="_top" rel="nofollow">http://dev.mysql.com/downloads/mysql/4.1.html#win32</a><br><br>Hope this gets you started.
<br><br>--Betsy
<br><br>On Sat, Oct 4, 2008 at 12:36 PM, josue =D <<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19923826&i=0" target="_top" rel="nofollow">joshua001985@...</a>> wrote:
<div class='shrinkable-quote'><br>> Hello i'm from Bolivia i have to migrate a library system, this is done with
<br>> WiniSIS and i was searching the different kinds of ILMS software and i
<br>> choosed koha, and i wanna know how can i install with XAMP,LAMP,EasyPHP or
<br>> AppServ. I tried but i can't do it well. and that is not all, if i can
<br>> install koha then i'll need to migrate the data in winisis to koha.
<br>> I'm triying to install on windows xp service pack2.
<br>> Please help me, Thanks in advance.
<br>>
<br>> ________________________________
<br>> Ahora llévate lo mejor de MSN y Windows Live, en tu móvil
<br>> _______________________________________________
<br>> Koha-win32 mailing list
<br>> <a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19923826&i=1" target="_top" rel="nofollow">Koha-win32@...</a>
<br>> <a href="http://lists.koha.org/mailman/listinfo/koha-win32" target="_top" rel="nofollow">http://lists.koha.org/mailman/listinfo/koha-win32</a><br>>
<br>>
</div>_______________________________________________
<br>Koha-win32 mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19923826&i=2" target="_top" rel="nofollow">Koha-win32@...</a>
<br><a href="http://lists.koha.org/mailman/listinfo/koha-win32" target="_top" rel="nofollow">http://lists.koha.org/mailman/listinfo/koha-win32</a><br><p>From forum: <a href="http://www.nabble.com/Koha---Win32-f14384.html" embed="fixTarget[14384]" target="_top" >Koha - Win32</a></p>tag:www.nabble.com,2006:post-19922944Re: Advanced search2008-10-10T10:46:58Z2008-10-10T10:46:58ZWinter, JamesI fixed the problem with the advanced search; I changed the record.abs file to match the subfields that we have in the 952 MARC tag and now searching by type works.
<br><br>But when I click on the link for Limit to currently available items I get zero results. Has anyone else run into this problem?
<br><br>Thanks.
<br><br>James Winter
<br>Arcadia University
<br>Systems Manager
<br>215.517.2588
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19922944&i=0" target="_top" rel="nofollow">winterj@...</a>
<br>
<br><br><br>-----Original Message-----
<br>From: Betsy Law [mailto:<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19922944&i=1" target="_top" rel="nofollow">betsy.law@...</a>]
<br>Sent: Thursday, October 09, 2008 2:49 PM
<br>To: Winter, James
<br>Cc: <a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19922944&i=2" target="_top" rel="nofollow">koha@...</a>
<br>Subject: Re: [Koha] Advanced search
<br><br>Doesn't look like there is a solution yet. Here's the bug:
<br><br><a href="http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2599" target="_top" rel="nofollow">http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2599</a><br><br>--Betsy
<br><br>On Wed, Oct 8, 2008 at 1:42 PM, Winter, James <<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19922944&i=3" target="_top" rel="nofollow">WinterJ@...</a>> wrote:
<div class='shrinkable-quote'><br>> I've seen others are having this problem but it wasn't clear on whether or
<br>> not there was a solution.
<br>>
<br>>
<br>>
<br>> When I search by item type I always get zero results. I have authorized
<br>> values in the itype column in the items table, but not in the biblioitems
<br>> itemtype column. I added some manually to that column and still couldn't
<br>> search by type.
<br>>
<br>>
<br>>
<br>> Is this a known bug, and is there a workaround?
<br>>
<br>>
<br>>
<br>> Thanks.
<br>>
<br>>
<br>>
<br>> James Winter
<br>>
<br>> Arcadia University
<br>>
<br>> Systems Manager
<br>>
<br>> 215.517.2588
<br>>
<br>> <a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19922944&i=4" target="_top" rel="nofollow">winterj@...</a>
<br>>
<br>>
<br>>
<br>>
<br>>
<br>> _______________________________________________
<br>> Koha mailing list
<br>> <a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19922944&i=5" target="_top" rel="nofollow">Koha@...</a>
<br>> <a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_top" rel="nofollow">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br>>
<br>>
</div>_______________________________________________
<br>Koha mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19922944&i=6" target="_top" rel="nofollow">Koha@...</a>
<br><a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_top" rel="nofollow">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br><p>From forum: <a href="http://www.nabble.com/Koha---Discuss-f14390.html" embed="fixTarget[14390]" target="_top" >Koha - Discuss</a></p>tag:www.nabble.com,2006:post-19921645Re: about postgresql and koha2008-10-10T09:26:50Z2008-10-10T09:26:50Zricardo mendoza-5<div dir="ltr">Thank you. That`s a good thing to know. I can see that Koha needs a better support for postgresql
. see you. <br><br></div>
<br />_______________________________________________
<br>Koha mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19921645&i=0" target="_top" rel="nofollow">Koha@...</a>
<br><a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_top" rel="nofollow">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br><p>From forum: <a href="http://www.nabble.com/Koha---Discuss-f14390.html" embed="fixTarget[14390]" target="_top" >Koha - Discuss</a></p>tag:www.nabble.com,2006:post-19920849Observation on Notices/Notice Trigger Tools2008-10-10T08:44:20Z2008-10-10T08:44:20ZBradley Peters-2Hello,
<br><br>I just started using Koha (version 3.0) and I was surprised to see the
<br>definition of overdue notices and triggers was located under Tools
<br>rather than under Administration. I expected them to be in the latter
<br>section because the patron category editor (under Administration) has
<br>a field that seems to define which patron categories appear in the
<br>notice editor.
<br><br>Sincerely,
<br>Bradley Peters
<br>_______________________________________________
<br>Koha mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19920849&i=0" target="_top" rel="nofollow">Koha@...</a>
<br><a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_top" rel="nofollow">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br><p>From forum: <a href="http://www.nabble.com/Koha---Discuss-f14390.html" embed="fixTarget[14390]" target="_top" >Koha - Discuss</a></p>tag:www.nabble.com,2006:post-19920143Re: LDAP authentication -- Joy!.....2008-10-10T08:06:22Z2008-10-10T08:06:22Zmourik jan c heupink-2> and Ta! Da! I had working LDAP authentication
<br>> (a BIG thanks to whoever wrote and posted this script to the wiki...it
<br>> worked perfectly!)
<br><br>That would be me :-)
<br><br>you're welcome!
<br>_______________________________________________
<br>Koha mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19920143&i=0" target="_top" rel="nofollow">Koha@...</a>
<br><a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_top" rel="nofollow">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br><p>From forum: <a href="http://www.nabble.com/Koha---Discuss-f14390.html" embed="fixTarget[14390]" target="_top" >Koha - Discuss</a></p>tag:www.nabble.com,2006:post-19919623Re: LDAP authentication -- Joy!.....2008-10-10T07:38:34Z2008-10-10T07:38:34ZScott OwenHi all,
<br><br>Just answering the my own issue for list(s) consumption, maybe it'll
<br>help someone in the future.
<br>(since it looks like win32 users may be stuck on 2.2.9 for a while...)
<br><br>I switched back to the css them (I was using the npl), and LDAP
<br>authentication started working MUCH more like I expected.
<br>
<br>I was able to pretty much just copy the script changes from
<br><a href="http://wiki.koha.org/doku.php?id=ldap&s=ldap" target="_top" rel="nofollow">http://wiki.koha.org/doku.php?id=ldap&s=ldap</a><br><br>and Ta! Da! I had working LDAP authentication
<br>(a BIG thanks to whoever wrote and posted this script to the wiki...it
<br>worked perfectly!)
<br><br>I made a couple modifications (see below) to allow users in different
<br>contexts to login.
<br>In my case I have a O=SCHOOL and two OU's ou=students and ou=staff.
<br><br><br> ##################################################
<br> ### LOCAL
<br> ### Change the code below to match your own LDAP server.
<br> ##################################################
<br><br> # LDAP connection parameters
<br><br> # LDAP server
<br> my $ldapserver = '10.1.1.7';
<br><br> # Base DN for users
<br> my $name = "ou=students,o=SCHOOL";
<br> my $name2 = "ou=staff,o=SCHOOL";
<br><br> # Bind uses the users full DN, if uid doesn't work try "cn"
<br> my $binddn = "cn=$userid,$name";
<br> my $binddn2 = "cn=$userid,$name2";
<br><br> my $db = Net::LDAP->new( $ldapserver );
<br>
<br> # do bind
<br> my $res =$db->bind(
<br> dn =>$binddn,
<br> password =>$password);
<br>
<br> # do bind
<br> my $res =$db->bind(
<br> dn =>$binddn2,
<br> password =>$password);
<br><br><br><br> # check result, any other result than LDAP_SUCCESS (0)
<br> # is a problem
<br> if($res->code != 0 ) {
<br> # auth refused
<br> warn "Auth failed. LDAP server not responding or invalid
<br>credentials provided";
<br><br><br><br><br><br><br><br><br><br>_______________________________________________
<br>Koha mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19919623&i=0" target="_top" rel="nofollow">Koha@...</a>
<br><a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_top" rel="nofollow">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br><p>From forum: <a href="http://www.nabble.com/Koha---Discuss-f14390.html" embed="fixTarget[14390]" target="_top" >Koha - Discuss</a></p>tag:www.nabble.com,2006:post-19919019Indicators for MARC fields2008-10-10T06:55:56Z2008-10-10T06:55:56ZLenora OftedahlWhere can I edit the indicators for MARC fields?
<br><br>I've imported records and am editing them now. I'd like to have the indicators filled in, especially for titles so I can skip initial articles in the title sort.
<br><br>thanx.
<br>Lenora
<br><br>--
<br>***************************************
<br>Lenora A. Oftedahl, MLS MEPM
<br>StreamNet Regional Librarian
<br>Columbia River Inter-Tribal Fish Commission
<br>729 NE Oregon St, Ste 190
<br>Portland, OR 97232
<br>503-736-3581 / ARIEL: 207.173.155.8
<br>503-731-1260 FAX
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19919019&i=0" target="_top" rel="nofollow">OFTL@...</a> <a href="http://www.fishlib.org" target="_top" rel="nofollow">http://www.fishlib.org</a><br>*************************************
<br>"One by one, the penguins are stealing my sanity"
<br>**************************************
<br>"Don't worry about the world coming to an end today. It's already tomorrow in Australia."
<br> --(Charles Schultz)
<br>**************************************
<br>"The problem with adults is that they are contaminated by experience."
<br> --Kumi Naidoo, General Secretary and CEO of CIVICUS
<br>**************************************
<br><br>_______________________________________________
<br>Koha mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19919019&i=1" target="_top" rel="nofollow">Koha@...</a>
<br><a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_top" rel="nofollow">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br><p>From forum: <a href="http://www.nabble.com/Koha---Discuss-f14390.html" embed="fixTarget[14390]" target="_top" >Koha - Discuss</a></p>tag:www.nabble.com,2006:post-19938961Re: LDAP authentication -- getting closer.....2008-10-10T03:20:58Z2008-10-10T03:20:58ZHenri-Damien LAURENT-2<div dir="ltr">Hi,<br><div class="gmail_quote">2008/10/8 Scott Owen <span dir="ltr"><<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19938961&i=0" target="_top" rel="nofollow">sowen@...</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi all,<br>
<br>
I seem to be making some headway getting the LDAP authentication working<br>
betwixt Koha and Netware/NDS/LDAP.<br>
<br>
A quick glance at the two login attempts below , shows that a username<br>
(in my case "test") without the full NDS context will not authenticate<br>
and will generate a failed user/password combination.<br>
<br>
However, using a NDS fully qualified distinguished name (in my case<br>
cn=test,ou=students,o=SCHOOL) seems to generate a successful login ?<br>
(Sending operation result 0:"":"" to connection 0xa7684b60)<br>
But then dies later on ......(Duplicate entry 'cn=test,ou=stude')<br>
<br>
A quick peek at the borrowers in the Koha MySQL data base (CSV export)<br>
<br>
<br>
338 71582 FA ZA PINE AVENUE ALMA<br>
339 71583 BR AU PINE AVENUE ALMA<br>
340 44863 ED ZA PINE AVENUE ALMA<br>
</blockquote><div><br>Those entries Are really weird.<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">341 cn=41337,ou=stud<br>
342 cn=test,ou=stude<br>
343 71584 test test 123 happy lane alma<br>
<br>
<br>
Shows that my test users (test and 41337) are being added to the<br>
borrowers ???? (FA ZA etc...are truncated user lastnames, firstnames...I<br>
truncated them for this post)<br>
And that my LDAP attrib mapping in NDS are correct (the firstname,<br>
lastname address and city are all correct for my "test" user...but they<br>
are under a user named 71584.....I have no idea where this username came<br>
from....but I'm guessing it was automagically added (after the two real<br>
studend ID number of 71582 and 71583))<br>
<br>
So...I'm guessing that some playing with the LDAP section of the Auth.pm<br>
file may allow me to use just a used ID (41337) rather than the fully<br>
qualified distinguished name ??? Any Ideas on that ??<br>
</blockquote><div><br>afaict, it is trying to add two borrowers when one should be enough, and adding a borrower with LDAP database information. Maybe there is a problem with some doublequoted data, maybe a problem of parenthesis in your data.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
Any ideas on the Duplicate entry error ?? (or might this go away as<br>
soon as the logins are working properly ???)<br>
<br>
<br>
<br>
<br>
<br>
********************************<br>
Logging in as "test"<br>
<br>
<br>
--Intranet Error Log --<br>
New cleartext connection 0xa7684b60 from <a href="http://10.1.1.192:3081" target="_blank" rel="nofollow">10.1.1.192:3081</a>, monitor =<br>
0x259, index = 1<br>
DoBind on connection 0xa7684b60<br>
Bind name:test, version:3, authentication:simple<br>
Illegal ndsname "test" in ldap2uNDSDN, err = 34 (0x22)<br>
ldap2uNDSDN ldapDN = "test" - error 34 (0x22)<br>
Failed to convert LDAP DN "test" in nds_back_bind, err = 34 (0x22)<br>
Sending operation result 34:"":"" to connection 0xa7684b60<br>
Operation 0x1:0x60 on connection 0xa7684b60 completed in 0 seconds<br>
Monitor 0x259 found connection 0xa7684b60 socket closed, err = -5871, 0<br>
of 0 bytes read<br>
Monitor 0x259 initiating close for connection 0xa7684b60<br>
Server closing connection 0xa7684b60, socket error = -5871<br>
<br>
<br>
<br>
--DStrace Error Log--<br>
[Wed Oct 08 10:01:47 2008] [error] [client <a href="http://127.0.0.1" target="_blank" rel="nofollow">127.0.0.1</a>] LDAP Auth failed<br>
server not responding or wrong user password combination at<br>
c:/usr/koha229/intranet/modules/C4/Auth.pm line 528., referer:<br>
<a href="http://127.0.0.1:8000/cgi-bin/koha/mainpage.pl" target="_blank" rel="nofollow">http://127.0.0.1:8000/cgi-bin/koha/mainpage.pl</a><br>
<br>
<br>
*******************************************************<br>
<br>
<br>
Logging in as cn=test,ou=students,o=SCHOOL<br>
<br>
--Intranet Error Log --<br>
New cleartext connection 0xa7684b60 from <a href="http://10.1.1.192:3088" target="_blank" rel="nofollow">10.1.1.192:3088</a>, monitor =<br>
0x259, index = 1<br>
DoBind on connection 0xa7684b60<br>
Bind name:cn=test,ou=students,o=SCHOOL, version:3, authentication:simple<br>
Sending operation result 0:"":"" to connection 0xa7684b60<br>
Operation 0x1:0x60 on connection 0xa7684b60 completed in 0 seconds<br>
DoSearch on connection 0xa7684b60<br>
Search request:<br>
base: "OU=STUDENTS,O=SCHOOL"<br>
scope:2 dereference:2 sizelimit:0 timelimit:0 attrsonly:0<br>
filter: "(cn=cn=test,ou=students,o=SCHOOL)"<br>
no attributes<br>
Empty attribute list implies all user attributes<br>
Sending operation result 0:"":"" to connection 0xa7684b60<br>
Operation 0x2:0x63 on connection 0xa7684b60 completed in 0 seconds<br>
Monitor 0x259 found connection 0xa7684b60 socket closed, err = -5871, 0<br>
of 0 bytes read<br>
Monitor 0x259 initiating close for connection 0xa7684b60<br>
Server closing connection 0xa7684b60, socket error = -5871<br>
Connection 0xa7684b60 closed<br>
<br>
<br>
--DStrace Error Log--<br>
[Wed Oct 08 10:14:01 2008] [error] [client <a href="http://127.0.0.1" target="_blank" rel="nofollow">127.0.0.1</a>] DBD::mysql::st<br>
execute failed: Duplicate entry 'cn=test,ou=stude' for key 1 at<br>
c:/usr/koha229/intranet/modules/C4/Members.pm line 155., referer:<br>
<a href="http://127.0.0.1:8000/cgi-bin/koha/mainpage.pl" target="_blank" rel="nofollow">http://127.0.0.1:8000/cgi-bin/koha/mainpage.pl</a><br>
************************************************<br>
_______________________________________________<br>
Koha mailing list<br>
<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19938961&i=1" target="_top" rel="nofollow">Koha@...</a><br>
<a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_blank" rel="nofollow">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br>
</blockquote></div><br></div>
<br />_______________________________________________
<br>Koha mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19938961&i=2" target="_top" rel="nofollow">Koha@...</a>
<br><a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_top" rel="nofollow">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br><p>From forum: <a href="http://www.nabble.com/Koha---Discuss-f14390.html" embed="fixTarget[14390]" target="_top" >Koha - Discuss</a></p>tag:www.nabble.com,2006:post-19912977Re: RFC: Koha 3.2 : Mandate item-level circulation rules2008-10-09T23:57:23Z2008-10-09T23:57:23ZFrederic Demians<br>> 1: the item-level_itypes system preference be removed.
<br>> 2: biblioitems.itemtype be renamed to biblioitems.default_itemtype
<br>> 3: items.itype be renamed to items.itemtype
<br>> 4: all circulation parameters will be determined by items.itemtype.
<br>> 5: AddItem and ModItem will automatically fill items.itemtype from
<br>> biblioitems.default_itemtype if items.itemtype is not supplied.
<br><br>Don't forget an upgrade script to populate items.itemtype with
<br>biblioitems.itemtype if necessary.
<br><br>--
<br>Frédéric DEMIANS
<br><a href="http://www.tamil.fr/u/fdemians.html" target="_top" rel="nofollow">http://www.tamil.fr/u/fdemians.html</a><br>_______________________________________________
<br>Koha-devel mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19912977&i=0" target="_top" rel="nofollow">Koha-devel@...</a>
<br><a href="http://lists.koha.org/mailman/listinfo/koha-devel" target="_top" rel="nofollow">http://lists.koha.org/mailman/listinfo/koha-devel</a><br><p>From forum: <a href="http://www.nabble.com/Koha---Dev-f14381.html" embed="fixTarget[14381]" target="_top" >Koha - Dev</a></p>tag:www.nabble.com,2006:post-19912077Re: RFC: Koha 3.2 : Mandate item-level circulation rules2008-10-09T22:04:14Z2008-10-09T22:04:14ZJesse Weaver-2<div dir="ltr"><br><br><div class="gmail_quote">On Thu, Oct 9, 2008 at 2:57 PM, Ryan Higgins <span dir="ltr"><<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19912077&i=0" target="_top" rel="nofollow">ryan.higgins@...</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div dir="ltr"><br>[ this text also available at: <br><a href="http://wiki.koha.org/doku.php?id=en:development:rfcs3.2:rfc32_item_level_itemtypes" target="_blank" rel="nofollow">http://wiki.koha.org/doku.php?id=en:development:rfcs3.2:rfc32_item_level_itemtypes</a> ]<br>
<br>RFC: Koha 3.2<br><br>Mandate item-level circulation rules.<br><br>Currently we use the system preference item-level_itypes to indicate whether Koha<br>should use the itemtype stored at the bibliographic level or the item level to control <br>
circulation parameters. This seems to be one of the more significant distinctions in general policy<br>between US and French libraries, and was also one of the major limitations of Koha 2.x<br>in the eyes of US libraries.<br>
<br>Koha 3.0 offers the option to define your itemtypes at either the bib-level or item-level.<br>However, this option adds unnecessary complexity and offers an easy spot for bugs to <br>appear. I propose that this option be removed for the 3.2 release, and that steps be taken<br>
to make this feature-removal relatively painless and invisible for those libraries that do <br>maintain circulation policy at the bib level.<br><br>I propose the following:<br><br>1: the item-level_itypes system preference be removed.<br>
2: biblioitems.itemtype be renamed to biblioitems.default_itemtype<br>3: items.itype be renamed to items.itemtype<br>4: all circulation parameters will be determined by items.itemtype.<br>5: AddItem and ModItem will automatically fill items.itemtype from biblioitems.default_itemtype if items.itemtype is not supplied.<br>
<br>This should allow French (and others using bib-level circ rules) libraries to continue<br>with their current workflows, and should essentially be unnoticeable to them, while allowing<br>us to remove the bug-prone distinction of item/bib level itemtypes.<br>
<br>Comments and suggestions welcome.<br><br clear="all"><br>-- <br>Ryan Higgins<br><br>LibLime * Open-Source Solutions for Libraries<br>Featuring KohaZOOM ILS<br>888-564-2457 x704<br>
</div>
<br>_______________________________________________<br>
Koha-devel mailing list<br>
<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19912077&i=1" target="_top" rel="nofollow">Koha-devel@...</a><br>
<a href="http://lists.koha.org/mailman/listinfo/koha-devel" target="_blank" rel="nofollow">http://lists.koha.org/mailman/listinfo/koha-devel</a><br>
<br></blockquote></div><br>This sounds like an excellent way to reduce complexity, and addresses the complaints the cataloger at my library had with item-level_itypes.<br><br>+1<br clear="all"><br>-- <br>Jesse Weaver<br>
Software Developer, LibLime<br>
</div>
<br />_______________________________________________
<br>Koha-devel mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19912077&i=2" target="_top" rel="nofollow">Koha-devel@...</a>
<br><a href="http://lists.koha.org/mailman/listinfo/koha-devel" target="_top" rel="nofollow">http://lists.koha.org/mailman/listinfo/koha-devel</a><br><p>From forum: <a href="http://www.nabble.com/Koha---Dev-f14381.html" embed="fixTarget[14381]" target="_top" >Koha - Dev</a></p>tag:www.nabble.com,2006:post-19907245RFC: Koha 3.2 : Mandate item-level circulation rules2008-10-09T13:57:18Z2008-10-09T13:57:18ZRyan Higgins-2<div dir="ltr"><br>[ this text also available at: <br><a href="http://wiki.koha.org/doku.php?id=en:development:rfcs3.2:rfc32_item_level_itemtypes" target="_top" rel="nofollow">http://wiki.koha.org/doku.php?id=en:development:rfcs3.2:rfc32_item_level_itemtypes</a> ]<br>
<br>RFC: Koha 3.2<br><br>Mandate item-level circulation rules.<br><br>Currently we use the system preference item-level_itypes to indicate whether Koha<br>should use the itemtype stored at the bibliographic level or the item level to control <br>
circulation parameters. This seems to be one of the more significant distinctions in general policy<br>between US and French libraries, and was also one of the major limitations of Koha 2.x<br>in the eyes of US libraries.<br>
<br>Koha 3.0 offers the option to define your itemtypes at either the bib-level or item-level.<br>However, this option adds unnecessary complexity and offers an easy spot for bugs to <br>appear. I propose that this option be removed for the 3.2 release, and that steps be taken<br>
to make this feature-removal relatively painless and invisible for those libraries that do <br>maintain circulation policy at the bib level.<br><br>I propose the following:<br><br>1: the item-level_itypes system preference be removed.<br>
2: biblioitems.itemtype be renamed to biblioitems.default_itemtype<br>3: items.itype be renamed to items.itemtype<br>4: all circulation parameters will be determined by items.itemtype.<br>5: AddItem and ModItem will automatically fill items.itemtype from biblioitems.default_itemtype if items.itemtype is not supplied.<br>
<br>This should allow French (and others using bib-level circ rules) libraries to continue<br>with their current workflows, and should essentially be unnoticeable to them, while allowing<br>us to remove the bug-prone distinction of item/bib level itemtypes.<br>
<br>Comments and suggestions welcome.<br><br clear="all"><br>-- <br>Ryan Higgins<br><br>LibLime * Open-Source Solutions for Libraries<br>Featuring KohaZOOM ILS<br>888-564-2457 x704<br>
</div>
<br />_______________________________________________
<br>Koha-devel mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19907245&i=0" target="_top" rel="nofollow">Koha-devel@...</a>
<br><a href="http://lists.koha.org/mailman/listinfo/koha-devel" target="_top" rel="nofollow">http://lists.koha.org/mailman/listinfo/koha-devel</a><br><p>From forum: <a href="http://www.nabble.com/Koha---Dev-f14381.html" embed="fixTarget[14381]" target="_top" >Koha - Dev</a></p>tag:www.nabble.com,2006:post-19906217Re: Viewing logs2008-10-09T12:59:43Z2008-10-09T12:59:43ZBetsy Law...and maybe I should read the whole question: how to view the logs.
<br>The logs are just text files but you may need administrator privileges
<br>to open them. To look at a log in the terminal, open it with a text
<br>editor. Here's an example using the text editor nano to open the
<br>koha-error_log file:
<br><br>nano /var/log/koha/koha-error_log
<br><br>If you can't access the file, use sudo:
<br><br>sudo nano /var/log/koha/koha-error_log
<br><br>Then enter the superuser password. To see just the last few entries
<br>in the log, you can use the tail command:
<br><br>tail -f /var/log/koha/koha--error_log
<br><br>This command, with the -f option, will keep the log file open and
<br>append the newest entries to your display. Thus, you can dink around
<br>in Koha and see what errors are occurring where.
<br><br>Probably way more than you needed to know but since I had to learn all
<br>this stuff when I started I thought I'd throw it out there for other
<br>newbies.
<br><br>--Betsy
<br><br>On Thu, Oct 9, 2008 at 12:44 PM, Betsy Law <<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19906217&i=0" target="_top" rel="nofollow">betsy.law@...</a>> wrote:
<div class='shrinkable-quote'><br>> Koha logs are in /var/log/koha. The Apache logs at /var/log/apache2
<br>> are also useful for diagnosis.
<br>>
<br>> --Betsy
<br>>
<br>> On Thu, Oct 9, 2008 at 12:27 PM, Winter, James <<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19906217&i=1" target="_top" rel="nofollow">WinterJ@...</a>> wrote:
<br>>> This should be a quick one, and you'll have to excuse my ignorance. Koha is
<br>>> my first exposure to Perl.
<br>>>
<br>>>
<br>>>
<br>>> Where are the logs, and how do I view them?
<br>>>
<br>>>
<br>>>
<br>>> James Winter
<br>>>
<br>>> Arcadia University
<br>>>
<br>>> Systems Manager
<br>>>
<br>>> 215.517.2588
<br>>>
<br>>> <a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19906217&i=2" target="_top" rel="nofollow">winterj@...</a>
<br>>>
<br>>>
<br>>>
<br>>>
<br>>>
<br>>> _______________________________________________
<br>>> Koha mailing list
<br>>> <a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19906217&i=3" target="_top" rel="nofollow">Koha@...</a>
<br>>> <a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_top" rel="nofollow">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br>>>
<br>>>
<br>>
</div>_______________________________________________
<br>Koha mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19906217&i=4" target="_top" rel="nofollow">Koha@...</a>
<br><a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_top" rel="nofollow">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br><p>From forum: <a href="http://www.nabble.com/Koha---Discuss-f14390.html" embed="fixTarget[14390]" target="_top" >Koha - Discuss</a></p>tag:www.nabble.com,2006:post-19905973Re: Viewing logs2008-10-09T12:44:59Z2008-10-09T12:44:59ZBetsy LawKoha logs are in /var/log/koha. The Apache logs at /var/log/apache2
<br>are also useful for diagnosis.
<br><br>--Betsy
<br><br>On Thu, Oct 9, 2008 at 12:27 PM, Winter, James <<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19905973&i=0" target="_top" rel="nofollow">WinterJ@...</a>> wrote:
<div class='shrinkable-quote'><br>> This should be a quick one, and you'll have to excuse my ignorance. Koha is
<br>> my first exposure to Perl.
<br>>
<br>>
<br>>
<br>> Where are the logs, and how do I view them?
<br>>
<br>>
<br>>
<br>> James Winter
<br>>
<br>> Arcadia University
<br>>
<br>> Systems Manager
<br>>
<br>> 215.517.2588
<br>>
<br>> <a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19905973&i=1" target="_top" rel="nofollow">winterj@...</a>
<br>>
<br>>
<br>>
<br>>
<br>>
<br>> _______________________________________________
<br>> Koha mailing list
<br>> <a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19905973&i=2" target="_top" rel="nofollow">Koha@...</a>
<br>> <a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_top" rel="nofollow">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br>>
<br>>
</div>_______________________________________________
<br>Koha mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19905973&i=3" target="_top" rel="nofollow">Koha@...</a>
<br><a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_top" rel="nofollow">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br><p>From forum: <a href="http://www.nabble.com/Koha---Discuss-f14390.html" embed="fixTarget[14390]" target="_top" >Koha - Discuss</a></p>tag:www.nabble.com,2006:post-19905663Viewing logs2008-10-09T12:27:00Z2008-10-09T12:27:00ZWinter, James<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal>This should be a quick one, and you’ll have to excuse
my ignorance. Koha is my first exposure to Perl.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Where are the logs, and how do I view them? <o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><b><span style='font-size:12.0pt;font-family:"Adobe Garamond Pro","serif"'>James
Winter<o:p></o:p></span></b></p>
<p class=MsoNormal><b><i><span style='font-size:10.0pt;color:#C00000'><a href="http://www.arcadia.edu/" target="_top" rel="nofollow"><span style='color:#C00000;text-decoration:none'>Arcadia
University</span></a><o:p></o:p></span></i></b></p>
<p class=MsoNormal><span style='font-size:10.0pt'>Systems Manager<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt'>215.517.2588<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt'><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19905663&i=0" target="_top" rel="nofollow">winterj@...</a><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Lucida Sans Unicode","sans-serif"'> </span><o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>
<br />_______________________________________________
<br>Koha mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19905663&i=1" target="_top" rel="nofollow">Koha@...</a>
<br><a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_top" rel="nofollow">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br><p>From forum: <a href="http://www.nabble.com/Koha---Discuss-f14390.html" embed="fixTarget[14390]" target="_top" >Koha - Discuss</a></p>tag:www.nabble.com,2006:post-19904998Re: Advanced search2008-10-09T11:49:19Z2008-10-09T11:49:19ZBetsy LawDoesn't look like there is a solution yet. Here's the bug:
<br><br><a href="http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2599" target="_top" rel="nofollow">http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2599</a><br><br>--Betsy
<br><br>On Wed, Oct 8, 2008 at 1:42 PM, Winter, James <<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19904998&i=0" target="_top" rel="nofollow">WinterJ@...</a>> wrote:
<div class='shrinkable-quote'><br>> I've seen others are having this problem but it wasn't clear on whether or
<br>> not there was a solution.
<br>>
<br>>
<br>>
<br>> When I search by item type I always get zero results. I have authorized
<br>> values in the itype column in the items table, but not in the biblioitems
<br>> itemtype column. I added some manually to that column and still couldn't
<br>> search by type.
<br>>
<br>>
<br>>
<br>> Is this a known bug, and is there a workaround?
<br>>
<br>>
<br>>
<br>> Thanks.
<br>>
<br>>
<br>>
<br>> James Winter
<br>>
<br>> Arcadia University
<br>>
<br>> Systems Manager
<br>>
<br>> 215.517.2588
<br>>
<br>> <a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19904998&i=1" target="_top" rel="nofollow">winterj@...</a>
<br>>
<br>>
<br>>
<br>>
<br>>
<br>> _______________________________________________
<br>> Koha mailing list
<br>> <a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19904998&i=2" target="_top" rel="nofollow">Koha@...</a>
<br>> <a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_top" rel="nofollow">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br>>
<br>>
</div>_______________________________________________
<br>Koha mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19904998&i=3" target="_top" rel="nofollow">Koha@...</a>
<br><a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_top" rel="nofollow">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br><p>From forum: <a href="http://www.nabble.com/Koha---Discuss-f14390.html" embed="fixTarget[14390]" target="_top" >Koha - Discuss</a></p>tag:www.nabble.com,2006:post-19904788Authority Control RFC2008-10-09T11:37:33Z2008-10-09T11:37:33ZBrian Harrington-3I was reading over the RFC for authority control enhancements in 3.2,
<br>and they look like great changes that we would love to see. I do have
<br>a quick question though. Will there be any provision for preserving
<br>local changes in an authority record when merging the imports. Maybe
<br>something as simple as preserving fields that have a subfield 5?
<br><br>Thanks,
<br><br>Brian
<br><br>--
<br>Brian Harrington
<br>Content and Resource Development Coordinator
<br>Project MUSE
<br>The Johns Hopkins University Press
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19904788&i=0" target="_top" rel="nofollow">brian@...</a>
<br>_______________________________________________
<br>Koha-devel mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19904788&i=1" target="_top" rel="nofollow">Koha-devel@...</a>
<br><a href="http://lists.koha.org/mailman/listinfo/koha-devel" target="_top" rel="nofollow">http://lists.koha.org/mailman/listinfo/koha-devel</a><br><p>From forum: <a href="http://www.nabble.com/Koha---Dev-f14381.html" embed="fixTarget[14381]" target="_top" >Koha - Dev</a></p>tag:www.nabble.com,2006:post-19904460Re: Koha 3.0 and LDAP2008-10-09T11:19:22Z2008-10-09T11:19:22ZWinter, JamesI changed the actual hostname to abc. I did figure out that I didn't have the ldapserver section within the config section of koha-conf.xml, so that part is "working." I'm still trying to figure out how to set up the mapping correctly.
<br><br>I forgot to mention I'm trying to use this with Active Directory. Has anyone setup this mapping yet to work with Active Directory?
<br><br>James Winter
<br>Arcadia University
<br>Systems Manager
<br>215.517.2588
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19904460&i=0" target="_top" rel="nofollow">winterj@...</a>
<br>
<br><br>-----Original Message-----
<br>From: mourik jan c heupink [mailto:<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19904460&i=1" target="_top" rel="nofollow">heupink@...</a>]
<br>Sent: Thursday, October 09, 2008 2:11 PM
<br>To: Winter, James
<br>Cc: <a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19904460&i=2" target="_top" rel="nofollow">koha@...</a>
<br>Subject: Re: [Koha] Koha 3.0 and LDAP
<br><br>Hi,
<br><br>Note: I'm not yet running koha 3.
<br><br>> No "ldapserver" in server hash from KOHA_CONF: /etc/koha/koha-conf.xml
<br>> at /usr/share/perl/5.8/CGI/Carp.pm line 314, <DATA> line 275.
<br>> <ldapserver id="ldapserver" listenref="ldapserver">
<br>>
<br>> <hostname>abc</hostname>
<br>Is abc really your ldapserver hostname? You may want to test with a
<br>fully qualified hostname, or an ip address, maybe that works?
<br><br>Hope that helps,
<br>mj
<br>_______________________________________________
<br>Koha mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19904460&i=3" target="_top" rel="nofollow">Koha@...</a>
<br><a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_top" rel="nofollow">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br><p>From forum: <a href="http://www.nabble.com/Koha---Discuss-f14390.html" embed="fixTarget[14390]" target="_top" >Koha - Discuss</a></p>tag:www.nabble.com,2006:post-19904410Re: Koha 3.0 and LDAP2008-10-09T11:10:57Z2008-10-09T11:10:57Zmourik jan c heupink-2Hi,
<br><br>Note: I'm not yet running koha 3.
<br><br>> No "ldapserver" in server hash from KOHA_CONF: /etc/koha/koha-conf.xml
<br>> at /usr/share/perl/5.8/CGI/Carp.pm line 314, <DATA> line 275.
<br>> <ldapserver id="ldapserver" listenref="ldapserver">
<br>>
<br>> <hostname>abc</hostname>
<br>Is abc really your ldapserver hostname? You may want to test with a
<br>fully qualified hostname, or an ip address, maybe that works?
<br><br>Hope that helps,
<br>mj
<br>_______________________________________________
<br>Koha mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19904410&i=0" target="_top" rel="nofollow">Koha@...</a>
<br><a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_top" rel="nofollow">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br><p>From forum: <a href="http://www.nabble.com/Koha---Discuss-f14390.html" embed="fixTarget[14390]" target="_top" >Koha - Discuss</a></p>tag:www.nabble.com,2006:post-19903283Re: Problem in /koha/members/memberentry.pl?2008-10-09T10:10:23Z2008-10-09T10:10:23ZOwen Leonard-4<div class='shrinkable-quote'>> After reading the code, only one of the three e-mail adresses asked in
<br>> this form is saved :
<br>> "
<br>> elsif ($newdata{email} =~ /\w\@\w/) {
<br>> $emailaddr = $newdata{email}
<br>> }
<br>> elsif ($newdata{emailpro} =~ /\w\@\w/) {
<br>> $emailaddr = $newdata{emailpro}
<br>> }
<br>> elsif ($newdata{B_email} =~ /\w\@\w/) {
<br>> $emailaddr = $newdata{B_email}
<br>> }
</div><br>The section you quote isn't related to saving any data, it's related
<br>to Koha sending an automated email that can be sent to newly
<br>registered patrons. That if...elsif block is looking for a valid email
<br>address to use.
<br><br>It's true there are three email addresses in the patron entry form,
<br>but each is different. At least in the English translation, email is
<br>"Home email," emailpro is "Work email," and B_email is the email
<br>address under "Alternate address." All are saved successfully to the
<br>database in my tests.
<br><br>> And there are more than one B_email input in the form (cf : Alternate
<br>> address).
<br><br>I don't find this to be the case.
<br><br> -- Owen
<br><br>--
<br>Web Developer
<br>Athens County Public Libraries
<br><a href="http://www.myacpl.org" target="_top" rel="nofollow">http://www.myacpl.org</a><br>_______________________________________________
<br>Koha-devel mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19903283&i=0" target="_top" rel="nofollow">Koha-devel@...</a>
<br><a href="http://lists.koha.org/mailman/listinfo/koha-devel" target="_top" rel="nofollow">http://lists.koha.org/mailman/listinfo/koha-devel</a><br><p>From forum: <a href="http://www.nabble.com/Koha---Dev-f14381.html" embed="fixTarget[14381]" target="_top" >Koha - Dev</a></p>tag:www.nabble.com,2006:post-19902186Koha 3.0 and LDAP2008-10-09T09:10:27Z2008-10-09T09:10:27ZWinter, James<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal>In trying to get LDAP authentication working with Koha 3.0,
I’m coming across the following error when loading the OPAC page:<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>No
"ldapserver" in server hash from KOHA_CONF: /etc/koha/koha-conf.xml
at /usr/share/perl/5.8/CGI/Carp.pm line 314, <DATA> line 275.<o:p></o:p></span></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Is this indicating that the LDAP connection is failing, or
that my koha-conf.xml isn’t configured correctly? This is my LDAP config
section:<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><ldapserver id="ldapserver"
listenref="ldapserver"><o:p></o:p></p>
<p class=MsoNormal> <hostname>abc</hostname><o:p></o:p></p>
<p class=MsoNormal> <base>dc=abc,dc=domain,dc=com</base><o:p></o:p></p>
<p class=MsoNormal> <replicate>1</replicate> <!--
add new users from LDAP to Koha database --><o:p></o:p></p>
<p class=MsoNormal> <update>1</update> <!--
update existing users in Koha database --><o:p></o:p></p>
<p class=MsoNormal> <mapping> <!-- match
koha SQL field names to your LDAP record field names --><o:p></o:p></p>
<p class=MsoNormal> <firstname is="givenname"
></firstname><o:p></o:p></p>
<p class=MsoNormal> <surname is="sn"
></surname><o:p></o:p></p>
<p class=MsoNormal> <address is="postaladdress"
></address><o:p></o:p></p>
<p class=MsoNormal> <city is="l"
>Athens, OH</city><o:p></o:p></p>
<p class=MsoNormal> <zipcode is="postalcode"
></zipcode><o:p></o:p></p>
<p class=MsoNormal> <branchcode is="branch" >MAIN</branchcode><o:p></o:p></p>
<p class=MsoNormal> <userid is="uid"
></userid><o:p></o:p></p>
<p class=MsoNormal> <password is="userpassword"
></password><o:p></o:p></p>
<p class=MsoNormal> <email is="mail"
></email><o:p></o:p></p>
<p class=MsoNormal> <categorycode is="employeetype"
>PT</categorycode><o:p></o:p></p>
<p class=MsoNormal> <phone
is="telephonenumber"></phone><o:p></o:p></p>
<p class=MsoNormal> </mapping><o:p></o:p></p>
<p class=MsoNormal> </ldapserver><o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Thanks for any insight into this.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><b><span style='font-size:12.0pt;font-family:"Adobe Garamond Pro","serif"'>James
Winter<o:p></o:p></span></b></p>
<p class=MsoNormal><b><i><span style='font-size:10.0pt;color:#C00000'><a href="http://www.arcadia.edu/" target="_top" rel="nofollow"><span style='color:#C00000;text-decoration:none'>Arcadia
University</span></a><o:p></o:p></span></i></b></p>
<p class=MsoNormal><span style='font-size:10.0pt'>Systems Manager<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt'>215.517.2588<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt'><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19902186&i=0" target="_top" rel="nofollow">winterj@...</a><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Lucida Sans Unicode","sans-serif"'> </span><o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>
<br />_______________________________________________
<br>Koha mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19902186&i=1" target="_top" rel="nofollow">Koha@...</a>
<br><a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_top" rel="nofollow">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br><p>From forum: <a href="http://www.nabble.com/Koha---Discuss-f14390.html" embed="fixTarget[14390]" target="_top" >Koha - Discuss</a></p>tag:www.nabble.com,2006:post-19901195Problem in /koha/members/memberentry.pl?2008-10-09T04:42:53Z2008-10-09T04:42:53ZNahuel ANGELINETTI-5Hi,
<br><br>An user of intranet ask me why there is two "E-mail (home):" input
<br>in /koha/members/memberentry.pl.
<br>After reading the code, only one of the three e-mail adresses asked in
<br>this form is saved :
<br>"
<br>elsif ($newdata{email} =~ /\w\@\w/) {
<br> $emailaddr = $newdata{email}
<br>}
<br>elsif ($newdata{emailpro} =~ /\w\@\w/) {
<br> $emailaddr = $newdata{emailpro}
<br>}
<br>elsif ($newdata{B_email} =~ /\w\@\w/) {
<br> $emailaddr = $newdata{B_email}
<br>}
<br>"
<br><br>Can you tell me why 3 e-mails are asked(with a duplicate input) and
<br>only one is saved?
<br>Why there is no asked only one e-mail? The member can choose which one
<br>he want to give.
<br><br>And there are more than one B_email input in the form (cf : Alternate
<br>address).
<br><br>I think it's strange to ask too much informations and keep only a bit.
<br><br>Regards,
<br>--
<br>Nahuel ANGELINETTI
<br>_______________________________________________
<br>Koha-devel mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19901195&i=0" target="_top" rel="nofollow">Koha-devel@...</a>
<br><a href="http://lists.koha.org/mailman/listinfo/koha-devel" target="_top" rel="nofollow">http://lists.koha.org/mailman/listinfo/koha-devel</a><br><p>From forum: <a href="http://www.nabble.com/Koha---Dev-f14381.html" embed="fixTarget[14381]" target="_top" >Koha - Dev</a></p>tag:www.nabble.com,2006:post-19890421Re: Holds Waiting to Be Pulled2008-10-08T17:58:50Z2008-10-08T17:58:50ZKathy Rippel<html>
<body>
I don't have an answer; but we agree with you wholeheartedly. This and
the fact that holds show up as "Available" in the OPAC unless
checked out are two of the serious issues about holds that need to be
addressed.<br><br>
Kathy<br><br>
At 05:38 PM 10/8/2008, Fooled One wrote:<br>
<blockquote type=cite class=cite cite="">Koha version
<a href="http://3.01.00.002" target="_top" rel="nofollow">3.01.00.002</a><br>
Debian Etch<br>
Perl version 5.008008<br>
MySQL version 5.0.32<br>
Apache version 2.2.3<br><br>
The "Holds Awaiting Pickup" and "Holds to Pull"
circulation reports do not show a list of items that are placed by
patrons from home that are already available in the library. The
"Holds Awaiting Pickup" report does seem to show a list of
items if they have been on hold while the item was checked out to another
patron and that patron just check it back in. <br><br>
The lack of "Holds to Pull" reporting is an important issue
because librarians need to know what items need to be pulled off the
shelf when a patron places a hold - even if the item is already
available.<br><br>
I have my preferences set to:<br><br>
AllowOnShelfHolds: ON<br><br>
emailLibrarianWhenHoldsPlaced: ON (though this does not work
either)<br><br>
Any thoughts on how to fix this this? Is there a job that needs to be
running? Am I just missing something?<br>
_______________________________________________<br>
Koha mailing list<br>
<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19890421&i=0" target="_top" rel="nofollow">Koha@...</a><br>
<a href="http://lists.katipo.co.nz/mailman/listinfo/koha" eudora="autourl" target="_top" rel="nofollow">
http://lists.katipo.co.nz/mailman/listinfo/koha</a></blockquote></body>
<br>
<body>
<font face="Comic Sans MS" size=2>Kathleen D. Rippel<br>
Pathfinder Central, Manager<br>
Central Kansas Library System<br>
1409 Williams<br>
Great Bend, KS 67530<br><br>
(620-792-4865) phone<br>
(800-362-2642) toll-free, KS<br>
(620-792-5495) fax<br><br>
<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19890421&i=1" target="_top" rel="nofollow">kdr@...</a></font></body>
</html>
<br />_______________________________________________
<br>Koha mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19890421&i=2" target="_top" rel="nofollow">Koha@...</a>
<br><a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_top" rel="nofollow">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br><p>From forum: <a href="http://www.nabble.com/Koha---Discuss-f14390.html" embed="fixTarget[14390]" target="_top" >Koha - Discuss</a></p>tag:www.nabble.com,2006:post-19888989Holds Waiting to Be Pulled2008-10-08T15:38:15Z2008-10-08T15:38:15ZFooled One<div dir="ltr">Koha version <a href="http://3.01.00.002" target="_top" rel="nofollow">3.01.00.002</a><br>Debian Etch<br>Perl version 5.008008<br>MySQL version 5.0.32<br>Apache version 2.2.3<br><br>The "Holds Awaiting Pickup" and "Holds to Pull" circulation reports do not show a list of items that are placed by patrons from home that are already available in the library. The "Holds Awaiting Pickup" report does seem to show a list of items if they have been on hold while the item was checked out to another patron and that patron just check it back in. <br>
<br>The lack of "Holds to Pull" reporting is an important issue because librarians need to know what items need to be pulled off the shelf when a patron places a hold - even if the item is already available.<br>
<br>I have my preferences set to:<br><br>AllowOnShelfHolds: ON<br><br>emailLibrarianWhenHoldsPlaced: ON (though this does not work either)<br><br>Any thoughts on how to fix this this? Is there a job that needs to be running? Am I just missing something?<br>
</div>
<br />_______________________________________________
<br>Koha mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19888989&i=0" target="_top" rel="nofollow">Koha@...</a>
<br><a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_top" rel="nofollow">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br><p>From forum: <a href="http://www.nabble.com/Koha---Discuss-f14390.html" embed="fixTarget[14390]" target="_top" >Koha - Discuss</a></p>tag:www.nabble.com,2006:post-19887202Advanced search2008-10-08T13:42:21Z2008-10-08T13:42:21ZWinter, James<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal>I’ve seen others are having this problem but it wasn’t
clear on whether or not there was a solution.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>When I search by item type I always get zero results. I have
authorized values in the itype column in the items table, but not in the
biblioitems itemtype column. I added some manually to that column and still
couldn’t search by type.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Is this a known bug, and is there a workaround?<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Thanks.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><b><span style='font-size:12.0pt;font-family:"Adobe Garamond Pro","serif"'>James
Winter<o:p></o:p></span></b></p>
<p class=MsoNormal><b><i><span style='font-size:10.0pt;color:#C00000'><a href="http://www.arcadia.edu/" target="_top" rel="nofollow"><span style='color:#C00000;text-decoration:none'>Arcadia
University</span></a><o:p></o:p></span></i></b></p>
<p class=MsoNormal><span style='font-size:10.0pt'>Systems Manager<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt'>215.517.2588<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt'><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19887202&i=0" target="_top" rel="nofollow">winterj@...</a><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Lucida Sans Unicode","sans-serif"'> </span><o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>
<br />_______________________________________________
<br>Koha mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19887202&i=1" target="_top" rel="nofollow">Koha@...</a>
<br><a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_top" rel="nofollow">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br><p>From forum: <a href="http://www.nabble.com/Koha---Discuss-f14390.html" embed="fixTarget[14390]" target="_top" >Koha - Discuss</a></p>tag:www.nabble.com,2006:post-19884637Re: error in opac-sendbasket.pl2008-10-08T11:28:40Z2008-10-08T11:28:40ZJoe Atzberger<div dir="ltr">This is almost surely a problem with UTF-8 handling. The error line is:<br><br><div style="margin-left: 40px;">my $isofile = encode_base64($iso2709);<br></div><br>From perldoc MIME::Base64:<br><br>"The string passed to encode_base64() contains characters with code above 255. The base64 encoding is only defined for single-byte characters. Use the Encode module to select the byte encoding you want."<br>
<br>And, specifically, regarding the error seen:<br><br>"Wide character in subroutine entry: The string passed to encode_base64() contains characters with code above 255. The base64 encoding is only defined for single-byte characters. Use the Encode module to select the byte encoding you want.... Perl v5.8 and better allow extended Unicode characters in strings. Such strings cannot be encoded directly, as the base64 encoding is only defined for single-byte characters. The solution is to use the Encode module to select the byte encoding you want. For example:"<br>
<br> use MIME::Base64 qw(encode_base64);<br> use Encode qw(encode);<br> $encoded = encode_base64(encode("UTF-8", "\x{FFFF}\n"));<br> print $encoded;"<br><br>
I will send a patch for review that attempts to follow this methodology.<br><br>--Joe Atzberger,<br>LibLime<br><br><div class="gmail_quote">On Wed, Oct 8, 2008 at 5:57 AM, Basu Talikoti <span dir="ltr"><<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19884637&i=0" target="_top" rel="nofollow">basudpl@...</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div dir="ltr"><h1>hi all</h1>
<div>we are using centos operating system and koha 3, when you send list of book through email saved in basket, it give the following error kindly help in resolving the problem.</div>
<h1>Koha error</h1>
<p>The following fatal error has occurred:</p><pre><code>Wide character in subroutine entry at /usr/share/koha/opac/cgi-bin/opac/opac-sendbasket.pl line 132.
</code></pre>
<table>
<tbody>
<tr>
<th>Apache</th>
<td>Server version: Apache/2.2.3 Server built: Jan 15 2008 20:33:30 </td></tr>
<tr>
<th>Koha</th>
<td><a href="http://3.00.00.107" target="_blank" rel="nofollow">3.00.00.107</a></td></tr>
<tr>
<th>Koha DB</th>
<td>3.0000107</td></tr>
<tr>
<th>MySQL</th>
<td>mysql Ver 14.12 Distrib 5.0.45, for redhat-linux-gnu (i686) using readline 5.0 </td></tr>
<tr>
<th>OS</th>
<td>Linux <a href="http://dplcat.com" target="_blank" rel="nofollow">dplcat.com</a> 2.6.18-92.el5PAE #1 SMP Tue Jun 10 19:22:41 EDT 2008 i686 i686 i386 GNU/Linux </td></tr>
<tr>
<th>Perl</th>
<td>
<div>5.008008</div>
<div> </div>
<div> </div>
<div> </div>
<div>with regard</div>
<div>basu</div>
<div> </div></td></tr></tbody></table></div>
<br>_______________________________________________<br>
Koha mailing list<br>
<a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19884637&i=1" target="_top" rel="nofollow">Koha@...</a><br>
<a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_blank" rel="nofollow">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br>
<br></blockquote></div><br></div>
<br />_______________________________________________
<br>Koha mailing list
<br><a href="http://www.nabble.com/user/SendEmail.jtp?type=post&post=19884637&i=2" target="_top" rel="nofollow">Koha@...</a>
<br><a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_top" rel="nofollow">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br><p>From forum: <a href="http://www.nabble.com/Koha---Discuss-f14390.html" embed="fixTarget[14390]" target="_top" >Koha - Discuss</a></p>tag:www.nabble.com,2006:post-19883934LDAP authentication -- getting closer.....