Bug 4848 - Ability for patrons to create their own accounts
Summary: Ability for patrons to create their own accounts
Status: RESOLVED DUPLICATE of bug 7067
Alias: None
Product: Koha
Classification: Unclassified
Component: Patrons (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Kyle M Hall
QA Contact: Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-03 03:41 UTC by Grant McLean
Modified: 2013-01-15 12:30 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Grant McLean 2010-06-03 03:41:41 UTC
It would be a useful feature if patrons had the ability to create their own accounts.  Obviously this would need to be an option that could be enabled for a given instance of Koha.

In my case, the Koha instance is on the public internet and I would be happy for anyone to create an account.  The main thing I want people to be able to do is to use the comments feature to add mini reviews of books.
Comment 1 Owen Leonard 2010-06-03 13:27:30 UTC
We've talked about this feature at my library before too. We've discussed the option as being used by "web only" patrons as well as "in person" patrons. Because we require "in person" patrons to be residents of the area, we would need a mechanism in place for making web-registered patrons probational until proof of address was brought into a library for confirmation. Perhaps web-registered patrons would be created under a new category with a close expiration date?

If patrons were to be able to create their own accounts, we would need to develop a system for sending confirmation emails which could be customized using the notices system.
Comment 2 Owen Leonard 2010-06-03 13:27:56 UTC
See also Bug 3059.
Comment 3 Jared Camins-Esakov 2013-01-15 12:30:05 UTC
This feature has been implemented on bug 7067.

*** This bug has been marked as a duplicate of bug 7067 ***