Symphony is an application that assists you with organizing, analysing, and reporting on themes found in text data. Generally speaking, any text that can be summarized into one or more thematic ideas is suited for use with Symphony. Examples include:
The Symphony Content Analysis Console is the launch point and home page for the web-based Symphony. From there you open projects and invoke all Symphony featues. The most frequently-used features are made accessible from a row of buttons at the top of the console. The remaining features are accessed through the main menu which is accessed by clicking the Menu button () in the upper-left corner.
|Microsoft IE (Edge)||Windows|
|Google Chrome||Windows, Linux, iOS|
|Firefox||Windows, Linux, iOS|
|Safari||Some mouse issues|
To use this application, you need to allow Symphony to validate your email address. Once validated, Symphony stores a cookie in your browser which will identify you as the owner of your Symphony projects. If your browser doesn't allow cookies to be stored, Symphony may not work as expected.
You can have your key emailed to you
Each project you create is an analysis initiative. Examples are 360 reviews, team assessments, employee engagement surveys, and Tweets containing a particular hashtag. Ultimately your objective is to uncover and measure themes in a body of text.
In the Home page, either double-click the project name in the Project List or click the project name then click the Open button above the Project List. The project will open and a summary of the project will appear in the Active Project Summary panel. At this point, opening any views or forms will display data relevant to the project.
Once you've completed your analysis, of if you want to start an existing project from scratch, you can delete it from the server. It is advisable that you make a backup of the project (using the Download option) if you think you might change your mind at a later date.
To delete a project:
If you have a Symphony project file that is not already on the server, you can upload it. You might do this if you created a project with Symphony Desktop, or if you downloaded and deleted a project from the server and now want to add it back.
To upload a project:
If you want to archive a project, or if you prefer to store your project on your computer instead of on the server, you can choose to download a copy to your computer.
To download a project:
Once you've created or uploaded a Symphony project, you can manage its content and produce reports from it. As a minimum, this means engaging in the following tasks:
Depending on the nature of your project, each of these tasks might be performed multiple times and might utilize different Symphony featues. The icons on the main toolbar toward the top of your browser give you access to the features that enable you to do most of your work. Additional features are available by clicking the Menu () button. Anytime while using Symphony you click the help () button or press function key F1, this help document will be loaded into your browser, preset to the topic that covers the view you have open.
Symphony in conjunction with the Symphony Synchronization Service can provide you and members of your organization the option to work collaboratively in real-time on the same project. For this feature to work, both you and your members must:
Anyone that fits these criteria will show up as being available for addition to your project
The Symphony Synchronization Service coordinates changes you and your team members make to ensure that everyone sees the project the same. When you make a change in Symphony, that change is also distributed to each of the team members that are connected to the project. If any members are using Symphony Desktop, they see the changes when they synchronize.
When added, an automated email will be sent out to each new team member, instructing them on how to access the project. The instructions cover both the web and desktop versions of Symphony.
Symphony accepts content from Microsoft Excel, Word, text files, and Tweets from Twitter.
Note that while you can import content from any of these electronic formats, you always have the option of directly typing or using copy/paste to enter you content.
The Excel Import utility lets you import Excel spreadsheets into Symphony. Typical uses:
To import an Excel worksheet, click the Menu button then click Excel Survey or Respondents Info under Import Content.
Start by uploading your spreadsheet to Symphony. Symphony reads the spreadsheet and returns a sample of rows -- the first 40 rows -- from the first worksheet. Symphony also returns a list of worksheets, so if your data is not on the first one, you can switch.
To import, you map the first respondent's data to Symphony. This is done by dragging cells from the spreadsheet to panels on the Excel Import form that are designated for various types of content. Symphony uses your cell mapping as a pattern to apply to each subsequent row. The pattern is repeated until Symphony encounters a row where the respondent name cell(s) have no value. At this point it is assumed that the end of the worksheet has been reached and processing stops.
Regardless of the nature of your data, you must include a cell or cells to identify the first respondent. If the worksheet doesn't include such a column, you will need to add one. (A column with an auto-incremented value will suffice.)
If your worksheet has columns for respondent demographics, or if you have ratings items, you can have them imported. To Symphony, demographics and ratings are the same thing, in that both become ways to aggregate your data around respondent characteristics.
When demographics or ratings are imported, they are done so as "Tag Groups" and "Tags".
If you are importing a survey, the comments are probably the main reason you are here. Symphony lets you import as many comment columns as your worksheet contains. You can also optionally import decorators -- codes, tags, and tag groups -- that are related to the comments.
You can have cells imported as codes, and have the comments initially coded to them. You might for example want to import the text of a question along with the comment. If you do this, a code will be created from the question and the comments that are in response to that question will be coded to it. This is a common practice; it provides an initial context for thematic coding. After all the comments have been coded to themes, the question code is empty and can be deleted.
Another practice is to import text that represents a high-level category for comments that are grouped together in the survey. For example, let's say the survey asks three questions relating to "Strategy". If your worksheet contains a cell with "Strategy" in it, you can map the three comments to it and they will all be coded to "Strategy" during the import.
You can optionally import Tag Groups and Tags along with comments. This is in addition to codes.
When you are satisfied with your Excel - to - Symphony mapping of content, click the Run () button. Your map will be uploaded and applied to the worksheet. A message will be displayed when it is finished. You can now close the form. If you go to People view or Coding view, you will see the comments and codes that were imported.
The Word Import utility is used to import interview transcripts that have been stored as Word documents. As a minimum, the document will contain the verbatim comments you will attribute to a single interviewee (respondent). It can however contain other text. For example, it is a commom practice for those who use an interview guide to transcribe the comments into a copy of the guide and them import the copy. Symphony can be directed to import only the texts that belong to the interviewee, or alternatively additional texts such as the actual questions can be imported and used as an initial code and/or a tag for the comments.
The extraction of text is based on Word Styles. So it is important that your document be consist with styles usage. If you are not familiar with Word styles, you will find an abundance of explanations if you Google it.
To import an interview transcript saved as a Word file, click the Menu button then click Word Interview Transcript under Import Content
To choose which respondent to attribute the comments to, click the Respondents dropdown list and click on a respondent.
The styles-to-content mapping is how you tell Symphony which content to import and what to do with it. The styles are the Word styles used by the texts in your document, the content-types are the various types of Entities you can create from the text.
When a style is mapped to a content type, an icon appears to the left of each paragraph that uses that style.
As mentioned before, the Text Paragraphs list shows all the paragraphs of text in your document. While doing the styles-to-content mapping, you might find it useful to hide text that is irrelevant and display only the text you are interested in. For example, if your document has a lot of boiler-plate text. You can do this by choosing to ignore all the text that uses a given style.
While previewing the document, you may see that you have content that is incorrectly styled. For example, you might see a comment that is not using the style mapped to comments. If you leave as-is, it will not be imported as a comment. You can fix it as follows:
When you are finished mapping Word styles to Symphony content, you are ready to perform the import. To do this,click the Run () button. A message will display when the import is finished. You can now close the form. If you go to People view or Coding view, you will see the comments and codes that were imported.
This feature enables you to import a text file. The entire contents of the file is imported as Comments, each one attributed to the Respondent you choose. A separate Comment is created for each paragraph. Example Uses:
To import an interview transcript saved as a text file, click the Menu button then click Text File under Import Content
From the drop-down list, choose the Respondent to whom you want to attribute the comments.
Click the File Browse/Choose File button and navigate to the text file you want to import.
Optionally enter one or more regex (regular expression) patterns. The intent of the expressions is to filter and/or substibute text prior to importing. If you are not familiar with regex, leave this blank. If you believe your data needs to be pre-processed, please contact us and we will help you with defining the correct regex patterns.
Click the Submit button to perform the import.
The Twitter Import utility lets you import Tweets into a project. You specify which Tweets to import by providing screen names (@) and/or hashtags (#). The Twitter author of each Tweet is set up as Symphony Repondent and a Comment is created for each Tweet. Various attributes of the Twitter account or of the Tweets can also be imported, providing additional ways of slicing the data.
In addition to the Tweets, Symphony imports other entities that can be used for deep analysis of the tweets:
Start by clicking the Menu button followed by Twitter under Import Content.
If you want to retrieve tweets from one or more specific Twitter users, enter their Twitter names here, one per line. This will return the tweets from the specified Twitter user(s) as well as the tweets that others have entered on their timeline -- for example replies to tweets. The name must include the "@" symbol. For example, @JohnDoe.
If you want to retrieve tweets containing specific user mentions or hashtags, enter them here, one per line. For user mentions include the "@" symbol; for hashtags include the "#" symbol.
This specifies the maximum number of tweets you want to retrieve. Processing is stopped once this number is reached. The overall limit is 20,000 tweets.
If this box is checked, retreats are filtered from the results.
When this box is checked, the user mentions and/or hashtags entered in the Searches box are excluded from the entities that Symphony keeps. For example, if the Searches box includes "#ManicMonday", the ManicMonday entry in the Hashtags group will be filtered out. The reason for this is that it may not be useful for analysis. For example, if you run a query of the most frequently used hashtags in project, the ManicMonday hashtag will appear first since every tweet is guaranteed to include it. If however your Searches box includes more than one hashtag or user mention, you might want to uncheck this box so that you can tell which search entry contributed the most tweets.
To begin importing tweets, click the Import Tweets button. Symphony will contact Twitter and begin downloading tweets. After the tweets are downloaded, Symphony inspects them to determine whether they should be kept.
After each import, Symphony tells you how many new tweets were added to your project.
Symphony Always tries to replace retweets with the original tweets. The reason for this is to 1) attribute it to the origiator, and 2) to ensure that the complete tweet text is included (the text of retweets are often truncated due to Twitter's tweet size limit).
If your import includes a lot of retweets, you might hit up against Twitter's rate limit. This is because each time a retweet is encountered, an additional request has to be made to Twitter for the original. Accordingly, it is possible that all retweets won't be resolved. In this case, wait 15 minutes then click the Resolve Retweets button and Symphony will make an attempt to resolve them.
People View is for managing respondents and their comments. In general, it is more efficient to import respondents from a spreadsheet and their comments either from a document or a survey spreadsheet, but this view provides the capability to add then one-by-on as well as edit their information after they've been added to the project through other means.
To open People View, click the People button on the console toolbar.
People View is organized into four sections:
In most cases, Symphony refers to people as "respondents". Comments are attributed to respondents. A respondent does not have to be a person; it can also be an event such as a focus group. Regardless of the actual entity, comments are attributed to respondents, and any attributes such as demographics that belong to the respondent are inherited by the comments attributed to the respondent.
Demographics are custom attributes pertaining to respondents. Examples are Gender, Location, and Tenure. Each demographic has "demographic values" such as Male and Female for Gender.
The primary purpose of demographics in Symphony is to provide ways of grouping and/or filtering respondents to perform deep analysis or targeted reports. For example, with a Gender demographic you can compare the average comment sentiment for Males and Females. Or run a Feedback Report that contains comments belonging to respondents from a particular country.
Symphony implements demographics as "tag groups" and "tags". A demographic such as Gender would be a tag group, and Male and Female would be tags within the group. What differentiates a demographic from other tag groups is that you define the tag group to be used for respondents only.
Generally if your comments exist in electronic form, it is more efficient to import them using the Excel or Word Import utilities. However, you can add/edit comments for a respondent directly in People View.
Code View has additional features to help you code efficiently. However, if you want to focus on coding comments belonging to specific respondents, you can also do it here.
The ideal comment consists of a single theme relevant to the project. This is so that only the data relevant to a report or analysis is included in filter criteria. For projects such as large employee engagement surveys, this might not be practical, in which case you may want to take advantage of Symphony's multi-codeAllows comments to be coded to more than one code feature. However, for projects such as team assessments or comparisons of job candidates, single-themed comments might add to the overall project quality. Symphony's split comment feature gives you a way to do this efficiently. When you split a comment, Symphony removes the split portion from one comment and creates a new comment with the split portion, and attributes it to the same respondent. The split portion inherits all tags attached to the original comment, but these can be managed separately without affecting the original.
Merge Comments is the opposite of splitting: you want to combine two comments into one. The result is the same as if you select the text of one comment, delete the comment, then paste it to the end of another comment. In addition, if the consumed comment has tags that the consuming comment doesn't have, they are added as well.
The text from the dragged comment is appended to the text of the target comment as a new paragraph, and then the comment is deleted. Any tags the dragged comment had are added to the target comment.
Field notes are basically comments about codes or comments. They are intended to provide you and your team with a way of communicating something about a comment, usually where you want to revisit it later on. For example, you might want to leave a field note asking a team member to reconsider the way they have a comment coded.
Field notes are visible in the comment's properties form. In Review view, an additional icon is displayed next to comments to indicate that they have field notess.
Symphony provides an efficient way of editing respondents, comments, and codes while navigating around the view.
Symphony's Coding view provides the capability to manage your coding structure and the location of comments within it.
To open Coding View, click the Coding button on the console toolbar.
Coding View is organized into three main areas:
|Coding Structure - Displays your coding structure as a hierarchy tree||Content List - Displays the codes and comments contained inside the code that is highlighted in the coding structure|
|Content Editor - Displays the text of the code or comment selected in the Content List. You can directly modify the text here|
Changes you make are sent immediately to the server and corresponding updates to the server project are sent back and displayed. If other users are connected to the same project, they see your updates, and you see theirs. If someone using Symphony Desktop synchronizes the project, their changes are also displayed.
This can be done one of two ways:
Codes can be deleted only when they contain no codes or comments.
Currently, management of comments is limited editing their text and to moving them between codes and changing their order amongst their peers. Comments must be added or removed using Symphony Desktop. If a team member using Symphony Desktop synchronizes after adding or removing comments, the changes will be reflected in your browser.
All changes you make to comments originate in the Content List. So in order to access a particular comment, its code must be the selected code in the Coding Structure. The following instructions assume that you have already selected the parent code.
Symphony provides the capability to make field notes for individual codes and comments. An example of a field note for a code is an elaboration on what you had in mind when you created the code. An example of a field note for a comment is you suggest to your team mates that the comment should be moved to a different code. You can use the code and comment field notes for whatever purpose you desire. But the general intent is to provide a way of making a statement or bringing attention to a code or comment.
Field notes are recorded in the lower section of the code and comment properties forms. To make a field note or to read one, simply double-click the code or comment to bring up its properties form.
Symphony's cluster analysis assists you with theme discovery and organization of comments around themes. The primary objective is to analyze some portion of your comments in groups, as opposed to reading and understanding them one-by-one.
To open the Cluster Analysis form, click the Cluster Analysis button on the console toolbar.
The Exploratory Analysis looks for word patterns. The results are heavily dependent on the frequency of patterns as well as the size of your project. It is further impacted by your settings such as "Min Phrase per Cluster". There is no "right" way to do this analysis other than to run it multiple times with different settings, code some of the results, run it again, and repeat this so long as you continue to get enough useful results to save you time over reading all the comments one-by-one. The more data you have, the better this analysis works.
The purpose of the Exploratory Cluster Analysis is to identify comments that have things in common. This commonality can be leveraged for a variety of other purposes:
As a general rule, the Exploratory Cluster Analysis should be run multiple times on your project. Each time, you will want to set a filter to narrow the scope of comments analyzed. For example, if you are looking for sub-themes inside a code, set a filter on that code so your analysis includes only the relevant comments. Be careful however, there is a point of diminishing returns. You should stop when your goals can be met using other methods.
An understanding of these steps can help you to understand what settings to use, and can help you to understand why the results are what they are:
When clusters are created, there is no actual changes made to your data. The clusters are merely a way of displaying your data that enables you to view it from this unique perspective and to enable you to act on the comments collectively if you choose to.
The Exploratory analysis results in a list of clusters. The cluster names reflect the phrase that the comments have in common. Clicking on a cluster fills the Comments list with the comments in that cluster. Clicking on a comment in the Comments list reveals the complete text of the comment below the list, where the portion of the text in the comment that matches the cluster is highlighted.
This results in a code being added to your coding structure and comments moved into it:
This results in the clustered comments being coded to an existing code. For example, let's say the cluster is named "Good Management" and you have a code named "Management is Great". Assuming the comments in both the cluster and the code reflect this idea, you would want the clustered comments to be moved to the existing code, without creating a new code.
Often there will be clusters that in your view should be one. For example, you might see "Teamwork", "Team Spirit", and "Working as a Team" all the same. You can of course code one of them, then use the "Code to Existing Code" technique to combine the others into the code. The same thing can be achieved within the Cluster list:
The Themed analysis looks at your existing coding structure and coded comments, and makes predictions as to where the comments in the scope of your analysis belong. In effect, your coding structure and coded comments function as a model for the analysis. It isn't looking for new themes, it merely helps you code within the confines of your existing coding structure. You would run a Themed Analysis when:
As mentioned under Themed Analysis above, Symphony identifies the codes in which it finds the best match for the comments being analyzed. This does not mean the comments belong in the codes it suggests! The results are based in part on:
So all it takes to be included is for one key word to exist in the comment. However, since Symphony returns only the best quality results it finds, the likelihood that a comment fits into the cluster is better than random; how much better is dependent on the extent to which comments that have something in common in one code are different from comments in all other codes.
The point being made here is that it is generally not advisable to simply take a code from the Cluster list in a Themed analysis and drop it on a code like you would a cluster in the Exploratory analysis. It is generally better to make individual decisions about comments. But this decision-making process is dramatically sped up by the fact that they have been pre-sorted to themes, and for you it becomes a "yes" or "no" decision as to whether a comment belongs in a code. You can drag a Themed cluster with the Alt key held down and it will code it to the target code. You should do this ONLY if you have already inspected the comments and you believe they belong together.
The Symphony Review is intended to enable you to get a feel of the overall flow of your analyzed content toward the end of your coding efforts. At the same time, it provides the same capabilies for creating and editing codes and comments and changing their positions as does Coding view. The difference is that Report view is not really optimized for coding. It provides a continuous flow through your coding structure, the same as it would be for a printed report.
To open Symphony's Review, click the Review button on the console toolbar.
In this view, the easiest way to code a comment is as follows:
A code or comment will move only if it can. For example, if a comment is the last in a code, clicking the down arrow will have no effect.
To modify the text of a code or comment:
The code and comment properties forms include an area for entering a field note about the code or comment. This can be used for any purpose you desire, such as a reminder to yourself about next steps related to the code or comment, or instructions to your colleagues. To indicate that a code or comment has field note, the Review displays an icon next to it.
To add or view a field note, double-click the code or comment to bring up its properties form. Also, you can quickly view field note by moving your mouse over the icon.
Decorators are additional pieces of information optionally displayed about a code or comment. For codes, decorators are a statistic. For comments, decorators are either Tags or the name or title of the respondent that the comment is attributed to.
To display decorators:
Symphony's Queries view enables you to define and run queries against your project. Queries consist of:
Symphony's Queries view is quite powerful and quick. It makes it possible for you to ask pretty much anything of your data and get an almost immediate response. If your project includes demographics or ratings items defined as demographics, you should find that Symphony's Queries view provides you with the tools you need to gain deep insights into your data.
To open Symphony's Query Utility, click the Queries button on the console toolbar.
If you decide to delete a query you defined, highlight it in the Queries list and click the Delete () button directly above the list.
In addition to the queries you define, Symphony also creates four queries in every project. These queries can be modified, but they cannot be deleted. Here's what they each do by default:
Queries View includes three lists of columns that can be added to queries. This section describes each.
Entity Columns represent the content in your project such as codes, tags, respondents, and so forth. Entities normally have relationships with other entities -- often many relationships. For example, a code has a relationship with all the codes and comments inside of it. When an entity column is included in a query, it effectively function as a row-level filter. What this means is that a row is output for each entity. If mutiple entity columns are included in a query, a row is output for each combination of entities.
Outputs the name of each Symphony user with access to your project. As a minimum it includes you but can include other users if you have a shared account and you give them access.
Outputs the name of each survey respondent or interviewee for your project Respondents are the entities to whom comments are attributed to.
TOutput the your codes at the respective levels.
If you have any demographics defined, they are listed next. Including one of them outputs the values of each of the demographic values. For example, a Gender demographic might output two rows: one for Male and one for Female.
Outputs a row for each Tag Group in your project. Tag Groups include demographics because demographics are set up as a special kind of Tag Group.
Outputs the Tags contained inside your Tag Groups.
Output each word/phrase found in the project.A key to understanding how to get what you want from a query is grasping the fact that when more than one entity column is included, an output row is created for each combination of values. For example if your project has demographics for Occupation and Gender, you will get a row for each Occupation/Gender pair if you include them both in a query. This effectively gives you the capability to create drill-downs into any slice of your project.
Statistic Columns produce numbers for you. They can be used by themselves, but when they are combined with one or more entity columns, a row is produced for each entity combination and the statistic is based on the entity.
A count of respondents.
A count of comments.
A count of words.
A count of how many times a word/phrase appears. This is used in conjuction with the Word/Phrase column from the Entities list.
Average # of words found in the underlying comments for each row. If no enties or attribute columns are included in the query, this is the average # of words found in all the comments in the project.
Generally speaking, these columns provide additional information about an Entity.
With Symphony Charts you can produce charts of your data. The charts use data from queries define in Queriess view. Currently you can product Bar, Column, Pie, and Line charts. Each of these charts take the same kinds of data sets: two columns where the first is an entity such as a Respondent, a Code, or a Tag, and the second column is a statistic calculated on the entity.
To open Symphony's Charts Utility, click the Charts button on the console toolbar.
The data used by charts is provided by queries defined in Symphony's Queries View. By default, new charts are set up to use the predefined "Sandbox" query. You can change this to any query in your project.
Symphony provides these types of charts:
|Column||Each data point as a vertical column from left to right|
|Bar||Each data point as a horizontal bar from top to bottom|
|Pie||Each data point as a pie slice where it's size is based on its percent of the values|
|Line||Each data point is at an x,y coordinate, where x is its position in the data series and y is the value|
To generate the chart, click the Run Query button. The query will produce the data, then the chart will be displayed.After you've run the query, you can change the chart type and size without running the query again; the chart will be updated automatically.
To resize the chart, drag the lower-right corner of the chart region in any direction.
After you've generated a chart, you can have it saved to your computer as a .PNG file. The dimensions of the file are the same as the chart region.
Symphony Word Cloud Generator creates a word cloud from text your project. A word cloud is an image that has words arranged in a way that conveys their relative frequencies. There is a variety of ways to depict word clouds. Symphony does it by varying the font size and font color. Words are arranged in a sprial, where the most common word appears in the largest font in the middle of the image, and the remaining words are placed around it in a clockwise rotation outward. The color and font size is varied along the spiral in order to accentuate the declining frequency of each word.
To open Symphony's Word Cloud generator click the Word Cloud button on the console toolbar.
No settings are required for a basic word cloud. Simply click the Create Word Cloud button and your word cloud will be generated
After you make a change to an option setting, click the Create Word Cloud button to update the word cloud.
This setting specifies the number of words to include in the word cloud. Symphony will include the most frequent words up to this number, and will only include as many words as will fit into the word cloud canvas.
When this is set to 1, the results are based on word counts. When it is set to 2 or 3, the results are based on frequncies of phrases of that length. Note that phrases take more space, so if you have this set to 2 or 3 consider using a suitably-low number for the Maximum Words setting.
The white region in the middle of the screen is the word cloud canvas. This is where the word cloud is output, and it determines the font sizes to use. You can resize it by dragging the lower-right corner with your mouse. While dragging, the size of the region is pixels is displayed.
This setting lets you control how large the word cloud is in terms of pixels. If you don't have much text you might want to make it smaller. Or if you have a document you want to include the word cloud in, you might want to set is to a size ideal for the document. These instructions assume that you have just generated a word cloud and it is currently being displayed.
This setting lets you exclude specific words. Symphony automatically excludes some words such as "the" and "is". If you see additional words that you don't want included, you can add them to the blacklist. When you update the word cloud, it is generated without those words.
This setting lets you specify a word that you want to make the subject of the analysis. When you specify a filter word, Symphony uses only paragraphs from your text that have that word in it. Paragraphs that don't have the word are ignored.
This setting works in conjunction with the Filter Word field; it has no effect on the result unless a Filter Word is specified. the Word Proximity is an additional filtering settting. It limits the words included in the analysis to those within the Proximity setting of the Filter Word. So only words that are within the proximity of the Filter Word are included in the analysis. If the Proximity is zero, the entire text of each paragraph containing the Filter Word is used.
Symphony's Feedback Report option produces a Microsft Word report from your project data. By default, the report consists of your coding structure and comments organized into a hierarch around the coding structure. Essentially, this report is intended to present your findings -- your coding structure -- as a single story, supported by the comments. Depending on the nature and size of your project, you may want all comments included, or only enough representative comments to support your conclusions.
The report is produced from a Word document that you provide as a template. As such, the report has the look and feel that you provide.
To open Symphony's Feedback Report Utility, click the Feedback Report button on the console toolbar.
Symphony lets you maintain a collection of templates. Templates can be used on each project, or you can have templates that are customized for specific projects. This can be any .DOCX file, but ideally should be one that is designed for your project, including boiler plate text and images, your organization's headers and footers, and so forth.
Symphony provides you with a starter template that you can use as-is or customize to look the way you choose.By default, Symphony adds the report content to the end of the document. You can however tell it to begin inserting at a specific location by creating a Word Bookmark named "Default" inside your template where you want the output to begin.
The Symphony Default template plus any you upload appear in the Word Templates list. The first step in generating a report is to specify which template you want to use. Once a template is chosen, the styles it contains are loaded into the Word Styles list. Symphony also makes an attempt to map content columns to styles.
After the template has been uploaded, you are ready to map Output Fields to Word Styles. If you are not familiar with Word Styles, a quick Google search will yield you more than you ever want to know.
When an Output Field is mapped to a Word style, a checkmark appears next to it. If you click on the Output Field, the style it is mapped to is highlighted and its radio button set.You may not know this but if you have ever used Microsoft Word, you are already familiar with styles. Heading 1, Heading 2, Title, and Normal are all examples. Word uses the Normal style by default. Styles determine how the text applied to it will look.
You may not need to map all the columns. For example, if your report only includes two levels of coding, you don't need to map styles for field that never get used. If while generationg the report Symphony encounters a field that needs a style, it will tell you so can fix it.
You can optionally set a filter to limit the scope of data output to the report.
Decorators are additional pieces of information attached to codes or comments and are displayed along with it. In the case of codes, a predefined statistic can be used as a decorator. In the case of comments, decorators can be the name or title of the owning Respondent, or Tags associated with the Respondent or comment.
A code can be decorated by at most one statistic. Comments can be decorated by as many items as are chosen, each separated by a comma.
To Add decorators:
The Report Distribution panel has settings for determining what to do with the result.
To run the report, click the Run () button and wait for your report.
When compared to Symphony Desktop, the online Feedback report has some limitations you should be aware of:
Symphony's Filter Group lets you limit certain output on a variety of criteria. It is available in the following views/forms:
When a filter is set, subsequent actions in that view/form behave as if your project consists only of data that fits the filter. Filters can be set on codes, tags, respondents, words, and sentiment.
When filters are set on items within one of these broad categories, the results are broader with each additional item. For example, setting a filter on two codes results in output related to either of the two codes.
When filters are set on more than one of these broad categories, the results are narrowed. For example if a filter is set on codes and tags, the results consist of the content related to the subset of filtered code further limited by the content that is related to the filtered tags.
Where the Filter Group is available, a button is provided that looks like this:. Clicking the button toggles the Filter Group open and closed.
When a filter is set on one or more codes, only content that is related to the included codes is included in the results. For example:
All codes that are checked are included in the filter.
When a filter is set of one or more tags, only content related to the included tags is included in the results. For example:
All tags or tag groups that are checked are included in the filter. Checking/unchecking a tag group causes all tags in that tag group as well as tag groups contain in that tag group to become checked/unchecked.
When a filter is set on one or more respondents, only content related to the included respondents is included in the results. For example:
You can limit filter results to comments and their related entities by the words contained in the comments, or by the size of comments. For example:
The sentiment filter lets you filter output based on comment sentiment. For example:
The sentiment filter consists of a group of radio buttons whose collective settings capture your intent. For Positive, Negative, and Neutral sentiment, you specify what to include as follows:
All settings are assessed for their impact but where they become mutually exclusive, the Neutral settings take precedence.
If you have content in one language but need it in another, Symphony can translate it for you. Symphony accesses Google's Translation API on your behalf, translating text from virtually any language to any language. Google detects the source language, and translates it to the language of your choice.
The Language Translation tool is opened by clicking the icon on the main toolbar. Clicking it more than once toggles it in and out of view.
The tool displays the quota balance on your account, the number of characters you will be charged to translate the current scope, and the projected quota balance.
Translation scope is based on what content is selected:
|A comment||The comment you clicked on|
|A group of comments (e.g. a selection range inside a code or belonging to a respondent)||The selected comments|
|A Respondent in People view||All the comments belonging to the Respondent|
|A group of respondents (by selecting a range)||All the comments belonging to the selected respondents|
|A Code||The comments inside the code and sub-codes.|
When the scope is changed the calculated usage is updated in the Language Translation tool.If the source language is the same as the language you want to translate to, it will still be processed and the utilization will be charged against your quota.
Every Symphony license and license renewal comes with a quota of 50,000 characters -- roughly 15 single-spaced typed pages. If you need more, you can add to your quota by purchasing additional characters.
This is a work in progress. Language features are being implemented gradually to improve the quality of the sentiment numbers.
Symphony attempts to measure the sentiment of each comment. This is done in the background as each comment is either added or edited, so there is nothing more you need to do. You can access the values by defining queries that include sentiment columns.
Sentiment reflects how someone might feel about a particular statement, and whether that feeling is positive or negative. Most would agree that the statement "I love the people I work with" has positive sentiment. This is what Symphony's sentiment analysis is looking to identify for you.
Symphony considers comments to have:
To truly capture the sentiment of text, one needs to take into consideration context as well as a human values system. The absense of either is a significant constraint. You should view Symphony's sentiment analysis with this in mind. Fortunately, Symphony does its analysis consistently, so comparing different aggregations (e.g. net sentiment across a demographic acrosss codes) can still be informative.
Symphony makes five sentiment statistics available in Query view. These in conjunction with query filters, entity columns, and range constraints on the sentiment query columns provide you with considerable possibilities for the values you can extract and their meanings. As with other statistic columns, new values are calculated for each query row based on the row data.
This is the sum of the positive sentiment minus the sum of the negative sentiment, divided by the number of comments. The statistic tells you whether the sentiment is truly positive or negative and to what extent. (A value of one means all the comments are positive and have no negative; a value of zero means they are equal.)
Tags are custom attributes you create for content. They can be associated with codes, comments, respondents, or any combination of these, and can serve a wide variety of purposes.
Tags always exist in Tag Groups. Tag Groups are merely containers that identify one or more tags as having something in common. Gender as a tag group for example would have Male and Female as tags. A tag group called Sentiment might have several tags, each one representing a different measure.
In addition to containing Tags, Tag Groups can contain other Tag Groups, so it is possible to define any level of complexity you need.
Tags are available in all views via a "Tag Widget", which floats above the view. When you click on a content item in a view, it becomes the "focus" of the Tag Widget, resulting in the attached tags to be highlighted. Tags can be attached to and detached from the focused item by clicking the radio button or checkbox next to the tag.
To open the Tag Widget, click the Tags () button on the main toolbar. Hide it by clicking a second time.
After Tag Groups have been created, you can change their attributes through the Tag Group Properties form.
If you no longer need a particular tag group or if you want to get a fresh start with it, you can delete it. Deleting a tag group also deletes all the tags and tag groups inside of it, as well as all tag attachments to entities, so be sure this is what you want.
By default, tag groups appear in the Tag Widget in the order they are created. The order of the tag groups matters in two cases:
You may want to move a tag from one group to another for a variety of reasons. For example, it is possible to define a tag in one group when you intended to define it in another. When you move a tag to another group, all attachments to the tag remain in place, so be sure the move is consistent with the constraints that have been defined for the destination tag group.
You will want to combine tags when you have two or more that have the same meaning. For example, let's say your data comes from a survey where respondents typed their Tenure into a free-style field and some entered "more than three years" while other entered "3 yrs". In such a case you will want the tag group to consist of tags that are a normalization of the values provided by the respondents.