RE: Validation of Millennium users

["Zhou, Don" <dzhou@xxxxxxxxxx>]

Hi, Marc:

Do you have to buy the patronapi product?

Don Zhou
Head, Technical Services
William Mitchell College of Law
St. Paul, MN

-----Original Message-----
From: innopac-bounces@xxxxxxxxxx
[mailto:innopac-bounces@xxxxxxxxxx] On Behalf Of Marc Davis
Sent: Thursday, April 22, 2004 7:45 AM
To: IUG INNOPAC List
Cc: Thomas_E_Kolakowski@xxxxxxxxxx
Subject: Re: Validation of Millennium users

Do you have PHP coding knowledge?
I have a PHP class that handles input/output from the Patron API.  So we

handle all user input and processing on a separate server that simply 
queries Innovative server and then parses the API output.
Let me know if you're interested.

------------------------------------------------------------------------
----
Marc Davis  --   Manager Support Services
University Library, University of Nebraska at Omaha

If you think you're always in control, then you're not 
going fast enough. -- Mario Andretti
------------------------------------------------------------------------
----



<Thomas_E_Kolakowski@xxxxxxxxxx> 
Sent by: innopac-bounces@xxxxxxxxxx
04/22/2004 06:19 AM
Please respond to
IUG INNOPAC List <innopac@xxxxxxxxxx>


To
<innopac@xxxxxxxxxx>
cc

Subject
Re: Validation of Millennium users






I had a similar problem, but got no help from III.  In my case the 
PatronAPI
is required.  III supplies the PatronAPI but refused to provide any 
support
for how to use it.
After much research, I found the following "imperfect" solution.
I use JavaScript, because our UNIX based Millennium server has NO CGI
capabilities available to the library.
The situation involved patrons logging into our website, but being 
validated
from the Millennium database.  The patrons are signing up for library
programs/classes.
We do not use PIN numbers.  We use the Patron last name as the
"password" 
to
match the given barcode.
1) Our website passes barcode to our Millennium server,
2) The Millennium server retrieves the PatronAPI (based on the given
barcode) into an "invisible" IFRAME.
3) The server requests the Last name and matches it against the
PatronAPI
(using InnerHTML).
4) The server also checks Money Owed and Expiration date before allowing

the
user to go further.
5) On success the patron is returned to our webserver, passing back key 
info
(Name, Telephone, Barcode and Email) to our website for processing to
our
website's program registration database (based on ColdFusion).

PROBLEMS: Netscape does not support the InnerHTML required to read the
PatronAPI.  Less than 2% of our patrons use Netscape.
Javascript is visible to the users who "View Source", but steps can be 
taken
to make it a little more secure by using external Javascript files.
--
This message was distributed through the Innovative Users Group INNOPAC 
list
Public replies:  INNOPAC@xxxxxxxxxx
Update your subscription options: 
http://innopacusers.org/mailman/listinfo/innopac



--- StripMime Report -- processed MIME parts ---
multipart/alternative
  text/plain (text body -- kept)
  text/html
---
--
This message was distributed through the Innovative Users Group INNOPAC
list
Public replies:  INNOPAC@xxxxxxxxxx
Update your subscription options:
http://innopacusers.org/mailman/listinfo/innopac

_______________________________________________________________________
This email has been scanned for all viruses.

_______________________________________________________________________
This email has been scanned for all viruses.