MétaCan
Menu
Back to cohort
Record W2006333896 · doi:10.1504/ijpp.2009.023490

Building shared accountability into service transformation partnerships

2009· article· en· W2006333896 on OpenAlex
John Langford, Jeffrey Roy

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.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueInternational Journal of Public Policy · 2009
Typearticle
Languageen
FieldSocial Sciences
TopicE-Government and Public Services
Canadian institutionsUniversity of Victoria
Fundersnot available
KeywordsAccountabilityGeneral partnershipService delivery frameworkPublic relationsPublic administrationBusinessService (business)Corporate governanceGovernment (linguistics)Agency (philosophy)Public servicePolitical scienceSociologyMarketingFinance

Abstract

fetched live from OpenAlex

Governments at all levels in Canada have entered into partnerships with the industry to effect user-focused, cross-agency service integration and multichannel service delivery. This article examines the problem of developing shared accountability mechanisms for public-private service transformation partnerships, which satisfy the demands of new business relationships and traditional democratic governance values. It first explores the widening canvas of collaborative information technology-driven partnerships and then draws on the emerging shared accountability literature and practices to set out five conditions which should be met in the establishment of a shared accountability regime for such partnerships. These criteria statements are used to analyse the accountability provisions of a new partnership between Service BC (the lead service delivery entity for the British Columbia government) and a consortium led by IBM Canada. The most significant shortcoming would appear to be its very limited public dimension. The article ends with a discussion of how that problem might be addressed.

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.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.806
Threshold uncertainty score0.582

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0010.004
Open science0.0010.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.082
GPT teacher head0.398
Teacher spread0.316 · 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