MétaCan
Menu
Back to cohort
Record W4400884871 · doi:10.2196/54590

Data Lake, Data Warehouse, Datamart, and Feature Store: Their Contributions to the Complete Data Reuse Pipeline

2024· article· en· W4400884871 on OpenAlexvenueno aff
Antoine Lamer, Chloé Saint‐Dizier, Nicolás Paris, Emmanuel Chazard

Bibliographic record

VenueJMIR Medical Informatics · 2024
Typearticle
Languageen
FieldDecision Sciences
TopicData Quality and Management
Canadian institutionsnot available
Fundersnot available
KeywordsComputer scienceData warehouseMetadataIdentifierData sciencePipeline (software)SoftwareUSableDatabaseReuseData transformationFeature (linguistics)Adaptation (eye)World Wide Web

Abstract

fetched live from OpenAlex

Unlabelled: The growing adoption and use of health information technology has generated a wealth of clinical data in electronic format, offering opportunities for data reuse beyond direct patient care. However, as data are distributed across multiple software, it becomes challenging to cross-reference information between sources due to differences in formats, vocabularies, and technologies and the absence of common identifiers among software. To address these challenges, hospitals have adopted data warehouses to consolidate and standardize these data for research. Additionally, as a complement or alternative, data lakes store both source data and metadata in a detailed and unprocessed format, empowering exploration, manipulation, and adaptation of the data to meet specific analytical needs. Subsequently, datamarts are used to further refine data into usable information tailored to specific research questions. However, for efficient analysis, a feature store is essential to pivot and denormalize the data, simplifying queries. In conclusion, while data warehouses are crucial, data lakes, datamarts, and feature stores play essential and complementary roles in facilitating data reuse for research and analysis in health care.

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.076
metaresearch head score (Gemma)0.126
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesMetaresearch
Consensus categoriesnone
DomainCandidate signal: Reproducibility · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.924
Threshold uncertainty score0.401

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0760.126
Meta-epidemiology (narrow)0.0020.003
Meta-epidemiology (broad)0.0020.003
Bibliometrics0.0140.018
Science and technology studies0.0020.005
Scholarly communication0.0190.044
Open science0.0070.025
Research integrity0.0030.011
Insufficient payload (model declined to judge)0.0080.006

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.278
GPT teacher head0.467
Teacher spread0.188 · 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.

Study designTheoretical or conceptual
DomainReproducibility
GenreEmpirical

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

Citations5
Published2024
Admission routes1
Has abstractyes

Explore more

Same venueJMIR Medical InformaticsSame topicData Quality and ManagementFrench-language works237,207