Biblica Base Plan

Global Project ManagerSets the Working Project progress parameters for the increment in the Paratext Registry – Scope: (Current Increment) – Status: Active – Expected Completion Date: (Current Increment)

Area Project Manager – Sets Scope of the increment in Project Properties – Assigns tasks to team members – Sets task due datesAfter thorough exegesis, Translators: – draft/revise chapters assigned to them: – resolve issues found by basic checks – use the Wordlist tool to check spelling – approve Major Biblical Terms using the Biblical Terms tool – use Parallel Passage tool – draft/revise book introductionsLinguist/Translator – Approves spelling and hyphenation using Wordlist tool

Technical Manager – Verifies checks are correctly done – Verifies markup is correctly applied – Cleans up any errors or inconsistencies

ChapterVerse; Marker; Character; Punctuation; Reference; QuotedText; RepeatedWord; MatchedPairs; Quotation; Numbers; Capitalization

Words with Unknown spelling status; Words with Incorrect spelling status

Notes Assigned to Me; Project Notes (Conflict)

Biblical Terms renderings found

Language Expert – Reads through text – Flags grammatical, clarity, and naturalness errors with “To Do” notesUsing Wordlist tool: – runs advanced spelling checks – marks misspelled word as incorrect – creates or comments on Spelling Discussion Notes

Co-translator – Makes suggestions using “To Do” Notes – Creates or comments on Rendering Discussion Notes (Biblical Terms tool)Suggested activities: – responds to translator notes – reads aloud for naturalness – checks against a model text for accuracy

Translation team – Organizes oral group reading of the entire text increment – Solicits comments from select members of the language community using “Guidelines for Oral Testing” document – Adds recommendations to the project as “To Do” notes

Translator – Reviews Co-translator, Language Expert, and community feedback – Resolves as many “To Do” notes as possible – Changes unresolved notes to “Consultant Check” notes – Edits text as necessary

Third-party Reader – Checks for orthography, punctuation, grammar, and written style using “Guidelines for Literary/Stylistic Check” documentMay use one or more of the following options:A. Flag errors with “To Do” notes in Paratext or Paratext LiteB. Edit the text directly in ParatextC. Comment on a Print Draft printout or PDF of the text

Consultant – Checks text using interlinear tool, parallel passage tool, and back translation if availableCreates or responds to: – “To Do” and “Consultant Check” notes – Rendering Notes in the Biblical Terms tool – Spelling Notes in the Wordlist tool

Translator – Does the Parallel passage check with consultant guidance – Resolves “To Do” and “Consultant Check” notes – Resolves Spelling Discussion Notes (Wordlist tool) – Resolves Rendering Discussion Notes (Biblical Terms tool) – Makes changes to text as necessary based on Notes and Parallel Passage check

Spelling Discussion Notes

Spelling Discussion Notes; Renderings Discussion Notes

Parallel Passages

Translation team – Completes translation of metatext in FRT and BAK books – Writes preface

Translators – Resolve any issues found by the Project Manager, Technical Manager, and Technical Director – Make changes to text as necessary

Area Project Manager or Translation Consultant – Verifies all tasks and checks have been done and all Notes resolved – If necessary, sends project back to the translation team to resolve outstanding issues

Project Technical Manager – Verifies that errors have not been denied inappropriately – Verifies that checking inventories have been marked correctly – Looks for additional issues that might need to be addressed using advanced checks and tools – Resolves as many checking issues as possible – If necessary, sends project back to the translation team to resolve outstanding issues

Translation Technology Director or designee: – Approves the quality of all Paratext checks – If necessary, sends project back to Technical Manager to resolve outstanding issues – Creates/Updates Publishing Project (PP) – Sets Paratext Registry Status to Typesetting (WP&PP) – With Global Project Manager input, authorizes the Project Manager to set the Scope in Project Properties and begin First Draft Editing of the next increment (Task 1.2)

Community members review the Preliminary Typeset using “Guidelines for Preliminary Typeset Review” document

Translation Technology Director or designee, in consultation with designated member of the translation team: – Resolves issues discovered during Preliminary typeset review – Corrects the Publishing ProjectTranslation team member – Updates the Working Project

Translation team proofreads the Final Typeset to correct inadvertent typesetting errors using “Guidelines for Final Typeset Proofread” document

Translation Technology Director or designee – Resolves any errors in the Publishing ProjectTranslation team member – Verifies corrections – Updates the Working Project

VP, Global Translation – Signs off on the translation project – Indicates completed status on the translation dashboard

Translation Technology Director – Submits completed books to the Digital Bible Library (DBL) – Sets Paratext Registry Status to Published (PP) – Authorizes the Global Project Manager to set the progress parameters for the next Project Increment in the Paratext Registry (WP) (Task 1.1)