RE: [IUG] Patron database standards - working on a partial solution

["Ammon, Mona" <ammonm at u dot library dot arizona dot edu>]

We are a university library.  One of the things we are trying to
institute are more specific patron templates.  We have a lot of
different users who get varying levels of privileges.

I have been able to create these templates so that ptype, stats code and
expiration date are automatically entered.   And that different fields
get prompted for different types of patrons.

One problem I am having is that I can set up the templates but I select
new patron button and choose a template that template wants to come up
all the time.  How do I make it so each time you can select from a list
of templates.  I have looked at the documentation but must be missing
something.

As for making sure name etc gets put in haven't figured that out.
Luckily we down load the majority of our records from the university
system which has all that information.   I think your suggestion that
the system will not allow you to close the record with out certain field
would be a great enhancement requests.  This is what is done with forms
on line all the time.

Mona

-----Original Message-----
From: innopac-bounces at innopacusers dot org
[mailto:innopac-bounces at innopacusers dot org] On Behalf Of Ronnie Morgan
Sent: Friday, February 10, 2006 8:34 AM
To: IUG INNOPAC List
Subject: [IUG] Patron database standards

We are having a lot issues with patron database integrity.  I am finding
out that certain rules we have in place for how patron account fields
should be entered simply aren't being followed.  Some accounts have all
upper case, some all lower, some are missing zip codes, missing area
code in the phone number, and more than I'm willing to admit have no
spaces in the name (after the comma).  Lots and lots of issues.  It
would be nice if III would make it so certain formats had to be
followed, or that certain fields be required (we have accounts with no
names...)  One of the latest enhancements that cause certain fields to
be red is great, but more functionality would be better.  Like, not
letting the staff member save the record if there are fields in red.  

So, my question to everyone is, how do you handle something like this?
What measures do you have in place to assure patron data accuracy?

Thanks,
Ronnie Morgan
IT Department Head
Genesee District Library

--
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