Currently, the "Event Name" field serves as both the system's unique identifier and the public title displayed to registrants. This creates friction for recurring annual programs (e.g., "NYC Happy Hour"), where we want the public-facing title to remain identical year after year. To keep events distinct in the backend, we are forced to append years or alter titles in ways that aren't ideal for registrant-facing marketing.

We would love to see Almabase decouple these fields by adding a dedicated "Internal Event Name" (or backend ID) separate from the "Public Display Name." This would allow admins to maintain distinct records in the database while keeping front-end event titles clean, consistent, and user-friendly year after year.