
This documentation is for current Self-Service Analytics users. For best use of Self-Service Analytics you should request a username and password from your Self-Service Analytics system administrator.
New users should consult the Getting Started Guide.
Users upgrading to version 2.2 should consult the What's New Guide.
The documentation to Self-Service Analytics is split into three sections:
Content management and administration guide ... |
Query and reporting guide ...Reference and Definitions |
| sitemap |
| recent |

The Search box, located on the toolbar
| sitemap |

Example list of results returned by Search. Highlighted is an example result, displaying document title, summary, author and creation dates
| recent |

Example list of recent items. Highlighted are the two most recent items, showing the type, title, author and modification date
| recent |

Example list of user specific recent posts. Highlighted is the tab menu clicked to view this list

The user login box, displayed for all unauthenticated users
| log out |
| home |

An example tree navigation browser of all folders. This is displayed as a block on the left hand side of the screen
| sitemap |
| Icon | Content Type | Description |
|---|---|---|
|
|
Folders | Groups of all types of content. |
|
|
Article | Simple content type for short write-ups — often used as notes, or points for discussion. |
|
|
Link to a Web Page | Link to another web page, often external to Self-Service Analytics. |
|
|
Document Upload | Documents of any type which are uploaded to Self-Service Analytics for viewing and searching. Typically used for publishing longer pieces of information created using a standard desktop package like Microsoft Office. |
|
|
Project Request | A work item or task requested by one of Self-Service Analytics users. Often used to aid collaboration between groups in defining and delivering work, while tracking the progress of the request. |
|
|
Query | A query result showing a summary of customer information, displayed with a variety of tables, charts and other viewers. |
|
|
Filter | A query component restricting the records which are used within the query calculations. Filters are only created by saving from the query page — though their description and definition can be viewed like any other content. |
|
|
Custom segmentation | A query component describing the breakdown of a segmentation field into groups of related values. Custom segmentations are only created by saving from the custom segmentations page — though their description and definition can be viewed like any other content. |
|
|
Custom measures | A query component describing the user-defined calculations performed on the query to generate a set of custom measures. These include simple arithmetic calculations as well as query-wide percentages, differences, ranks and accumulations. Custom measures are only created by saving from the custom measures page — though their description and definition can be viewed like any other content. |
|
|
Audit | An audit of a dataset, providing simple profiles over all fields, displayed as a simple web page. |
|
|
Dataset | A Portrait Customer Analytics analytical dataset (a focus), displayed as a summary of the dataset with a comprehensive data dictionary. |
|
|
Dataset series | A collection of datasets within a single folder, displayed as a summary of the series with a list of timeline queries and datasets, and supporting simple administrative operation. |
|
|
Databuild | A description of the tasks undertaken as part of a data preparation process. |
*single asterisks* or _single underscores_ = emphasis
**double** or __double__ = strong
[a link](http://the.link.com "the optional title text") = a link
| add |
| reply |

An example email response, with the original message quoted at the top
| edit |
| delete |

The Comment viewing options section, displayed beneath the main body of the post and providing customization of the way comments are displayed
| edit |

The add content page, listing links to create all the available types of content. Highlighted is the tab used to view this page

An example tree navigation browser of all folders. This is displayed as a block on the left hand side of the screen

An example of the attachments section available when creating certain content types
| bookmark |

An example of the manage bookmarks page, with options to edit or delete the bookmarks
| bookmark |

An example of the manage bookmarks page, with options to edit or delete the bookmarks
| bookmarks |
| manage |
| my account |
| my account |
| my account |
| my account |
| my account |
| my account |
| my account |
| my account |
| subscribe |
| subscriptions |
| unsubscribe |
| subscriptions |

An example project history, displaying the states the Project Request has moved through, when the transitions were made and who changed the state
| Project Request |

An example of the Project Requests search results, displaying all current Project Requests and summarizing their title, author, priority, specification and target user for completing the request
.qsdv, .qstv, .qspv or .qsmv files) on the Portrait Customer Analytics server
directly to Queries on Self-Service Analytics.
.ftr.
An example of publishing a focus from the Quadstone System Explorer
.qsb..qshtml files) on the Portrait Customer Analytics server
directly to Audits on Self-Service Analytics.
.qshtml.qppublish -folder -title "February Databuild Results" -location 225 -description "Regular databuild." -user me -password ****
qppublish -title "Customer Audit" customer.qshtml -location 225 -user me -password ****
| my account |
?q=,home to select the site wide homepage, orhttp://myserver/?q=profiler/...).
| my account |
| my account |
| my account |
%QSHOME%\qp2.2A\portal\apache2\php.ini and find the
[mail function] section. Information similar to the following should
be entered:
[mail function] SMTP = email.quadstone.com smtp_port = 25 sendmail_from = quadstone@company.net
Self-Service Analytics can be configured to allow users to reply to outbound emails, with these replies captured within the Collaborative Framework content.
The inbound mail is where you set up a POP or IMAP-accessible mailbox, which Self-Service Analytics automatically polls during it's background cron processing. This can be used to add content into Self-Service Analytics via email. Currently it is setup to post replies to subscription notification mail as a comment to the original node. This mailbox should be configured as the 'outbound' email address, the mailhandler module should then be enabled and configured it via .
Please ensure cron processing is enabled and that 'Delete messages after they are processed?' is ticked.
Email address: quadstone@company.net Folder: INBOX (leave default) POP3 or IMAP: select IMAP mailbox domain: mailbox port: 143 mailbox username: quadstone mailbox password: <leave blank> mime preference: select plain text security: disabled send error replies: enabled from header: <leave blank> default commands: "type: comment" (without the quotes) signature separator: --
| query |

The query page, showing all available tabs and the current query

An example of finding fields in a dataset. The letters "ge" are found in fields "Age" and "Lifestage"

The query options for a field. Highlighted is the option to add this field as a segmentation to the current query

The query options for a field. Highlighted is the option to add a measure of this field to the current query

The query options for a numeric field. Highlighted are the options to add filters on this field as a record restriction to the current query

Query elements available for deletion. Highlighted is the change in cursor when you hover over a deletable query component.

The default measures list containing the count measure. Highlighted is the way to add this measure to the query.

The query type selector — highlighted is the choice between crosstab, profile and dataview queries

The filter combination selector — highlighted is the choice between including using all or any filter combinations

Clear the current query

Undo the last action
| save query |
| save filter |

Save a query or filter popup. Highlighted is the default "Profiler area" destination folder once saved.
| open query |
| open filter |

Load a query or filter popup.

Include or exclude selected records choice

Include or exclude missing values

Select on labels. Highlighted is the user choice to include or exclude the selected values from the query.

Select on ranges. Highlighted is the user choice to include or exclude the selected ranges from the query.

Select on user defined ranges

Select on pre-defined date ranges

Select on ad-hoc date ranges. Highlighted is the calendar helper for selecting date values.

Select on single string value. Highlighted is the opportunity to exclude a value from the query.

Creating a filter from a table label. Highlighted is a segmentation field label, which adds a filter on this field to the query.

Creating a filter from a table cell. Highlighted is a link which would add a filter on all segmentation fields defining this cell.

Creating a filter from a chart. Highlighted shows clicking on a bar to add a filter defined by the two segmentation fields of the chart.

Creating a filter from a dataview result table. Highlighted shows clicking on a value to add a filter defined by the the segmentation field and its value.

Display dataview query results of individual records

To export all selected records from a query.

Export record details.
QSHOME/2.2A/ws/config/jobscripts/exportrecords.qsb
This script takes the following parameters:
focus
exportlist.focus.pathname). This focus is created for
this export script in a temporary directory with a record
selection of the relevant population in-place (on field
qs_vfield_portalSelection_selectOnes). You can
delete it upon completion of the export.exportlist.drupal.user.uidexportlist.drupal.user.companyusernameexportlist.drupal.user.name).jobnamejobidexportfieldCampaignTargetingField).fieldscampaignnidexportlist.nid).
exportlist.titleexportlist.cellcodeexportlist.date| dataset |

To rerun a saved query.

The options available to change how the Queries are displayed. Highlighted is the selection box of the five key combinations.

The options available to change how the Queries are displayed

The layout preview. Highlighted is the graphical preview of charts for the current layout settings.

Sorting results in the layout tab

Display results using line charts.

Display results using single table display type.

Dual-axis chart showing Age by count and average income.

Dual-axis layout.

Compatible measures, all displayed on a single chart. This example includes measures on the Income field.

Composite profiles, all displayed on a single table or chart. This example includes three segmentation fields with identical segementations.
kmbinlabels attribute of each required field element to false.ymdlabels attribute of the metadata element to true.currency attribute of each relevant field element to the currency character of choice (e.g. $).
percentage attribute of each relevant field element to true.
custombinlabel attribute to each relevant field. You can then configure a specific label to represent a range of values by adding upperboundary, lowerboundary, and label attributes.

Setting the current dataset in a dataset series

Request query suggestions. Highlighted is the button to press to receive query suggestions.

Run a query suggestion. Highlighted is a link to run the selected query.

Adding structured query elements to your suggestions. Highlighted is an example of where a filter on Gender has been added.

Show the current query in suggest mode. Highlighted is the link to flip query modes to suggest queries.

Show the current query in build mode. Highlighted is the link to flip query modes to build queries.

Custom segmentations on the advanced tab

A custom segmentation on a field. Highlighted is the add link, required to add the segmentation to the query.

Highlighted is the indication in the current query of a custom segmentation on a field.

Changing the custom segmentation from the results page. Highlighted is the link on the segmentation name to take you back to the custom segmentation of this field.

User defined custom segmentation.

User defined custom segmentation.

Highlighted is the action link to save a custom segmentation.

Save a custom segmentation popup

Highlighted is the action link to load a custom segmentation.

Load a custom segmentation popup

Custom measures on the advanced tab

The table of custom measures

Adding an arithmetic custom measure

Selecting to change the constant used in an arithmetic custom measure

Adding a percentage custom measure

Percentage of column. Highlighted is a column of results, all expressed as a percentage of the column summary figure.

Percentage of table. Highlighted is a cell value, the summary across the whole table, and this cell value expressed as a percentage of the table summary.

Percentage of first column. Highlighted is the first row of the table, another row of the table, and that row expressed as a percentage of the first row.

Percentage of first row. Highlighted is the first column of the table, another column in the table, and that column displayed as a percentage of the first.

Adding a difference custom measure

Difference from column. Highlighted are rows which show the difference between the values and the summary values.

Difference from table. Highlighted are a cell in the table, the table summary cell, and these cells displayed as a difference from the overall table summary cell.

Difference from first column. Highlighted are the first row in the table and another row in the table, both displayed as differences from the first row.

Difference from first row. Highlighted are the first column and another column, both displayed as differences from the first column.

Adding a rank custom measure

Rank from column. Highlighted are a column of counts, and their corresponding (largest to smallest) ranks across that column alone.

Rank from table. The (largest to smallest) ranks are across the whole table, individually ranking all cells.

Adding a cumulative custom measure

Cumulative. Highlighted is a column which is accumulated independently from the others.

Table cumulative. Highlighted are the values, and the accumulated totals, column-wise across the whole table.

Highlighted is the checkbox to remove a custom measure from the current query.

Highlighted is the link to delete a custom measure from the custom measures list

Save a custom measure

Save a custom measure popup

Load custom measures

Load a custom measure popup

The field description in a query data dictionary
aggregation attribute of the metadata element in the focus metadata.

The query usage summary report.
This is a DBC for publishing content into Self-Service Analytics.
There are four cases — publishing content, datasets and articles and creating new folders.
qppublish [options] <filename>| Option | Required | Type | Default | Description |
|---|---|---|---|---|
-portal |
y | URL | URL for accessing Self-Service Analytics | |
-user |
y | text | Self-Service Analytics username to login to Self-Service Analytics as | |
-password |
y | text | the password for that Collaborative Framework username | |
-location |
y | folder node-id | node number of folder in which to create the new content | |
-title |
y | text | the name for the new node | |
-description |
n | text | the description text for the content, provided as a string on the command line | |
-description @ |
n | filename | the description text for the content, provided through a file |
qppublish [options] <focus filename>.ftr| Option | Required | Type | Default | Description |
|---|---|---|---|---|
-portal |
y | URL | URL for accessing Self-Service Analytics | |
-user |
y | text | Self-Service Analytics username to login to Self-Service Analytics as | |
-password |
y | text | the password for that Collaborative Framework username | |
-location |
y | folder node-id | node number of folder in which to create the new dataset | |
-title |
y | text | the name for the new dataset | |
-description |
n | text | the description text for the content, provided as a string on the command line | |
-description @ |
n | filename | the description text for the content, provided through a file | |
-default |
n | make this focus the default dataset | ||
-metadata |
n | filename | path to specify focus metadata | |
-translations |
n | filename | path to specify focus translations |
qppublish [options] -article| Option | Required | Type | Default | Description |
|---|---|---|---|---|
-portal |
y | URL | URL for accessing Self-Service Analytics | |
-user |
y | text | Self-Service Analytics username to login to Self-Service Analytics as | |
-password |
y | text | the password for that Collaborative Framework username | |
-location |
y | folder node-id | node number of folder in which to create the new article | |
-title |
y | text | the name for the new article | |
-description |
n | text | the description text for the article, provided as a string on the command line | |
-description @ |
n | filename | the description text for the article, provided through a file |
qppublish [options] -folder <foldername>| Option | Required | Type | Default | Description |
|---|---|---|---|---|
-portal |
y | URL | URL for accessing Self-Service Analytics | |
-user |
y | text | Self-Service Analytics username to login to Self-Service Analytics as | |
-password |
y | text | the password for that Collaborative Framework username | |
-location |
y | folder node-id | node number of folder in which to create the folder | |
-description |
y | text | the description text for the folder, provided as a string on the command line | |
-description @ |
y | filename | the description text for the folder, provided through a file |
In both cases, the DBC will report the node-number of the new content node that it has created.
This is a DBC for monitoring the state of a particular instance of Self-Service Analytics.
qpstatus <URL>qpstatus http://myserver.mycompany.com:996report on the system details of Self-Service Analytics.
The command will print out:
This is a DBC for checking whether a particular instance of Self-Service Analytics is still running.
qpping <URL>qpping http://myserver.mycompany.com:996report whether an active Collaborative Framework was available.
The command will print out Quadstone Portal running
at ... if there is a working Collaborative Framework at this URL (and
give an error otherwise).
This is a DBC for removing foci from the pool of web-servers supporting a particular instance of Self-Service Analytics.
qpunload <URL> [ <focus> ... ]qpunload http://myserver.mycompany.com:996would remove all the foci from the web services.
qpunload http://myserver.mycompany.com:996 myfocus.ftrwould remove the
myfocus.ftr focus from the web services.
A metadata file is an XML description of a focus and provides the formatting and display information for use within a Dataset. Specifically, it contains details on how fields are grouped together, descriptions for these groups and information about which fields are available for different aspects of the query creation process.
You can edit this metadata in Excel from Quadstone System Explorer (with theext/excel_metadata extension
installed), including field display labels, interpretations,
tags, derivations, and comments with the following steps:
metadata| Attribute | Required | Type | Default | Description |
|---|---|---|---|---|
aggregation |
n | min | max | mean | mode | median | sum | default measurement to add to the query for the field with the Objective | |
defaultdatefield |
n | field name | default date field for date-filters for suggestions | |
defaultfield |
n | field name | default field for aggregations or breakdown for suggestions | |
level |
n | text | name of record-type (e.g. "household" or "customer") | |
name |
n | text | name of dataset | |
ymdlabels |
n | true|false | false | format dates as YYY/MM/DD as opposed to DD MMM YYYY
|
schemaLocation |
n | text | location of the RELAX-NG schema definition | |
xsi:noNamespaceSchemaLocation |
n | text | location of the XSD schema definition | |
| Content | Required | Type | Description | |
fields |
n | subelement | list of fields | |
groups |
n | subelement | list of top-level field groupings | |
campaign |
n | subelement | campaign information about this dataset |
<?xml version="1.0" encoding="UTF-8"?>
<metadata level="customer" name="DirectBankUSA">
<fields>
<field name="CustomerNumber" display="Customer Number"/>
<field name="HomePostCode" display="Home PostCode"/>
</fields>
</metadata>
Note: no field grouping is being defined — so all fields will appear in a linear list.
<?xml version="1.0" encoding="UTF-8"?>
<metadata defaultdatefield="DefaultDate"
defaultfield="RespondPress" aggregation="mean">
<groups>
<group> <!-- no group name, ensures placement of field within hierarchy -->
<field name="CustomerNumber"/>
</group>
<group name="Demographics">
<comment>Core customer level descriptions provided as part of
the application process.</comment>
<field name="HomePostCode"/>
<field name="BranchPostCode"/>
</group>
</groups>
</metadata>
Note: no field display names are set. Two groups are created and all other fields are displayed in a flat list below the groups.
fields| Content | Required | Type | Description | |
|---|---|---|---|---|
field |
n | subelement | field definition |
<fields>
<field name="CustomerNumber" display="Customer Number"/>
<field name="HomePostCode" display="Home PostCode"/>
<field name="BranchPostCode" display="Branch PostCode"/>
<field name="StateCode" display="State Code"/>
</fields>
groups| Content | Required | Type | Description | |
|---|---|---|---|---|
group |
n | subelement | group definition |
<groups>
<group name="Service Information">
<field name="CallsPerMonth"/>
</group>
<group name="Campaign Details">
<group>
<field name="RespondPress"/>
</group>
<group name="Trial Campaign Details">
<field name="TrialTarget"/>
</group>
</group>
</groups>
Note: all other fields are displayed after the groups in the field list.
field| Attribute | Required | Type | Default | Description |
|---|---|---|---|---|
name |
y | field name | short / Portrait Customer Analytics field name | |
buckets |
n | true|false | true | should this field be presented as buckets in a query filter? (if any metadata is present) |
currency |
n | currency symbol | display using this currency symbol. | |
display |
n | text | long / display field name (if different from short name). Note: this string must not contain any punctuation (e.g. single quote, double quote) — as these will not be displayed correctly. | |
filterable |
n | true|false | true | can this field be used in a filter clause? |
id |
n | true|false | false | is field part of the 'key'? |
kmbinlabels |
n | true|false | true | use numeric abbreviations in chart labels. |
percentage |
n | true|false | false | display this field measures as percentages |
profile |
n | true|false | false | is this field profile-able (for suggestions)? |
querydimension |
n | true|false | true | can this field be used as a query axis dimension? |
querymeasure |
n | true|false | true | can this field be used as a query measure? |
showdata |
n | true|false | false | show this field in any dataview query result. |
visible |
n | true|false | true | is this field implicitly included in the group structure if not explicitly mentioned? |
| Content | Required | Type | Description | |
custombinlabel |
n | subelement | add user-defined labels to chart and table ranges | |
info |
n | subelement | query search 'additional comment' text |
<field name="CustomerNumber" display="Customer Number"/>
<field name="TimeAtAddressMonths" display="Tenure in Months At Address"/>
Note: by default the short (Portrait Customer Analytics) name is displayed.
<field name="DummyField" visible="false"/>
<field name="IntermediateCalculation" visible="false"/>
Note: by default all fields are displayed.
<field name="CustomerNumber" querydimension="false"/>
<field name="HomePostCode" querydimension="false"/>
<field name="ZipCode" querydimension="false"/>
Note: by default all fields are available for query breakdown.
<field name="CustomerNumber" querymeasure="false"/>
<field name="AgeRangeLabel" querymeasure="false"/>
Note: by default all fields are available for use within query measures.
<field name="HomePostCode" filterable="false"/>
<field name="BranchPostCode" filterable="false"/>
Note: by default all fields are available for use within query value based filters.
<field name="HomePostCode" buckets="false"/>
<field name="BranchPostCode" buckets="false"/>
<field name="StateCode" buckets="false"/>
Note: by default all fields are available for use within query range or label based filters.
<field name="Income" currency="$"/>
<field name="Spend" currency="$"/>
<field name="CustomerIdentifier" showdata="true"/>
<field name="ZipCode" showdata="true"/>
<field name="Response" percentage="true"/>
<field name="EligibilityFlag" percentage="true"/>
<field name="Age">
<custombinlabel label="Too young" upperboundary="18"/>
<custombinlabel label="Too old" lowerboundary="80"/>
<custombinlabel label="Middle aged" lowerboundary="30" upperboundary="50"/>
</field>
custombinlabel| Attribute | Required | Type | Default | Description |
|---|---|---|---|---|
label |
y | string | label to use for defined range | |
lowerboundary |
y | numeric | lower value for the range (included) | |
upperboundary |
y | numeric | upper value for the range (excluded) |
<custombinlabel label="Too young" upperboundary="18"/>
<custombinlabel label="Too old" lowerboundary="80"/>
<custombinlabel label="Middle aged" lowerboundary="30" upperboundary="50"/>
group| Attribute | Required | Type | Default | Description |
|---|---|---|---|---|
name |
y | text | group name (missing for a 'virtual' group) | |
| Content | Required | Type | Description | |
comment |
n | subelement | optional comment to be displayed with the grouping | |
field |
n | subelement | field group contents | |
group |
n | subelement | subgroup group contents |
<group name="Service Information">
<field name="CallsPerMonth"/>
<field name="ThreeMonthTrend"/>
</group>
Note: all other fields are displayed after this group.
<group name="Campaign Details">
<comment>Summary of phased credit card rollout marketing campaigns.</comment>
<group>
<comment>Initial press offering - no direct mail</comment>
<field name="RespondPress"/>
</group>
<group name="Trial Campaign Details">
<comment>Direct mail campaign follow up to initial press offering</comment>
<field name="TrialTarget"/>
<field name="TrialRespond"/>
</group>
</group>
Note: all field level information is set in the fields element above — not within the field elements within a group.
comment| Content | Required | Type | Description | |
|---|---|---|---|---|
| n | text | Comment or descriptions |
<group name="Campaign Details">
<comment>Summary of phased credit card rollout marketing campaigns.</comment>
<group>
<comment>Initial press offering - no direct mail</comment>
<field name="RespondPress"/>
</group>
<group name="Trial Campaign Details">
<comment>Direct mail campaign follow up to initial press offering</comment>
<field name="TrialTarget"/>
<field name="TrialRespond"/>
</group>
</group>
campaign| Content | Required | Type | Description | |
|---|---|---|---|---|
display |
n | subelement | Option determining the default layout of the campaign reports | |
financial |
n | subelement | Financial information about the campaign | |
infofields |
n | subelement | Data fields relevant for use within the campaign | |
populations |
n | subelement | Identified groups of customers for specific campaign analysis | |
responserates |
n | subelement | Expected response rates for treated and control groups |
<campaign>
<infofields>
<response name="CardVisa"/>
<reporting>
<field name="Age"/>
<field name="Gender"/>
<field name="Income"/>
</reporting>
</infofields>
<display showcharts="true"/>
</campaign>
display| Attribute | Required | Type | Default | Description |
|---|---|---|---|---|
showcharts |
n | binary | true | Show charts as well as tables in campaign report |
<display showcharts="false"/>
financial| Attribute | Required | Type | Default | Description |
|---|---|---|---|---|
currency |
n | text | Symbol to use for currency values in all reports | |
| Content | Required | Type | Description | |
costs |
n | subelement | Campaign costs | |
revenue |
n | subelement | Campaign revenues |
<financial currency="US$">
<costs action="1.2" response="2"/>
<revenue response="10.7"/>
</financial>
costs| Attribute | Required | Type | Default | Description |
|---|---|---|---|---|
action |
n | value or field name | Cost of contacting one customer | |
response |
n | value or field name | Cost of fulfilling the response from one customer |
<costs action="1.2" response="2"/>
revenue| Attribute | Required | Type | Default | Description |
|---|---|---|---|---|
response |
n | value or field name | Revenue collected from one customer's response |
<revenue response="10.7"/>
infofields| Content | Required | Type | Description | |
|---|---|---|---|---|
response |
n | subelement | Campaign response | |
treatment |
n | subelement | Campaign cell codes | |
championmodel |
n | subelement | Campaign champion predictions | |
reporting |
n | subelement | Campaign reporting fields | |
analysis |
n | subelement | Campaign modeling fields |
<infofields>
<response name="TrialRespond"/>
<treatment name="TrialMailing"/>
<championmodel name="TrialPropensity"/>
<analysis>
<field name="Age"/>
<field name="Gender"/>
<field name="NumberOfDependants"/>
<field name="MaritalStatus"/>
</analysis>
</infofields>
reporting| Content | Required | Type | Description | |
|---|---|---|---|---|
field |
n | subelement | Field for using in campaign reports |
<reporting>
<field name="Age"/>
<field name="Gender"/>
<field name="Income"/>
</reporting>
analysis| Content | Required | Type | Description | |
|---|---|---|---|---|
field |
n | subelement | Field for considering in modeling |
<analysis>
<field name="Age"/>
<field name="Gender"/>
<field name="NumberOfDependants"/>
<field name="MaritalStatus"/>
</analysis>
response| Attribute | Required | Type | Default | Description |
|---|---|---|---|---|
name |
y | field | name of field containing response values |
<response name="TrialRespond"/>
treatment| Attribute | Required | Type | Default | Description |
|---|---|---|---|---|
name |
y | field | name of field containing treatment cell codes | |
controlvalue |
y | value | treatment cell codes corresponding to the control group |
<treatment name="TrialMailing"/>
championmodel| Attribute | Required | Type | Default | Description |
|---|---|---|---|---|
name |
y | field | name of field containing champion model predictions |
<championmodel name="TrialPropensity"/>
populations| Attribute | Required | Type | Default | Description |
|---|---|---|---|---|
reporting |
n | text | node id of the reporting population | |
analysis |
n | text | node id of the modeling population | |
targeting |
n | text | node id of the targeting population |
<populations reporting="120" analysis="119" targeting="121"/>
responserates| Attribute | Required | Type | Default | Description |
|---|---|---|---|---|
treated |
n | text | expected response rate (between 0 and 1) for treated customers | |
untreated |
n | text | expected response rate (between 0 and 1) for untreated customers |
<responserates treated="0.05" untreated="0.02"/>
A translations file is an XML description of the meaning of fields in a dataset — a thesaurus for fields and customer groups. It provides the basis for the query search to convert plain language search strings into queries which can be executed against a dataset. Full examples of this file format are provided in the downloads area of this site.
<?xml version="1.0"?>
<qtrans>
<map to="male">man</map>
<map to="age >">older than</map>
<map to="NumberOfDependants > 0">parent</map>
<qtrans>
map| Attribute | Required | Type | Default | Description |
|---|---|---|---|---|
to |
y | text | what the phrase is mapped to | |
| Content | Required | Type | Description | |
| y | text | the phrase that gets mapped |
<map to="male">man</map>
<map to="age >">older than</map>
Note: the result of this comparison must be expressed using entitized characters.<map to="NumberOfDependants > 0">parent</map>
Note: exact case of the field name used in the mapping gives a more exact match for suggestions.
This is one of the blocks appearing in a column on the side of your screen and displays a list of the ten most recently published items of content, who published them and when they were published.

An example of the Recent items block, displayed down one side of the screen
This is one of the blocks appearing in a column on the side of your screen and displays a tree browser covering all folders for easy navigation of Self-Service Analytics, as well as a shortcut to adding new folders.

An example folder navigation block, displayed on the left-hand side of the screen. Clicking on the square beside the folder opens or closes the folder. Clicking on the folder name opens that folder in the main page
This is one of the blocks displayed in a column on the side of your screen and displays which users are currently logged into Self-Service Analytics and how many unauthenticated guest users are viewing the content.

An example list of all the users who are currently logged in, displayed at the side of the page
This is the primary toolbar within Self-Service Analytics, displayed in the header bar at the top of each page. It's primary function is providing shortcuts to navigation, allowing you to quickly find content published in Self-Service Analytics as well as being the main way of accessing Self-Service Analytics documentation.

Highlighted are the primary site navigation aids provided to all users
This is the secondary toolbar within Self-Service Analytics, displayed in the header bar at the top of each page. It's primary function is providing shortcuts to functions to manage your use of Self-Service Analytics — and in particular how it looks to you.

For authorised users, this Manage toolbar allows you to control how your view behaves
This is a navigation aid displayed at the top of each page, displaying the location of the page you are viewing within the context of all its parent folders. Clicking on the breadcrumb bar will take you back to that level in the folder hierarchy.

Highlighted is an example of the navigation provided at the top of every page, relating the current content with the hierarchy of folders within which its was placed
When comments are added to some content, they are displayed with this toolbar, which will allow you and other users to take action based on the comment posted. Specifically which actions depends on your permissions.

Highlighted is an example of the actions available to you when viewing a comment
This is what is displayed if you click on
| sitemap |

An example of the sitemap, displaying the contents of the DirectBankUSA folder
This is what is displayed if you click on
| home |

Highlighted are two example channels displayed on the homepage
On the the homepage there is a short mission statement (describing what your Collaborative Framework is all about) but also a set of blocks with links to a folder and a small number of most recently modified contents. These blocks are channels — and you can add other channels to the homepage if you have the right permissions.

Highlighted are two example channels displayed on the homepage
A query is a generic term to describe what users create when they are running fast-counts or reports on a dataset. They provide a summarised of the data. The summary metrics form part of the query. As do the breakdown fields (or segmentation) and any filters which define the set of records which are used by the query. Within Self-Service Analytics there is a distinction between a saved query — which just contains a definition of the query — and a published query — which contains both the definition and snapshot of results of the query.
An Article is a simple document which can be used to record notes or short discussions in Self-Service Analytics. It consists of a and a — which can be formatted to be more easily readable.
When viewed, an Article just displays the title and body within the main Collaborative Framework page.
An Upload Document provides a way to publish any type of written document or file to Self-Service Analytics. It can be used to give access to a, for example, Powerpoint presentation or Word document report to any authorized user of Self-Service Analytics. It consists of a and a — which can be formatted to be more easily readable — and an — with to select the file to publish to Self-Service Analytics.
When viewed, an Uploaded Document page displays the title and body within the main Collaborative Framework page but includes a link to allow the viewer to download the associated document.
An Link to a Web Page is a way to publish a reference to a page on another website to capture interesting content available elsewhere on the intranet or internet. It consists of a and a — which can be formatted to be more easily readable — and a — which you can paste directly into from your web browser's Address bar.
When viewed, a Link to a Web Page displays the title and body within the main Collaborative Framework page along with a hyperlink to the associated web page.
A Dataset is a way to publish a reference to an analysis dataset (a focus) hosted on Portrait Customer Analytics analysis server. Further it offers a way to undertake fast counts or data selections on that dataset. It consists of a and a — which can be formatted to be more easily readable — and a — which may have been completed automatically when you publish the reference to the data from outside Self-Service Analytics, but which can also be entered manually if you know the location of the data.
When viewed, an Dataset displays the title and description within the main Collaborative Framework page, as well as details of the dataset as a whole, the individual fields and a number of action options to allow you to analyze the dataset.
An Query is a simple report stored and displayed within the Collaborative Framework. It consists of a and a — which can be formatted to be more easily readable — a checkbox to allow users to share their saved queries; a — with a to allow you to upload a Query result file from your PC, and an option to include a reference to the which in turn enables future queries to be executed on the same dataset. Alternatively these latter two values may be automatically completed when the Query is published from a Collaborative Framework fast counts session or from Portrait Customer Analytics analysis.
When viewed, a Query displays the title and description within the main Collaborative Framework page, as well as a summary of the Query contents, its visibility and the details of the report as a whole. The way this information is displayed depends on the layout at the time it was published, or last edited.
An Filter is a query component to restrict which records take part in the query. It consists of a and a — which can be formatted to be more easily readable. The definition of the query is created at the time of saving.
When viewed, a Filter displays the title and description within the main page, as well as a summary of the Filter contents, its visibility and the definition of the filter in terms of fields and comparisons.
An Audit is a specialist report created by Portrait Customer Analytics to give a high-level overview of the contents of a dataset and the correlations which are contained within it. It consists of a and a — which can be formatted to be more easily readable — and a — with a to allow you to upload a Audit file from your PC. Alternatively this last values may be automatically completed when the Audit is published directly from Portrait Customer Analytics System analysis.
When viewed, a Audit displays the title and description within the main Collaborative Framework page, as well as the contents of the Audit as a whole.
An Databuild is a way to publish a reference to an analysis databuild process hosted on Portrait Customer Analytics analysis server. It consists of a and a — which can be formatted to be more easily readable — and a — which may have been completed automatically when you publish the reference to the data from outside Self-Service Analytics, but which can also be entered manually if you know the location of the databuild script.
When viewed, a Databuild displays the title and description within the main Collaborative Framework page, as well as details of the parameters and task incorporated in the data build process as a whole.
When viewing content, titles or other Collaborative Framework content marked with * indicates this is new or recently published.
When submitting content, form elements marked with * indicates a required field which must be completed before the request is submitted.
Self-Service Analytics is configured to restrict the size of any single document to upload and also the total volume any individual user can upload.
By default these settings are:
The current query is displayed in a pane at the top of the query page. It is present for all tabs on the query page and shows the query which will be executed when is pressed. It contains both descriptions (of fields, measures and filters) and actions (remove elements from the query, build crosstabs or profiles, combine filters with and or or).

An example current query
Roles are a key concept in Self-Service Analytics — each user is assigned one or more of them and they govern what functionality or content that user can access. As part of the demonstration content provided with every Collaborative Framework there are a number of predefined roles (the standard roles — in addition to the default 'anonymous user', for guests, or 'authenticated user', for users with logins) which are intended to show different aspects of user functionality. The standard roles are:
When users publish content to Self-Service Analytics they are required to select a location (a folder) into which that content is placed. A default save location provides a simple way for users to customize the saving of their content to make the process more efficient and easier to use.
The customer module provides support for separating users into separate groups, who can work completely independently, while sharing content within their group (their content is stored within separate secure group folders), but have no access to any content published by users in any other group, nor even see the existence of any other groups or users (as user identities are anonymized). This separation of groups is targeted for service providers who host many different organizations within their Collaborative Framework installation.
The content in Self-Service Analytics is organized into folders. Everytime a user creates a new piece of content they are given the option to place the content in a folder. It is possible to set a default folder on a per user basis. If content is created, but not placed in a folder, the content is stored in the root folder. This is not directly browsable from the folder tree. However, you will be able to see this new content in the recent files list. When this content has been viewed, it is advisable to move it to a known folder as soon as possible.
A timeline query has been created to be refreshed everytime a new dataset is added to the dataset series. This automatic scheduling of update of the query results creates a new set of results for every dataset. You can view any of the results in the timeline by navigating through the results.
A dataset series is a grouping of related datasets within a single folder. This forms the basis of automatically updating timeline queries to show results on new data.
A custom segmentation is an alternative grouping, classing or banding of values into ranges on segmentation fields. In Portrait Customer Analytics terms, this is equivalent to a binning. This custom segmentation is used primarily when evaluating queries --- with the result tables and charts using the custom segmentation in its display.
Decisionhouse is the module within the Portrait Customer Analytics which enables interactive analysis (fast counts integrated with predictive modeling).
It can be used to publish Queries directly to Self-Service Analytics.
The Quadstone System Explorer is the module within the Portrait Customer Analytics which enables browsing of the file system on the analysis server from the users PC — as well as enabling a number of data preparation processes.
It can be used to publish many types of content directly to Self-Service Analytics.
This is the component of the Portrait Customer Analytics that controls the execution of data build plans.
This is the component of the Portrait Customer Analytics that executes the individual tasks within the data build process. There are over 20 separate data build commands, grouped by function into areas for importing and exporting data, enhancing datasets, joining datasets, managing datasets and producing reports. A special data build command is available to manage the data build process. Typically they are executed from the command-line or via a build plan.
A focus is a Portrait Customer Analytics analytical dataset. This is a
proprietary, binary, compressed format which allows
Portrait Customer Analytics to access data extremely quickly. It has a
.ftr file extension. It is the underlying data
representation behind a Collaborative Framework Dataset content type.
A Profile and Audit is a web page which contains simple
profiles over all fields and against set measures. It is a
specialist report created by Portrait Customer Analytics to give a
high-level overview of the contents of a dataset and the
correlations which are contained within it. It has a
.qshtml extension. It forms the basis for an Audit content type.
A Model Snapshot is a web page which contains simple profiles
over all fields in a dataset against a model score result. It
is a specialist report created by Portrait Customer Analytics to give
a high-level overview of the performance of a model. It has a
.qshtml extension. It forms the basis for an Audit content type.
A crosstab file is an XML description of a query definition
and its results. These are created by Portrait Customer Analytics and
are stored on the analysis server. They have file extensions
.qsdv, .qstv, .qspv,
.qsmv, or .qsxt (depending on what
tool generated the crosstab file). These files can be uploaded
to Self-Service Analytics and are stored and displayed as saved query.
The objective is a field which specifies some attribute of each record that the user is particularly interested in e.g. wishes to predict in a model or report across. The objective field is sometimes called the outcome, dependent variable or response. It contains a known historical outcome for each customer. Only one objective field may be set in any dataset.