MétaCan
Menu
Back to cohort
Record W4376611448 · doi:10.3390/educsci13050492

Embracing Co-Design: A Case Study Examining How Community Partners Became Co-Creators

2023· article· en· W4376611448 on OpenAlex
Liam Murdock, Libby Osgood, Luke McCarvill

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

VenueEducation Sciences · 2023
Typearticle
Languageen
FieldEngineering
TopicDesign Education and Practice
Canadian institutionsUniversity of Prince Edward Island
Fundersnot available
KeywordsEngineering design processProduct designDesign educationExperience designCo-designDesign processProcess (computing)Qualitative researchProduct (mathematics)Research designPsychologyEngineeringComputer scienceSociologyOperations managementBusinessWork in process

Abstract

fetched live from OpenAlex

Co-design increases the number of voices in a design project, which enhances the experience for all co-creators and produces a better product. A case study is presented of a ten-month co-design project-based learning experience between two engineering design students and two community partners during a first-year engineering design course, which resulted in the implementation of the device across campus. This paper evaluates the elements of co-design in the design process that was employed, documents the design product that was produced, and examines the experience of the community partners through a qualitative study. Through a retrospective examination of artifacts and files, the design process demonstrated an increase in the amount of collaboration between co-creators as the project progressed and identified 15 iterations of the design. Comparing the experience of community partners throughout the design process, five themes emerged from the semi-structured interviews: (1) emotional effects, (2) physical and mental effects, (3) productivity, (4) safety, and (5) job satisfaction. Documenting the experience of community partners throughout the design project can encourage educators to adopt co-design practices in project-based learning.

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.003
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: Qualitative · Consensus signal: Qualitative
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.489
Threshold uncertainty score0.734

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0030.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.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.281
GPT teacher head0.457
Teacher spread0.176 · 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