6 ms·
My approach is a flat date-based file structure with a markdown-based Zettelkasten on top: File are mostly in a flat structure. In ~/, I have directories like
by mo_42 3y ago
My approach is a flat date-based file structure with a markdown-based Zettelkasten on top:
File are mostly in a flat structure. In ~/, I have directories like documents, photos, videos that directly contain all the files. For certain topic, I create separate directories (e.g., PhD, major projects). The filenames always start with an ISO date (yyyy-mm-dd). For documents, it could be like 2024-03-24_inv_google.pdf. Here, inv means it's an invoice and Google is the organization where the invoice comes from. After the date, there's always a three letter code that tells me the type of document. All physical documents are scanned and OCRed and put in the same structure.
On top of that I curate a Zettelkasten. It's just a directory with a set of markdown files (also a flat hierarchy). This Zettelkasten is layer of information on top of the remaining filesystem. The markdown files link to external resources (e.g., on the web) and also to internal files (e.g., (something)[../docuemnts/something.pdf]). This way I can browse my personal information like it's the web.
This file structure is my single source of truth. I try to export all other information as text files there (e.g., emails, contacts). I'm using restic to backup my entire home folder. I don't use any sophisticated tools, just a basic PDF reader, vim, Gimp, and other standard tools of the Linux ecosystem. I used to sync my home directory using unison but currently, I'm just using a single one.
- jackthetab 3y agoWhat do you use for scanning and OCRing? I haven't found a solution that _doesn't_ make me want to throw it all out and just retype the doc by hand. I too am moving towards a flat hierarchy with dates after attempting Zettlekasten and PARA. I like your "Zettlekasten layer on top of the fs" idea. Def going to do something similar.
- kkfx 3y agoNot OP but for some stuff I only get on paper, so I need to scan I've simply have a rough "import" semi-automated workflow: - scan to an image/as many as needed - mogrify -deskew 90% - for i in .png; do; convert $i ${i/ng/df}; rm $i; done - pdftk cat output aname.pdf - ocrmypdf --force-ocr -c -i (wrap tesseract and others) I normally get a good enough scan. If it's not the case I might manually edit images than feed to the rest of the pipeline. Gimp G'Mic QT Repair Scanned Document filter works IME far better than unpaper and others, but it's not that automatic, need to be tuned case by case. However that's rare. For notes, personally I go for time-based notes, similar to ZK but with the time-constraint, I've described the system in this page.
- mo_42 3y agoI have some high end scanner (because I sometimes scan negatives from film photography). It has a built-in OCR that works pretty well. That's basically the only reason I need to boot MacOS because the Linux drivers are rather bland.