Thank you for your timely response!
I did download the trial version of EF last night and have begun poking my nose around a bit. Thus far, it appears EF may fit my needs. I use Apple products exclusively, iMac, MBP and iPad Mini. I have only a few documents I need to view outside of the office/home, but will bring a lot of data from the field back to the office I need to put into EF, such as photos, drawings, expenses, invoices, and handwritten notes.
It may take a few minutes for my brain to sync with your application format (library structure, etc). I am not a programmer of any sorts. I am totally ignorant on that front. However, I am in need of an application that will handle all of my work and personal needs for managing documents I create, receipts, pdf’s, etc. to allow me to maintain a paperless filing system.
If I may use an analogy, EF’s library system is similar to iPhoto library, in that, all of the metadata for a file is stored in that library? So, if I move only the file, the metadata is left behind in the .eflibrary? Which is fine! I am just trying to understand.
Also, I can move another file into a .eflibrary via Finder (not using EF UI) and EF will later detect that new document?
When reviewing the link you provided to the Library Rules, some of it is foreign to me only because I have not started to use EF yet. So, I look forward to looking into it in more detail over the next few weeks.
Do you have a list of “use cases” one could review for ideas to use EF? If you have any further suggestions on documentation to review to better understand EF, I am interested in reading!
Thank you for the opportunity to review your product.