- Re using the ScanSnap: DEVONthink Pro Office works very smoothly with ScanSnap Manager to receive and OCR PDFs produced by the scanner. ScanSnap Manager would allow one to name each document as it is scanned, but that would require opening Settings and typing the Name of each document. I don’t bother to do that. An option to name the PDF at the time of OCR is provided in DEVONthink’s Preferences > OCR. I don’t use that option, as I usually scan multiple paper documents and don’t want the queue to stop and wait for me to name each one. So DEVONthink captures the PDFs by the Names assigned in ScanSnap Manager (YYYYMMDDTime).
It’s a simple matter to name the searchable PDF after capture to a database. Usually, there’s a selectable text string that would make a good Name. I select that string and press Control-Command-I to make it the document Name.
If you have problems with the scanning workflow, send a message to Support and we will try to help.
- Re the problem of carrying over the names generated by your scripts in FileMaker:
I understand your frustration in trying to handle large numbers of files produced by FileMaker, with carefully customized Names. DEVONthink captures files without modifying them, including the filename, filetype, creation and modification dates, etc. I regard that as a positive feature. On the downside, you are faced with having to manually type in document Names if you use the "print as PDF’ procedure.
As someone suggested above, I don’t think the “print as PDF” to DEVONthink will be appropriate. DEVONthink uses an OS X feature that allows printing a displayed document (from almost any application) as a PDF file. The option to “print” to DEVONthink Pro Office as PDF internally uses an alias of the application as the referent, rather than, e.g., the Desktop. The OS X routine used doesn’t carry over the title produced by your script, but rather the database name. (Note: If the Name assigned by the script is printed in the PDF report, the document can be quickly renamed by selecting that title string in the PDF and pressing Control-Command-I to make that the document Name.)
You might check with the scripting gurus at FileMaker to see if they can figure out how to pass the titles created by your scripts to the “print as PDF” procedure.
The brute force procedure of having your FileMaker scripts send PDFs of reports to a Finder folder, then capturing them to DEVONthink is workable, but a two-step procedure. The documents have the appropriate Names, but then need to be captured.
A possible shortcut would be to attach a Folder Action to the Finder folder into which the FileMaker Script saves files. DEVONthink includes a Folder Action script to import the files, then delete them from the Finder folder. Cautionary note: timeouts might occur if the documents are very large and/or a large number are dumped into the Finder folder simultaneously. Generally, if a script fails, the original PDF will still be in the Finder folder and can be imported manually.