Export nomination data to JSON

[aJanuary]

Motivation

Currently the process of generating the nomination report is time-consuming and error-prone. The combination of this means there is only really scope to generate one form of the report in a pdf. Ideally the report would be created in multiple formats, including a machine-readable format that others can use to analyse the results and create alternative presentations.

If nomnom exported the data it has in a machine readable format, this can be supplemented with additional data by the Hugo team and fed into scripts that can generate the pdf report, as well as other formats.

The raw data out of nomnom would not be expected to be publishable. Instead, it would need to be cleaned up (e.g. nominee names suitable for publishing added) before it would be published. The Hugo admin team would be responsible for arranging how and where it would be published.

Proposed format

I have been working on the JSON schema for a JSON format that would be suitable for the final publication. I propose nomnom generates a subset of this format, that can then be supplemented with additional data by the Hugo team.

https://ajanuary.github.io/hugo-nomination-stats-schema/nominations-2025-10/

Where the nomnom export format would differ:

• Nominee name would be the internal name used for tracking deduplication, rather than the name on the published ballot.
• The finalist and removed properties on the nominees would never be provided.

[offbyone]

tl;dr, I think this is a good idea and I'm happy to add it to the plan.

NomNom has not yet grown an "api", public or otherwise. I'm giving some thought to how I want that to take shape, possibly including some of the dependencies involved. I like the idea of the modern FastAPI self-documenting style, but I'm quite content in the Django ecosystem and do not foresee bolting FastAPI style WSGI apps into NomNom. I have a quartet of candidates I'll be evaluating to see if they make sense:

• djangorestframework
• django-ninja
• drf-pydantic
• djantic2

The latter 3 allow various forms of mounting Pydantic models as API endpoints, the first is a classical REST API framework. I can also just ignore all this formal API bullshit and vend a JSON file. That might make the most sense.

I'll have to think about it, but hopefully I'll have something in the 2026 version series, by end of LAcon nominations.