[Koha-devel] [Fwd: Re: Some Info on KOHA]

[Roger Buck]

> From: Rosalie Blake <rosalie at library.org.nz>
> To: Olugbenga Adara <gbengaadara at yahoo.com>
> Cc: chris Cormack <chris at katipo.co.nz>

[--snip--]

> > 3. The library intends to start computerisation by
> > only using the opac - allowing patrons to search for
> > books. Could Koha function (OPAC) without patron
> > information?
> I think so, although it will not be able to report
> on whether an item is on issue or available for borrowing.

What we have:
 Three levels of access:

 1. OPAC browse only - anyone can access catalogue for search only.

 2. OPAC browse and request only - Members must log in using personal
username and password. Users can register on-line and make on-line
requests. Details of all requests are recorded in database and email
notification sent to library admins (including details such as graphical
and alphanumeric barcodes, hot links to user accounts, current request
lists etc. If you don't want to use swipeable barcodes you can still use
barcode numbers and enter/view them in human readable format.

 3. All the standard koha and opac stuff using unmodified distribution
to access a unified database.

What we have done:
We have reorganized the "standard" koha distribution so that we can run
"public" and "private" versions side-by-side on same server but
protected by Apache/MySQL (in our case, mod_auth_mysql) authentication.
The "public" opac is a modified sub-set of the "standard" koha
distribution, plus some extra perl scripts, javascript, cookies and
soupermail for email integration purposes (soupermail.sourceforge.net)



Main Benefits:
 Can provide a complete on-line environment with no requirement for
users to physically attend library (items are sent to borrowers by
standard mail).

 Staff can track status of reserves, borrowings etc (users can do that
too if you want to allow it).

Seems to work ;^)



Main Liabilities:
 Privacy and security are _major_ issues. It is very difficult to
maintain a detailed,web-accessible database and still protect your users
to the extent that they deserve!

 Our approach to solving these issues is to simply by minimise the
amount of information stored in your database. Apart from information
about resources, our on-line database only stores member username and
password details... minimal additional information (such as email
address) is stored using cookies (not stored in server database).

 This is _much_ less than most library admins would accept... and it is
very inefficient... but it allows us to provide a good service to users
and we are willing to accept the administrative limitations until we
have time to develop a better solution to address on-line privacy and
security issues



Summary:
 The opac options described above need more work to provide a
"professional" solution - but they do work.

 It is possible to run OPAC web based services using minimal user
information in the database. Patron information (stored in on-line
database) is only required if you wish to provide on-line requests
and/or other extended services.

 We have only just started testing the setup as described above, but
looks like it will work for our specific needs -  about 6,000 items and
1,500 geographically remote library members - resource library
specialising in resources for k-12 learning difficulties.

 We'd like to see the extended web access features as part of Koha main
distribution but we have been holding off as we think Kapito/others are
already working on some of these extended features... and that they will
do a much better job than us :)

I can organise a tarball (upload to CVS or whatever) if anyone is
interested.

R.