This checklist provides guidance for translators who are in the process of translating Scriptures to successfully publish a Scripture App Builder app with appropriate attributions for copyright and licensing.<\/p>\n
Our analysis has shown that building quality checks into the front end of the translation process, keeping Paratext data clean (using tools to maintain completeness, consistency in term use and word spelling, etc.) can shave months of clean-up time off the back end of projects while providing a higher quality Scripture app. We encourage translators to use the tools included with Paratext<\/a> to keep data in good shape as the translation process proceeds.<\/p>\n Does the quality of the content to be published pass required publishing consistency checks in Paratext? The data quality of the content to be published needs to be high: spelling is consistent, key term use is verified, all chapters and verses to be published are complete, number and punctuation format is specified and followed, references used are present in version to be published, quotations are properly opened and closed, etc.<\/p>\n Paratext Basic Checks<\/a> (Checking \u2013 Run Basic Checks\u2026) pass all checks without errors.<\/p>\n Are the front matter and back matter prepared and ready to be included in your app? (optional content)<\/p>\n Y = VERIFY<\/strong> clean validation results in Paratext. Does this app only contain text on which a consultant with qualifications consistent with FOBAI (Forum of Bible Agencies International) standards has signed off? Has the translation been done consistent with SIL\u2019s DFT (Divine Familial Terms) standards? If an appropriate consultant has not signed off on the text or if DFT compliance is not assured by the translation consultant, SIL may NOT provide SAB services. STOP!<\/em>) Provide the name and email address of the last translation consultant who signed off on the Scripture content.<\/p>\n Y = VERIFY<\/strong> via email approval from Consultant, and\/or attachment of documentation to your Area Publishing Coordinator and GPS ScripturePubCoord_Intl@sil.org<\/a>. Go to Administrator Decision<\/strong>. Does this app have an SIL Entity Directorate-level sign off?<\/p>\n Y = VERIFY<\/strong> via email response from Directorate to your Area Publishing Coordinator and GPS ScripturePubCoord_Intl@sil.org<\/a>. Go to Consistency and DBL Bundle Decision<\/strong>. Does app text pass Paratext Scripture Text Consistency Checks and DBL Schema checks (Checks – (hold Shift key down and click) Run Basic Checks\u2026 and check only \u201cSchema\u201d)? If there are any errors, get help from your Area DBL Publishing representative or GPS lois_gourley@sil.org<\/a>.<\/p>\n After your app is published, the appropriate DBL publishing representative will submit your Scriptures to the DBL<\/p>\n a. Does this app only contain Scripture text?<\/p>\n Y =<\/strong> Go to Attribution Decision<\/strong> (licensing is most likely easy). b. Does this app contain illustrations, video and\/or audio recordings?<\/p>\n Y =<\/strong> Include each attribution and redistribution license from each content supplier in the app rights data. Go to Attribution Decision<\/strong>, or if licenses cannot be obtained STOP!<\/strong> This app cannot be redistributed<\/em>. Is this an SIL managed project? (is SIL funding and making the project decisions?)<\/p>\n Y =<\/strong> Go to Distribution Decision<\/strong>. a. Will this app be shared beyond the Google play store (e.g. also by Bluetooth, SD card, Wi-Fi, etc.)?<\/p>\n Y =<\/strong> Go to 7.b below. b. Do you have a redistribution (sharing) license for all additional content included in the App (written permission for anyone who gets this App to share it with others)?<\/p>\n Y =<\/strong> Include each license and attribution in the App rights data. Go to WBT App Attribution and License Statements<\/strong>. Copyright Information examples are below.<\/p>\n The Scriptures in <Language Name> (<language code>) Text: \u00a9 YYYY Wycliffe Bible Translators, Inc.\n<\/p>\n If this app also contains illustrations, video and\/or audio, add the appropriate statements. If there are multiple IP sources for a category, list each source and identify what artifact they contributed.<\/p>\n Artwork: Video:1. Translator Decision<\/h3>\n
\nN = STOP!<\/strong> SIL cannot provide services to produce this App.<\/em><\/p>\n2. Translation Consultant Decision<\/h3>\n
\nFOBAI Consultant Standards: http:\/\/www.forum-intl.org\/resources<\/a>
\nDFT compliance: http:\/\/www.sil.org\/translation\/sil-standards-translation-divine-familial-terms<\/a><\/p>\n
\nN = STOP!<\/strong> SIL cannot provide services to produce this App. Contact your Area Publishing Coordinator or Global Publishing Services (GPS) (ScripturePubCoord_Intl@sil.org<\/a>) with questions<\/em>.<\/p>\n3. Administrator Decision<\/h3>\n
\nN = STOP!<\/strong> SIL cannot provide services to produce this app. Contact your Area Publishing Coordinator or GPS with questions.<\/em><\/p>\n4. Consistency and DBL Bundle Decision<\/h3>\n
5. Content Decision<\/h3>\n
\nN =<\/strong> Go to item 5.b below [if the app contains additional types of content, then additional licenses will be needed for each type].<\/p>\n
\nN =<\/strong> Go to Attribution Decision<\/strong>.<\/p>\n6. Attribution Decision<\/h3>\n
\nN =<\/strong> You must obtain the appropriate approvals for attribution from each content supplier used, or if attribution cannot be obtained, STOP<\/strong> and remove the additional content! SIL cannot provide services to product this App<\/em>.<\/p>\n7. Distribution Decision<\/h3>\n
\nN =<\/strong> Go to WBT App Attribution and License Statements<\/strong>.<\/p>\n
\nN =<\/strong> Get a redistribution (sharing) license from each content supplier and include each in the App rights data, then go to WBT App Attribution and License Statements; or, STOP!<\/strong> This App can not be redistributed.<\/em><\/p>\n8. WBT App Attribution and License Statements<\/h3>\n
\n\u00a9 YYYY* Wycliffe Bible Translators, Inc.
\nThis app is made available to you under the terms of the Creative Commons License: Attribution-Noncommercial-No Derivative Works.
\nhttp:\/\/creativecommons.org\/licenses\/by-nc-nd\/4.0\/<\/a><\/p>\n
\n\u00a9 YYYY <Name>. http:\/\/creativecommons.org\/licenses\/by-nc-nd\/4.0\/<\/a> or other redistribution (sharing) license.<\/p>\n
\n\u00a9 YYYY <Name>. http:\/\/creativecommons.org\/licenses\/by-nc-nd\/4.0\/<\/a> or other redistribution (sharing) license.<\/p>\n