MétaCan
Menu
Back to cohort
Record W7099345175

Multidatabase Querying by Context 1 University of Calgary 2000-663-15 University of Manitoba TR-00-16

2008· article· en· W7099345175 on OpenAlexaboutno aff

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldEngineering
TopicSAS software applications and methods
Canadian institutionsnot available
Fundersnot available
KeywordsQuery languageViewSQLQuery by ExampleRelational databaseQuery optimizationData definition languageRDF query languageDatabase schemaSemantics (computer science)
DOInot available

Abstract

fetched live from OpenAlex

The overwhelming acceptance of the SQL standard [10] has curtailed continuing research work in relational database query languages and processing.Since all commercial relational database systems conform with the SQL standard, there is little motivation for developing new query languages. Despite its benefits and wide-spread acceptance, SQL is not a perfect query language.Complex database schema challenge even experienced database users during query formulation.As increasing numbers of less sophisticated users access numerous data sources within an organization or across the Internet, their ability to accurately construct queries with the appropriate structure and semantics diminishes.SQL can be hard to use as it provides only physical access transparency not logical transparency. That is, a user is responsible for mapping the semantics of their query to the semantics and structure of the database.Although graphical tools for query construction and high-level programming languages mask some of the complexity, the notion of querying by structure is intrinsic to most forms of data access. In this work, we overview a new query language developed in conjunction with our integration architecture for automatically integrating relational schema.Although the major focus of this work is on database interoperability, the contribution of this paper is a language for specifying queries on the

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.002
metaresearch head score (Gemma)0.003
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: Methods
Teacher disagreement score0.075
Threshold uncertainty score0.150

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0020.003
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0020.004
Science and technology studies0.0020.001
Scholarly communication0.0060.005
Open science0.0020.004
Research integrity0.0010.001
Insufficient payload (model declined to judge)0.0130.003

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.019
GPT teacher head0.200
Teacher spread0.181 · 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
Published2008
Admission routes1
Has abstractyes

Explore more

Same topicSAS software applications and methodsFrench-language works237,207