MétaCan
ENFR
Menu
Cohort builder

4,299,418 works, Canadian by any of four routes.

Every filter state is a URL; the URL is the query; the query is citable via /q/⟨hash⟩. The page, the API and the export parse the same parameters.

Export CSVExport JSONAPI query

The current cohort, streamed from the database: every work column, the machine labels, the provisional scores, and the per-row validation status. Exports are capped at 100,000 rows. Mints a permanent /q/ link for this exact query. The same filters always produce the same link, whoever asks.

Search term
Year range
→
Sort
Language
Type
Field
Venue
Topic
Software Engineering Techniques and Practices
Retraction
Abstract
Evidence source
Study design
Label agreement
Label status

Direct Codex and Gemma labels are unvalidated and sparse. Distilled predictions cover the full frame and are also unvalidated. Choose the evidence source explicitly; absence of a direct label is never a negative label.

affaffiliation
fundfunder
venuejournal
aboutaboutness

The four routes compose: require the funder route and exclude affiliation to get the funder-only stratum no affiliation-based frame ever sees.

1,138 results · 1 filter active ·
Categories
Machine labels · sparse coverage
Evidence
An unlabeled work is unknown, not a negative. Label coverage is reported on every query.
1,138 works in the cohort · of 4,299,418page 1 of 23

Labels cover 1 of 1,138 works in this cohort. The rest are unlabeled, which is not a negative label: the label table is sparse today and grows as labeling rounds land.

Distilled predictions cover 1,138 of 1,138 works in this cohort. Predictions are machine_predicted_unvalidated teacher distillation outputs. Candidate is the union; consensus is the intersection.

fundno affno abstractunlabeled
Experimentation in Software Engineering
2000· book· en· Kluwer international series in software engineering· Computer Science
distilled prediction:candidate · metaepi_narrowconsensus · none
1,769
citations
affunlabeled
Boundary work in knowledge teams.
2009· article· en· Journal of Applied Psychology· Computer Science
distilled prediction:candidate · noneconsensus · none
305
citations
affunlabeled
How to read a paper
2007· article· en· ACM SIGCOMM Computer Communication Review· Computer Science
distilled prediction:candidate · noneconsensus · none
139
citations
affunlabeled
Trade-off Analysis for Requirements Selection
2003· article· en· International Journal of Software Engineering and Knowledge Engineering· Computer Science
distilled prediction:candidate · noneconsensus · none
114
citations
affunlabeled
Status Quo in Requirements Engineering
2019· article· en· ACM Transactions on Software Engineering and Methodology· Computer Science
distilled prediction:candidate · metaepi_narrowconsensus · none
112
citations
affno abstractunlabeled
What do software architects really do?
2008· article· en· Journal of Systems and Software· Computer Science
distilled prediction:candidate · noneconsensus · none
107
citations
affno abstractunlabeled
Knowledge Sharing in Agile Software Teams
2004· book-chapter· en· Lecture notes in computer science· Computer Science
distilled prediction:candidate · metaepi_narrowconsensus · none
93
citations
next →

How this was built: Screen · Findings · About