Publishing infrastructure · Open metadata · Rights-first workflow

Open Book Publishing & Metadata Infrastructure

English institutional workflow for preparing Rawafid / Health Renewal open-book metadata for Thoth Oasis, including rights, identifiers, ONIX readiness, translation provenance, public-record safeguards, and quality control.

Policy version 1.0 · 12 September 2026Production records onlyIndexable · Stable canonical

Independence notice: this is Rawafid / Health Renewal's own implementation and governance workflow. Mention of Thoth Open Metadata does not imply that Thoth has reviewed, endorsed, accredited, or scientifically validated Rawafid, this page, or any future title.

Scope before tooling

What Thoth means in the Rawafid publishing workflow

Rawafid uses a rights-first model: a metadata platform is not a substitute for publishing authority, copyright clearance, editorial review, or scientific quality assurance. Thoth Oasis is treated as a structured metadata-management and export layer for eligible open-access books and chapters.

Oasis: metadata layer

Thoth describes Oasis as its free self-service metadata platform. It supports structured metadata management and standards-based exports. Rawafid prepares records before entry so public metadata is complete, attributable, and internally auditable.

Public metadata, not a sandbox

Thoth's terms make metadata publicly accessible and available under CC0. Rawafid therefore does not create placeholder or speculative production records. A title must pass the authority, rights, editorial, identifier, and metadata gates first.

Distribution is a separate decision

Automated distribution, DOI registration support, hosting, and archiving are separate services in Thoth's added-value packages. This page does not claim that those services are enabled for Rawafid or that a title has been distributed anywhere.

Prevent publisher-role confusion

Three publishing lanes

A. Rawafid-original titles

Books genuinely published by Rawafid / Health Renewal can enter the production workflow after authorship, publishing authority, edition identity, copyright, licence, and quality-control records are complete.

B. Authorised translations

A translated title requires a documented legal basis: an open licence that permits the intended translation/adaptation or written permission. The translated edition must retain source-work provenance, translator credit, source identifiers, and licence compatibility.

C. Third-party discovery only

Books published by another publisher remain that publisher's works. Rawafid may discover, cite, review, or link to lawful sources, but it does not create a Rawafid publisher record for them without explicit publishing or metadata-management authority.

Zero speculative public records

Mandatory pre-ingest gates

Authority & rights

  • Publisher/co-publisher/authorisation evidence.
  • Copyright holder confirmed.
  • Licence text and URL verified for the exact edition.
  • Translation/adaptation rights documented when relevant.
  • Cover, images, and third-party material cleared separately.

Editorial & quality

  • Final title/subtitle and edition fixed.
  • Contributor names and roles checked.
  • Citations and references reviewed where applicable.
  • Scientific/technical review completed for health and education titles.
  • Accessibility and file-readiness checks completed for released formats.

Identifiers & metadata

  • ISBN mapped to the correct format/edition.
  • DOI used only where legitimately assigned.
  • ORCID/ROR links verified rather than guessed.
  • Subjects, description, language, dates, URLs, and licence normalized.
  • Canonical source and verification date recorded.
Rawafid pre-ingest profile

Minimum metadata readiness profile

This profile is deliberately stricter than a simple title spreadsheet. It is the internal minimum Rawafid aims to have available before a public production record is created.

Field group 1

Record status and internal work identifier

Field group 2

Title, subtitle, edition, language, and publication date

Field group 3

Publisher and imprint identity

Field group 4

Contributors, contributor roles, and ORCID where available

Field group 5

ISBNs by format and DOI where applicable

Field group 6

Series and work/edition relationships

Field group 7

Abstract, keywords, Thema/BISAC subjects, and audience

Field group 8

Open-access status, copyright holder, licence name, and licence URL

Field group 9

Canonical landing page and format-specific access URLs

Field group 10

Translation source, source identifier, translator credit, and permission basis when relevant

Field group 11

Funder/institution identifiers such as ROR where relevant

Field group 12

Metadata source, verification date, reviewer, and correction provenance

Controlled production path

From book file to public metadata record

1. Authority gate

Confirm that Rawafid / Health Renewal is the publisher, co-publisher, or explicitly authorised metadata manager for the work. A discovery relationship alone is not enough.

2. Rights gate

Document copyright ownership, the exact licence for each released format, cover/illustration rights, and any translation or adaptation permission.

3. Editorial and scholarly gate

Confirm that the release has completed the applicable editorial, scientific, accessibility, citation, and conflict-of-interest checks before public metadata is created.

4. Identifier gate

Validate title-level and format-level ISBNs, DOI where applicable, contributor ORCID records, and organisation/funder identifiers such as ROR.

5. Metadata normalization

Normalize names, roles, dates, languages, subjects, descriptions, relationships, URLs, and licence values in the Rawafid pre-ingest record.

6. Thoth entry or bulk upload

Create the production record through the Thoth interface or use the current official CSV/ONIX bulk-upload template. The Rawafid worksheet is not a substitute for the current Thoth template.

7. Public-record verification

After creation, inspect the public record, identifiers, contributor roles, licence, landing links, and exports. Correct inconsistencies rather than allowing stale metadata to propagate.

8. Export and downstream validation

Validate required ONIX/MARC/KBART/CSV/BibTeX or other exports for the intended workflow. Distribution, hosting, DOI sponsorship, and archiving are treated as separate services and decisions.

Translation provenance is metadata

Additional controls for translated books

Translation work must not begin from the assumption that “open access” automatically permits translation. The team records the exact licence or written permission, source edition, source publisher, source ISBN/DOI, translator(s), review responsibility, modification notes, and the licence applied to the translated edition.

Source identity

Preserve the original title, edition, publisher, publication date, canonical URL, ISBN/DOI, and source language so the relationship can be audited later.

Permission basis

Record whether translation is permitted by the source licence or by explicit written authorisation. If permission is conditional, retain those conditions in the internal rights record.

Derivative-edition transparency

Credit translators and reviewers, distinguish translation from adaptation, disclose material changes, and never imply that the source publisher or author reviewed the Arabic edition unless that review actually occurred.

Public metadata needs maintenance

Corrections, withdrawals, and provenance

Because metadata can propagate into catalogues and downstream systems, corrections are treated as publication maintenance rather than cosmetic edits. Rawafid keeps a verification date, change reason, responsible reviewer, and previous value where material. If a production record must be withdrawn or deleted, the team follows Thoth's current support procedure instead of assuming that a public record can be silently erased.

Withdrawal of a book, replacement of a file, a corrected edition, a changed licence, or a contributor correction must be reflected consistently in the canonical landing page and metadata record. A new edition is not silently overwritten as if it were the same manifestation.

Operational asset

Rawafid metadata-readiness template

Use the CSV below to collect and verify a title before entry into Thoth. It is intentionally a Rawafid pre-ingest worksheet, not an official Thoth import file. For an actual bulk upload, download the current CSV or ONIX template from the Thoth interface and map only verified production data.

Current implementation boundary

What is ready, and what is deliberately not claimed

Ready

Publisher-integrity rules, a rights-first intake model, a metadata-readiness profile, a pre-ingest worksheet, a public discovery/licence guide, canonical/indexable pages, and post-deployment checks.

Title-level production

No book should be described here as successfully published or distributed through Thoth until its actual production record and relevant downstream outputs have been verified.

No implied partnership

Rawafid's use of Thoth infrastructure is not described as accreditation, scientific review, endorsement, or institutional supervision by Thoth unless a separate written relationship explicitly says so.

Operational FAQ

Frequently asked questions

Does a Thoth metadata record mean Thoth reviewed or endorsed the book?

No. It is a metadata and publishing-infrastructure record, not a scientific endorsement or accreditation.

Can Rawafid create records for another publisher's books?

Only with documented authority that permits Rawafid to act as publisher/co-publisher or metadata manager for those works. Otherwise, the correct role is discovery, citation, review, or linking.

Does CC0 metadata make the PDF, EPUB, cover, or text CC0?

No. The metadata and the work's content are separate rights layers. Each file and content component must be checked under its own licence and permissions.

Is the downloadable CSV the official Thoth bulk-upload template?

No. It is our quality-control worksheet. The current official template must be obtained from Thoth at the time of upload.

Primary documentation

Official Thoth sources used for this workflow

Checked 12 September 2026