Skip to content

Import FileMaker Personnel as facilitator affiliations; retire fm:import_affiliations (ADR-0011) - #3004

Open
maebeale wants to merge 15 commits into
mainfrom
maebeale/affiliations-importer-build
Open

maebeale wants to merge 15 commits into
mainfrom
maebeale/affiliations-importer-build

Conversation

@maebeale

@maebeale maebeale commented Nov 15, 2026 •

Copy link
Copy Markdown
Collaborator

🤖 suggested review level: 5 Inspect 🔬 new import that writes facilitator affiliations, which drive org program status

Brings FileMaker's Personnel records in as facilitator affiliations, one table at a time, and retires the old all-in-one affiliations import. Only rows we're sure about are imported; the rest go to staff instead of being guessed.

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

  • ADR-0011 replaces ADR-0008's all-in-one affiliations pass with small rounds shaped like fm:import_orgs (Fm org import min #2957).
  • Round one: Personnel → Facilitator affiliations, since those drive program status, reports and reconciliation.

How did you approach the change?

  • fm:import_personnel places each row at the one org carrying its project code (never the umbrella).
  • Skipped for staff review, with the reason:
    • odd statuses, missing or pre-1990 start dates;
    • person or project codes on no record or several;
    • Active rows on closed projects;
    • conflicts with a portal Facilitator affiliation;
    • a person code that's an agency card (agencies are orgs, not people), or that has no Rolodex card in the archive.
  • Fills dates only on the portal's undated Facilitator rows that FileMaker agrees are open; never overwrites a portal date.
  • An Active row links to a current FA the portal already has starting within 90 days (usually the same 2026 training), keeping the training's dates.
  • Ended rows get an end date as they import, since program status reads only dates.
    • The latest dated entry in their own notes saying they stopped, else the project's close date, their own last workshop log, the day the row was last saved, the project's last log, else Dec 31 of the start year (a stand-in).
    • Notes saying the program never started make a zero-length FA, which program status skips.
    • The comment says which; the report counts them by source.
  • Activity: each new affiliation keeps one create event, dated and credited as FileMaker recorded it; the rest is dropped, and each run logs one summary event.
  • ADR-0011 records the production numbers behind each rule.

Features seed (optional)

  • Added a features seed (optional) — a rake task, nothing in the UI

Retires fm:import_affiliations

  • Deleted the old all-in-one ADR-0008 pass (service, task, specs).
  • Run after the new import, it would place by guessing the rows round one sends to staff.
  • What it did that nothing replaces yet is listed in ADR-0011's later rounds: agency-card contact people, the AWBW Placeholder, rows with no project.

Anything else to add?

  • Blazer queries for the staff review live outside the repo (they need the portal's host).

🤖 Generated with Claude Code

maebeale and others added 5 commits November 14, 2026 22:12
… with open questions

ADR-0011 replaces ADR-0008's all-in-one affiliations pass with one table per round, shaped
like fm:import_orgs. Round one brings in only Personnel rows every rule is sure of, so a
wrong affiliation can't quietly change an org's program status; the rest are skipped with
a reason for staff to review.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…-to-organizations

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… not audience copies

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…the affiliation

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
It did every affiliation job in one run and, run after fm:import_personnel, would place by
guessing the rows round one sends to staff. What it did that nothing replaces yet is listed
in ADR-0011's later rounds.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@maebeale maebeale changed the title Import FileMaker Personnel as facilitator affiliations (ADR-0011 round one) Import FileMaker Personnel as facilitator affiliations; retire fm:import_affiliations (ADR-0011) Nov 15, 2026
…several orgs

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@maebeale
maebeale marked this pull request as ready for review November 16, 2026 14:12
maebeale and others added 9 commits November 16, 2026 09:15
…irst clue, Combined included

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…eMaker recorded it

Bulk runs shouldn't write thousands of activity events, but an affiliation's history should
still show when FileMaker recorded it. The rest of the run's events are dropped and the task
logs one summary event pointing at the saved report.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…iliations

Program status reads only dates, so an ended row with no end date reads as running. Pass two
takes the first evidence that fits, else Dec 31 of the start year, and says which in a comment.
Also: a Personnel row naming an agency card is skipped as such, and job rows whose notes say
the person left get no start date (recorded in ADR-0011).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…filiations

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The inferred end dates were a separate task only to keep them apart for review. With the rule
settled, one task is simpler and leaves no window where ended rows read as running. Also names
a person code with no Rolodex card in the archive as its own skip reason.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ng the lifecycle buffer

With no Current.source the run's saves queue nothing, so there's nothing to discard; the
import writes one create event per new affiliation itself.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ning's FA as the same stretch

The notes carry dated sign-offs ('1/5/2012: No longer at agency') for most rows that would
otherwise get the Dec 31 stand-in. And most 'two current stretches' were one 2026 training
entered in both systems a few days apart, so an Active row now links to a current FA starting
within 90 days and keeps the training's dates.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant