I might be the first person in history to timeout your 150-hr trial period while still importing EN. ;->
A couple of points on the “primative comment” I was referring to the iOS app. Unfortunately, most of my work is field work in a mobile office: iFon, iPad, and a Bluetooth Keyboard, a couple of pretty good quality Zoom mics for the iPhone (one for interviews the other for videos), some tiny tripods all in a rucksack.
I’ve come to depend on “on the fly” sync from the field to safeguard my material, wifi when I can, cellular when I must.
I don’t doubt the sophistication of DTPO, but don’t doubt the ease or sophistication of EN either. You can decide where and if “primitive” applies:
Attached are two screen shots of one business card I took with the EN iOS iFon app and the automatic OCR (a top & bottom half) plus adding it to my Contacts. This was detected effortlessly.
Today I took a scan of a Death Certificate using the Evernote Scanable app. This certificate had all of the usual state paper filigree printing and security paper issues. I’d just read the comment on the board that EN “claimed” to scan all the PDFs with OCR, so I found the name of the cemetery “Resthaven” and searched through my entire database with no hits. I scanned the document and sync’ d up & searched again. No results. However, three hours later I checked and EN returned “Resthaven” in the PDF of the Death Certificate.
Also, I read the “File This” thread with interest last night, since I use it. And today a question came up about a charge I’d made back in September. Even though I’d never opened the PDF VISA statement that File This had swept into my EN account, when I searched the VISA folder in EN for the name of the company, the charge was highlighted when I downloaded the PDF to my iPad in the field.
I think it’s clear EN OCRs & indexes PDFs (at least those of Premium account holders).
So, as I said, every effort that EN has put into the front end of sweeping up and indexing information is top drawer. There is nothing wrong with admitting that.
Their problem is, as someone above put it, the Roach Motel status of the backend. If you collect to no purpose, or not much purpose, or are only concerned with archiving, EN is a great product.
It remains to be seen if DTPO is going to be a spectacular backend. My problem, like most contractors, is that I live and die by the job. Taking time out to learn the in’s and out’s of DPTO is going to cost me big time if I change over.
I really wish you had a pre-populated sandbox to test drive.
What I’m really interested in is the “connecting the dots” aspects of DTPO, I spend a lot of time drawing out timelines and diagrams of actions/inactions or missed opportunities before I create my final reports. That’s where EN really fails, at the production end.