Custom Filter and Column Requirements

Please review all 3 pages of this document and return it to your Business Consulting Team

Filter Requirements

The following requirements should be documented when defining a new Customer Specific Filter/Column:

1.    Filter Name:  Name that will appear within Targeter for users to reference.
2. Filter Location: Heading location of where the new filter should appear under in the Add Filter dialogue box. The default is Customer Specific.
3.    Filter Types: 
   1. Drop Down Text Input (examples: AF Expected Value, Gift Officer)
   2. Multi Select (example:  Relationship Type, Home Core Based Statistical Area) – this is the most common filter type for Customer Specific Scores and Codes
4.    Data Source File: Source file name of where the related data for the filter is located.
5.    Help Text:  One to two sentence explanation of the filter that should appear on roll over.
6.    Use Case:  Brief statement on how the filter will be used by the user.
7. Sorting: Any special sorting necessary in the case of codes or if the content contains symbols (such as a "$") or number ranges ($100-$999). The default will sort A-Z for words or high to low for numbers.

Column Requirements

For the purposes of this document, Columns need to be defined as static figures that can be created in batch each night.  This means that the information in the Columns cannot be dynamically generated based on the Filters selected in the user’s Query.  The majority of columns are defined so that each Entity ID is related to one value (e.g. MG EVI, Net Worth, etc.).  However, in some cases Entity records are related to more than one value that needs to be displayed (e.g. Gift Officers).  If an Entity could be associated with more than one value then the requirements will need to document how that information should be displayed (i.e. only include primary, show all and wrap data in column by separating with commas, etc.).  For this reason, you should also give thought to the name of the Column so that it is clear to the user.

Requirements for Targeter Column include:

1. Column Name:  Name that will appear as heading on column.  May or may not be identical to Filter Name.
2. Column Location:  Heading location of where the new column should appear in the Add Column dialogue box.  This should be consistent with where similar columns currently exist and with the location of a related Filter. The default is Customer Specific.
3. Score Type:  Is the score a numeric value or dollar value ($)? Is the score a code that is translated as text (e.g. name, description, rating type), numeric range (50 – 75), or dollar range ($100-$999)? Is the score actually a free text field that is to be displayed (like a salutation line or city location)?
4. Data Source File:  Source file name of where the related data for the column is located.
5. Help Text:  One to two sentence explanation of column that should appear on roll over.  May or may not be identical to related Filter help.
6. Use Case:  Brief statement on how the column will be used by the user (may be the same as filter’s use case).
7. Handling if more than one value per Entity, if applicable:  If there is more than one value per entity, what is the preferred way for the information to be displayed (i.e. only include primary, show first value, only most recent score/value, show all and wrap data in column by separating with commas, etc.). 
8. Sorting:  Any special sorting necessary in the case of codes or if the content contains symbols (such as a "$") or number ranges ($100-$999). The default will sort A-Z for words or high to low for numbers.

Special Sorting Specification Requirements

By specifying the special sorting, you will be stating the order of how you would like the description/values to appear in the filter and the column in Targeter. 

The following requirements should be documented when defining the special sorting of a new Customer Specific Filter/Column:
 

1. Code/Value: The code or value for the data (e.g. P1, T1, CA, A, B, etc.).
2. Description: The description or code translation of that code or data value (e.g. $100-$999, Level 1, Top Prospect, Major Gift Potential, etc.).
3. Sorting Order: Desired sorting order of the descriptions/values and how they would appear in the filter and column indicated by ordering 1 (seen first in order), 2 (second in order), 3, etc.

Please add additional rows as needed.