Skip to content

Normalize event location countries (locations.country) to the country dropdown #2832

Closed

Description

@maebeale

🤖 From Claude:

Event venues (locations) still hold free-text countries, so they can disagree with the country dropdown everything else now uses.

Context

What's needed

  • Decide whether Location is still used. The model is marked # TODO remove this class if unused, and nothing in the app creates rows; events pick one in EventsController (@locations).
  • If it stays: translate locations.country (and state) through AddressTranslation#country / #state — e.g. a locations pass in AddressServices::TranslateExisting, logged the same way.
  • If the registrations importer work touches event locations, route any country/state it writes through AddressTranslation so nothing off-dropdown lands.

Registrations importer rework — build on #2829

Assigned to Justin because he's reworking the registrations importer, which this sits next to.

Activity

  1. maebeale commented on Oct 24, 2026

    @maebeale
    CollaboratorAuthor

    🤖 From Claude: Checked prod: locations has 2 rows (Hawthorne, California / Darmout, MA — both USA), and 0 events point at either. The Location model looks safe to remove (with events.location_id and the event-form picker) rather than translate; if it stays, it's just two USA → United States rows.

  2. maebeale commented on Oct 24, 2026

    @maebeale
    CollaboratorAuthor

    @jmilljr24 i think we can ignore these bc here is the data:
    country
    locations_total
    events_total
    USA 2 0

    2 rows

    id
    city
    state
    country
    1 Hawthorne California USA
    2 Darmout MA USA

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions