RE: [IUG] Patron self-registration (what happens upon error)

[Martin Lindén <martin at lib dot kth dot se>]

Hi,

We have solved the duplicate problem like this, and the solution originates
from Elisabeth Frigell at Karolinska here in Sweden.

As the selfreg page which contains the form for registration makes a POST to
itself the solution is to have the form on another page and from there send
in the registration to the server and let the selfreg page become a page for
error messages. (If the self-registration is successful the data is saved on
the server and the program continues with selfregconfirm.) 

I chose to delete the form on the selfreg page and I have now only error
message on it with the duplicate field showing. One could I believe let more
fields remain on the page for another try to register.

So the page from where you send your data displays as same as before but
with another name.

In our case  selfregxhbanst.html  with the form.

We of course have the regular selfreg page  in our case
selfreg_reghbanst.html  and that page contains the error message etc.

If you want more information on our solution or you want to test it please
email me and you can also email Elisabeth Frigell at
Elisabet dot Frigell at kib dot ki dot se .


Regards,

Martin Lindén
Systems Librarian
KTHB
Osquars backe 31
100 44  Stockholm
 
070 641 39 64










-----Original Message-----
From: innopac-bounces at innopacusers dot org
[mailto:innopac-bounces at innopacusers dot org] On Behalf Of Philip Youngholm
Sent: Tuesday, March 20, 2007 11:14 PM
To: innopac at innopacusers dot org
Subject: [IUG] Patron self-registration (what happens upon error)

We're about to implement patron self-registration in Release 2006.

We've found that if the form is rejected by the server (for instance,
because it fails the server-side email address validation, or the system
finds a duplicate patron record), the patron receives no indication of that.
The form is just re-displayed, and there is no error message.

Obviously, in this circumstance, we'd like some kind of message, such as
"We're sorry, but we can't complete your registration online.  Please
contact the library for assistance."  A more specific message or an error
code that the patron could give staff indicating the exact reason for
rejection would be nice too, but we're not foolish enough to expect that.

Do other libraries with patron self-registration experience this, or did we
miss something while setting it up?

I have had a call open with Innovative for three months on this.

Note that this doesn't have anything to do with client-side (JavaScript)
validation, or (apparently) the known issue that is being fixed in Release
2006 1.3.

Phil Youngholm
MARINet
www.marinet.info
--
This message was distributed through the Innovative Users Group INNOPAC list
Public replies:  INNOPAC at innopacusers dot org Update your subscription options:
http://innopacusers.org/mailman/listinfo/innopac