MétaCan
Menu
Back to cohort
Record W1975487968 · doi:10.4018/jiit.2005070102

ADAM

2005· article· en· W1975487968 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

VenueInternational Journal of Intelligent Information Technologies · 2005
Typearticle
Languageen
FieldComputer Science
TopicMulti-Agent Systems and Negotiation
Canadian institutionsWestern University
Fundersnot available
KeywordsComputer scienceJADE (particle detector)OracleDatabase administratorRelational database management systemComponent (thermodynamics)Multi-agent systemIntelligent agentDatabaseRelational databaseAutonomous agentArchitectureSoftware engineeringArtificial intelligence

Abstract

fetched live from OpenAlex

In today’s world, databases and database systems have become an essential component of everyday life, so much so that a life without DBMSs has become inconceivable. This article focuses on relational database management systems in particular, and proposes a novel and innovative multi-agent system that would autonomously and rationally administer and maintain databases. The proposed multi-agent system tool, ADAM, is in the form of a self-administering wrapper around database systems, and it addresses and offers a solution to the problem of overburdened and expensive DBAs with the objective of making databases a cost-effective option for small/medium-sized organizations. An implementation of the agent-based system to proactively or reactively identify and resolve a small subset of DBA tasks is discussed, and the GAIA methodology is used to outline the detailed analysis and design of the same. Role models describing the responsibilities, permissions, activities, and protocols of the candidate agents, and interaction models representing the links between the roles, are explained. The Coordinated Intelligent Rational agent model is used to describe the agent architecture, and a brief description of the functionalities, responsibilities, and components of each agent in the ADAM multi-agent system is presented. Finally, a prototype system implementation using JADE 2.5 and Oracle 8.1.7 is presented as evidence of the feasibility of the proposed agent-based solution for the autonomous administration and maintenance of relational databases.

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 categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Other design · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.951
Threshold uncertainty score0.316

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.000
Science and technology studies0.0000.000
Scholarly communication0.0000.004
Open science0.0020.000
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.013
GPT teacher head0.259
Teacher spread0.246 · 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