-
Notifications
You must be signed in to change notification settings - Fork 9
Closed
Labels
administrator-featureIndicates that the feature will be driven by the Hugo AdminIndicates that the feature will be driven by the Hugo Admin
Milestone
Description
Specifically, this is to implement a user interface and data model to support manual canonicalization of the nomination data by the Hugo Award administrator and their team.
Automatic assistance in this process should be advisory and optional.
- [ ] Define the `nomnom.canonicalize` Django app.
- [ ] Construct a view for the canonicalize process as described in the attached document: [WireFrame.pdf](https://github.com/user-attachments/files/17809398/WireFrame.pdf)
Data
A nomination record itself might:
- be rejected entirely
- be associated with an existing canonical nomination
- be associated with a new canonical nomination
A canonical nomination might be
- marked ineligible
- moved to a different category
- edited to clarify description
- identified as a Finalist
- declined as a Finalist
It is important to retain the original nominating ballot associations for each nomination record, as that information is required in order to implement EPH.
UI
The user interface can be built either based on the Kansa canonicalization UI, which works by way of small requests updating individual nominations, or as a conventional Django form view.
Metadata
Metadata
Assignees
Labels
administrator-featureIndicates that the feature will be driven by the Hugo AdminIndicates that the feature will be driven by the Hugo Admin