MétaCan
Menu
Back to cohort
Record W2972532415

Primo VE Troubleshooting: Is it Primo? Is it Alma? Is it something else?

2019· article· en· W2972532415 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.

Bibliographic record

VenueBond University Research Portal (Bond University) · 2019
Typearticle
Languageen
FieldEngineering
TopicPower Systems and Technologies
Canadian institutionsUniversity of Manitoba
Fundersnot available
KeywordsTroubleshootingComputer science
DOInot available

Abstract

fetched live from OpenAlex

Hear from Primo VE sites all round the world to learn their top tips for troubleshooting Primo VE issues. Sometimes it is tricky to figure out whether the problem is arising in Alma, or is it something you have configured in Primo VE? Sometimes it’s just a plain thorny problem to sort out even if you know where to go. <br/>We all need a little help sometimes. If your Library is new to Primo VE, then this session may be especially helpful for you. In a series of lightning talks each presenter will: (1) Describe a problem or two they encountered in Primo VE, (2) Explain how they tracked down the cause, (3) Reveal the outcome. <br/>Troubleshooting stories cover integrations, FRBR and Dedup processes, local fields, custom search boxes and working with external data sources.

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 categoriesMeta-epidemiology (narrow), Insufficient payload (model declined to judge)
Consensus categoriesInsufficient payload (model declined to judge)
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: Not applicable
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.333
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.001
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0020.002
Science and technology studies0.0010.000
Scholarly communication0.0000.001
Open science0.0020.001
Research integrity0.0010.002
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.050
GPT teacher head0.271
Teacher spread0.221 · 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