Reference Desk Employees Need Both Research Knowledge and Technical Skills for Successful Reference Transactions
Bibliographic record
Abstract
A Review of: Chan, E. K. (2014). Analyzing recorded transactions to extrapolate the required knowledge, skills, and abilities of reference desk providers at an urban, academic/public library. Journal of Library Administration, 54(1), 23-32. doi:10.1080/01920836.2014.893113 Abstract Objective – To determine the essential knowledge and skills required by reference positions serving academic and public library patrons. Design – Data analysis of recorded reference transactions using author-created categories. Setting – The reference desk of a joint academic and public library in downtown San José, California. Subjects – A total of 9,683 in-person and phone reference transactions recorded between August 20 and December 29, 2012. Methods – All reference transactions recorded in the tracking software Gimlet during the fall 2012 semester were downloaded and analyzed in Excel using 17 author-created reference service categories. Of the original 13,827 transaction entries, 4,135 were eliminated because the actual reference questions, an optional entry in Gimlet, were not recorded. Thus these transactions could not be properly categorized for analysis. Main Results – The most frequently occurred type of reference transaction (16.6%, or 1,607 out of 9,683) out of the 17 categories was assistance for printing, copying, scanning, and wireless network assistance. The next most regularly recorded categories were catalog searching for non-known items (15.0%) and general research (10.9%), which included formulating research questions and selecting the appropriate resources for searching. When clustering the 17 reference question categories into 4 broader thematic groups, “research-oriented assistance,” including question categories for catalog searching and general research, emerged as the most common question type (31.7%). Technical and equipment assistance (30.8%) was the second most popular category group, followed by facility and policy questions (19.2%), and quick search requests (18.3%). Conclusion – The study findings suggest that successful reference desk transactions would require library employees to master research knowledge as well as technical computer and equipment skills.
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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.009 | 0.038 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.002 | 0.003 |
| Science and technology studies | 0.002 | 0.001 |
| Scholarly communication | 0.004 | 0.005 |
| Open science | 0.001 | 0.002 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.023 | 0.011 |
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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".