Organize a PhD candidate's research paper PDFs by chapter on a Linux laptop

To organize a PhD candidate's research paper PDFs by chapter on a Linux laptop, create a zero-padded chapter folder structure, move each PDF into its mapped chapter folder, rename it with a consistent convention, and split or convert any files that need cleanup before filing. The complete workflow takes about 20–30 minutes once the chapter mapping is defined.

What You Will Need

• A Linux laptop (the commands below assume a Debian/Ubuntu-family distribution with a Bash terminal; they work with minor adjustments on most other distros)
• A terminal window, opened from your application menu
• poppler-utils — provides pdfinfo and pdftotext; install with sudo apt install poppler-utils
• qpdf or pdftk — for inspecting and splitting PDFs; install with sudo apt install qpdf or sudo apt install pdftk
• Optional: Python 3 with the pypdf library (python3 -m pip install pypdf) for scripted splitting and text extraction
• Optional: Zotero, for bibliographic metadata that the file system alone cannot hold
• Optional: a browser-based PDF tool that processes files locally (one option is OctopusPDF) for visual splitting, organizing, and PDF-to-Markdown conversion without uploading files
• The collected research paper PDFs, typically in ~/Downloads

Step-by-Step Instructions

Step 1. Inventory every PDF on the laptop

Run this command to list all PDFs and where they live:

find ~/Downloads ~/Documents ~/Desktop -type f -iname "*.pdf" -printf "%p\n" 2>/dev/null | sort

Keep the output open in a second terminal tab; you will use it as a checklist in Step 4. Watch out for duplicate copies of the same paper saved under different filenames — note them now so you do not file both into the same chapter later.

Step 2. Map each thesis chapter to its topic keywords

Decide which research topics belong to which thesis chapter before touching the files. Draw a simple mapping like this:

Keep the mapping in a text file. The point of this step: a paper about evaluation methods may belong under 03-methods, not under 01-literature-review, depending on where you will cite it in the thesis.

Step 3. Create the chapter folder structure

Create a root folder for the literature and one subfolder per chapter:

mkdir -p ~/thesis-literature/{00-unsorted,01-literature-review,02-background,03-methods,04-experiments,05-discussion,09-appendix}

The 00-unsorted folder is intentional: it gives you a temporary home for files you cannot classify yet. Use zero-padded two-digit prefixes (01, 02, … 09) so the folders sort correctly — 1, 2, 10 would sort as 1, 10, 2.

Step 4. Move each PDF into its chapter folder

For each PDF in your Step 1 manifest, move it to the matching chapter folder:

mv ~/Downloads/survey_of_attention.pdf ~/thesis-literature/01-literature-review/

Move files in groups of 5–10, then run ls ~/thesis-literature/*/ to confirm each folder contains what you expect. Watch out: if mv reports “Permission denied,” check ownership with ls -l before reaching for sudo; the file may belong to another user or sit in a read-only directory. Also use mv -i so the shell asks before overwriting when two source folders contain a PDF with the same filename.

Step 5. Rename every file with a consistent pattern

Adopt one pattern and apply it to every PDF: AuthorLastName_Year_ShortTitle.pdf. For example:

mv ~/thesis-literature/01-literature-review/survey_of_attention.pdf \
   ~/thesis-literature/01-literature-review/Vaswani_2017_Attention.pdf

For bulk work, cd into the chapter folder first and run for f in *.pdf; do echo "$f"; done to preview the list before applying a rename loop. Keep the pattern alphanumeric with underscores — spaces and special characters cause quoting problems in later shell commands and in LaTeX or bibliography pipelines.

Step 6. Split combined or multi-paper PDFs before filing

If one PDF contains several papers (common with downloaded proceedings or merged scans), split it into one PDF per paper before considering it filed. With qpdf, split a file into two-page chunks:

qpdf --split-pages=2 combined.pdf split-page-%d.pdf

With pdftk, extract an exact page range instead:

pdftk combined.pdf cat 3-5 output paper_1.pdf

If you prefer a visual workflow, a browser-based splitter that runs entirely on your device lets you drag a page range into a new file without uploading anything. Note that DRM-locked files will fail no matter which tool you use — in one test set of 113 real-world PDFs, 91.2% were processable and the remainder were DRM-locked, so treat a single split failure as a DRM problem rather than a tool malfunction.

Step 7. Convert key papers to Markdown for AI-assisted note-taking

For papers you will feed into an LLM or a notes app, convert them to Markdown so the text and its heading hierarchy survive cleanly. Structure-aware extraction respects headings and paragraphs, which saves tokens when you later send the text to an LLM.

A quick command-line extraction is:

pdftotext -layout Vaswani_2017_Attention.pdf Vaswani_2017_Attention.txt

For Markdown output, use a browser-based PDF-to-Markdown tool that extracts the document structure locally (one option is OctopusPDF), or use pandoc for born-digital PDFs (PDFs originally produced from Word or LaTeX). Watch out: scanned papers have no text layer, so pdftotext produces empty or garbled output. For those, run OCR first with Tesseract, or convert the pages to images at up to 216 DPI and then OCR the images. Store the converted files in a notes/ subfolder next to the PDFs.

Step 8. Create a chapter README index

In each chapter folder, create a short README.md:

for f in ~/thesis-literature/*/; do
  touch "$f/README.md"
done

Then edit each README by hand. At minimum, record: the claim the paper supports, the thesis section it maps to, and whether you have already converted it to Markdown. This index is what keeps the folder structure searchable six months later.

Common Mistakes / Troubleshooting

How to Verify Success

• Every PDF appears in exactly one folder under ~/thesis-literature/, and ~/Downloads contains no stray PDFs
• find ~/thesis-literature -type f | wc -l matches your Step 1 manifest count, accounting for newly created split files
• Filenames follow one pattern (AuthorLastName_Year_ShortTitle.pdf) with no spaces or special characters
• Each chapter folder has a README.md listing the papers and their purpose
• Any split, OCR, or Markdown conversion produced readable output before the file was considered “filed”
• From the terminal, you can open a sample paper, its notes file, and its README entry without leaving the shell

FAQ

Q1. Should I organize by chapter folders or by Zotero collections?

Use both for different jobs: put the PDF files in chapter folders so they are sorted on disk, and keep bibliographic metadata (DOI, tags, abstracts) in Zotero. Never store two copies of the same PDF — file the PDF once in the folder and let Zotero link to that single file.

Q2. One paper is relevant to two chapters. Where do I put it?

Put the PDF in the chapter where you will cite it most often, and create a Linux symbolic link in the other chapter folder:

ln -s ../01-literature-review/Vaswani_2017_Attention.pdf \
  ~/thesis-literature/04-experiments/Vaswani_2017_Attention.pdf

The link costs zero extra disk space and keeps a single source of truth.

Q3. Are browser-based PDF tools safe for confidential PhD research?

Only if the tool processes files locally in the browser instead of uploading them. Tools built on in-browser PDF libraries can parse and manipulate files on your device with zero bytes uploaded. Confirm the tool’s architecture before using it with unpublished results; command-line tools such as poppler-utils, qpdf, and pdftk are always fully offline.

Key Facts

• The reliable workflow is: inventory → map chapters → mkdir -p → mv → rename → split → convert → index.
• Command-line tools (poppler-utils, qpdf, pdftk) run fully offline on Linux and keep sensitive dissertation research on the laptop.
• Browser-based PDF tools can run entirely on the device; one in-browser architecture uses PDF.js for parsing and pdf-lib for manipulation, so no bytes are uploaded.
• In a test of 113 real-world PDFs, 91.2% were processable by browser-based tools and the remainder were DRM-locked.
• Structure-aware PDF-to-Markdown conversion preserves headings and saves tokens when the resulting text is fed into LLMs.