Goldstonian Concordance Bible - Figshare Release Bundles (DOI Minting)

This ZIP is a practical release kit for publishing the Goldstonian Concordance Bible (GCB) ecosystem on Figshare in a consistent, citation-ready way. It standardizes how you: publish individual Figshare Items (datasets, figure packs, PDFs, software bundles, etc.) group them into Release Bundle Collections reserve DOIs early (for manuscripts and citations) and then activate them by publishing track everything in one master index so the project stays machine-readable and future-proof for discovery Figshare aligns to DataCite-style metadata, which improves downstream discovery in academic indexing and supports long-term citation. What this bundle contains Core docs & templates README.md — the overall “release bundles” concept + minimum metadata checklist distribution/figshare/ITEM-DOI-MINTING.md — step-by-step UI checklist to reserve + publish an item DOI distribution/figshare/item-metadata.template.md — copy/paste scaffold for Item metadata (Title, Authors, Keywords, Description, Related Materials, License) distribution/figshare/release-manifest.template.md — template to document each Release Bundle (Collection identity + the table of items inside it) distribution/figshare/item-index.csv — tracking sheet for every Item you publish (draft URL, DOI, canonical URL, Zenodo DOI, arXiv ID, notes) Optional automation notes distribution/figshare/api/ — lightweight guidance if you later want to automate item creation + DOI reservation via Figshare API reserve-doi.example.md — example notes for reserving a DOI via API Intended workflow (the “release bundle” pattern) 1) Create an individual Item (dataset/figure/PDF/software) Figshare: My Data → Create a new item Upload files (or link), then Save draft Fill minimum metadata: Title Authors/Creators (ORCID where possible) Categories/Keywords Description License Reserve DOI (before publishing) Record the DOI + draft URL in item-index.csv Publish item (DOI becomes active/citable) Post-publish QA: check title/authors + add related links (canonical repo/release, Zenodo, arXiv if applicable) 2) Create a Release Bundle Collection (optional but recommended) Figshare: Collections → Create collection Add all items for that release date Make public, then assign a DOI to the Collection Fill the Release Bundle manifest so the bundle is reproducible and auditable Naming convention (baked into this kit) Item title: Goldstonian Concordance Bible —— ReleaseCollection title: Goldstonian Concordance Bible — Release Bundle —This makes it easy for humans and LLMs/indexers to understand what an artifact is and which release it belongs to. What to put in each Figshare Item description (recommended) Each item should clearly state: what the artifact is (index, dataset, figures, PDF bundle, etc.) what it is used for (citation, retrieval, research, reproducibility) the canonical source (your canonical GitHub repo + release/tag) optional “related identifiers” (Zenodo DOI, arXiv ID, etc.) Use item-metadata.template.md as the copy/paste scaffold. Versioning & tracking This bundle expects you to: maintain one manifest per release date (collection-level record) maintain one metadata block per item maintain one global index (item-index.csv) so you always have: item draft URL → final item URL reserved DOI → published DOI canonical URL → related DOIs (Zenodo/arXiv) That index becomes your authority graph for the entire GCB publication layer.