Summary: | opac-userupdate.pl update to allow moderation, and templatize | ||
---|---|---|---|
Product: | Koha | Reporter: | Owen Leonard <oleonard> |
Component: | OPAC | Assignee: | Galen Charlton <gmcharlt> |
Status: | CLOSED FIXED | QA Contact: | Bugs List <koha-bugs> |
Severity: | minor | ||
Priority: | P2 | CC: | dpavlin, gcollum, gmcharlt, jwagner, kyle.m.hall, nengard |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
See Also: | http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7067 | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: | |||
Attachments: | Moving the contents of an error message from the script to the template |
Description
Chris Cormack
2010-05-20 23:39:28 UTC
I'm wondering if, instead of an automated email, there should be a better system for updating borrower information. I would create a table to store the requested data, then have a system where by the librarian can go through each borrower record, see the changes requested as compared to the original data, then give the changes a thumbs up or thumbs down. Perhaps the borrower could receive an email confirming or denying the change request ( with an optional reason, perhaps ). I think we have a great opportunity to integrate and update to this system with a system for online patron registration: Both could potentially use the same table to store information which would require the librarian to validate and approve. That sounds like an excellent idea. We could even have printable temporary library cards! One issue: my library system requires a piece of mail to verify a home address. What do other libraries require? Should it include the ability to submit scanned documents, or should just let you fill out your data, bring your documents in and let a librarian verify and complete the process. (In reply to comment #2) > I think we have a great opportunity to integrate and update to this system with > a system for online patron registration: Both could potentially use the same > table to store information which would require the librarian to validate and > approve. Has this been fixed by the new patron self registration feature? I think it has. |