Record what a sector or age group used to be called

[maebeale]

🤖 suggested review level: 3 Read 📖 one new table and lookup, plus a seeder carrying the translation tables; no existing behavior changes

Four systems asked facilitators who they serve, each with its own wording — FileMaker, the older registration and scholarship forms, Story Share, and the portal's earlier sector list. The portal settled on one vocabulary, but nothing recorded how an old word becomes one of today's tags, so every import had to guess.

What is the goal of this PR and why is this important?

• The Rolodex import (Import people from the FileMaker Rolodex archive #2630) needs it first; a forms backfill and a Story Share migration will need the same answers.
• The renames and merges already ran, so the old names are gone from the data. This is what's left of them.
• Measured against the real archive: 17,734 of its 17,757 mentions are now translated, deliberately untranslated, or proposed. The 23 that remain all name an organization or a facilitator's own circumstances.

How did you approach the change?

• docs/adr/0007 — the translation tables, from the mapping spreadsheet plus the decisions AWBW made on the terms the spreadsheet didn't cover.
• TagAlias — one row per legacy term: the tag it resolves to (a Sector or an AgeRange Category), the system it came from, who recorded it, and whether it's ignored or proposed.
• TagTranslation#resolve — the lookup. Answers with both the sector ids and the age-group ids a term means.
• TagAliasSeeder / data:seed_tag_aliases — the tables as rows, idempotent, part of db:seed.

Five decisions worth a look

• Data, not a constant. The archive's free text keeps producing new spellings, so an admin should be able to record one without a deploy — and the rows outlive the imports as the record of what a tag used to be called.
• A name resolves only while the tag is published; an alias may point at a retired one. Sector.all would have resolved Poverty — a retired row — and handed it to 634 more people by accident. A recorded alias is the opposite of an accident, so Poverty still reaches the sector that already carries its older taggings.
• The vocabularies cross. Elder Abuse is a life experience that means the Elders age range; Children's Services is a service area that means Children. So #resolve answers with both kinds, and primacy stays the caller's call since it follows from the field, not the term.
• A term can name several tags — C & T, Families (every age), and the compound cells like Sexual Assault & Domestic Violence.
• A term can name nothing on purpose (ignored): the Settings that say where someone works, Other, n/a, and People Who Have Experienced War, which AWBW chose to leave untagged rather than file under a sector it doesn't mean.

What's proposed rather than decided

About 90 readings of hand-typed free text are marked proposed — Immigration Clinic, Grief support group, Supervised visitation sessions for foster youth…. They resolve, so no import waits on a review, and TagAlias.proposed is the list to walk with staff. Anything naming an organization, a place that identifies one, or a facilitator's own circumstances is deliberately not read — that text stays in the archive.

Anything else to add?

• Splitting is on line breaks and semicolons, not commas — the archive's own wording contains commas inside parentheticals ("Community violence (gang violence, mass shootings, etc.)").
• Nothing consumes the lookup yet — Import people from the FileMaker Rolodex archive #2630 switches the import over to it.

🤖 Generated with Claude Code

[jmilljr24]

I like the model for this.

Will it still exist after the fm import? If not, can we open a blocked issue for its removal?

[maebeale]

@jmilljr24 i was thinking it'd be helpful to them post-import. and i was also thinking there's likelihood of other data coming out of the woodwork later that would need it. but yeah, if they think 100% not needed we can delete after for sure.