Reporting guidelines used varying methodology to develop recommendations
Bibliographic record
Abstract
BACKGROUND AND OBJECTIVES: We investigated the developing methods of reporting guidelines in the EQUATOR (Enhancing the QUAlity and Transparency Of health Research) Network's database. METHODS: In October 2018, we screened all records and excluded those not describing reporting guidelines from further investigation. Twelve researchers performed duplicate data extraction on bibliometrics, scope, development methods, presentation, and dissemination of all publications. Descriptive statistics were used to summarize the findings. RESULTS: Of the 405 screened records, 262 described a reporting guidelines development. The number of reporting guidelines increased over the past 3 decades, from 5 in the 1990s and 63 in the 2000s to 157 in the 2010s. Development groups included 2-151 people. Literature appraisal was performed during the development of 56% of the reporting guidelines; 33% used surveys to gather external opinion on items to report; and 42% piloted or sought external feedback on their recommendations. Examples of good reporting for all reporting items were presented in 30% of the reporting guidelines. Eighteen percent of the reviewed publications included some level of spin. CONCLUSION: Reporting guidelines have been developed with varying methodology. Reporting guideline developers should use existing guidance and take an evidence-based approach, rather than base their recommendations on expert opinion of limited groups of individuals.
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 imitationNot 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.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.705 | 0.917 |
| Meta-epidemiology (narrow) | 0.005 | 0.006 |
| Meta-epidemiology (broad) | 0.008 | 0.011 |
| Bibliometrics | 0.040 | 0.036 |
| Science and technology studies | 0.005 | 0.009 |
| Scholarly communication | 0.019 | 0.021 |
| Open science | 0.012 | 0.013 |
| Research integrity | 0.009 | 0.010 |
| Insufficient payload (model declined to judge) | 0.004 | 0.002 |
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 itClassification
machine, unvalidatedMachine predicted; the direct Gemma label and the distilled Codex classifier agree on what is shown here.
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".