Chapter Submission and Formatting Guidelines

Please note: The initial chapter proposals do not need to be formatted – they can be sent in an email. Please see the Call for Contributions page for what we need with the chapter proposals.

Guidelines for preparing your chapter

For chapters (or similar contributions), there are some guidelines which we ask authors to please follow (it makes everyone’s life easier):

The book will be constructed in chapters of no more than 8,000 words + illustrations/figures/tables. Any author is welcome to submit more than one chapter, but each can only be 8,000 words maximum (including any references, data, etc.), and chapters should be thematically different (i.e. no titles like “clustering for analytics – part 1” and “clustering for analytics – part 2”). Chapters can be aligned around similar topics, but must be independently readable and self-contained. Chapters longer than 8,000 words will not be accepted. Please contact the editorial team if you have an idea for a chapter that will require more than 8,000 words.
When writing a submission, consider the broad target audience of the book, and aim the chapters contents aligned after this.
The intended audience for the book is professionals and amateurs, students and instructors. The language should be styled for this broad audience. Specialised chapters requiring specific knowledge are welcome, as it is expected that introductory chapters will provide the basics of GUR, thus giving readers a chance to familiarise themselves with the terminology and fundamental principles. If you are in doubt about whether a topic is too specific or requires too much expertise on the readers, please do not hesitate to contact the editorial team.

All chapters must include the following components/formatting

  • Submissions must be in MS WORD and PDF format
  • Submissions must use 12 point Times New Roman font, with headers and sub-headers marked with bold, italics or underlined (1st, 2nd and 3rd level). Standard 1” margins.
  • The title must be 16 point Times New Roman font, centred on top the first page. Following the title the names of all authors.
  • Right after the title and author names should be an abstract listing the key takeaways of the chapter in bullet point form. Please include 2-5 takeaways. Takeaways should be described using layman’s terminology to the extent possible.
  • At the end of the chapter should be a bio of max. 150 words per author, plus a picture.
  • All image files should be embedded in the file (eventually, we will ask for these separately, in high-resolution JPG or TIFF. Please do not use low-resolution images).
  • At the end of the chapter, before the bios, include a section called “next steps” with references to sources where readers can go to learn more about the topic/-s you are covering in the chapter. References can be to anything useful – software, blog posts, books, scientific writings, videos, etc.
  • Language must be clear and concise.
  • English (US or UK) are the only accepted languages.

General guidelines

Arguments should not be made without backing evidence or argumentation. This is critical for the credibility of what you write. For example, you may think that a particular algorithm or method is superior to all others for doing something, but stating this without backing it up weakens the argument. When something is your opinion, say so.

The submitted chapter should have a high quality and be ready-to-print. While editors and peers will read and provide feedback on contributions, the best way to avoid errors is to make sure what you submit is correctly formatted and that the language is top-notch.
Avoid over-use of in-text references. Contributions will be judged on their value, not on how many papers they cite. References and suggestions for further reading can also be provided at the end of the chapter under “next steps”.
Keywords must be defined (there are a lot of divergent opinions about the key terms in the field).
You are welcome to use text boxes, highlights or similar to break up the text, for example, to add an explanation to a term or method.
The editorial team stands by to assist with any questions or provide help with the submission guidelines.

No Comments