MétaCan
Menu
Back to cohort
Record W2073158914 · doi:10.1300/j120v46n95_05

Evaluating Virtual Reference from the Users’ Perspective

2006· article· en· W2073158914 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

VenueThe Reference Librarian · 2006
Typearticle
Languageen
FieldSocial Sciences
TopicLibrary Science and Information Literacy
Canadian institutionsWestern University
Fundersnot available
KeywordsComputer sciencePerspective (graphical)Reference modelService (business)Reference dataVirtual machineWorld Wide WebPsychologyDatabaseArtificial intelligence

Abstract

fetched live from OpenAlex

Abstract This article discusses the evaluation of virtual reference services from the user perspective. It is one outcome of a long-term research project, The Library Visit Study, which has been conducted in three phases at the University of Western Ontario for more than a decade. These studies have identified the need for, and essential components of, reference interviews and good reference behaviors. The third phase of this research focuses on the factors that make a difference to the users’ satisfaction with their virtual reference experience and whether these are the same or different from the ones we identified as important in face-to-face reference. An examination of user accounts of virtual reference transactions indicates that the reference interview has almost disappeared. Among the reasons identified for staff failure to conduct reference interviews in the virtual environment are: the nature of written vs. spoken interaction; the librarian's perceived need to respond quickly in this environment; and the rudimentary nature of the forms used in e-mail reference. The article includes a list of behaviors that users identified as either helpful or unhelpful and concludes with some implications of the research for good virtual reference service.

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 categoriesScience and technology studies, Insufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.638
Threshold uncertainty score0.999

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.0020.001
Scholarly communication0.0010.009
Open science0.0020.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0020.001

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.098
GPT teacher head0.354
Teacher spread0.255 · 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