MétaCan
Menu
Back to cohort
Record W2484021251 · doi:10.1145/2963143

The Six Pillars for Building Big Data Analytics Ecosystems

2016· review· en· W2484021251 on OpenAlexaff
Shadi Khalifa, Yehia Elshater, Kiran Sundaravarathan, Aparna Krishna Bhat, Patrick Martin, Fahim T. Imam, Dan Rope, Mike McRoberts, Craig Statchuk

Bibliographic record

VenueACM Computing Surveys · 2016
Typereview
Languageen
FieldBusiness, Management and Accounting
TopicBig Data and Business Intelligence
Canadian institutionsIBM (Canada)Queen's University
Fundersnot available
KeywordsAnalyticsComputer scienceBig dataData scienceProcess (computing)Data analysisEcosystemWeb analyticsWorld Wide WebData miningEcologyThe InternetWeb intelligence

Abstract

fetched live from OpenAlex

With almost everything now online, organizations look at the Big Data collected to gain insights for improving their services. In the analytics process, derivation of such insights requires experimenting-with and integrating different analytics techniques, while handling the Big Data high arrival velocity and large volumes. Existing solutions cover bits-and-pieces of the analytics process, leaving it to organizations to assemble their own ecosystem or buy an off-the-shelf ecosystem that can have unnecessary components to them. We build on this point by dividing the Big Data Analytics problem into six main pillars. We characterize and show examples of solutions designed for each of these pillars. We then integrate these six pillars into a taxonomy to provide an overview of the possible state-of-the-art analytics ecosystems. In the process, we highlight a number of ecosystems to meet organizations different needs. Finally, we identify possible areas of research for building future Big Data Analytics Ecosystems.

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.019
metaresearch head score (Gemma)0.014
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: Theoretical or conceptual
GenreCandidate signal: Review · Consensus signal: Review
Teacher disagreement score0.022
Threshold uncertainty score0.100

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0190.014
Meta-epidemiology (narrow)0.0020.002
Meta-epidemiology (broad)0.0010.002
Bibliometrics0.0110.014
Science and technology studies0.0050.013
Scholarly communication0.0220.036
Open science0.0050.015
Research integrity0.0100.013
Insufficient payload (model declined to judge)0.0050.005

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.357
GPT teacher head0.390
Teacher spread0.033 · 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
GenreReview

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

Citations45
Published2016
Admission routes1
Has abstractyes

Explore more

Same venueACM Computing SurveysSame topicBig Data and Business IntelligenceFrench-language works237,207