Devonthink 3.0.4 on MacOS 10.14.6.
When I scan a document in SnapScan on import to Devonthink the PDF is automatically OCRd. If I manually drag a PDF to the Inbox the PDF is not indexed. I have to OCR it, and then delete it.
Is there a way to automatically OCR things (all text) put into the Inbox?
This is usually not necessary, most PDF documents are already searchable. But you could use a smart rule to achieve this using the conditions Kind is PDF/PS and Word Count is 0 and performing the action OCR > Apply on import.
I have exactly this rule – see below.
It has worked consistently for a long time but is now applying OCR to imported print-to-PDF files whose word count (as can be seen from adding a Word Count column to the file list) is very much not zero – and thereby rasterising those files.
Is this a new bug?
I just tried to reproduce this but it works as expected (DEVONthink 3.5.1, macOS 10.15.5). What kind of file did you print in which app?
The rule seems to be triggering with every PDF, including PDFs printed directly from Word and PDFs that have already been OCR’d. Both kinds show their word counts correctly on import.
I have tried restarting the Mac; still happening.
Set the smart rule to On Demand and look at the matches.
Choose View > Columns > Word Count to see if there are any items that have a word count.(They shouldn’t.)
Those are the only files that should be processed by the smart rule.
If I change it to On Demand, it only shows PDFs with zero word count BUT if I watch that view when I drop a print-to-PDF into the inbox, it appears very briefly in the view and then disappears again.
If I change it back to On Import, the same thing happens and it OCR’s the file.
[accidentally deleted last post]
I have another smart rule that does some regex-based renaming, higher up the list than the OCR rule. If I delete the rename rule, the OCR rule works as it should.
Your smart rule looks incomplete. You’re looks for ANY file in ALL databases whose name is not obviouslynot. Why are you using such a broad search?
— Ideally it would search for files with names matching the regex rule but that doesn’t seem to be an option.
— It should in fact be operating on import. I turned it to On Demand to see if that fixed the problem. It doesn’t.
— Whether it’s set to On Demand or On Import, surely its existence should not break the OCR rule?
I have removed the file renaming rule entirely for now, quit and restarted DTP, and PDFs printed directly from office that correctly report large word counts are getting OCRd on import. Any troubleshooting tips would be helpful as this is really not what I want the app to be doing.
There seems to be a delay in recognising the word count on import, so it briefly appears as if nil: see video.
Well, the file needs to be indexed and the UI updated.
Regarding the smart rule, I would strongly suggest you don’t use such broad scopes.
Specify file types with particular names if you want to apply renaming instead of matching basically everything in your databases.
I understand the file needs to be indexed and the UI updated – I was pointing this out in an effort to get to the bottom of why the OCR rule is kicking in when it shouldn’t, even after deleting the renaming rule completely.
On the renaming rule, as far as I understand there’s no way to match file names by regex, so I don’t see how I could do that, but very happy to be corrected.
No, you can’t use full regex but you are clearly looking for specific filenames not just things not matching obviouslynot. You should be as specific as possible in your targeted locations and criteria.
You could use a criterion like: name:[0-9][0-9][0-9][0-9]+[0-9]+[0-5] to reduce the number of matches to process.
Is there a way of specifically capturing a period (or other specially treated character) in a wildcard name match?
Like a period? So I can use your approach above to find files that are named eg 2021.10.12 letter but not 2021-10-12 letter, which is what the regex scan would change the first one to
From the Help > Documentation > Appendix > Search Operators section…
And RegEx isn’t supported in the toolbar search field.
Thanks. I know regex isn’t supported in the search field. I was trying to implement your suggestion of using a targeted search to narrow the application of regex in a rule. And I had seen the manual, I was just wondering if there was a trick I was missing. So the answer is no.