a metadata config that adds entity attributes

[Tom Scavo]

On Fri, Apr 10, 2015 at 2:17 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:
> On 4/10/15, 9:59 AM, "Tom Scavo" <trscavo at gmail.com> wrote:
>>
>>The MetadataProvider I have in mind has two <MetadataFilter> elements
>>and one <DiscoveryFilter> element (in that order). The first
>><MetadataFilter> *adds* an entity attribute while the second
>><MetadataFilter> filters away all entity descriptors that do not have
>>a special entity attribute. Finally, the <DiscoveryFilter> customizes
>>the discovery UI based on three entity attributes, one of which was
>>the entity attribute added at the beginning of the process.
>>
>>Am I on the right track here? Thanks in advance. Tom
>
> Yes, I think so, though I'd probably avoid the third value and just assign one of the existing ones for convenience and because it's shorter, but that's just personal style/preference.

Right, I was going to post exactly that but then I thought: hmm, what
if some human inspects the cached metadata in the filesystem? Wouldn't
it be easier to debug a metadata issue if a completely new entity
attribute were used? (I'm probably over-engineering here.)

Anyway, thanks for looking at this. And I have to say, the SP has way
more power than I thought, almost as much as a standalone metadata
aggregator.

Tom