Home

Welcome to the OpenSourceMemberManager wiki!

System architecture

Philosophy

Simple is elegant

We have 3 parts

1. Backend for storing and loading membership information
2. Frontend for managing memberships
3. Database schema

First version goals

• Backend
  • PHP pages replying/recieving with JSON using sqlite store
• Frontend
  • Basic HTML frame with AJAX handling communication with backend.
• Database schema
  • Basic members: id, name, email-address, last-enrollment

Chosen not to do:

• logins. Right now open to all. Yes it's crazy, but we need something working first.

Second version

• Add authorization to mix
  • administrator users,
  • deny direct public access to db-file (e.g. .htaccess)

#Other solutions

• SOCmanager - member management software for a choir
  • https://code.google.com/p/socmanager/