Introduction
The Authentication and Accounting Module (AAM), is an optional product that works in conjunction with other EnvisionWare products to provide a variety of special services related to accounting and user validation. AAM is a set of TECHNOLOGY FEATURES plus the tools to create a database. In other words, AAM provides special capabilities for other products that are dependent on a centralized database. AAM does not include a database, it builds a database with back end available products. It is important to note that the database used with AAM is simply a data repository. The database does not contain any scripts or triggers. Some AAM users connect directly to an ILS for certain AAM functions.
Components
• AAM Database Administrator — creates a database structure in a MySQL database. It provides import and export utilities, SQL queries, and a method of creating and managing groups and individual users. The Administrator operates in an Admin mode to do all of the above, and a staff mode to create and modify users.
• AAM User Account Manager —a tool used by staff to add or deduct funds for a user, or in self-service mode a different interface permits a user to query his or her account balances and deposit funds into the account using a credit card (with eCommerce Services) or cash (using a vending device or Network Add Value Station).
• Web Query for AAM— a set of scripts that run on a web server to provide self-service or staff access to a variety of built-in reports including cash reconciliation, user account queries, daily transaction reports, and many others for use with MySQL databases. Note that some ILS users may use the ILS reporting system for certain reports.
The rest of the functionality is built into the individual products that take advantage of the AAM database.
What Does it Do?
One example might be a campus or a small library that owns an ILS (Integrated Library System) that cannot support SIP. The institution may wish to create users in an AAM database and use that database to validate users for the above products.
Another more common use is service as a repository of payment accounts. In most cases, we have no control over the actual validating authority database (such as a patron or student database). As such, we can validate against those sources but we cannot write financial transactions back to those systems. For this application we create a repository for funds accounts and link the data to a common user ID (barcode or student ID) which is the key for the AAM database and the ILS.
A third use is service as a central repository of data. LPT:One (print management), PC Reservation (time/access management), and BarcodePlus (account-based copier control) can write data to the AAM database which serves as a central repository of information. Advanced-level administrators can then create reports with common reporting tools for statistical analysis.
Why MySQL?
MySQL is powerful and easy to use. More importantly, it’s cross platform so you can install it on the operating system of your choice: Windows, Linux, UNIX. HP-UX, Solaris, and more. Some ILS vendors actually build the AAM structure into the primary patron server. There are no EnvisionWare components, scripts, or processes that run on an AAM database; it is used only as a data repository. For more information, visit www.mysql.com.
MySQL is used by Nokia, Scholastic, Yahoo, Associated Press, Facebook, Adobe, Wikipedia, del.icio.us, and hundreds of thousands more.
Using your ILS?
Some ILS vendors have developed a special interface using the EnvisionWare open extensions to facilitate direct access to an ILS-hosted deposit account. For those uses, the AAM back end may be the ILS database for certain functions.
NOTE: AAM also works with a a Jet or Access-style dabase with limited capabilites. Access may be used for testing or a lab setting but is not suggested for production environments hosting user funds.
