MetaScope. ScopeTools

Table 1 Data

Table 1 and the reproducibility supplement, from one spreadsheet

Table 1 is pure rework — and the methodological reviewer now asks for the per-arm dataset and cited conversion notes.

You give

The extraction spreadsheet (.xlsx or .csv).

You get

Table 1 as .docx, the dataset as .json and .xlsx, and the handling notes as .md — ready for the supplementary material.

How it works

# Table 1
$ scopetools run table1-repro
Deterministic — no model.
It reads your extraction sheet, builds the study table, the per-outcome per-arm dataset (N/mean/SD or events/total), records every conversion and imputation with its reference (Wan, Luo, Hozo) and exports the dataset as .json and .xlsx.

Deterministic; from your extraction spreadsheet come four files: Table 1 (.docx), the per-outcome per-arm dataset (.xlsx plus a machine-readable .json) and handling notes that record every conversion and imputation with its reference (Wan, Luo, Hozo) — the package described as method in the supplementary material.

What it costs

5 credits per spreadsheet (US$0.25).

Charged only when it delivers — a failed run costs nothing.

Credits are shared across every MetaScope tool — buy once, spend anywhere.

Limits

Columns it cannot map are listed as warnings; fix the header and run again.

Frequently asked questions

What goes in the reproducibility package?
The per-arm dataset per outcome, the handling notes with cited conversion methods, and the machine-readable .json for Supplementary Data.
Do I need a template?
No; it maps your own columns and lists what it could not map.
Why does the reviewer want this?
It lets anyone recompute every pooled estimate from the reported arms.

Same spreadsheet, next table: the GRADE Summary of Findings — 5 credits.

Gabi runs it with youUpload the file, get the deliverable back.Charged only when it delivers — a failed run costs nothing.
Run this tool