Hi Rob,

There are various scenarios but none that have been implemented yet (as we're still in the designing/planning stage). I'm looking for best practices so that I don't design something that depends on something that doesn't work.

For instance, we manage claims files. It would be useful to have metadata that indicated maybe the claim number and type, but again, our VAR mentioned that doing this isn't a good idea because people may not fill in the metadata.

-Robyn

I can definitely understand the care that has to be given when using metadata to automate business processes.

In my experience, situations where the accuracy (or, even more important, the mere presence) of metadata is critical are best handled by external tables (for template population in the client or field population in Forms). Is it possible to leverage a database table to automatically populate template fields according to some value picked up by OCR or maybe determine by folder path, etc.?

What type of report do you hope to generate? In my experience, any metadata is better than no metadata!