Managing Your Subscriber Profiles

The SAS Information Delivery Portal enables you to update the subscriber profile that is maintained for you in the SAS Publishing Framework. When you subscribe to a publication channel, your subscriber profile controls the method of transport and the destination for package delivery. You can also enter name/value pairs in your subscriber profile to serve as filters. When the method of transport is e-mail or queue, you will receive only those packages that meet your filter criteria. These filters do not affect the channel content that appears in the portal.

You can set up multiple subscriber profiles, each with a different transport method and a different set of filters. The SAS Publishing Framework will treat each profile as a separate subscriber. When you subscribe to a publication channel in the portal, you will be prompted to specify which subscriber profile to use.

Regardless of your subscriber profile settings, you will still be able to use the portal to view content that is published through any of the available channels.

Adding a Subscriber Profile

To add a new subscriber profile for yourself:

If you have not already done so, open the SAS Information Delivery Portal, log on with your user name and password, and click Personalize on the toolbar. The Personalize window appears.
At the prompt Select what to personalize, choose Subscriber Profiles from the drop-down list. The Subscriber Profiles control panel appears.
Click opposite Add a new personal profile. The New Personal Profile control panel appears.
Enter a description for the profile.
Select a radio button to indicate the delivery transport method you would like:
- Select Email if you want published packages to be sent to your e-mail address. Click Next. Then enter the address in the field provided, and select a radio button to indicate whether the information is to be in text or HTML format. Then click Next.
- Select Queue if you want published packages to be sent to a message queue. Click Next. Then enter the queue address in the field provided, and click Next.
- Select None if you want to view packages in the portal instead of having them sent. Then click Next. All content published through available channels will be viewable through the portal, regardless of your subscriber profile settings.
In the Name/Value inclusion field, you can enter name/value pairs to be used as filters for the inclusion of packages. If the delivery transport method is Email or Queue, packages will be delivered to you only if they have these name/value pairs associated with them. The name/value pairs do not affect channel content that appears in the portal. For the delivery transport method Queue, you can also specify files and entries to be included.
In the Name/Value exclusion field, you can enter name/value pairs to be used as filters for the exclusion of packages. If the delivery transport method is Email or Queue, packages will not be delivered to you if they have these name/value pairs associated with them. The name/value pairs do not affect channel content that appears in the portal. For the delivery transport method Queue, you can also specify files and entries to be excluded.

For more information, see the section on Filter String Syntax.
Click Create Profile. The Subscriber Profiles control panel will reappear with the new profile listed under Manage personal subscriber profiles. You can now proceed by choosing another Personalize function, choosing another task, or opening another window.

For information about how to subscribe to a channel, see Managing Your Subscriptions.

Viewing and Editing Your Subscriber Profile

To view or edit your subscriber profile:

If you have not already done so, open the SAS Information Delivery Portal, log on with your user name and password, and click Personalize on the toolbar. The Personalize window appears.
At the prompt Select what to personalize, choose Subscriber Profiles from the drop-down list. The Subscriber Profiles control panel appears.
Find the desired profile under Manage personal subscriber profiles.
Click opposite the profile name. The Update Personal Profile control panel appears.
Update Description field as necessary.
Update the Delivery Transport method as necessary.
- Select Email if you want published packages to be sent to your e-mail address. Click Next. Then enter the address in the field provided, and select a radio button to indicate whether the information is to be in text or HTML format. Then click Next.
- Select Queue if you want published packages to be sent to a message queue. Click Next. Then enter the queue address in the field provided, and click Next.
- Select None if you want to view packages in the portal instead of having them sent. Then click Next. (All content published through available channels will be viewable through the portal, regardless of your subscriber profile settings.)
In the Name/Value inclusion field, you can enter name/value pairs to be used as filters for the inclusion of packages. If the delivery transport method is Email or Queue, packages will be delivered to you only if they have these name/value pairs associated with them. The name/value pairs do not affect channel content that appears in the portal. For the delivery transport method Queue, you can also specify files and entries to be included.
In the Name/Value exclusion field, you can enter name/value pairs to be used as filters for the exclusion of packages. If the delivery transport method is Email or Queue, packages will not be delivered to you if they have these name/value pairs associated with them. The name/value pairs do not affect channel content that appears in the portal. For the delivery transport method Queue, you can also specify files and entries to be included.

For more information, see the section on Filter String Syntax.
Click Update Profile. The Subscriber Profiles control panel window will reappear. You can now proceed by choosing another Personalize function, choosing another task, or opening another window.

Filter String Syntax

In the SAS Publishing Framework, publishers can specify name/value pairs that describe the package being published. To construct meaningful name/value filters, it is helpful to know the conventions that the publisher will use to describe packages at the time of publication.

Use the following syntax to enter name/value pairs to be used as filters

	name < operator  value >

where name is a variable to which a value might be assigned. Name is not case-sensitive. Operator relates the variable to the value. Commonly used operators are the comparison operators and the logical operators, which follow:

Comparison	Logical
`= equals`	`& AND`
`!= not equal`	`\| OR`
`? contains`

Value in the form of a string or a numeric value is appropriately assigned to the variable. Value is case-sensitive.

Examples

The following is an example of a package description using name/value pairs that a publisher has assigned to a published package:

   market=(Mexico, US) type=report Quarter4 sales _priority_=low

The following examples illustrate filter strings that determine whether the preceding example entity would be selected by the filter. If the package meets the filter's conditions, the package is delivered to the subscriber.

market=(US, Asia, Europe): NO MATCH. Because the equals comparison operator (=) is used, the subscriber's values and the publisher's values that are assigned to the variable name MARKET must match exactly. In this example, the subscriber filters are US, Asia, and Europe, whereas the publisher assigns a value of Mexico and US. The conditions for selection are not met. Therefore, the package is not delivered to the subscriber.
market=(mexico, us): NO MATCH. Because the equals comparison operator (=) is used, the subscriber's values and the publisher's values that are assigned to the variable name MARKET must match exactly. In this example, the subscriber's values do not match the publisher's values because of case differences. Therefore, the package is not delivered to the subscriber.
market=US | market=Asia | market=Mexico: NO MATCH. Because the equals comparison operator (=) is used, the subscriber's values and the publisher's values that are assigned to the variable name MARKET must match exactly. In this example, although the OR operator (|) might seem to cause a matching condition, the equals operator (=) requires that each name/value pair that is separated by an OR operator (|) match the publisher's name/value pair entirely. A match would result if the subscriber's values were written as follows:
market=Mexico, US | market=Asia | market=Mexico
The first name/value pair in the series would match. Therefore, the package would be delivered to the subscriber.
market=(Mexico, US): MATCH. Because the equals comparison operator (=) is used, the subscriber's values and the publisher's values that are assigned to the variable name MARKET must match exactly. In this example, the value set does match. Therefore, the package is delivered to the subscriber.
market=(US, Mexico): MATCH. Because the equals comparison operator (=) is used, the subscriber's values and the publisher's values that are assigned to the variable name MARKET must match exactly. In this example, the value set matches, regardless of the order of values within the value set. Therefore, the package is delivered to the subscriber.
market?US & market?Asia & market?Mexico: NO MATCH. The conditions that are specified in the subscriber's name/value pair read: Variable name MARKET must contain the values US and Asia and Mexico. The contains comparison operator (?) identifies the eligible values for consideration. In this example, although the publisher's variable MARKET contains US and Mexico, it does not also contain Asia. Because the logical AND operator (&) is used, its condition is not satisfied. Therefore, the package is not delivered to the subscriber.
market?US | market?Asia | market?Mexico: MATCH. The conditions that are specified in the subscriber's name/value pair read: Variable name MARKET must contain the values US or Asia or Mexico. The contains comparison operator (?) identifies the eligible values for consideration. In this example, the publisher's variable MARKET contains US, and the logical OR operator (|) condition is satisfied. Therefore, the package is delivered to the subscriber.
Quarter4=sales: NO MATCH. Because the equals comparison operator (=) is used, the subscriber's values and the publisher's values that are assigned to the variable name QUARTER4 must match exactly. In this example, because the publisher's variable name QUARTER4 does not contain a value and the subscriber's variable name QUARTER4 does contain a value of sales, the value sets do not match. Therefore, the package is not delivered to the subscriber.
Quarter4: MATCH. Variable names are not required to have values. In this example, because the publisher's variable name QUARTER4 does not have an assigned value and the subscriber's variable name QUARTER4 does not have an assigned value, the value sets match. Therefore, the package is delivered to the subscriber.
type=report & forecast: NO MATCH. Two conditions must be met. The equals comparison operator (=) requires that the subscriber's values and the publisher's values that are assigned to variable name TYPE match. In this example, the first condition is met because both the publisher and the subscriber assign the value report to variable TYPE. However, the AND logical operator (&) also requires that the variable name TYPE also be assigned the value forecast. Because the publisher's variable name TYPE is not assigned a value of forecast, the final condition is not met. Therefore, the package is not delivered to the subscriber.
type=report & sales: MATCH. Two conditions must be met. The equals comparison operator (=) requires that the subscriber's value and the publisher's value that are assigned to variable name TYPE match. In this example, the values match. Both assign the value report to the variable name TYPE. The AND logical operator (&) also requires that the variable name SALES match. Because both the publisher and the subscriber identify a variable name SALES with no assigned value, the final condition is also met. Therefore, the package is delivered to the subscriber.