Very important technical requirements for Judgment and Decision Making (JDM)

This information applies to articles that are accepted for publication. Articles submitted for review do not need to follow these guidelines, although they should be in pdf, with page numbers, and with the footnotes, figures and tables in the text rather than at the end.

However if you are preparing an article with the idea that you might submit it to JDM, then you can save time later by anticipating some of the technical requirements that you will eventually need to meet (explained in more detail below), in particular:

So far we have no charges for authors. This is because we (Jon Baron, mostly) do the production, with the help of lots of open-source software. We can tolerate a few minor deviations from these guidelines, but, if the deviations require extra work, I will ask you to fix them. This may delay publication. You are free to hire someone to help you meet these requirements, and this will probably cost you much less than the usual "article processing charges" of proprietary journals.

Timing: Regular issues of the journal appear every two months starting January. Final versions of articles are due the 15th of the month in which the issue appears. In most cases, when an ariticle is accepted pending revision, the revision (with a letter explaining what was done) is the final version, even if some further editing is required.

Checklist for users of Microsoft Word: Details below

  1. If possible, use our Word template for writing the paper. It will make some things easier.
  2. Title page without any formatting. No bold, italics, or centering. Just a simple list: author, affiliation, author, affiliation, etc., all separated by double line breaks.
  3. Semantic formatting of headings, sub-headings, ... No numbers. (LaTeX assigns them automatically.) The Styles menu does this.
  4. No unnecessary fonts, positioning, or indenting.
  5. No images for math. Use LaTeX for more than a little math.
  6. Simple tables.
  7. EPS figures, not converted from other formats, sent separately as well as in the paper.
  8. Footnotes in the text, not at the end.
  9. APA reference style. (Not other aspects of APA style.)

Style notes

  • For additional thoughts about writing style see these recommendations.


    Please submit all graphics as separate files, as well as leaving them in the document. If you use Overleaf to submit the final version of the paper, after review, then you do not need to include the graphics in the tex file that Overleaf produces (although it is fine if you do); just send the graphics separately.

    For graphs, use pure EPS (Encapulsated PostScript) if possible. These graphs are vector graphics, so they can be re-sized easily without loss of clarity. Please specify Helvetica or Arial font, if possible. Do not try to make EPS from some other format that is not itself vector graphics, such as png, tiff, wmf, emf, or jpg.

    Whatever you use, choose options for "no preview" and "convert to postscript fonts" if these are available. One program that does everything correctly "out of the box" is R, which is what I use when I need to re-draw something. If you use R, send the R code. Stata, Matlab, and SigmaPlot produce good EPS output without much trouble. If you do not use R and want a really nice graphics tool, try Matplotlib.

    With SPSS, use "export charts", choose "graphics only" for Document Type, "Encapsulated Postscript (*.eps)" for Graphics Type, 100 for "Size in percentage", "No" for "Inclue TIFF preview image", and "postscript fonts" for "Fonts". (Do not use "replace fonts with curves".) Try to make sure that Helvetica or Arial font is used for everything. To do this, select the area of the graph with fonts, double click on the title of the graph, and look at "Properties".

    How to view EPS on Windows

    Excel and PowerPoint usually cannot make EPS. They make raster images by default, so you cannot convert these to EPS either; the needed information is not there. However, LibreOffice can produce EPS from some Excel files (or PDF that can be converted to EPS). You can try sending me your Excel or PowerPoint files and I can see if LibreOffice can use them. (If you want to try this yourself, copy the file into LibreOffice Draw and export it as EPS or PDF.)

    For diagrams, another useful and easy-to-use tool is Mayura Draw. It makes nice EPS output.

    For photos or screen shots, a bitmap (raster) format is necessary (e.g., png or gif). The bigger the better. It is easy to shrink, but hard to expand. Use jpg only for photos.

    Text formats

    For articles with only a little math or a few tables, word-processor formats usually work: Open Document Format; LibreOffice (or OpenOffice) Writer; Word Perfect; Microsoft Word (doc, docx).

    I prefer text files formatted in LaTeX. This is required for articles with a lot of math or tables. See below for special notes about LaTeX or for word processors.

    You can also submit the article in plain text or Google doc (without Paperpile) format.

    Special notes for LaTeX

    LaTeX is the preferred format. You can use this template. You will also need to download hevea.sty and apalike3.bst and put them where latex can find them (e.g., in the same directory/folder as your paper). Or you can use our Overleaf template to make the tex file by cutting and pasting, or by writing directly on their web site, but the template will work better for those who already use latex.

    Our template provides some guidance about how to do things. Please do not do fancy things. More specifically:

    See the instructions for the title page for word processors, below, to make sure you include all relevant information.

    Every published article has a .tex version. To find it, look at the URL of the html version, replace "html" with "tex". Later articles are better examples to imitate.

    Special notes for word processors

    Do not try to control appearance. Do not use unnecessary fonts. Do not control position or size of text, ever. (Read on for details.) The general principle is that I convert these to LaTeX using many wonderful open-source programs described below. But these programs cannot tell what is necessary and what isn't. When you do things that are not part of the final document, I must undo them, often one by one. This is especially true for references cut and pasted from other formats (e.g., Apple to Microsoft).

    Tables in word-processor formats

    Tables produced with Microsoft Word are extremely difficult to deal with. The conversion system I use does not convert them consistently. The simplest way to do this, if you have already written the paper in Word, is this: First make a pdf version (with page numbers, without breaking up tables over two pages, and without sideways tables). This is so that I know what you want the tables to look like. Submit this. Then remove the formatting from the tables in the Word file. To do this select each table, got to Styles in the main tools, click "More", then "remove formatting". (Or, for LibreOffice, click Format, then "Clear direct formatting".) Submit this too. Here are some other "hints".

    If you use docx or have many tables or complicated tables, then submit the tables separately, as well as in the article, and send a pdf version of the tables or the entire article. (This helps me see where they go and what you want them to look like.) The simplest way to send them separately is in the form of plain text, of the sort you use in writing an email message. Separate the cells in each row with "&", and end the row with "\\". You can break lines in the middle of a row (because the "\\" indicates the end of the row). That is sufficient for simple tables, but LaTeX formatting is even more helpful:

    Detailed instructions (much more than you need) are here. The LaTeX template has two examples. If you have your table in Excel, just send it. If you use R, the xtable packages produces LaTeX tables, so you may send me either the tables or the R code. (Apparently Matlab can also produce LaTeX tables.)

    To create LaTeX tables with a graphical user interface, use this table editor (with "Booktabs table style" rather than "Default table style", upper right); you can also cut and paste from Excel.

    Some technical details

    Authors do not need to read this section, but it seems to be a good place to document some of the methods used in production. The basic idea is to produce a .tex file, with settings in the header for two columns and other things like foreign characters, math, and nice tables. To get this from a word-processor document I use LibreOffice to produce .odt, then writer2latex to produce .tex. After I fix this up, when everything is final and the proof is approved, I use hevea to produce the html version. When the whole issue is done, I produce files for RePEc, DOAJ, the various indexing organizations, and the rss feed. The table of contents is a by-product of these operations, as is the listing by author.

    My summary of the whole process, including notifications.

    For converting word-processor formats to LaTeX, and LaTeX to html.
    My notes on LaTeX
    Batch file to convert .odt (made by LibreOffice) to .tex, using writer2latex
    configuration file for writer2latex
    configuration file for HEVEA (for making html)
    CSS file for html version

    For RePEc (Research Papers in Economics), table of contents, citations, and notifications. (Perl scripts by Adam Kramer and Alan Schwartz.)
    notes on usage
    Template for 'dat' format
    Make table of contents
    Convert 'dat' to APA format
    Make RePEc 'rdf' format
    Make 'ris' format
    Extract abstract from .tex files
    R script for making rss feed from RePEc rdf
    R script for DOAJ (and archives)

    When I need to re-draw figures, I use R. Here are some old examples. The numbers are related to the articles. For example, "8221/figs.R" has results in "8221/jdm8221.pdf".

    Jonathan Baron