20 lines
873 B
Markdown
20 lines
873 B
Markdown
 
|
# Proposal: Support Organization Members
|
||
|
|
|
||
|
|
## Summary
|
||
|
|
Update the member data model to support both individual persons and organizations. Organizations will have a company name instead of a mandatory first name.
|
||
|
|
|
||
|
|
## Background
|
||
|
|
Currently, the system only supports individual members with a mandatory first name. We need to accommodate organizational members (companies, associations, etc.) where the primary identifier is the organization name.
|
||
|
|
|
||
|
|
## Goals
|
||
|
|
- Allow distinguishing between individual and organization members.
|
||
|
|
- Make `first_name` optional for organizations.
|
||
|
|
- Add `company_name` field, mandatory for organizations.
|
||
|
|
- Ensure data integrity based on member type.
|
||
|
|
|
||
|
|
## Non-Goals
|
||
|
|
- Complex hierarchy of organizations and contacts (for now, just a simple distinction).
|
||
|
|
|
||
|
|
## Technical Note
|
||
|
|
- Field name: `memberType` (not `kind` to avoid GraphQL introspection conflicts)
|