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

1 row where adjudicated = "include", pcf_id = "2.0" and screener_verdict = "include"

✎ View and edit SQL

This data as json, CSV (advanced)

set 1

screener_verdict 1

  • include · 1 ✖

in_sample 1

frame 1

adjudicated 1

  • include · 1 ✖
Link rowid ▼ frame candidate screener_verdict screener_code screener_reason adjudicated adjudication_reason in_sample pcf_id set
416 416 F2 Userback include I Feedback and bug-report management for product teams: organisational records, multi-user. include Feedback and bug-report management for product teams: organisational records, multi-user. 1.0 Develop and Manage Products and Services 2.0 build

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]);