Realizing this is an old thread and things may have changed, in my search to find out if EagleFiler has “integrated” scanning capabilities this is where I ended up. In trying to make the transition between Win OS and Mac I found EF as a possible replacement for FileCenter Pro (Win). Actually, I prefer the look and feel of EF (from screenshots and researching this site) but am very concerned about loosing some capabilities that I’ve come to rely on FCP for.
90% of the material I want to save digitally enters my “paperless office” on paper and has to be scanned. Web content, emails and digital docs can all be “printed to file” so no scanner needed there. In either case I typically choose to save in PDF format, although FCP will allow storage of any file in any format within its structure and clicking will open it with whatever app that file is associated with. But back to practical application, once set up, scanner dialog is integrated into FCP (in fact you don’t even see the scanner’s native dialog windows when it scans, unless you choose that option). So the scan/save process is, I open FCP, choose a storage location folder (or file) within FCP’s file structure, click Scan and choose options from a FCP dialog box (unless I just want to go with the options I’ve set as a default), Enter in a File Name and type or choose to append the doc/jpg/whatever to an existing file. The image is scanned, OCRd and saved in the appropriate location. Indexes are performed on a user-set schedule as a db for local searches.
As you can tell, at the user level this is process is quite simple. No second or third party apps are required. FCP is set as my default PDF viewer/editor. It also allows me to combine (append or prepend) PDF files into a single file or extract pages from a multi-page file to make it multiple files (pre or post scan). I have the option of saving incoming images to an Inbox and choose a final destination later or save it directly to its final destination, whether that’s as a new file or appended to an existing multi-page file.
So I guess my question is, how much of this functionality would I be loosing by switching to EF?? I could deal with loosing some in the short term, especially if upgrades to address some of these functions are in the works. Please don’t take these questions/comments negatively, EF looks like a fantastic program and I’m looking forward to using it!