Real organization use cases / requirements

jdleonard → credited ridefree → .

@ridefree contributed one for Blackfly Sustainable Living Co-Op →

Thanks @jdleonard

Should we put one together for a neighbourhood/housing association (as I heard that come up a few times in discussion) and a few others?

Other possibilities that are low resourced w/ 1 or 2 staff. Though many of these are likely overlapping needs.

- Small Professional Associations
- Arts & Culture Collectives
- Community Radio Station
- Local Environmental Advocacy Group
- Local Historical or Preservation Society
- Rural Food Buying Co-op
- Parents' Group for a School
- Running Club

I drafted requirements for Austin Drupal Users Group / TexasDUG. Undoubtedly it could use some more detail. I'm also engaging other organizers to further refine the requirements.

#Atlanta2025 working on this issue with @igorgoncalves

Unique requirements from working with national car clubs, specifically Porsche Club of America (PCA) and Mercedes-Benz Club of America (MBCA).

- Generate a uniquely formatted Member ID using tokens such as date, last name initial, and incrementing numbers. For example, PCA uses the join year, month, and an incrementing 3 digit number (YYYYMM001), while MBCA uses the first initial of the primary member’s last name followed by an incrementing 4 digit number (X0001).

- Assign the Member ID to the Membership as a whole, not to the individual user accounts under the membership.

- The Membership that can include multiple individual members, such as a primary member and one or more secondary members (typically spouses, and occasionally children).

- Each unique user under a Membership has separate login credentials and profile (available profile fields differ between primary vs secondary members).

- Primary and secondary users may have different roles/permissions

- Roles and access should be updated automatically for all associated user accounts based on the status of the Membership.

- Track a complete history of membership terms—including joins, renewals, and any lapses—as lapses affect a member's seniority in the club.

- Option to include a grace period (e.g., one month) before a late renewal is considered a lapse. If a renewal occurs within this grace period, backdate the start of the new term to the end of the previous term to ensure that no lapse is recorded.

- Membership profile fields are split between the Membership itself, membership terms, and individual user accounts. User dashboard needs to show information from all three locations.

- Ability to track member referrals.

- Loyalty rewards programs based on membership longevity, referrals, purchases from participating dealerships, and other unique criteria. Generate loyalty certificates for printing.

- Reporting dashboard for office staff, quickly lookup membership status and lapses.

• Event Registration: While some of our events can be quite large and already use an existing ticketing infrastructure, some of the less formal meetings such as board meetings could benefit from the "Meetup Lite" approach outlined in the TxDUG document.
• Non-Meeting Calendar events: We have a number of Calendars tracking events that don't correspond to events that will be attended, e.g. scheduled email newsletters.
• Member Management: SSO across all our platforms (including non-drupal) has historically been a pain point.

• Custom Condition Plugins: We have created Condition Plugins for the following use cases:
  • Dues Status (e.g. paid, unpaid, lapsed)
  • Subscription Expiration: User has a subscription that will expire in the next X days, or has expired within the last X days. Blocks on the pages corresponding to those subscriptions can include reminders to renew within a configurable window of the expiration date.
• Self-Service PDF Certificates: Many organizations issue membership certificates, certificates of attendance or completion, etc. We have created a framework that allows us to add new downloadable PDF certificates by adding an access control method and a route, reusing the other assets such as background images and template files.

• Sync with 3rd party CRMs: We're currently in the process of regenerating our API Client code, so now is a good time for us to look at what else is in the community, such as OpenY.
• Integration with large event-management 3rd parties: such as cvent

jdleonard → credited rocketeerbkw → .

@rockthedrop Spot on! Thank you to everyone who has contributed to date.

Crediting @rocketeerbkw who contributed to the TxDUG use case linked in a previous comment.