MemberHandling

Current status

• Member handling has almost reached stability

Future improvments

These changes are to be made in a cvs branch and not merged until stable
Since these changes will not require changes to the database or data there is no urgency to get them in before the start of the year. Changes in a branch will also not affect the live website as previous changes did. This means that changes do not need to be merged until they are stable.

• Make use of mem_id and pid consistant.

• Improvments to the anonimity of people who have not agreed to give us their details
  • The names of non-members do not need to be stored. Uni_no is enough to uniquely identify someone
  • The details of people who's memberships have expired do not need to be held
  • Member functions will check permissions required

• All uses of person / member data must be done through the member function

• In many cases member funcions do not need to include DB queries. Such functions should make use of other functions
  eg. wscauth_getrealname can call get_name_by_id(wscauth_getid()) and does not need to have its own DB query that does the same thing
  • It may be possible to eventually reduce all functions down to using the search_query for DB queries. This will mean that any changes to member handling or permissions are a lot easier to implement.