attribute resolver script

[Tom Poage]

> On Nov 22, 2016, at 11:16 AM, Cantor, Scott <cantor.2 at osu.edu> wrote:
> 
> My issue with it seems to be that I'm not sure under what conditions it seems to produce output that makes sense. It doesn't seem to do what I would think it would, so I'm not clear on whether that's a failure in design or if we're just missing a plugin that does what I would expect.
> 
> To me, given each value of input, I would think you'd get *a* mapped or default value out (or nothing if there's no match and no pass through). If that's not what it does, then I don't know why or why that's useful.

Back ported to an old 2.4 instance I have lying about. Same behavior. I never did properly understand how Mapped worked.

Tom.