Enter political information and COPE data¶
As a Membership Staff member, I want to record a member's voter/district information and COPE contribution history, so that the local can run VAN imports and GOTV mailings accurately and keep PAC/COPE deduction history straight per member.
Screen: Members > Political
Membership Staff has Add/Update on the Political tab, same as Super User. Every other role —
Business Agent, Management, Accounting, Contract, H&W Staff, ETF Staff — has View Only: they
can see a member's political/COPE data but not change it.
This tab exists to serve two distinct things at once, and it's worth keeping them separate in your head: voter/district demographics (for VAN import and GOTV targeting) and COPE contribution history (for PAC/COPE deduction tracking).
Key fields¶
Voter/district demographics: Party Affiliation; "Voted In Last Election?" checkboxes (Registered Voter / Local / State-Federal / Presidential); Supervisor, Alderman, US Congress, Ward, State Assembly, State Senate.
COPE History grid: Effective Date, Contribution, Frequency, Expiration Date.
Actions available: Save Changes (for the demographic fields), Add (to add a new COPE History row).
No documented click-by-click walkthrough exists yet for this screen beyond its field inventory — the crawl that produced this reference captured a partially-populated example (one COPE History row, no voter/district fields filled in) but didn't exercise Save Changes or Add against live data.
Things to watch out for¶
The district fields hold numbers, not names — this has already caused a false bug report
Supervisor, Alderman, US Congress, Ward, State Assembly, and State Senate hold voting district numbers, not the names of the people who represent those districts. A prior complaint about a short character limit on these fields turned out to be a misunderstanding for exactly this reason — the fields are sized for a district number, not a representative's name, because the whole point of capturing them is to support a VAN (Voter Activation Network) file import for GOTV/mailer targeting by district. If a staff member reports that one of these fields "won't fit the name," the fix is training, not a ticket. (IUOE-2516)
COPE data entry is its own grid, separate from the voter fields
The signed BLR calls for a dedicated COPE data-entry grid on the Political tab (Effective Date / Contribution / Frequency / expiration), distinct from the voter-demographic fields above it. Don't conflate a COPE contribution record with a political/voter-demographic update — they're entered in different parts of the same screen and serve different downstream uses (PAC/COPE deduction tracking vs. VAN/GOTV targeting).
Political File Import is a signed requirement — but not something this crawl has confirmed live
The signed Union BLR (User Story Scenario 5.3.3, Political File Import) spells this out in its standard As-a/When/Then/So-that form:
As an IUOE 399 Union employee, when I am managing PRIZM standard member voter demographics/PAC info, then I should be able to import a file from a third-party source that provides this information, so that I can easily fill out this member information with the most recent data.
That's a bulk-import path, distinct from the one-member-at-a-time Political tab documented
above. It hasn't been confirmed live anywhere in this crawl's reference material: this
document's own crawl of the Political tab shows no import control, and a targeted search of
e2e/crawl/docs/utilities.md and training-docs/reference/utilities.md — the two places a
bulk-import screen would most plausibly surface — turns up no mention of "political,"
"voter," or "VAN" in either file. No Utilities screen or other crawled module currently
exposes this import path. This is a genuine open gap between a signed requirement and
confirmed live behavior, not a documentation oversight to paper over — it's worth a dedicated
UAT check against the live app rather than guessing at where (or whether) the import lives.