MétaCan
Menu
Back to cohort

Converting a Legacy Database to Object-Oriented Database

2005· book-chapter· en· W108265174 on OpenAlexaff
Reda Alhajj, Faruk Polat

Bibliographic record

VenueIGI Global eBooks · 2005
Typebook-chapter
Languageen
FieldComputer Science
TopicAdvanced Database Systems and Queries
Canadian institutionsUniversity of Calgary
Fundersnot available
KeywordsRelational databaseDatabaseComputer scienceDatabase modelDatabase designObject (grammar)Relational modelDatabase theoryViewDatabase schemaRealmArtificial intelligence

Abstract

fetched live from OpenAlex

We present an approach to transfer content of an existing conventional relational database to a corresponding existing object-oriented database. The major motivation is having organizations with two generations of information systems; the first is based on the relational model, and the second is based on the object-oriented model. This has several drawbacks. First, it is impossible to get unified global reports that involve information from the two databases without providing a wrapper that facilitates accessing one of the databases within the realm of the other. Second, organizations should keep professional staff familiar with the system. Finally, most of the people familiar with the conventional relational technology are willing to learn and move to the emerging object-oriented technology. Therefore, one appropriate solution is to transfer content of conventional relational databases into object-oriented databases; the latter are extensible by nature, hence, are more flexible to maintain. However, it is very difficult to extend and maintain a conventional relational database.

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.004
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.009
Threshold uncertainty score0.031

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0020.004
Meta-epidemiology (narrow)0.0000.001
Meta-epidemiology (broad)0.0000.001
Bibliometrics0.0020.003
Science and technology studies0.0010.001
Scholarly communication0.0060.006
Open science0.0030.003
Research integrity0.0010.002
Insufficient payload (model declined to judge)0.0090.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.020
GPT teacher head0.265
Teacher spread0.245 · 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 designTheoretical or conceptual
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
Published2005
Admission routes1
Has abstractyes

Explore more

Same venueIGI Global eBooksSame topicAdvanced Database Systems and QueriesFrench-language works237,207