Submission Preparation ChecklistAs part of the submission process, authors are required to check off their submission's compliance with all of the following items, and submissions may be returned to authors that do not adhere to these guidelines.
- The submission is previously unpublished (prior conference presentation or posting of drafts on a site dedicated for open peer review is not considered ‘publication’ for these purposes) and not under consideration at any other publication.
- The submission is in Microsoft Word (DOCX), Open/Libre Office (ODT), or rich text (RTF) format.
- The submission uses only Unicode fonts (this includes Times New Roman, Arial, and most common fonts found in Microsoft Office and other major suites; consult a full list of Unicode fonts if you are unsure whether your fonts are Unicode-compliant). SBL Hebrew and SBL Greek, both freely available, are preferred for those languages. If specialized fonts are necessary to your manuscript, please state this at the time of submission. In that case, the author will be required to provide fonts for production and publication and also to supply proof that the fonts are available for this use via an open license, or else that permissions have been granted through a purchased license agreement or otherwise obtained from the owner.
- All citations in the submission conform to the current Chicago Manual of Style using the in-line author-date format, with endnotes retained only for commentary or other ancillary, discursive, or explanatory content.
- If images are included, full attribution or citation has been provided within the text of the submission (including title, artist, etc., as well as the URL if the image came from a website). If the image is reproduced with permission of the copyright holder, evidence of such permission should be attached as a separate file during the submission process. If the image is licensed via Creative Commons, or if the author has reason to believe that the image is otherwise available for use (public domain, fair use, etc.) this should be stated in the comments field during the submissions process.
- If the submission is intended for peer review, it has been stripped of personally identifying authorial information in headers/footers, references, or embedded metadata. (Note: You must check off this box even if your submission is not for peer review.)
- The submission files are named with a short form of the submission’s title based on the first three major words (e.g., the file for a submission titled “The Future of Theological Libraries” might be FutureTheologicalLibraries.docx). Supporting files, such as images, tables, etc. indicate the type of supporting material after an underscore, with a number if there are multiple files of the same kind (e.g., the third image supporting the above submission might be FutureTheologicalLibraries_Image3.png). No file name should exceed 50 characters. (Note: The OJS system may alter the name of your file during upload, particularly by appending your user name. During the upload process, please click the pencil-and-paper editing icon next to the file name on the "Review Details" screen to correct this and ensure that the final, uploaded file name conforms to these guidelines.)
- During the upload process, titles are entered in title capitalization (not sentence capitalization or all capitals) and abstracts are in roman text (not bold or italic; italics for specific words and phrases within the abstract are permitted).
The data collected from registered and non-registered users of this journal falls within the scope of the standard functioning of peer-reviewed and non-peer reviewed academic or scholarly serial publications. It includes information that makes communication possible for the editorial process; it is used to inform readers about the authorship and editing of content; it enables collecting aggregated data on readership behaviors, as well as tracking geopolitical and social elements of scholarly communication.
This publication’s editorial team and Atla staff use this data to guide their work in publishing and improving this publication. Data that will assist in developing the OJS publishing platform may be shared with its developer Public Knowledge Project in an anonymized and aggregated form, with appropriate exceptions such as article metrics. The data will not be sold by this publication, Atla, or PKP nor will it be used for purposes other than those stated here.
Those involved in editing, publishing and hosting this journal seek to be compliant with industry standards for data privacy, including the European Union’s General Data Protection Regulation (GDPR) provision for “data subject rights” that include (a) breach notification; (b) right of access; (c) the right to be forgotten; (d) data portability; and (e) privacy by design.