MétaCan
Menu
Back to cohort
Record W1491166376 · doi:10.18352/lq.7656

Why the Bath Profile Makes Z39.50 Work

2001· article· en· W1491166376 on OpenAlexfundno aff
Peter Gethin

Bibliographic record

VenueLIBER Quarterly The Journal of the Association of European Research Libraries · 2001
Typearticle
Languageen
FieldComputer Science
TopicLibrary Collection Development and Digital Resources
Canadian institutionsnot available
FundersMemorial University of Newfoundland
KeywordsComputer scienceTask (project management)Consistency (knowledge bases)ImplementationStandard Model (mathematical formulation)Work (physics)Protocol (science)Information retrievalSoftware engineeringArtificial intelligence

Abstract

fetched live from OpenAlex

The Z39.50 standard has been in productive use for several years now. However, due to the way the standard has been interpreted by some Integrated Library System (ILS) vendors, the results of using the standard have often been somewhat varied at best and, at worst, non functional. The lack of consistency in the use of Z39.50 has lead to the standard being held in rather lower regard than it deserves in some quarters. It is a matter that can be debated whether the inconsistency in the implementation of the standard is the fault of the implementers ignoring aspects of the standard to make their task simpler or simply a lack of precision in the standard itself. To circumvent the debate, the Z39.50 Implementers Group (ZIG) has defined profiles for the use of the standard that are clearly defined and can be measured. This paper takes a look back at why the Z39.50 standard was invented in the first place and defines briefly how Z39.50 works. The paper then considers why implementations of the standard appear to fail and how those failures manifest themselves. With this information in hand, it is possible to make sense of the answer to the question, how does the Bath profile make Z39.50 work?

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 imitation

Not 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.

metaresearch head score (Codex)0.043
metaresearch head score (Gemma)0.082
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.043
Threshold uncertainty score0.225

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0430.082
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0020.002
Science and technology studies0.0060.015
Scholarly communication0.0180.027
Open science0.0030.009
Research integrity0.0070.008
Insufficient payload (model declined to judge)0.0070.009

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.031
GPT teacher head0.246
Teacher spread0.215 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designNot applicable
Domainnot available
GenreMethods

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".

Quick stats

Citations1
Published2001
Admission routes1
Has abstractyes

Explore more

Same venueLIBER Quarterly The Journal of the Association of European Research LibrariesSame topicLibrary Collection Development and Digital ResourcesFrench-language works237,207