Update 20.20.paper-templates.md

docs/20-research/20_processes/20.20.paper-templates.md

@@ -44,6 +44,7 @@ The manuscript template creates the following files (additional [files for the a
 │                    directory)
 ├── Dockerfile    <- Describes the pandoc container for building the paper
 │                    (called by the Makefile)  
+├── literature    <- Directory containing literature summaries for Obsidian
 ├── figures       <- Directory contains all conceptual figures
 ├── output        <- Directory contains all output, such as data plots and
 │                    tables, which is generated by the scripts (do not store
@@ -169,6 +170,11 @@ Formatting the bibliography (*.bib file)
 - Journal field: use long version (e.g., "Journal of Information Technology", not "JIT"). For CSL styles that require abbreviations, temporarily replace the journal field in the bib-file since CSL does not handle style-specific journal abbreviations ([1](https://citationstyles.org/authors/#/csl-limitations){: target="_blank"}). JSON-files containing journal abbreviations can be passed to pandoc using the [citation-abbreviations](https://pandoc.org/MANUAL.html#option--citation-abbreviations){: target="_blank"} field.
 - Inproceedings: when using crossrefs (e.g., `crossref = {icis2010}`) for conference papers, the year and month field should _not_ be set, only the original \@Proceedings entry should include the date formatted as follows: `date    = {2015-12-13/2015-12-16}`.
 
+{: .highlight }
+> **Literature summaries: Obsidian**
+>
+> Literature summaries for each paper are stored in Obsidian format in the `literature` directory.
+
 ## Resources
 
 The paper-template is based on the following underlying architectural principles and considerations.