Many public libraries charge monthly subscription fee (e.g. INR 30 per month)for patrons. We would like to see a provision for charging monthly fee in coming version.
I think Koha can already do what you want:
Set up a patron category which has an enrollment period of one month and an enrollment fee of INR 30. Each month the patron's account will expire. When you renew the account the fee will be automatically added.
If that sounds like what you need please mark this bug as resolved-invalid.
Thank you for the information.
I will share the information to public library people.
Owen: No this actually does not solve the issue. Here is why :
1/ There is often an one-time enrolment fee and then a monthly subscription in some cases.
2/ The membership categories in public libraries are often defined in Acts of the state and hence has statutory parameters. A 30-day enrolment would "solve" the problem "technically", but it will create legal non-compliance. An example:
A solution as proposed will be in violation of Section 3(3) sub clause (b), Section 3 (5), Section 5 (4) sub-clause (a) and (b) of West Bengal Sponsored Public Library Management Rules, 2005 - http://www.wbpublibnet.gov.in:8080/openenrichv41/LIBRARY_new/pdf/man-rules.pdf as notified by the Government of West Bengal.
3/ Likely to complicate matter than solve it.
Changed component to Patron (from Circulation), Importance to P3 enhancement (from 'new feature) as it calls for extending the patron category.
*** Bug 9096 has been marked as a duplicate of this bug. ***
Each month the patron's account will expire,the solution practically not possible bacause most of the members subscription fee payment lumsum in 6 months or 3 months sometime due 3 or 4 months.In this case the solution deosent work..? circulation continues.Clear subscription fee every month, most of public libraries survival is not possible..
I think "New" is the correct status for this bug since it's open and unassigned. We don't have an established procedure for using "verified" or "wishlist."
*** Bug 18038 has been marked as a duplicate of this bug. ***