Low-friction paperless workflow
I've been trying to shift much more of the paperwork in my life into the digital world, but I was very keen that filing a bit of paper electronically should be as easy as putting it in a folder in the filing cabinet. "Wouldn't it be nice", I thought, "if the only thing I had to do was type a name or a few keywords and everything else happened automatically?"
So I built a system which did just that. This video describes in some detail how the script is set up. You may want to use the full-screen and HD options to make things more readable. If you're less interested in the details and would just like to see it in action, watch the first couple of minutes and then skip to about 13:30.
One thing I don't talk about in the video is the fact that Hazel rules can also look at the contents of the file. So, once the document has been OCRed, the automatic filing can happen based on words that actually occur on the paper -- it might detect your car's registration number (licence plate), for example, in a document and know to file that under 'car stuff' -- which I think is very cool.
Some further links:
- David Sparks' Paperless ebook
- Hazel, and some more things you can do with it.
- PDFpen, from Smile Software.
- Fujitsu Scansnap scanners
Comments
Hi Robin -
Mmm... yes - that's a challenge - I don't think there's a way to tell Hazel not to process the next file until it's completely finished with the current one. I suspect you'd have to do some more coding for that - detect when the folder has been changed and include loops in the script which goes through each file in the folder one at a time. Or you could move items from the inbox folder to a 'renaming' folder, but only do that when the renaming folder is empty. Or, you could use the renaming features of Preview itself, but this is made more complicated by the fact it's not scriptable. You might be able to do something like bind a keystroke to File > Rename and then use Applescript to send that keystroke to Preview...
I found a similar problem shortly after making the video: it was that Hazel couldn't always tell when my (somewhat elderly) ScanSnap software had finished creating the file. I suspect this is a problem on multi-page documents - the scanning software probably (foolishly) opens and closes the file repeatedly. So my script would prompt me to rename an incomplete file, and then all sorts of confusion could follow. (All my tests were with single pages which worked fine!)
One solution is to modify the Hazel rules so that they only kick in when the last-modified time of the file is more than a minute ago, but that hardly makes for an interactive experience. In the end, my solution was not to use Hazel for the very first stage. Instead, I get the scanning software to call my renaming script directly, when it knows it has finished scanning. The script puts the resulting file into the 'OCR before Action' folder, and Hazel takes it from there. All works happily now.
That seems like a pretty good solution to me!
Best, Q
Hi Sam -
Yes, I think that's best - I'd be happy to post the scripts, but you'd probably want to tweak them for your own folders etc anyway.
I've made a couple of other tweaks, which I should write up soon...
All the best, Quentin
Hi Sam -
I've probably modified the scripts a bit since then... I'll try to do an update at some point, but yes, the basic system works for me under Yosemite.
There's also some related stuff in my video clip here: http://www.statusq.org/archives/2014/07/12/5957/
but I don't think I went into much detail about the actual scripts...
Do you know where it's actually breaking for you?
All the best, Quentin
Leave a Comment