Date Matching - OCR-Problem letter "O" and #0

[speedy_99]

Hi,

the Date Matching Token is working fine. But sometimes there is a OCR-problem with letter "O" and #0.
Incorrectly the #0 of the date it's recognized as letter "O" and the date matching is not working.

My scans are done with 300 dpi and I am using Nuance Omnipage Ultimate (Win) for OCR.

Is it possible to combine "Date Matching Token" with a replace text function?
The date format 2O.01.2016 would match, but the "O" ist replaced by #0 --> 20.01.2016

For a custom token I am using the replace text function. The Patient-ID in my office is 00012345, but the OCR makes mistakes, so that the OCR'd result could be OO012345. For renaming I combine the custom token with "replace text" and letter "O" will replaced by #0.

For my custom token it works fine, possible for "Date Matching Token"?

Juergen

[Mr_Noodle]

Can't really do that with date attributes now. The only way I can see doing it is if you do a custom text attribute to match it, store it into the file's comments, using replace text to correct it. Then have another pass which checks for the comment and parses that as a date. A bit tedious but it might work.