MétaCan
Menu
Back to cohort
Record W3125652129 · doi:10.5703/1288284317172

Approvals, Slips, and DDA! Oh My! The Yellow Brick Road to Collaborative Approval and DDA Profiling

2020· article· en· W3125652129 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

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicLibrary Collection Development and Digital Resources
Canadian institutionsPurdue Pharma (Canada)
Fundersnot available
KeywordsProfiling (computer programming)VendorWorkflowComputer scienceUpgradeLicenseWorld Wide WebEngineering managementBusinessEngineeringMarketingDatabaseOperating system

Abstract

fetched live from OpenAlex

In the last several years, approval profiling has changed significantly and grown increasingly complex, particularly due to the prevalent shift toward collecting in electronic formats. While approval profiles have been predominantly e-preferred for some time, the growth of demand-driven acquisition (DDA) has led to new license models, modes of acquisition, and tighter integration of DDA with approvals. With the advent of the DDA-preferred approval plan came options for the inclusion of multiple e-book platforms as well as complexities involving publisher embargoes. Additionally, the numerous approval and DDA profile parameters, workflow options, and administrator settings vary widely, resulting in a seemingly endless array of possibilities that can affect how titles are ultimately profiled. The task of creating a new profile or preparing profile reviews can be overwhelming, especially for those new to profiling or trying a new vendor. However, it can and should be a collaborative experience with vendors that leads to more than just great profiles. While library staff should strive to learn how to make the most of what a vendor offers, vendors should inquire about the library’s collection development strategies, issues, and needs. Vendors can also share current trends and offer advice modeled on how other libraries handle similar issues, as well as gather feedback for potential development. This paper supplies tips that will help library staff who are preparing to create or review approval or DDA profiles or to profile with new vendors, to be better prepared in order to maximize their time profiling with vendors.

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.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesScholarly communication
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.753
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0010.001
Open science0.0000.001
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

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.016
GPT teacher head0.200
Teacher spread0.184 · 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