Anyone can configure Omniscope files systematically following the 6-phase checklists outlined below. Most issues in configuring Omniscope files arise because essential steps like changing default data typing assigned on data import are not addressed BEFORE moving on to other tasks. Following the checklists below, anyone can achieve rapid, reliable results and make best use of Omniscope. This phased outline and checklists also serve as a useful guide for structuring training sessions.
Options for importing data into Omniscope include importing from delimited data files like CSV and XLS, relational tables/reporting views created using SQL statements that return a table, various remote-hosted or 'cloud' based data sources via connectors, transformed tabular XML [7] and some multi-dimensional 'cube' data structures (Data Manager Edition only). The Enterprise and Data Manager Editions (2.6+) has a dedicated visual drag and drop data assembly, filtering and transformation Data Manager [8] workspace that can be used independently of Omniscope. The Professional Edition has Most of the options are documented in the Importing Data [9] chapter of this User Guide, which includes sectons on creating [10]and importing data files [11], making and refreshing database connections [12], using connectors [13] to online/remote data sources and more. More technical articles and examples relating to importing data via Data Manager or the Professional EDition Data Import and Merge Wizards are available in the KnowledgeBase [14], which includes sections on supported data file formats [15], examples of database connections [16] using ODBC and JDBC, and other related topics.
This checklist covers tasks you should perform AFTER importing a starting data set for the first time, but BEFORE beginning to analyse how to filter, visualise or present the complete data set. Most of these tasks are coved in the Editing Data [17] and Managing Data [18] chapters of the User Guide.
The Data Management phase focuses on data set completeness and correctness. Data typing assumptions made by Omniscope on import should be checked, columns duplicated, expanded, collapsed or tokenized to facilitate end-user interaction with your file. In this phase, 'data scrubbing' view configurations (rather than final presentational views and layouts) are used, normally working on a single tab entitled 'Data Set' or similar. Use Table View column sorting and the Chart View to examine extreme values in each column, correct null (blank) and missing values, and add related content to the file, such as image sets, maps and links to related web pages and web services.
At the end of this phase, the single 'DataSet' tab should reveal all non-empty and non-uniform data fields and filters, using both Sidebars if necessary to check all the filter devices in the Table/Chart View(s) without aggregations or groupings. You may need to duplicate certain columns so that they can be typed or formatted differently, providing different filtering options for users. Note: it is good practise to always leave this unfiltered 'Data Set' tab accessible as the final tab on the far right of the file tab set, providing an instant, credibility-enhancing maximum granularity view of the data to any user who clicks on the tab.
This phase focuses on optimising the data set for its intended audience. The checklist covers tasks you should perform, or options you should consider AFTER you have imported/merged all the data sources and 'scrubbed' the data to ensure correctness and completeness, but BEFORE you begin to define the best ways to visualise and present the data set as a presentation or reporting 'dashboard' file. Most of these tasks are covered in the Managing Data [18] and Configuring Files [19] chapters of this User Guide.
In this phase, column re-naming should be used to shorten names to save space and make them instantly meaningful to the end-user audience. Unneeded columns (especially empty or uniform-value columns) can be hidden or deleted, and the number of unique category values can be reduced, either via re-naming/consolidating values with data edits, or by adding formula columns that re-categorise records into fewer categories. Formulae can also be defined to transform imported data fields into more useful values and to detect alert conditions to be highlighted. If you use formulae to convert/reduce total category values, or to extract useful data fields from within text strings, your changes will be re-evaluated on every refresh. Aggregations can be set and aggregation formulae specified to create transformed views of the data for use with most views.
At the end of this phase, all the data, images, maps and link references required to meet end-users' requirements should be in the file, and the single 'Data Set' tab should show all the fields, both data and formula, which have not been globally hidden. Additional 'Subset', 'Formula' and 'Aggregated' tabs will have been added to show useful data subsets made reference-able as Named Queries, the inputs and results from defined Formulae, and various Aggregation settings with key values calculated according to specified aggregation functions displayed. Don't worry, you will delete all these preliminary testing tabs by the end of the next phase.
This checklist covers tasks your should perform, or options you should consider, AFTER you have optimised your data set, defined reference-able data subsets i.e. Named Queries, added Formula fields that calculate useful values and alert conditions, and defined useful Aggregation settings (including aggregation functions by field/column), but BEFORE you decide the optimal combinations of views that best suit the requirements of the file. Most of the documentation of the Views and how each is best used is in the Exploring Data [20] chapter of the User Guide.
Omniscope offers a large and growing number of views, each of which is highly configurable. In the Visualisation phase, you test each View on its own tab, seeking the best configuration(s) of each view for the data set and the requirements of your intended audience. You may create more than one variant of each view. Views determined to be of limited value to the audience can be hidden.
At the end of this phase, you should have a tab for each view you plan to use, with one or more variations of the view on each tab, perhaps some displaying subsets of the data defined by Named Queries, and others displaying Aggregated views with column-specific functions as defined in the Aggregation settings in each view.
This checklist covers tasks your should perform, or options you should consider, AFTER you have defined the views you plan to use, but BEFORE you create the tab sequence that will convert your file into a final presentation. Most of these tasks in this phase are documented in the Reports & Presentations [21] chapter of the User Guide.
Unlike previous phases, the Presentation phase takes a minimalist, 'zero-based' approach to file configuration, i.e. the bias is that everything should be hidden unless it is needed on a specific tab to make a specific point or enable a particular end-user interaction. Working with the most useful view configurations created in the previous phase, the objective of this phase is to create a multi-tabbed presentation where each tab is addressed to a specific issue with a specific message supported by the data. In this phase the philosophy is "less is more" to simplify the audience experience, but with credibility-building granular detail always only one click away. Don't be afraid to create many different tabs, each focused on specific user groups and points to be made, rather than trying to put too much on one tab. The objective is to create a file that opens and navigates just like a slide presentation.
At the end of this phase, you should have a highly-visual, interactive, multi-tabbed presentation file that your users can quickly and easily consult, filter, and print.
This checklist covers the final file configuration options relating to branding, data refresh and how others will be able to use the file. Most of the tasks in this phase are documented in the Save & Export Files [22] chapter of the User Guide.
In this phase, Help screens are added, along with selected branding options (opening screen, closing screen, banner ads, corner logos, etc.). File settings relating to refresh, file security, and other publishing options configured in the file when saved are all considered in this final phase.
The Data Import phase is documented primarily in the Importing Data [9] sections of this User Guide, which includes topics such as importing data files [11], making and refreshing database connections [12], and using connectors [13] to online/remote sources and more. More technical articles and examples are available in the KnowledgeBase [14], which includes sections on supported data file formats [15], examples of database connections [16] using ODBC and JDBC and other related topics, such as importing transformed XML. [7]
Getting started with Omniscope usually involves importing a copy of a structured table of data, such as a spreadsheet file or a reporting view from a SQL-based relational database. Options include:
1-01 Create new file [10] - manually type or cut and paste data into a blank Omniscope file
1-02 Open data file [11] - import data from a delimited data file (see potential issues list below)
1-03 Connect to database [12] - connect to a relational database using ODBC or JDBC protocols
1-04 Using Connectors [13] - use one of the available Connectors to access/import remote-hosted data
1-05 Open image collection [23] - open and import a folder of images, together with user-editable tags
1-06 Folder of files [24] - access and analyse a folder of files (documents, audio/visual media, etc.) to create a data set of filenames/paths and user-editable tag names
1-07 Open map [25] - access our Map Library [26], download a geo-coded map file and build a data set, including manual or automatic placement of records by decimal longitude/latitude. Alternatively, screenshot an online map image, note some reference coordinates, then use Omniscope to geo-code the image and build a data set to overlay the image map.
1-08 Perform merges [27] - Use the Merge Wizard if additional data from other sources needs to be joined or concatenated with your initial data set. Before performing a join, test the uniqueness of join criteria columns using the Table View: View Tools > Tools > Select duplicate records command.
Note: If new, currently unspecified columns might be added to one or more of your merge files in future, do not specify the fields to import, so that Omniscope will continue to import all fields in future. You can then Hide or Delete any unneeded fields as a remembered action.
Data files are often not delivered formatted according to precise international standards. Differences in formatting of data within tables and delimted files around the world can affect data import and display in Omniscope. Below are some common issues which you may encounter when importing data tables into in Omniscope:
Regional formatting - When importing data by opening a CSV or Excel XLS file, Omniscope analyses the data in the file to determine how the data is arranged and which fields (columns) are most likely of data type Text, Numbers, or Dates & Times. The regional settings in your computer's operating system (Windows, or Mac, etc.) have a strong influence on this operation. For some combinations of settings and data formats, Omniscope cannot reliably detect the situation automatically. If your data opens incorrectly and your fields are not correctly structured, numbers have the wrong decimal place, etc. please consult the File > Open file [11] dialog page, which contains options to help with these situations.
For example, if you know your data has been formatted for a different region, change the Locale drop-down accordingly. For example, if you live in Germany but have received a CSV from an American customer, you should choose "English (US)". If you find Omniscope gets things wrong and your data is incorrectly recognised, you can disable auto-detection of dates and numbers by deselecting the two Recognise... check boxes on the File > Open file [11]dialog. All fields will open as Category or Text data and their text values will be preserved. You can then use Data > Manage fields [28] [29]to configure each field (column) as you would like it to display.
Data file delimiters - CSV stands for "Comma Separated Values", which means the cells in each record (row) of the data table are separated by the comma character. However, this is not a formally-documented standard, and if you are in a region that also uses the comma in numbers instead of the decimal point (e.g. several European countries, such as France), some versions of Excel create CSV files that use a semicolon as the separator character. Sometimes these multi-column tables files are saved with a CSV or even a TXT extension. Omniscope is unable to detect this situation automatically. If you open such a file in Omniscope, your data will very clearly be wrong, with most columns appearing as text with semicolons. To avoid this problem, use the File > Open file [11]Customise data import dialog to change the separator character to a semicolon " ; ". You can also do this with 'pipe' "|" delimited files, but you must first change the file extension on the data file to .CSV, even though the file is really is 'pipe' and not comma delimited.
Dates & numbers - If you are running on Windows, when importing data that is in a delimited text format such as Excel XLS, CSV or TSV (tab-separated values), Omniscope will use your Windows Regional Settings to try to automatically recognise data. For example, for a PC with United States Regional Settings, Omniscope will recognise "5/13/2005" as a date and "1,500.5" as a number. For some international users, however, this may not work as expected and the result will be an import of all columns as data type Text (shown in Omniscope either as multi-coloured Category columns or white Text columns). If this occurs, you can usually manually convert fields (columns) containing numbers or dates and times using the Data > Manage fields [28]dialog. For more information on formatting dates and times and managing time zones, see the section on Dates & Times [30].
Go to Data Management Phase [2]
This checklist covers tasks you should perform AFTER importing a data set (or merging in another) for the first time, but BEFORE adding further content or beginning to analyse how to filter, visualise or present the data.
The Data Management phase focuses on data set completeness and correctness. Data typing assumptions made by Omniscope on import should be checked, columns duplicated, expanded, collapsed or tokenized to facilitate end-user interaction with your file. In this phase, 'data scrubbing' view configurations (rather than final presentational views and layouts) are used, normally working on a single tab entitled 'Data Set' or similar. Use Table View column sorting and the Chart View to examine extreme values in each column, correct null (blank) and missing values, and add related content to the file, such as image sets, maps and links to related web pages and web services.
Using the X in the upper right-hand corner, close all the default opening Views on the opening Tab, except for the Table View [31].
2-01 Check data typing [28] - On import, Omniscope assigns a data typing assumptions to each column in the data set: 'Text', 'Numeric' or 'Date & Time'. If the number of unique text values in a column is less than a defined threshold, the field will be further typed 'Category'. Sometimes, columns of identification numbers which are not used in calculations and usually searched as Text are mistakenly typed 'Integer Number' with separators added. Data typing can be reviewed and changed using the Data > Manage fields [28] dialog. Make sure to remove the separators from numbers before changing them to text by unticking Data > Manage fields > {column} Options > Show thousands separator. Ensure that data which is stored in the source file as a valid data and time has been recogised and imported as Date and Time rather than Text, as discussed here [30].
2-02 Set default global column order [28] - the order of the columns on import may not be the most useful to your users. You can set the global default column order for the file from the Data > Manage fields [28]dialog by dragging the 'hands at the far right upwards or downwards. Column order is view specific, and you can modify the order in each Table View by dragging the columns. Use Data > Manage fields > Reset view field orders to reset columns to the default order. If you have defined tab-specific view orders, Omniscope will ask if you want to return all tabs to the global default order.
2-03 Add new fields [28] - you may want to add new fields in order to add more data. Use Data > Manage fields > Add new field to create the field at the bottom of the list, then drag the new column into proper position in the defualt column order and assign it a name. You can convert it to a formula field and define the calculation logic later.
2-00 Address null (blank) values - Omniscope is a powerful tool for completing data sets and improving data quality.
2-00 Expand, collapse or tokenize columns -
Note: Expanding and collapsing columns are data edits that will not survive a data refresh. If the changes are to be made persistent, they should be made in the source data.
2-00 Look for aberrant values -
Note: Data deletions and corrections will not survive a data refresh. If the changes are to be made persistent across refreshes, the changes should also be made in the source data.
2-00 Import image sets -
2-00 Download/import maps [25] -
2-00 Define links -
Commit all changes Tab > Commit changes for all and File > Save (Ctrl+S) the file, preserving the link to the source data if required for subsequent refresh.
At the end of this phase, the single 'DataSet' tab should reveal all non-empty and non-uniform data fields and filters (use both Sidebars if necessary to see all the filter devices) in the Table/Chart View(s) without aggregations or groupings.
Note: it is good practise to always leave this 'Data Set' tab accessible as the final tab on the far right of the file tab set, providing an instant, credibility-enhancing view of the data at maximum granularity to any user who clicks on the tab.
This checklist covers tasks you should perform, or options you should consider, AFTER you have imported/merged all the data sources and 'scrubbed' the data to ensure correctness and completeness, but BEFORE you begin to define the best ways to visualise and present the data set.
In this phase, column re-naming should be used to shorten names to save space and make them instantly meaningful to the end-user audience. Unneeded columns (especially empty or uniform-value columns) can be hidden or deleted, and the number of unique category values can be reduced, either via re-naming/consolidating values with data edits, or by adding formula columns that re-categorise records into fewer categories. Aggregations can be set and aggregation formulae specified to create transformed views of the data for use with most views.
Close the Chart View (if still open after scrubbing) and continue working initially with a single Table View [31] on a single 'Data set' tab
3-01 Rename fields/columns [27] - horizontal space is always at a premium in Omniscope and DataPlayer files, so changing/shortening the field names used in the source databases to shorter names meaningful to the intended audience not only communicates better, but also presents better. You can enable multi-line display of field (column) names in the Table View from Table View: View Tools > Column options > Column header height. Insert a "\" character when renaming field names to introduce custom line breaks, which will appear in Table View column headers (assuming multi-line headers are enabled) and also in filter devices displayed on the Sidebar.
3-02 Hide or delete fields/columns [28] - empty, uniform value and fields not needed by end users for filtering can be globally hidden or deleted using Data > Manage fields [28]. Deletions are a remembered action, and will be re-performed on every file refresh. Values in hidden columns can still be displayed in details and used in Sidebar filters and links.
3-03 Define formula fields [32] - Formula fields are used to transform imported data into new columns containing more useful, calculated values and to detect alert conditions to be highlighted. If you use formulae to make calculations, convert/reduce total category values, or to extract useful data fields from within text strings, your changes will be re-evaluated on every refresh. Formula fields can be added from the Main Toolbar: Data > Formulas command, the Manage fields [28] dialog, or the Table View: View Toolbar: Formulas drop down. [31] Functions available for use in formulae are documented in the Functions Guide [33]. This page lists useful formulae [34] commonly used in Omniscope. You may need to use Subset functions [35] unique to Omniscope to define formulae involving defined subsets of the data.
3-04 Duplicate/re-format selected fields - sometimes it is useful to duplicate a data/formula field (column) so that each can be typed two different ways to facilitate use of different filter types, often while allowing one of the columns to also be used as a splitting category. For example, the display format and data typing of Dates & Times sometimes needs to be changed so that the values sort better as categories or otherwise better facilitate user interactions. To create a duplicate of a given column, right-click {Column Header} > Tools > Create duplicate of this field.
3-05 Order Sidebar devices - if it is not already visible, reveal the Right Sidebar using Main Toolbar: Toolbars > Right Sidebar and its Devices drop down. Using the dragging 'hands' (or by dragging the Device headers themselves) set the display order by dragging various devices upwards or downwards. Now also open the Left Sidebar and its Devices drop down. Starting from the bottom, check the empty devices boxes to move the devices from the Right Sidebar to the Left Sidebar.
3-06 Define Named Queries/subsets [36] - In addition to the 'Data Set' tab already configured, create a new tab from the current layout and name it 'Defined Subsets' or similar. The new tab should show a Table View and one or both Sidebars should still be displaying all the relevant filters just as they are on the 'Data Set' tab from which this tab was derived. Use the Sidebar filters to select a useful subset of the data, then define and name the results of these filter settings as a persistent Named Query (data subset) using Main Toolbar: Queries > Create queries from filters. Confirm that your Named Query has appeared at the top of the MainToolbar Queries listing and on the bottom of the Data Subset selector drop-down on the Table View View Toolbar. Perform a Main Toolbar: Reset, then choose another combination of filters and create another Named Query subset.
3-07 Define aggregations [37] - use the Aggregate drop-down menu to define & check aggregations, specifying the aggregation functions to be applied in each column. For formula fields, consider whether it is appropriate to apply the formula to the aggregated values.
Commit all your changes using Main Toolbar: Tab > Commit changes for all, then File > Save (Ctrl+S) to save the file.
At the end of this phase, all the data, images, maps and link references required to meet end-users' requirements should be in the file, and the single 'Data Set' tab should show all the columns, both data and formula, which have not been globally hidden. Separate 'Subset', 'Formula' and 'Aggregated' tabs should be used to show useful data subsets made reference-able as Named Queries, the inputs and results from defined Formulae, and various Aggregation settings with key values calculated according to specified aggregation functions displayed. Don't worry, you can delete all these tabs in the next phase.
Go to Visualisation Phase [4]
This checklist covers tasks your should perform, or options you should consider, AFTER you have optimised your data set, defined reference-able data subsets i.e. Named Queries, added Formula fields that calculate useful values and alert conditions, and defined useful Aggregation settings (including aggregation functions by field/column), but BEFORE you decide the optimal combinations of views that best suit the requirements of the file.
Omniscope offers a large and growing number of views, each of which is highly configurable. In the Visualisation phase, you test each View on its own tab, seeking the best configuration(s) of each view for the data set and the requirements of your intended audience. You may create more than one variant of each view. Views determined to be of limited value to the audience can be hidden.
The default opening settings for each view will be defined, and the paning and field selection drop-down menus edited so that only useful options are presented to the end user in each view.
In this phase, the focus is on making best use of the various views for visualisation and navigation.
4-00
4-01 Table View [31]: In addtion to the 'Data Set' tab you have been working on, create a new tab [38] called 'Table View' which will be used to experiment with the presentational aspects of the Table View using Grouping and the various settings for the overall Summary Row.
Commit changes to the tab using the drop down at right of tab, or from Main Toolbar:Tab > Commit changes
4-02 Chart View: [39]
Commit changes to the tab using the drop down at right of tab, or from Main Toolbar:Tab > Commit changes
4-03 Pie View: [40] Define multiple pies with different combinations of Value and Split-by settings...experiment with horizontal and vertical paning, save best/most useful visualisations on tab called Pie Views or similar.
Commit changes to the tab using the drop down at right of tab, or from Main Toolbar:Tab > Commit changes
4-04 Bar View: [41]
Commit changes to the tab using the drop down at right of tab, or from Main Toolbar:Tab > Commit changes
4-05 Graph View [42]:
Commit changes to the tab using the drop down at right of tab, or from Main Toolbar:Tab > Commit changes
4-06 Tile View [43]:
Commit changes to the tab using the drop down at right of tab, or from Main Toolbar:Tab > Commit changes
4-07 Pivot View [44]:
Commit changes to the tab using the drop down at right of tab, or from Main Toolbar:Tab > Commit changes
4-08 Network View: [45]
Commit changes to the tab using the drop down at right of tab, or from Main Toolbar:Tab > Commit changes
4-09 Portal View: [46]
Commit changes to the tab using the drop down at right of tab, or from Main Toolbar:Tab > Commit changes
4-10 Map View: [47]
Commit changes to the tab using the drop down at right of tab, or from Main Toolbar:Tab > Commit changes
4-11 Venn View: [48]
Commit changes to the tab using the drop down at right of tab, or from Main Toolbar:Tab > Commit changes
4-12 Dial View [49]:
Commit changes to the tab using the drop down at right of tab, or from Main Toolbar:Tab > Commit changes
4-13 Content View: [50]
Commit changes to the tab using the drop down at right of tab, or from Main Toolbar:Tab > Commit changes
4-14 Web View: [51]
Commit changes to the tab using the drop down at right of tab, or from Main Toolbar:Tab > Commit changes
4-15 Details View: [52]
Commit changes to the tab using the drop down at right of tab, or from Main Toolbar:Tab > Commit changes
4-16 DataPlayer View: [53]
Commit changes to the tab using the drop down at right of tab, or from Main Toolbar:Tab > Commit changes
Commit all changes Main Toolbar: Tab > Commit changes for all and File > Save (Ctrl+S) the file, preserving the link to the source data if required.
At the end of this phase, you should have a tab for each view you plan to use, with one or more variations of the view on each tab, perhaps some displaying subsets of the data defined by Named Queries, and others displaying aggregated data and functions as defined in the Aggregation settings in the view(s).
This checklist covers tasks your should perform, or options you should consider, AFTER you have defined the views you plan to use, but BEFORE you create the tab sequence that will convert your file into a final presentation. Most of the tasks in this phase are documented in the Reports & Presentations [21] chapter of the User Guide.
Unlike previous phases, the Presentation phase takes a minimalist, 'zero-based' approach to file configuration, i.e. the bias is that everything should be hidden unless it is needed on a specific tab to make a specific point or enable a particular end-user interaction. Working with the most useful view configurations created in the previous phase, the objective of this phase is to create a multi-tabbed presentation where each tab is addressed to a specific issue with a specific message supported by the data. In this phase the philosophy is 'less is more' to simplify the audience experience, but with credibility-building granular detail always only one click away.
At this point your file consists of view-specific tabs and perhaps some other tabs created in previous phases. Starting with the most useful view-specific tabs, you will now create multi-view versions of each tab, combining efffective views/data subsets and re-naming the tabs to focus on messages and user groups. Don't be afraid to create many different new tabs, each focused on specific user groups and points to be made, rather than trying to put too much on one or two tabs. The objective is to create a file that opens and navigates just like a slide presentation.
5-00 Add titles and annotations [54] - add titles and annotations to each tab, styling and sizing the text and adjusting spacing between views, using the commands available from the Main Toolbar: Layout > View Spacing, Titles, and Annotations [55]
5-00 Select & Edit layout modes [56] - choose the Layout mode you wish to apply to each tab in your file, making edits to the default modes, or adding new modes of your own.
5-00 Select & Edit Styles [57] - use default styles suited to each Layout mode, or create a new Style to match your corporate standards.
5-00 Specify tab toolbar defaults [58] - set the tab-specific visibility of various toolbars and other on-screen tab navigation and filtering aids.
5-00 Hide user options in drop-downs [59] - the filed (column) options available to the end user should be reuded to the minimun useful set by toggling the Show' option revealed by clicking on the spanner/wrench on each drop-down header. Toggle the 'All' option to hide the filed from all drop-downs on th same tab. This operation is tab-specific.
Note: any of the experimental view-specific visualisation tabs created in the previous Visualisation phase can now be deleted in favour of new, message-oriented tabs in the presentation.
Order tabs, commit all changes & save - make sure that your desired opening tab is open, then commit all changes using Main Toolbar: Tab > Commit changes for all and File > Save (Ctrl+S) the file, preserving the link to the source data and merge history if required.
In the Publishing phase, we focus on final file configuration options relating to branding, data refresh and how others will be able to use the file. Help screens are added, along with selected branding options (opening screen, closing screen, banner ads, corner logos, etc.). File settings relating to refresh, file security, and other options configured in the file when saved are all considered in this final phase.
6-00 Create help page - this pop-up screen is accessible from the Main Toolbar 'Help with this file' icon at the far right, as well as from the Help > Help with this file
6-00 Create cover page - this opening screen
6-00 Create back page - this closing screen is displayed for a designated period of time when the file is closed.
Make sure that the opening tab is open, then commit all changes from Main Toolbar: Tab > Commit changes for all and then File > Save (Ctrl+S) the file, preserving the links to the source data and merge history if required.
Links:
[1] http://kb.visokio.com/import-data-phase
[2] http://kb.visokio.com/data-mgt-phase
[3] http://kb.visokio.com/analysis-phase
[4] http://kb.visokio.com/visualisation-phase
[5] http://kb.visokio.com/presentation-phase
[6] http://kb.visokio.com/publication-phase
[7] http://kb.visokio.com/xmldata
[8] http://kb.visokio.com/using-data-manager
[9] http://kb.visokio.com/importing-data
[10] http://kb.visokio.com/create-new-file
[11] http://kb.visokio.com/file-open
[12] http://kb.visokio.com/connect-to-database
[13] http://kb.visokio.com/using-connectors
[14] http://kb.visokio.com/kb
[15] http://kb.visokio.com/kb/data-file-formats
[16] http://kb.visokio.com/kb/dbconnections
[17] http://kb.visokio.com/editing-data
[18] http://kb.visokio.com/managing-data
[19] http://kb.visokio.com/configure-file
[20] http://kb.visokio.com/exploring-data
[21] http://kb.visokio.com/reports-presentations
[22] http://kb.visokio.com/saving-exporting
[23] http://kb.visokio.com/open-image-set
[24] http://kb.visokio.com/open-folder
[25] http://kb.visokio.com/file-open-map
[26] http://kb.visokio.com/maps
[27] http://kb.visokio.com/merge-data
[28] http://kb.visokio.com/manage-fields
[29] http://kb.visokio.com/node/246
[30] http://kb.visokio.com/dates-and-times
[31] http://kb.visokio.com/table-view
[32] http://kb.visokio.com/formulas-variables
[33] http://kb.visokio.com/kb/functions-guide
[34] http://kb.visokio.com/kb/useful-formulae
[35] http://kb.visokio.com/kb/subset-functions
[36] http://kb.visokio.com/queries-subsets
[37] http://kb.visokio.com/aggregate-data
[38] http://kb.visokio.com/managing-tabs
[39] http://kb.visokio.com/chart-view
[40] http://kb.visokio.com/pie-view
[41] http://kb.visokio.com/bar-view
[42] http://kb.visokio.com/graph-view
[43] http://kb.visokio.com/tile-view
[44] http://kb.visokio.com/pivot-view
[45] http://kb.visokio.com/network-view
[46] http://kb.visokio.com/portal-view
[47] http://kb.visokio.com/map-view
[48] http://kb.visokio.com/venn-view
[49] http://kb.visokio.com/dial-view
[50] http://kb.visokio.com/content-view
[51] http://kb.visokio.com/web-view
[52] http://kb.visokio.com/details-view
[53] http://kb.visokio.com/dataplayer-view
[54] http://kb.visokio.com/managing-tab-layouts
[55] http://kb.visokio.com/layout-menu
[56] http://kb.visokio.com/edit-layout-modes
[57] http://kb.visokio.com/configuring-styles
[58] http://kb.visokio.com/toolbar-menu
[59] http://kb.visokio.com/using-drop-downs