Want to make several modifications, need advice

[cypherpunks]

I am about to make the following modifications:

1) Anonymous users do not see the schedule at all
2) Permissions to use resources are assigned to groups, not users.
3) A registered user uses an "enrollment password" to join a group after registering. That "enrollment password" is an alternate key for a group.
4) A registered user only sees resources that are available for reservation to the group(s) he/she is a member of
5) A registered user only sees which slots are reserved (does not see who reserved slots)
6) A resource is available only on particular days of the week. Using blackouts for restricting days of the week is not elegant (too many database rows inserted), I would like to specify days of the week in addition to hours.

And I am writing a "wallet system" - users can pay using Paypal to get credits, and can use their credits by reserving slots. Or credits can be incremented by admins if users pay cash or by other means that do not have automated means of processing.

If you have implemented some of the features above or similar features, I am interested in your advice.

[jimdolyn]

Hello -- i am very interested in your "wallet" system, I would like to implement something similar.

We run an Open Sewing studio, and users can purchase hours -- I would like to have a wallet system so we can offer discounts on the price of hours, and manage a "wallet" of purchased credit, deducting as they use their credits up.

Please share any insight you may have into this -- thanks alot!

-jim

[Nick]

Most of these features on in development right now except number 3.  Number 5 can be enabled currently with the use of privacyMode in the config file.