search

BoTreeConsultingTeam / HealersConnnect

Bringing pranic healers together
MIT License
0 stars 0 forks source link

Split Registration model in to three models #27

Closed ghost closed 10 years ago

ghost commented 10 years ago
  1. The final models will be as below

Registration Following fields will remain same as before in Registration model all other fields will be moved to other table

:fresher, :payment_type_id, :cheque_no, :bank_name, :cheque_date, :registration_date :workshop_id

UserProfile

t.string :first_name t.string :middle_name t.string :last_name t.date :birth_date t.string :education t.string :occupation t.string :gender t.boolean :married t.text :address t.string :mobile t.string :telephone t.string :email t.string :location t.float :long t.float :lat t.references :registration t.references :user

Workshop

workshop_place: string workshop_dated: string workshop_instructor: string

  1. Also write script for migrating data. So they are not lost during migration.
  2. Also change the view forms affected by this change.
amitpatelx commented 10 years ago

Mail conversation with the Client

Requirement: We would be keeping the details of user(via registration of any course) and would create user for the same in our system so that next time user don't have to fill the form with personal details and courses he attempted.

Assumption : We are implementing this system for Ahmedabad/Surat/Halvad Centers

Yes. But it should be extendable

Questions:

  1. Are we going to keep details and create users who has not done any courses in above centers? e.g., Hinduism Revealed. In this course many healer would be from other centers. We are capturing all personal and course details right now in current system. The question is are we going to create user so they login and manage their data?

    Yes

  2. How are we going to ask/create records of the healers who have already done advance/higher course?

    Our suggestion: Send an invitation email to ask for registration. The email will contain benefits for registration and using the system.

    I agree with your suggestion

amitpatelx commented 10 years ago

@HardikJoshi-BTC @chetan-beaverlogic This issue is related to refactoring existing implementation. Please close this if it is done.

As discussed with @HardikJoshi-BTC the are different scenario in registration process but let us not club everything in one issue/branch. I would create separate issues for all the enhancements to the registration.