MétaCan
Menu
Back to cohort
Record W7083696846 · doi:10.61669/001c.122845

A Collaborative Process to Establishing PLOs at a Canadian University

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

Bibliographic record

VenueIntersection A Journal at the Intersection of Assessment and Learning · 2024
Typearticle
Languageen
FieldComputer Science
TopicGeochemistry and Geologic Mapping
Canadian institutionsOkanagan University CollegeUniversity of British Columbia, Okanagan CampusUniversity of British Columbia
Fundersnot available
KeywordsProcess (computing)ObstacleStakeholderFace (sociological concept)Higher educationFoundation (evidence)Distance educationCollaborative learningAdult Learning

Abstract

fetched live from OpenAlex

In 2007, the Ministers of Education across Canada adopted the Canadian Degree Qualifications Framework, articulating learning outcomes for bachelor’s, master’s, and doctoral degrees. Yet, by 2016, only 30% of Canadian institutions reported having learning outcomes for all programs (MacFarlane & Brumwell, 2016). One obstacle institutions face when developing program learning outcomes (PLOs) is faculty resistance. Unfortunately, faculty participation is critical to successfully implementing PLOs. This paper describes the process used to develop PLOs in the Faculty of Science at UBC Okanagan, which is deeply collaborative and consultative, to gain faculty buy-in and initiate a positive culture around learning outcomes and assessment. This was accomplished by educating faculty on the benefits and rationale for implementing PLOs, fostering faculty ownership of PLOs, supporting faculty through the process, and engaging with various stakeholders. This collaborative process led to community building, increased stakeholder commitment, laid the foundation for future collaborations, and fostered robust PLOs.

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.001
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: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.492
Threshold uncertainty score0.634

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0010.000
Scholarly communication0.0000.001
Open science0.0000.000
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.008
GPT teacher head0.253
Teacher spread0.244 · 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