Skip to content

✨ Creating a user-friendly, non-duplicative Election Name field #203

@rc-ms

Description

@rc-ms

Is there an existing issue for this?

  • I have searched the existing issues

Suggestion

When an election administrator creates an election entry in the setup tool, we want them to use a descriptive name that allows them to uniquiely identify the election they're preparing for, such as:

  • Hamilton County April General Election
  • Harris County Special Election May 13, 2023
  • Eureka Township Mayoral Runoff # 2

We want to make sure these character formulations are possible. If there are problematic characters (e.g., '?', '%', '$', '@', etc.) we should alert the user and prevent their being submitted/displayed in the text box.

To avoid downstream application errors, we want to ensure each Election Name is unique. From a UX perspective, we should enforce uniqueness at name creation.

When a user finishes creating an Election Name, if they press the Enter key or the Create Election button, before proceeding to the next screen the name is submitted, instead an animation that the name is being checked.

If the name is unique, the animation turns green and the user progresses to the next page in the sequence

If the name is not unique, an alert is triggered and an error message displayed: "There is already an election named [foo]". The cursor focus is returned to the text box where the original submission text is displayed with an appended set of text such as [1]. If there is already a [1] entry, then [2].

From that point, if the user simply hits return again the new item can be submitted since it's already been "pre-screened" as unique. Alternatively, the user can move the cursor or hit the delete or backspace keys to change the text themselves and resubmit

Possible Implementation

No response

Anything else?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions