MétaCan
Menu
Back to cohort
Record W4285249993 · doi:10.2991/assehr.k.220504.321

A Review of JavaScript Object Notation in Data Analysis

2022· review· en· W4285249993 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

VenueAdvances in Social Science, Education and Humanities Research/Advances in social science, education and humanities research · 2022
Typereview
Languageen
FieldComputer Science
TopicAlgorithms and Data Compression
Canadian institutionsQueen's University
Fundersnot available
KeywordsComputer scienceJavaScriptProgramming languageNotationObject (grammar)Artificial intelligenceMathematicsArithmetic

Abstract

fetched live from OpenAlex

JSON is an extremely popular data format in the 2000s. It is used for transforming the data type. It is not different for reading and writing, and it is simple for machines. As time goes through the age of big data, there appears a group of applications, for example, the two that will be discussed in this essay: NoSQL and NewSQL, for data analysis and big data. The SQL database is always a popular database since the 1980s. In recent years, key-value storage, which always means NoSQL, became more and more popular. Also, the NewSQL database type was developed to solve a similar challenge more efficiently. This essay aims to find the application of these data formats in the real world. According to the research results, JSON could be used as the data format when the data are shifting between the Android application and the Web server.

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.022
metaresearch head score (Gemma)0.002
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow), Bibliometrics, Science and technology studies, Scholarly communication, Open science
Consensus categoriesScience and technology studies
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Review · Consensus signal: Review
Teacher disagreement score0.939
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0220.002
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0020.000
Bibliometrics0.0110.024
Science and technology studies0.0060.012
Scholarly communication0.0020.011
Open science0.0070.004
Research integrity0.0000.002
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.256
GPT teacher head0.544
Teacher spread0.288 · 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