MétaCan
Menu
Back to cohort
Record W2763626063

Open Data and Big Data Programs in Local Government Policy Analysis

2014· article· en· W2763626063 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

aboutThe title or abstract carries a Canadian signal from the geographic lexicon.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueScholarship@Western (Western University) · 2014
Typearticle
Languageen
FieldComputer Science
TopicPrivacy-Preserving Technologies in Data
Canadian institutionsnot available
Fundersnot available
KeywordsOpen dataBig dataGovernment (linguistics)Local governmentComputer scienceOpen governmentData scienceBusinessPolitical sciencePublic administrationWorld Wide WebData mining
DOInot available

Abstract

fetched live from OpenAlex

This paper examines the development of policy around the open data programs for local government. Through a literature review, a survey of large municipalities in Ontario, and in-depth interviews, the research attempts to identify if there are factors that ensure whether the policy development process is more likely to be implemented along with the program or if there is a lack of policy development as a result of it. The findings reveal a definite lack of policy development with the open data program, which is likely due to the challenge for policy makers to ensure appropriate access and privacy protection, as technology makes information more accessible, and there are also emerging social issues that result from different generational expectations and values.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Direct model labels (unvalidated)

Per-model category and study-design labels from the labeling rounds. They are machine output, unvalidated, and the disagreement between models ships as data. No study design here is MEDLINE-validated yet.

Model armCategoriesStudy designConfidence
gemmaOpen science
Domain: not available · Genre: Empirical
About the Canadian research system: no · About a Canadian topic: no
Observationallow
gptno category
Domain: not available · Genre: Empirical
About the Canadian research system: no · About a Canadian topic: no
Other designlow
models splitAgreement compares identical category sets and study designs across arms.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.002
metaresearch head score (Gemma)0.003
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow), Scholarly communication, Open science
Consensus categoriesOpen science
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.387
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.003
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0010.003
Science and technology studies0.0000.000
Scholarly communication0.0020.008
Open science0.1290.517
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.255
GPT teacher head0.356
Teacher spread0.101 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it