User table schema

[carlsednaoui]

These are the fields we'll need in our User table.

SuperAdmin

• [ ] SuperAdmin [bool]

  Volunteer

• [ ] Receive newsletter [bool]
• [ ] Demographic Information
  • Name
  • Gender
  • Age
  • Email
  • Phone
  • Ethnicity (optional)
• [ ] Location Preference
  • Borough
  • Neighborhood
• [ ] Time Preference
  • Day (s) - day of week checklist
  • Time (s) - morning, afternoon, evening
• [ ] Skill to Provide
  • Design
  • Language (check box)
  • Non-Tech

[miclovich]

Yea; this makes sense...

I think we'll create other tables and make references to them (in the User table) such as Location, TimePreference, and Skill... perhaps for the Skills, they could belong to an Organization and this will give indication to the volunteer of the potential skill-sets otherwise, the volunteer can "add new skill" and this could maybe lead organizations to adopt this skill..

[carlsednaoui]

Yah, or maybe the skill is tied to a program since an organization can have many programs.

The end goal here is to allow organizations to filter/ search the DB by skillset.

[miclovich]

Right on!

[miclovich]

Strongly considering thoughts around http://api.rubyonrails.org/classes/ActiveRecord/NestedAttributes/ClassMethods.html

General User --> a volunteer profile (optional)

And then general users can create Organizations (which can be accepted by super admins); from our previous discussions, this potential user would then accept requests to join the organizations by a volunteer.

[carlsednaoui]

Sounds good to me!

[carlsednaoui]

This issue is outdated. Please refer to #20.