- Explain the position of templates in the manuscript production process
How to develop templates 1:
- Describe things to consider when using the templates (general and template-specific checklists)
- Important for word reference documents: modify the pandoc template instead of including other word documents)
docker run --rm --volume "`pwd`:/data" --user `id -u`:`id -g` pandoc_dockerfile -o reference.docx --print-default-data-file reference.docx > reference.docx
- For conferences: replace the templates from previous years
The basic template offers a simple Latex template for developing manuscripts before finalizing them with a custom journal/conference template. Since this template does not include journal-specific layouts, all manuscripts are formatted consistently. In addition, the template includes header information on the current version of the manuscript (based on the git history and the markdown header):
ShortTitle (YYYY-MM-DD, Committer, branch, commit-id)
Adding this information to the PDF allows you to easily find the version (git commit) that corresponds to the PDF. This is particularly useful when printing PDFs or sharing them for feedback.
Using the basic template requires gitinfo2, which must be set up in the individual manuscript repositories:
cp /usr/share/texlive/texmf-dist/tex/latex/gitinfo2/post-xxx-sample.txt .git/hooks/post-checkout
cp .git/hooks/post-checkout .git/hooks/post-merge
cp .git/hooks/post-checkout .git/hooks/post-commit
It has to be installed in the pandoc-docker container as suggested in this Dockerfile. To build the container, simply run:
docker build -t pandoc_dockerfile .
- Manuscript template
- CSL for references
- Author guidelines
- Notes:
- Manually update: Heading style for abstract and reference should be "subtitle"
- Manually update the short title (header)
- Authors: should be in individual lines.
- Status: Developmental
- Manuscript template
- CSL for references
- Author guidelines
- Notes:-
- Status: Developmental
- Manuscript template
- CSL for references
- Author guidelines
- Notes:
- No strict formatting requirements
- Bibliography should use journal abbreviations (described here): abbreviations-ltwa.json
- Status: Developmental
- Manuscript template
- CSL for references
- Author guidelines
- Notes:-
- Status: Developmental
- Manuscript template
- CSL for references
- Author guidelines, Latex style files, Style guide
- Notes:
- Booktitles need to be abbreviated manually (conference proceedings)
- Bibliography should use journal abbreviations (described here): abbreviations-informs.json
- Status: Developmental
- Manuscript template
- CSL for references
- Author guidelines
- Notes:-
- Status: Developmental
- Manuscript template
- CSL for references
- Author instructions
- Notes:
- Remove authors (title page and document properties) for review.
- Include keywords on page 1.
- Copy paper title to page 2.
- Fix manually: Third Subhead: On same line as beginning of text, flush left, bold, upper/lower case, followed by a colon.
- Citation style changed to APA-7: https://misq.umn.edu/
- Status: Developmental
- Manuscript template
- CSL for references
- Author instructions
- Notes:
- There is no need to follow a specific template when submitting your manuscript in Word. However, please ensure your heading levels are clear, and the sections clearly defined.
- Status: Developmental
Searching CSL by example: https://csl.mendeley.com/searchByExample/ Word reference document, heading numbers: https://www.layoutheo.de/tutorials/ueberschriften/ueberschriften-nummerieren-blog.html Particular styles (e.g., "Figure") in Word document may need to be activated/added to the catalogue before editing them in the reference document.