OCR & Hazel Workflow on Finder before importing into DT

[killerspots]

ah cool. But this is probably not the whole script block I need to include into hazel to work, right? Could you show me what the whole scripting block should look like?
Many thanks

[BLUEFROG]

You are assuming @chrillek is also using Hazel.

[chrillek]

@killerspots

But this is probably not the whole script block I need to include into hazel to work, right?

I don’t know. That depends on what you’re doing when and where in Hazel. And as @BLUEFROG hinted at, I’m not using Hazel (anymore) for integration with DT. Instead, I wrote my own script to do everything I’d done with Hazel before.

Using a single smart rule instead of Hazel (maybe)

Some people (me included) use a naming convention for their files and put them in certain goups depending on sender and/or content. I’m doing that for bank statements, some of the regularly arriving invoices and income statements. In DT, you’d need one smart rule per target group, since it’s not possible to move a record to a group depending on some criteria. So if you have 5 bank accounts and two companies regularly sending you invoices, you’d need seven separate rules. Which is not good, beca…

[killerspots]

Ah I see. I actually thought youn were using hazel. but thanks for the link, I will dive into it on the weekend.

I thought of another way. I index a folder in DevonThink, where those files will be moved that need OCR. in DevonThink I could create a rule to automatically OCR those files and will be put into the same folder, from where hazel could then take over in finder-base.
The only thing I have to think of: how could I get the original non-ocr files out of the indexed folder after they have been ocred? otherwise I would create an unlimited workflow inside this indexed folder.

[BLUEFROG]

how could I get the original non-ocr files out of the indexed folder after they have been ocred?

You don’t have to if you use the OCR > Apply action and also make sure DEVONthink’s Preferences > OCR > Original Document: Move to Trash is enabled.

[killerspots]

I already tried, but the original file still remained inside the indexed folder after the intelligent rule has found and ocred the document.
I needed to include an DELETE action into the rule after the ocr.

[BLUEFROG]

Post a screen capture of the smart rule.

[killerspots]

here we go.
using the german version (obviously )

[cgrunenberg]

Just use OCR > Apply. This won’t create a new document and therefore the Delete action isn’t necessary.

[BLUEFROG]

Criss reiterated what I said previously. Use OCR > Apply.