What data must be stored for a User?

[pohlm01]

A used should have the following data associated (up for discussion):

• First name
• Last name
• Initials ?
• Birthdate ?
• Address ?
• IBAN ??
• Email
• Password hash
• Roles (multiple possible, please see enum below)
• Membership status (one possible, see enum below)
• Certificates gained (multiple possible, see enum below)

Possible Roles:

• Admin
• Treasurer
• Secretary
• Chair,
• ViceChair,
• ClimbingCommissar,
• ActivityCommissionMember
• EducationiCommissionMember
• Kader
• What else?

Possible Membership status:

• Pending (if signed up at the website, but not yet confirmed by the board)
• Member
• Extraordinary
• NonMember

Please comment on anything that should likely be adopted. During the design of the website, we should likely pay special attention to be able to easily extend the possible roles, but having a good initial data set is nice.

[robintup598]

Additions to user:

• Phone number
• Student number
• NKBV (or other national climbing association) number
• Sportcard number of the RSC
• ICE contact details (name, mail, phone)

Then it is also nice for weekends and other activities to know other kinds of info of members, things like:

• Driving license
• Medical information
• Dietry wishes
• Info about owned climbing stuff: rope, quickdraws, helmet, harness, belay-device, NKBV klimjaarkaart

For the possible roles few additions, but yeah should be easily added later on.

• AdvisoryCommissionMember
• AlpenCommissionMember
• ConstructionCommissionMember
• IntroductionCommissionMember
• KasCommissionMember
• MaterialCommissionMember
• PaparacieCommissionMember
• StawijcieCommissionMember
• WinterWandelWeekendCommissionMember
• WebsiteCommissionMember