As an administrator reviewing requests, sometimes people include years in the event name and sometimes they don't. This causes the requests for the same event to be split between two or more groups, making it difficult to review them together (or requiring work to rename events). I would like users to be warned before including years in the Event Name field.
Concrete example
Some staff enter the event title as "Code4Lib" and some use "Code4Lib 2023".
Acceptance criteria
When I review events, there are not duplicate events with/without the year included
When I try to enter an event name including a year, I am warned and/or prevented from submitting the request
User story
As an administrator reviewing requests, sometimes people include years in the event name and sometimes they don't. This causes the requests for the same event to be split between two or more groups, making it difficult to review them together (or requiring work to rename events). I would like users to be warned before including years in the Event Name field.
Concrete example
Acceptance criteria