include some cap dependencies
we're not using redis for caching at the moment
changes in the default template profile changed the order of fields rendered. may want to sort transformations in the future to prevent such issues
drying up a couple extractors
support hiding fields (e.g. fields used only to fetch and provide data for other fields can then be discarded)
support loading remote field data
allow field definitions to get data as it has been processed by preceeding fields (use one field to load data for other fields to use), allow individual processors to gain access to the original fied value
perhaps temporary: get a hash from a mods doc. (could move this to an extractor or break it down into individual processors