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

Koha3.0 against Active Directory
by Library Guy 27 Oct '08

27 Oct '08

> > On Fri, Sep 26, 2008 at 09:17:13AM -0600, Michael Hafen wrote: > >* that Active Directory does not have the attribute auth_with_ldap.pm is > *>* looking for to compare to the user entered password. > * > this can be set with xpath /ldapserver/mapping/password at is <http://lists.koha.org/mailman/listinfo/koha-devel> but it will > fail because you can't compare a clear text with an AD encrypted passwd! > > >* problem is that auth_with_ldap.pm expects an attribute with password > *>* stored in the plain, > * > i don't think so! can you imagine a password stored in plain in a modern > > and secure system? i think that the current code expect that the plain > text used for comparaison will be encrypted by the server. > > >* $db->unbind; > *>* $db->disconnect(); > *>* $db = Net::LDAP->new( [$prefhost] ); > * > why unbind ? you'll loose the benefit of mod_ldap cached data. > > $dbuser = Net::LDAP->new( [$prefhost] ); > > >* $res = $db->bind( $userldapentry, password = $password ); > * > password = $password will fail as perl vars begins with $ sigil! > > $res = $db->bind( $userldapentry, password => $password ); > > works better > > > regards > > marc > > so what would the suggested final mod look like if the current auth section of Auth_with_ldap.pm is: sub checkpw_ldap { my ($dbh, $userid, $password) = @_; my $db = Net::LDAP->new([$prefhost]); #$debug and $db->debug(5); my $uid_field = $mapping{userid}->{is} or die ldapserver_error("mapping for 'userid'"); my $filter = Net::LDAP::Filter->new("$uid_field=$userid") or die "Failed to create new Net::LDAP::Filter"; my $res = ($config{anonymous}) ? $db->bind : $db->bind($ldapname, password=>$ldappassword); if ($res->code) { # connection refused warn "LDAP bind failed as $ldapname: " . description($res); return 0; }

3 4

Re: [Koha-devel] bulkmarcimport and jacket cover images (Jesse Weaver)
by Nicholas van Oudtshoorn 25 Oct '08

25 Oct '08

What about the Google Books Jackets API? Does that work okay with 13 digit isbns? (Oh, and on this, I've got a patch lying around somewhere to combine Amazon and Google Jackets in the OPAC so that only one picture is shown - the Google picture if there is one, the amazon picture [including the "no image" picture] otherwise. Any interest in this?) Nicholas van Oudtshoorn Perth Bible College library.pbc.wa.edu.au koha-devel-request(a)lists.koha.org wrote: > Cover images in koha work through the 10-digit ISBN. Koha uses images from > Amazon. > > If you have any books that only have 13-digit ISBNs, they will_not_ have a > cover image at this time; this is a known problem with the Amazon API. >

1 0

bulkmarcimport and jacket cover images
by zang＠zang.co.za 24 Oct '08

24 Oct '08

Is it possible to 'import' the cover images with the bulkmarcimport utility? The cover image shows 100% with z39.50 import. I will appreciate more info on how this meganism works? Thanks!

2 1

RFC: New System Preference to Determine which 'Types' and associated icons to display in advanced Search
by Joshua Ferraro 24 Oct '08

24 Oct '08

Hi all, It seems like every library has a different definition of what they want to display as 'Type' limits in the advanced search area. The API is currently flexible to support any defined indexes, but customizing this beyond the default itemtypes currently requires editing of the advsearch.tmpl templates -- not horrible, but still kinda annoying. I propose a new syspref that allows the user to specify either 'itemtypes' (default) or any codes from authorised_values to be the limits in place of itemtypes (so for example, ccode). This would allow every library to define their own authorised-values, and then use those as search limits in advsearch.tmpl, without any template modifications. It's a fairly trivial addition, and if we default to itemtypes, won't affect any existing Koha installations. Thoughts? Cheers, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE CEO migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf(a)liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS

4 4

Two Koha intranets
by Karen Myers 24 Oct '08

24 Oct '08

Hi I am wondering if it possible to have two Koha Intranets running at the same time on different computers as we have two cataloguers needing to catalogue at the same time. Also, can anyone point me to any information regarding getting your Koha LMS available via the Internet? Or any companies that provide this kind of service? cheers Karen Myers _________________________________________________________________ _______________________________________________ Koha-devel mailing list Koha-devel(a)nongnu.org http://lists.nongnu.org/mailman/listinfo/koha-devel

2 1

"Till Reconciliation" Report
by Joe Atzberger 23 Oct '08

23 Oct '08

Besides the security hole I just patched, I think the "Till Reconciliation" report in 3.x has other serious deficiencies, mostly related to simplistic structure underlying fines. If it seems unfamiliar, it should be. I commented it out of the interface just before the 3.0 release when I started to realize the problems with it, but the report script itself was still there. Recently some of our clients found it and started trying to use it. So here's my argument that it should be removed outright. The branch of the fine payment transaction does not exist in the accountlines table. No provisions to record that information exist. Even if branchcode were recorded it would not be effective as a real P.O.S. reconciliation report, because it wouldn't differentiate between any of the various stations in the same branch. Here's the part I really don't like. In the retail world a "Till Reconciliation" report is used daily to balance out a cash drawer and total up the day's transactions before an evening deposit. This is the type of "evidence" used to fire someone when their register comes up short. The report as it stands, despite appearances, is totally useless for that purpose and should not be attributed any authority at all. Basically, Koha does not have 1-to-1 assurances for the physical location or uniqueness of the remote user, system or branch. Koha does not establish the identity of remote systems, only the remote user. In that sense it is a web application, and not a P.O.S. system. It doesn't care where on the Internet you are, as long as you remember your login. We can have multiple terminals on the same IP, mutliple browsers on the same system, the same system on multiple IPs, the same user on multiple sessions, etc. In short, we don't know what "till" any payment went to, and as it stands we don't even know what branch. IP level filtering can be used to restrict access to known networks, but that is not tracked by any internal logic. Adding the branch and operator to fine transactions, and outputting it is relatively modest refinement compared to making that data verifiable. None of the fines enhancement LibLime is currently discussing include establishing the remote system identity in a truly auditable way (like, say, client-side certificates). Please keep in mind I support the idea/workflow of this report, I just think that we cannot allow the current implementation to be mistaken for valid. Any complaints about removing it until fines is overhauled, comments or considerations? --Joe Atzberger, LibLime

1 0

itiwm Jonny wants to chat
by itiwm Jonny 23 Oct '08

23 Oct '08

----------------------------------------------------------------------- itiwm Jonny wants to stay in better touch using some of Google's coolest new products. If you already have Gmail or Google Talk, visit: http://mail.google.com/mail/b-a0940ec1ca-4c8aaad9c5-110523522bdae39e You'll need to click this link to be able to chat with itiwm Jonny. To get Gmail - a free email account from Google with over 2,800 megabytes of storage - and chat with itiwm Jonny, visit: http://mail.google.com/mail/a-a0940ec1ca-4c8aaad9c5-216c7ab9bd Gmail offers: - Instant messaging right inside Gmail - Powerful spam protection - Built-in search for finding your messages and a helpful way of organizing emails into "conversations" - No pop-up ads or untargeted banners - just text ads and related information that are relevant to the content of your messages All this, and its yours for free. But wait, there's more! By opening a Gmail account, you also get access to Google Talk, Google's instant messaging service: http://www.google.com/talk/ Google Talk offers: - Web-based chat that you can use anywhere, without a download - A contact list that's synchronized with your Gmail account - Free, high quality PC-to-PC voice calls when you download the Google Talk client Gmail and Google Talk are still in beta. We're working hard to add new features and make improvements, so we might also ask for your comments and suggestions periodically. We appreciate your help in making our products even better! Thanks, The Google Team To learn more about Gmail and Google Talk, visit: http://mail.google.com/mail/help/about.html http://www.google.com/talk/about.html (If clicking the URLs in this message does not work, copy and paste them into the address bar of your browser).

1 0

Patron attributes tables
by Owen Leonard 23 Oct '08

23 Oct '08

I was looking at the new "Additional attributes and identifiers" feature and have some questions about the table structure. I was curious why "Patron attribute type code" is not editable. I see that in the borrower_attribute_types table there is no unique numeric id, just the "code": borrower_attribute_types +--------+--------------------------------------------+ | code | description | +--------+--------------------------------------------+ | pet | The patron's pets | | school | A student patron's educational institution | +--------+--------------------------------------------+ And in the borrower_attributes table, each line for that particular code has to repeat the value of "code:" borrower_attributes +----------------+--------+-----------------+----------+ | borrowernumber | code | attribute | password | +----------------+--------+-----------------+----------+ | 51 | school | Ohio University | NULL | | 52 | pet | Chappie | NULL | | 52 | pet | Ivy | NULL | | 52 | pet | Rascal | NULL | +----------------+--------+-----------------+----------+ I would think there should be an auto-incrementing numeric id in the borrower_attribute_types table for each code which would get entered into the borrower_attributes table. Then you could freely edit "code"'s value without having to worry about updating every line in borrower_attributes. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org

2 4

Introduction
by Allen Reinmeyer 22 Oct '08

22 Oct '08

Hello All, Just wanted to quickly introduce myself, now that I'm got my first patch submitted to Koha (Bug #2030). You can find me either on gtalk with the above email or on IRC as areinmeyer. I look forward to working and conversing with everyone in the near future. -- Allen Reinmeyer LibLime p. 770-888-9743

1 0

RFC 3.2 - general hold request changes
by Galen Charlton 22 Oct '08

22 Oct '08

Hi, I've already sent out a couple of RFCs about hold requests and friends, and will be sending out some more that relate to specific customer projects for LibLime, but I wanted to toss out a few ideas for general improvement. A large number of bugs have been turned up recently, most of which were postponed to 3.2, so I think the module is in need of some attention beyond the specific enhancements to be proposed. First, the reserves table needs at least one more column to handle item-level requests properly. Right now, reserves.itemnumber serves two purposes: (a) identifying the requested item if the hold is item-level and (b) identifying the item selected to fill a title-level request. This is a problem because it can be hard to distinguish between bib- and item-level requests, and impossible to do so once the request is filled and the item is waiting on the hold shelf. I propose to replace reserves.itemnumber with two columns: requested_itemnumber (NULL for bib-level requests, non-NULL otherwise) supplied_itemnumber (non-NULL once the request is filled) During a version upgrade, the value of reserves.itemnumber would be moved to requested_itemnumber if the priority > 0, and to supplied_itemnumber if the priority is 0. This is not a perfect heuristic, as a filled item-level request should set both columns, but I'm not sure we can do much better. Second, i think the reserveconstraints table needs to be removed. It appears to date to a time when a biblio could have more than one bilbioitem, but now that the relationship is one-to-one, it cannot serve its original purpose of limiting a request to only specific formats attached to a bib. Removing reserveconstraints would leave Koha supporting bib-level and item-level requests. If something in between bib-level and item-level is still needed, I suppose that it would have to be based on selecting which item types are suitable for filling a request on a given bib - for example, if the library attaches codex and audiobook items to the same bib and gives them different item types, reservecontraints (or its successor) might contain a list of item types. Third, since larger Koha libraries can have hold request queues a couple hundred patrons long or longer, I'm going to experiment with ways of managing the priority value so that it is possible to fill hold requests without having to touch every request in the queue, both to aid performance and to possibly avoid bugs where multiple requests for a given bib have the same priority. Fourth, I want to add an auto_increment reserve_id column to reserves to give us an opaque request ID to simplify FK relationships with tables such as the successor to reserveconstraints and additional tables that we may need as we extend the request system to handle recalls and other types of requests. Fifth, I want to do some work with C4::Reserves to cleanup the FIXMEs, improve the POD, and add functions to separate handling when items can be requested versus when they are available to fill hold requests. Regards, Galen -- Galen Charlton VP, Research & Development, LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709 skype: gmcharlt

2 1