Claims

Collaborative features of Lab4CE saw very little use in the exploratory study

Claim · All claims
Evidence · 1 study · design r2 · q2
Currency · newest study 2017 · checked against its sources 2026-10-27 (automated, 1 of 1 entry) · not reviewed by a person

Subclaims

Reading the evidence codes

q is the design tier, i the impact, n the sample, and the kind with its r the rigour judged within that kind: what each code means.

This claim: no standardized effect is recorded in observations/ for it yet, so no benchmark reading is possible.

q2 i? Only 75 messages were posted in the public chat room (most without pedagogical interest), and only two students worked collaboratively, exchanging 7 posts in a private room. → Julien Broisin 2017

Evidence

Julien Broisin 2017

Julien Broisin, Rémi Venant & Philippe Vidal. (2017). Lab4CE: a Remote Laboratory for Computer Education. International Journal of Artificial Intelligence in Education 27:154–180. https://doi.org/10.1007/s40593-015-0079-3

q2 · i? · design · r2

Usage analysis of the exploratory study's collaboration data across the four sessions. The authors attribute the low collaboration to individual report requirements, students' unfamiliarity with remote collaboration, and activities not advanced enough to require peer help.

"Only 75 messages were posted on the public chat room of the experiment, most of them being without pedagogical interest. Only two students worked collaboratively on the same virtual machine and exchanged 7 posts within the matching private chat room."

Discussion

Page metadata
Field Value
type claim
id lab4ce-collaboration-low-usage
title Collaborative features of Lab4CE saw very little use in the exploratory study
description Collaborative features of Lab4CE saw very little use in the exploratory study
status review
evidence_strength weak
newest_evidence 2017
source_checked 2026-10-27
generated by process:wiki-ingest on 2026-10-27
trust unverified — no one has confirmed this page's content
sources 1 — julien-broisin-2017

Frontmatter is the page's machine-readable record — see the Schema & Guide.