Publication History: A Double-DOI-Based Method for Storing and/or Monitoring Information about Published and Corrected Academic Literature
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.
Bibliographic record
Abstract
The status of published literature can change at any time in its history following publication, although existing structures in academic publishing for recording these changes, despite the existence of a number of robust tools—such as the digital object identifier (DOI)—appear to be insufficiently robust, or used too inconsistently or inefficiently, to deal with multiple corrections. In this article, an information storage method and corrective measure or tool is proposed—the ‘publication history’—that considers the full history and background of an article’s publication. The ‘publication history’ is adjusted to record changes to an article over time, and is thus a ‘live’ document, always open to modification and updating. The ‘publication history’ has the potential to accommodate, in a single document (in both PDF and HTML format), information about pre-publication (e.g., preprints) and post-publication events, including submission, resubmission, acceptance date, handling editors, peer-review format, corrections, expressions of concern, and retractions. The ‘publication history’ employs two DOIs, one for the article and one for any and all edits, to document these changes. Our proposal offers one possible solution for fortifying the integrity of peer review and the publication process pre- and post–peer review. The double-DOI-based ‘publication history’ can be applied to any document.
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 imitationNot 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.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.050 | 0.049 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.003 | 0.002 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.063 | 0.126 |
| Open science | 0.002 | 0.001 |
| Research integrity | 0.000 | 0.002 |
| Insufficient payload (model declined to judge) | 0.000 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it