screening

Every candidate application drawn from the two sampling frames, the screener model's verdict and reason, the adjudication where one was recorded, and whether it entered the sample.

Data license: Not yet licensed — internal review only · Data source: Ahmed ElBatanony, Innopolis University

4 rows where in_sample = "1.0", pcf_id = "2.0" and set = "holdout"

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: screener_reason

frame 2

set 1

  • holdout · 4 ✖

screener_verdict 1

in_sample 1

adjudicated 0

Link rowid ▼ frame candidate screener_verdict screener_code screener_reason adjudicated adjudication_reason in_sample pcf_id set
2 2 F1 opf/openproject include I Deployable multi-user business application with English feature documentation.     1.0 Develop and Manage Products and Services 2.0 holdout
10 10 F1 logchimp/logchimp include I Deployable multi-user business application with English feature documentation.     1.0 Develop and Manage Products and Services 2.0 holdout
408 408 F2 Jira include I Multi-user business application managing organisational records.     1.0 Develop and Manage Products and Services 2.0 holdout
415 415 F2 Aha! include I Multi-user business application managing organisational records.     1.0 Develop and Manage Products and Services 2.0 holdout

Advanced export

JSON shape: default, array, newline-delimited

CSV options: 

CREATE TABLE [screening] ([frame] TEXT, [candidate] TEXT, [screener_verdict] TEXT, [screener_code] TEXT, [screener_reason] TEXT, [adjudicated] TEXT, [adjudication_reason] TEXT, [in_sample] REAL, [pcf_id] TEXT, [set] TEXT, FOREIGN KEY ([pcf_id]) REFERENCES pcf_categories(pcf_id));
CREATE INDEX [idx_screening_frame] ON [screening]([frame]);
CREATE INDEX [idx_screening_in_sample] ON [screening]([in_sample]);