🇺🇸United States @ldpm

jdleonard → credited ldpm → .

As per consensus from the general contribution table at DrupalCon ATL:

The following use cases for tracking individuals should ideally be supported:

• Participation in events should not require each participant to have an "account" (e.g. RSVPing for oneself and a guest)
• Organizations should be able to extend their membership status to their employees or members

• 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