List Manager VS. Extractions

Hi Samantha,

We don't have a chart or anything, but a few guiding principles factor when deciding what to use:

1. Extraction Manager is better for creating segmented lists
2. Extraction Manager is better (more streamlined and intuitive) for including suppressions. Suppressions can be built into List Manager, but it's a bit round-about to get there.
3. List Manager is good to see everyone who meet one or two criteria
4. List Manager can also be used as a kind of cross referencing tool, i.e. to see "who meets criterion-x AND criterion-y" or "who meets criterion-x BUT NOT criterion-y." Anyone building criteria sets should have an awareness of when to select "search household" and operator selection (i.e. IN vs HAS; NOT IN vs DOES NOT HAVE), but I find these things particularly relevant when using them for cross-referencing.
5. Lists can also be helpful as criteria in and of themselves -- whether employed in List Manager or in Extraction Manager. Since Tessitura's UI doesn't allow for nested criteria, I use Lists to bundle criteria in place of nesting.
6. List Manager would also be the tool for use if the dynamic functionality is warranted. (I'm typically using dynamic lists in the case of item 5).
7. Lists can be run through reports and utilities. And if set to dynamic, users can refresh counts on each lists built by other users if they're otherwise restricted by user permissions from editing each others lists.

I'm sure this is just scratching the surface, but those are the things that most immediately come to mind.

I'll be curious to see what people share.

-Emilie

Hi Samantha,

We don't have a chart or anything, but a few guiding principles factor when deciding what to use:

1. Extraction Manager is better for creating segmented lists
2. Extraction Manager is better (more streamlined and intuitive) for including suppressions. Suppressions can be built into List Manager, but it's a bit round-about to get there.
3. List Manager is good to see everyone who meet one or two criteria
4. List Manager can also be used as a kind of cross referencing tool, i.e. to see "who meets criterion-x AND criterion-y" or "who meets criterion-x BUT NOT criterion-y." Anyone building criteria sets should have an awareness of when to select "search household" and operator selection (i.e. IN vs HAS; NOT IN vs DOES NOT HAVE), but I find these things particularly relevant when using them for cross-referencing.
5. Lists can also be helpful as criteria in and of themselves -- whether employed in List Manager or in Extraction Manager. Since Tessitura's UI doesn't allow for nested criteria, I use Lists to bundle criteria in place of nesting.
6. List Manager would also be the tool for use if the dynamic functionality is warranted. (I'm typically using dynamic lists in the case of item 5).
7. Lists can be run through reports and utilities. And if set to dynamic, users can refresh counts on each lists built by other users if they're otherwise restricted by user permissions from editing each others lists.

I'm sure this is just scratching the surface, but those are the things that most immediately come to mind.

I'll be curious to see what people share.

-Emilie

Emilie's guiding principles are spot on.  I'd add

8. lists have a character limit for how much 'code' you can include, so you might have to 'nest' multiple lists to get all the desired performances or postal codes or whatever. (List D criteria are List A and List B and List C is what I mean by nest here.)  While extraction segments have the same character count limitation, just create a new segment in the same extraction, so all the parts are clearly together in the same place. 

9.Extracted output can be ideal for mail house list or export to WordFly as part of a clearly defined process (that's probably beyond the scope of this introduction) which includes promotion.