Patron API product, WAM issues

[Dave Haslett <d.haslett@xxxxxxxxxx>]

We're interested in hearing from folks who are using Innovative's 
"Patron API (URL)" product. How are you applying it and how is it 
working?

  We are  dissatisfied with the limitations present in the current WAM 
product. We would prefer to use the command link (token) style method 
for patron verification on our leased databases to avoid the somewhat 
awkward proxy method where you have to provide various sets of 
configuration instructions for users of different browsers. The 
problem, of course, with the token (command link) method is that it 
can't handle sites that use Java(script). Javascript is used with a 
majority of our leased databases and this seems to be the trend for 
most websites as of late.

We've recently talked to Innovative about the problems and apparently 
several other libraries have voiced similar concerns. They are 
working on a new solution for patron verification re Java but there's 
no estimate of how soon this will be available. We were urged to find 
out more about the Patron API product on the list and would like to 
hear more of how it's being used, how often you export the patron 
data out to keep it current, etc.

Other libraries (non-Innovative) seem to be using other methods to 
successfully patron-verify on some of the same Java-based databases 
we have without having their patrons reconfigure their browsers. 
We're interested in hearing if Innovative libraries are getting 
around this problem with the Patron API product or some other 
solution. I thank you very much in advance for your responses!

-Dave Haslett
-- 

_/__/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
Dave Haslett
Head of Automated Services
St. Joseph County Public Library
304 S. Main St.
South Bend, IN  46601
voice: (219) 282-4661
fax: (219) 282-4662
e-mail: d.haslett@xxxxxxxxxx
www:  http://sjcpl.lib.in.us
_/__/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/