I have a few questions about extending the Member datamodel that are assploding my brain!
I have been reading and reading and reading posts in the forums / docs / blogs / dev-list about Extending vs Subclassing the Member object but I'm still struggling to figure out the correct application of this info to what I need to build.
Firstly, I have three primary types of Members - developers, contacts and staff. A Member can be any combination of these.
I'm not overly concerned about the Security tab in the admin as the plan is to have candidate and contact creation on the front end. Though staff would potentially be added via that tab (probably - but not necessary). Initially these Members will be logging in to keep their information up to date, so a profile page is also required - but obviously needs to only show the fields appropriate to the type/s of Member logged in...
If I've extended Member with multiple 'roles', what is the best method for me to determine which one/s they are?
As the app progresses they will have access to different areas of the site upon logging in.
Linking developers and contacts to companies and fellow developers and contacts - ie maintaining a range of relationships - will be critical too. At the end of the day this will end up as effectively a CRM. A contact will have a parent company but may be associated with others too, just as a developer may be associated with other companies but not require a parent. Both would have a primary link to a staff member.
eek! My brain is assploding. Please help if possible!