MétaCan
Menu
Back to cohort
Record W2462144764 · doi:10.17645/up.v1i2.607

Planning with Citizens: Implementation of an e-Planning Platform and Analysis of Research Needs

2016· article· en· W2462144764 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.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueUrban Planning · 2016
Typearticle
Languageen
FieldSocial Sciences
TopicE-Government and Public Services
Canadian institutionsUniversity of Calgary
FundersCentro de Desarrollo Urbano Sustentable
KeywordsCitizen journalismPublic participationProcess (computing)Context (archaeology)Work (physics)Knowledge managementArchitectureParticipatory planningCitizen scienceComputer scienceProcess managementBusinessEngineeringPublic relationsWorld Wide WebPolitical science

Abstract

fetched live from OpenAlex

Citizen participation should be an essential part of an urban planning process if the needs of the local population are to be addressed. Citizen participation should also improve acceptance of private construction projects by residents that live in or near such development. A complementary form of citizen participation to public planning meetings is to permit citizen engagement via Web 2.0 technologies, which also has the potential to get citizens involved that are usually difficult to reach. We aim to build a social, i.e. participatory, planning platform that allows technology savvy citizens to inform themselves of future and ongoing development projects and to also discuss them online. In this work we discuss the functional needs and context-of-use constraints of such an e-planning platform. A conceptual model of the technical architecture is outlined and a prototype implementation is presented. This prototype is built on free and open source software components, including a social network, to enable platform adoption in other locations. Finally, we discuss the research needs that are to be addressed if the development of participatory e-planning platforms should advance.

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.

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.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.378
Threshold uncertainty score0.348

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.001
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0000.000
Research integrity0.0000.000
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.087
GPT teacher head0.413
Teacher spread0.326 · 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