WordPress already associates an E-Mail address with *users*. In order for a *patron* to do things like place holds on items (from the front end), they need a *WordPress* user login (eg created by the normal, built-in, WordPress user registration process). Once the *patron* has a user login (it need only be as a ‘subscriber’), that *user* login can be associated with a *Patron* id. I saw no point in duplicating information, which would be a problem keeping syncronized.
One of the points of having a plugin like this is to leverage some of WordPress’s existing features and functionallity. This includes the front-end web interface, which allows patrons to search the library’s catalog and place holds. Using WordPress’s user login feature, this also gives users/patrons limited ‘back end’ access for things like checking on due/overdue items, self-renew items, and check on the status of items on hold. And BTW, gives the Librarian access to the user/patron’s E-Mail address. Oh, and the user/patron can self-maintain personal information, like address and phone number.
