Differences between kMDItemTextContent and Hazel Importer
Posted: Sun Oct 19, 2014 5:05 pmI know this has come up before, but I am trying to get a date out of a mortgage statement and the rule is failing.
I ran the hazelImporter utility and it discovered 3089 characters of OCR text which seems to be missing the top half of the document. I then ran the same document through mdimport and the kMDItemTextContent variable contained 7745 characters and included what seems to be the entire document.
Before I head off and start writing scripts, does this sound like something I should expect? Is there anything I could have done in the scanning process to cause this? Since I am only using the OCR'ed file in this test, I'm not sure this is something I caused, but the results seem surprising.
Did I miss something ?
Thanks
I ran the hazelImporter utility and it discovered 3089 characters of OCR text which seems to be missing the top half of the document. I then ran the same document through mdimport and the kMDItemTextContent variable contained 7745 characters and included what seems to be the entire document.
Before I head off and start writing scripts, does this sound like something I should expect? Is there anything I could have done in the scanning process to cause this? Since I am only using the OCR'ed file in this test, I'm not sure this is something I caused, but the results seem surprising.
Did I miss something ?
Thanks