APProjects commited on
Commit
a4e71f7
·
verified ·
1 Parent(s): a9c68af

daily refresh mirror

Browse files
Files changed (1) hide show
  1. README.md +10 -0
README.md CHANGED
@@ -216,6 +216,16 @@ Only want this year? The companion [**US layoffs 2026 dataset**](https://hugging
216
  is the 2,684 notices filed in 2026 (242,410 workers named, 45 states),
217
  with by-state, by-month and top-employer rollups already computed. Same rebuild, same ids.
218
 
 
 
 
 
 
 
 
 
 
 
219
  Want it one row per COMPANY instead of one row per notice? The companion
220
  [**employer layoff-history dataset**](https://huggingface.co/datasets/APProjects/us-warn-act-employer-layoff-history)
221
  rolls all 61,312 notices up into 29,897 canonicalized employers with
 
216
  is the 2,684 notices filed in 2026 (242,410 workers named, 45 states),
217
  with by-state, by-month and top-employer rollups already computed. Same rebuild, same ids.
218
 
219
+ Only want the tech layoffs? The companion [**US tech company layoffs dataset**]
220
+ (https://huggingface.co/datasets/APProjects/us-tech-company-layoffs-warn-act-notices-daily)
221
+ is the 1,732 filings from software, internet, semiconductor and
222
+ electronics employers (191,215 workers, 367 companies,
223
+ 1989-2026), with the per-company history already rolled up.
224
+ Unlike the trackers built from news stories, every row there is a filing with a state,
225
+ a site and an effective date. No state publishes an industry field, so sector is assigned
226
+ from the employer NAME and the file is a floor, not a census: 47.4% of
227
+ all notices carry a name that reveals no sector. Same daily rebuild, same ids.
228
+
229
  Want it one row per COMPANY instead of one row per notice? The companion
230
  [**employer layoff-history dataset**](https://huggingface.co/datasets/APProjects/us-warn-act-employer-layoff-history)
231
  rolls all 61,312 notices up into 29,897 canonicalized employers with