MétaCan
Menu
Back to cohort
Record W2185338037

How to Create a Data Dictionary for an Oracle Database using

2012· article· en· W2185338037 on OpenAlexaboutno aff
Christopher Battiston

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldEngineering
TopicSAS software applications and methods
Canadian institutionsnot available
Fundersnot available
KeywordsOracleComputer scienceDilemmaQuality (philosophy)Task (project management)SoftwareWorld Wide WebProgramming languageEngineeringMathematicsEpistemology
DOInot available

Abstract

fetched live from OpenAlex

SAS®9.3 Christopher Battiston, SickKids, Toronto, Canada INTRODUCTION SAS® is one of the most versatile software packages available on the market today; with it you can analyse everything from genetics to market research, financial to quality and risk data all using variations of SAS. However, with that versatility comes a price sometimes there is something you absolutely have to do and cannot seem to find an easy way of doing it. When that happens, it is as if the earth stops; What do you mean I can't do this in SAS? you ask yourself. You spend sleepless nights online, looking at every paper Lex Jansen has, convinced someone has done what you're trying to accomplish. In some cases you may find that obscure paper with the lines of code you have been so desperately searching for. Sometimes, you don't then comes a hard decision; do you figure out a way of accomplishing your seemingly impossible task in SAS® or do you (gasp) go elsewhere? This was the decision I was forced to make, and I went with SAS® (obviously, because I am writing about it!). The dilemma how to make a data dictionary for an Oracle database, where PROC

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.016
metaresearch head score (Gemma)0.104
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: Not applicable
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.113
Threshold uncertainty score0.377

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0160.104
Meta-epidemiology (narrow)0.0010.002
Meta-epidemiology (broad)0.0020.002
Bibliometrics0.0060.005
Science and technology studies0.0010.001
Scholarly communication0.0070.008
Open science0.0030.004
Research integrity0.0020.006
Insufficient payload (model declined to judge)0.1130.141

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.242
GPT teacher head0.397
Teacher spread0.155 · 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

Citations0
Published2012
Admission routes1
Has abstractyes

Explore more

Same topicSAS software applications and methodsFrench-language works237,207