I'm reading the documentation, looked at a few DevNet posts, but I'm still a bit confused as to whether I can specify filters in my DD config file to do what I want.
Essentially I'm looking to do two things here:
- Globally filter "out" any non-DCRs that might have been passed in through a filelist
- Deployment definition level filtering to specify that a given definition applies to only certain DCR types
The first part
seems to be something like this:
<field name="TeamSite/Templating/DCR/Type" value="[a-zA-z0-9]*"/> however:
- It isn't clear if I can reference an EA via this directive if I'm deploying content as opposed to metadata
- It's unclear if I can use perlre-type expressions in value - like
value="^\w+"
so as to avoid having to specify an explicit character-class ([...]
) - It's unclear if I can use regex-style values or if I have to use SQL-style directives -- the documentation seems to show both the use of things like '
*
' and the use of '%
' within the value-side of a field element
So - given all that confusion - I have to ask:
Is it possible to filter [for inclusion] DCRs based on EAs when you are deploying content and not EAs?
If so - what is the proper filter clause for doing so?
The second item is within the
deployment
section, after the
source
element - where I would place something like:
...
</source>
<filter use="global_filter"/>
...What I'm trying to understand here is whether I can specify
multiple filter specifications here, e.g.:
...
</source>
<filter use="global_filter"/>
<filter use="dcr_specific_filter"/>
<filter name="and_this_to">
...
</filter>
...The DTD seems to indicate that this is legal ("
(.... filter)*
" or "
(... | filter | ...)*
" - but I didn't see any examples of such in the documentation, so I'm just looking for verification.
--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com