Scholar Review Studio

The need

Final manuscripts need consistent checks for text extraction, abstract agreement, captions, callouts and submission-file integrity.

Why it was developed

Run repeatable local technical preflight and evidence-linked manuscript observations before manual editorial review.

How to use it

1. Install Python, then double-click Launch Scholar Review Studio.cmd. The launcher creates the environment and opens the app at http://localhost:8501.
2. Alternatively install requirements.txt into an activated virtual environment and run streamlit run app.py.
3. Upload a local manuscript for checks; for final preflight supply the exact blinded manuscript DOCX, title-page DOCX and portal abstract.
4. Optional model review uses a locally running Ollama service. Review every observation before editing the paper.

How it can save time or money

Finds recurring abstract, numbering and callout discrepancies in one pass; repeatable checks reduce manual cross-checking after each document revision.

These are potential benefits, not measured savings. Include setup, maintenance, review and local operating costs when comparing your own workflow.

Current scope & limits

Technical preflight does not validate scientific novelty, establish acceptance likelihood or replace expert review. OCR quality varies. Source manuscripts and review reports are excluded.