Configure Data

Configuring Your Data

Make your data interesting...

Once your data has been opened and imported into Omniscope, there are four general steps to configuring how Omniscope displays your data for maximum impact, utility and ease of navigation.

  1. Confirm data typing, default column order & settings
  2. Configure Side Bars, show/hide filter devices
  3. Configure opening views
  4. Modify appearance (optional)
Suggestion: Remember to click File > Save as IOK/IOM to start the process, and save your .IOK/.IOM file frequently as your configuration work progresses.

Data Typing & Column Order

Omniscope uses four Data Types to help it display the most appropriate filter/query devices and in many other ways. When importing new a new data set, Omniscope inspects all the values in each field (column), and sets an assumed Data Type for each field (column) to be one of five types:

The first step in configuring your own data file is to confirm that Omniscope has correctly typed all the fields (columns) in your data. To do this, click on Edit > Manage Fields to display the Manage Fields dialog:


 

The Edit > Manage Fields panel provides an overview of all the fields (columns) in a data set, their current Data Type settings, and allows you to Change Data Types, Add, Rename or further Configure a field, Hide Fields from all views, and Remove fields (columns) from the file. The drag handle 'hands' at the far right are used to grab and re-order the fields from the default import order, to a more useful 'master' order. Once you have the fields (columns) in the order you want, click on Reset field orders and the new order will become the starting point in each view you configure. You can make persistent changes to the field (column) order view by view, and in Report Pages, but whenever you return to Edit > Manage fields > Reset view field orders, the field (column) order in all views will be reset.

For more on adding, removing, hiding, renaming and converting field Data Types, see the section on Managing Data

For a more detailed explanation of all the commands and options in the Edit > Manage Fields dialog, see the Main Toolbar Commands section Edit > Manage Fields.

Data formatting, layout and transposition issues

Data formatting, layout and transposition issues can arise for various reasons. Date & time formats can sometimes not be imported automatically until you assist Omniscope by clarifying the format your date and time data is in. International differences in data formatting may need to be . You may also want to use the ability of Omniscope to manage more than one value in a cell (e.g. to capture one-to-many relationships) using tokenized data fields. Omniscope time series data needs to be oriented 'vertically' with all the dates and values of repeated observations in columns (not rows). You can use the Omniscope De-pivot/Re-pivot functions to transpose (change the orientation) of some or all of your data.

For more detail on these and other data formatting, layout and orientation issues...see the Managing Data section.

Configure Side Bars/Filter Devices

The default opening configuration includes an open right-hand Side Bar. If it is not visible, the Show side bar icon on the Main Toolbar can be used to reveal one or both Side Bars.

The Side Bars display filters/query devices, which can be used for instant filtering of records based on the values in a given field (column). By default, devices for all fields (columns) are visible. Many of these will not be useful for filtering, and should be hidden. Different combinations of devices can be shown on different Report Pages, using one or both Side Bars. To configure, re-order or show or hide devices on the Side Bar(s), click on the Devices drop-down at the upper left of the Side Bar:

The Devices drop-down menu begins with options to show or hide the Reports Panel (for more detail see Creating and Managing Report Pages), the global Search All text search device (works like a search engine across the whole data set), an Exclusions device (places the Move and Keep buttons on the Side Bar when ticked), folowed by all the fields (columns) in the data set. Unticking Reports and Exclusions options (Move & Keep buttons) removes them from the Side Bar (Reports will be shown as the default tabs, and the Move and Keep buttons will re-appear on the Main Toolbar as usual.)

Filter/query devices for fields that are not useful for filtering should be hidden by unticking the boxes under Devices. The order of the filters can be changed by dragging the 'hands' at the right up or down to re-order the devices. You can also drag and drop devices themselves up and down to re-order them on the Side Bar. If you have a large number of fields (columns) in your data set, use the search box to find the field you want to display devices for and drag them to the top...ticked and in the order you want the devices displayed from top to bottom on the Side Bar.

Right-clicking on a displayed filter/query device displays sub-menus containing many of the same commands as are available in Edit > Manage Fields. Devices displayed can also be expanded by clicking on the field (column) name. Text devices, for example, expand to reveal a keyboard and a bulk list import function for matching. Category fields expand to show the full list of categories. Hovering on a device shows information about the values in the field (column), including any Field Notes which you may have been entered to attribute sources or describe important limitations and assumptions in the data.

Although fields (columns) can be hidden in the various Omniscope views, hidden columns can still can be used for filter/query devices. If you wish to use both the right and left Side Bars, please note that a device can only appear on one Side Bar at a time. Adding a field filter/query device to one Side Bar will remove it from the other. For more detail, see Using Side Bars.

Configuring Opening Views & Appearance

Omniscope has 12 different views, any or all of which can be used to bring your data to life. In Creating and Managing Report Pages, we will see how combinations of open views, filter and variable settings, plus explanatory title and annotation text can be saved as Report Pages. Report Pages you configure for your users will always be available on tabs above the Main Toolbar or on buttons in the Side Bar Reports Panel.

Regardless of which views you think are most appropriate, or which views you configure as persistent Report Pages, you should always loook at you data and try to configure all the views. Any time the user exits Reports Mode, they can open or add any one of the 12 available views you have not hidden, and the default configuration of each individual view will be displayed. To learn how to hide views, see Managing Appearance.

You can discourage (but not prevent) users from exiting Reports Mode and opening and navigating views on their own. If you by close all views outside of Reports Mode, then return to the opening Report Page and save the file, any user exiting Reports Mode will see only a blank screen unless they start adding views. In general, however, you should assume that users of your file could eventually open any non-hidden views (and some will soon learn to un-hide those views as well). It is important for you as creator/publisher of the file to open each of the 12 views in turn, decide the best way to configure each view (or decide to hide the view) and then close each view looking as it should if and when it is ever opened.

Warning: Whenever you save your Omniscope file, all views will remember their last open configuration. File recipients will see these configurations if they exit Reports Mode and open and navigate any views you have not hidden. See Creating and Managing Report Pages, Managing Appearance and Help > Edit Help page for discussion of the options most useful for authoring user help displays and managing the branding, layout and overall usability of your file.

Below, we briefly introduce configuration considerations for each of the 12 views currently available to make the most of your data. Details on configuring each view are covered in the Views Reference section.


Table View:

The Table View shows the underlying data values by record (row) for selection, browsing and editing. It displays all non-hidden values with instant sorting, aggregation, and zooming views of related images. Many powerful data management features are available under View Tools, including tools for splitting/combining text strings across columns, checking for duplicates, specification of formulae to generate calculated columns, etc. The Aggregation menu allows grouping of records by field values and calculation of sums, means and other statistics based on the values in other columns.

 

 

Start by clicking Reset on the Main Toolbar to reset your data (all records return to the green IN universe) and confirm the reset by looking at the (all green) barometer. Close all Views but the Table View. Decide which fields (columns), if any, you want hide from this view using View Tools > Columns to show. Untick the names of any fields you wish to hide in this view only. Also, use the 'hands' at the right to drag field names up and down to set the field (column) order for this view only. Click and roght-click on the column headers to experiment with aggregation and sorting options. You may also wish to try defining new Formula fields whose values are given by calculated formulae. For more detail, see the User Guide section Using the Table View .

 


Chart View:

The Chart View gives the most comprehensive overview of the contents and structure of your dataset; proportions, ranges, missing values, etc. are all revealed. The Chart View shows each of your columns of data using horizontal visualisation ‘devices’ for numbers/dates, categories, and text fields. Each chart view device shows the spread of values within each field (column). Missing values are shown with a grey background. Zero values will show with a white background. Clicking on a device will expand that device to show more detail. Right-clicking on a field reveals a rich set of options for further analysis. You can select multiple segments or ranges across multiple devices and execute power queries using the Move or Keep commands.

 

 

When preparing Omniscope .IOK/.IOM files for use by others, or when looking at an .IOK file whose data has been imported for the first time or just refreshed, some 'quality-control' filtering of a file is required to ensure the data is correct and complete. Some people call this phase of preparing/evaluating a new/refreshed data set ‘scrubbing’. The Chart View is a powerful view for reviewing, understanding and correcting large data sets.

Reset your data and close all but one view. Change the view to a Chart View, which is ideal for visual data scrubbing. Click on each of the horizontal devices representing each field (column). The device will expand. Look for inconsistencies, such as Text fields (signified by the alphabet motif on display) where the character count is too short or too long. Right-click on segmented multi-coloured Category devices to plot them as bars or pies. Look for erroneous spellings, which appear as small categories with one record. Select and keep suspicious records using the Add to basket option at the top right of the View Toolbar. Continuous values like numbers and dates are plotted...check the end point values. If a numeric device looks very white, right-click and select logarithmic rather than linear scaling to reduce the effect of a wide range of values. When you are ready, click on the Basket icon on the Main Toolbar to see your collection of suspicious records in detail. For more detail, see Using the Chart View.

 


Pie View:

A familiar view, with single or multiple (paned) display modes and some new twists, including animated displays to aid legibility. Commonly used in report pages to show the composition of aggregates.

 

 

Click Reset to reset your data. Confirm the reset by looking at the barometer. Add a Pie View. Choose the field (column) that will be represented as 100% of the pie, then choose another category field to split the pie into wedges. Choose the most useful display and close the Pie View. For more detail, see Using the Pie View.

 


Bar View:

Displays bars stacked vertically or horizontally, in single or multiple (paned) configurations, mixing positive and negative values and with many other powerful options. The Bar View is used in most reports for comparing magnitudes and showing the composition of aggregates.

 

 

Click Reset to reset your data. Confirm the reset by looking at the barometer. Close all views but one and change that view to a single Bar View. At the top of the Bar View display window, use the drop-down field selector to select an amount to display (or number of records), and directly to the right, use the Split-by drop-down to select a field to use to divide the amount into bars. Try selecting various combinations of amount fields and Split by fields. Notice that the amount total/record count is shown to the right of the Split by drop down. Use the Pane by selectors at the bottom right or upper left to create multiple bar displays.

Once you have an informative display of bars, try using the first two icons on the View Toolbar, labelled Flip (changes the base of the bars between horizontal and vertical) and Cascade (plots the bars in ascending, staircase style). For more detail, see Using the Bar View.

 


Graph View:

Creates highly-customisable scatter plots with options for colouring and sizing of markers and using marker aggregation to display record density. Automatically calculates correlations to find trends. Used to spot anomalies and for spatial selections of plotted data.

 

 

Click Reset to reset your data. Confirm the reset by looking at the barometer. Change the open view to a Graph View. Select which fields you wish to see graphed using the X-axis selector at bottom right and the Y-axis selector at upper left. Try graphing various quantities against each other, and using a time/date field (if you have one) as the X-axis. On the Graph View Toolbar, click on the Trends drop-down and tick 'show line of best fit' to see statistics on the relationship (if any) between the values in the fields you are graphing. Use the other View Toolbar drop-downs from left to right, starting with Mode (set to 'lasso select' and try encircling a group of points with the mouse), Zoom (move the X and Y sliders to expand the plots), Colour, Size and Shape all select other fields to use to modify the colour, sizing and shape of the markers on the plot. For more detail, see Using the Graph View.

 


Tile View:

Used as a simple image browser or as a complex 'tree map', a tile representing every record shows its characteristics using size, order, colour and grouping. Used to display 'heat maps' and convey other image-based attributes of records. Enables selection of records based on related images in the data set.

 

 

Click Reset to reset your data. Confirm the reset by looking at the barometer. Change the open view to a Tile View. From the View Toolbar, select which column values you wish to represent as tiles in various groupings, with sizing and colour used to display variations. Using the View Toolbar drop-down field selectors, try changing the Group, 2nd Group, Size, Sort and Colour fields, the groupings and the sizing and colouring options. For more detail, see Using the Tile View.

 


Pivot View:

Aggregates record data by two fields, applying various functions (record count, sum, mean, etc.) at the intersection of the visible fields. Tables can be sorted both ways, and display hover plots showing breakdowns of values in specific cells. Widely used in both analysis and reporting.

 

 

Click Reset to reset your data. Confirm the reset by looking at the barometer. Change or open new views to reveal multiple Pivot Views. Using the drop-down field selectors on the View Toolbar, choose different values for the X: (top) and Y: (side) displays. The cells show the number of records (rows) that share each X and Y value. Use the Function drop down to the right of the Y: to show the Sums, Means (averages) etc. Try the sorting by clicking on a given row and column. Clear the sorts by clicking the X in the upper left. Also try switching the axes using the switch arrow to the right of the clear sorts X in the upper left corner. For more detail, see Using the Pivot View.


Tree View:

Presents a hierarchical view of your data. You can change the structure of your hierarchy at any time by re-ordering the fields with your mouse. Useful for display and navigation of both pure hierarchies (like organisation charts and family trees), and comparative hierarchies present in the structure of most data sets.

 

 

Click Reset to reset your data. Confirm the reset by looking at the barometer. By default, the Tree View opens showing a few random categories from your data. On the View Toolbar, to the left of View Tools is a Fields drop-down selector. Click the selector, then un-tick all the field boxes to clear the display. Now select 2 related field boxes and the Tree View will display. Tick another box to add another field to the display. Click one of the boxes to see that branch of the tree. Click on the All box at the top of the tree to Reset, or use the Reset command on the Main Toolbar. You can change the order of the columns by dragging the column headers left or right. You can change the colouring of the tree by clicking the column header you wish to colour by. For more detail, see Using the Tree View.


Map View:

Omniscope allows you to plot coordinates on both online map services, such as Google Maps, or embedded zooming maps with multiple layers users can hide or reveal. Users can switch between mapping sources at any time. comes with a wide selection of maps which can be added into any file. Decimal coordinate columns are automatically plotted on maps or scanned images, allowing easy zooming, selection and editing.

 

 

Opening the Map View for a given data file for the first time, you are offered the embedded world map as a backdrop and are asked to specify whether your existing data set already has coordinates. If your data already has decimal longitude/latitude coordinates, select Use existing columns and specify which ones they are. Your data should be plotted automatically. You can switch between Google Maps and the embedded world map. Once you have verified that all coordinates are correct, you can add more detailed country or city maps to the file from our Maps Library.

If you do not already have decimal coordinate columns, select "create new coordinate columns". There are many options for adding decimal coordinate values; 1.) using merge files to import them automatically, 2.) placing markers on embedded vector maps or the online Google Maps, and 3.) by using the Google Earth search engine to look up missing values, setting a place marker, then cutting-and-pasting the decimal coordinates into Omniscope. For more detail, see Using the Map View, and the Knowledge Base section on Maps & Coordinates.

 


Portal View:

A familiar web-style interface allowing easy searching and browsing of data with a coloured, text-based field breakdown. Global search box combined with text-based selection enables rapid search. Can be configured to show record counts and re-group values dynamically us the number of records under consideration (via Moves and Keeps) is reduced.

 

 

Click Reset to return all records to the IN universe. Confirm the reset by looking at the barometer. Switch the open view to a Portal View. Add a Table View using Add View on the Main Toolbar. By default, the Portal View features a global Search Box (it can be hidden). Try typing terms in your data set into the global search box as you would an Internet search engine. In the barometer on the main Omniscope Toolbar you will see the number of 'hits', i.e. records that contain what you have entered, in whole or in part. Clicking on Keep will display only those records in the Table View, and update the Portal View display to reflect the breakdowns of only the records you have kept in the IN universe. Try clicking on several different items on the Portal View. The barometer shows the number of records that share all the values you have selected. If 'no matches' shows in the barometer, click again on selected values to deselect them. For more detail, see Using the Portal View.


Details View:

Whenever just one record is selected, the Details View (or a pop-up details window) displays data and images as configured. The Details view can also provide buttons/links to related content and services, or as an editable form for data correction and input.

 

 

Open a Table View and a Details View. If no record is selected in the Table View, the Details View will show all the values for the first record at the top of the Table View (depending on the Sorts which are applied in the Table View). Click on the row header of the second, or a subsequent record in the Table View and the details of that record will appear in the Details View. The Details View is highly configurable, with a drag-and-drop orientation bar and options to display related images. For more detail, see Using the Details View.


Web View:

Omniscope is totally web-aware, with built-in browser functionality. If you are online, any configured links to web pages related to the data file can be displayed in one or more Omniscope Web Views.

 

 

By default, upon opening a data file which has no web links configured and associated with the Web View, the Web View will display the Google home page. You can have multiple web views open at any time. Try creating a new, single record (row) Omniscope file containing the URLs of three major websites, then open 3 Web Views and associate them each with a different field (column) in your data. Each view should point to a different page.

Before you can use the Web View dynamically, you need to configure or add web links/services that relate to your data. Omniscope comes with a menu of preconfigured links that use field (column) values as inputs to the web service request, for example a Google or Wikipedia search on names in your file. By adding links to your data file, you can use the Web View to display web-based charts, detail, images, adverts, etc. related to the values in specific records selected by the users of your file. To configure links and web services, go to Tools > Links on the Main Toolbar (see Adding Links).

For more detail, see Using the Web View.

Next section: Using the Side Bars


User Guide Top

Manage Data

Managing Data

 

Omniscope easily imports tabular data, but making the most of the data in Omniscope sometimes requires modifying the names of the fields (columns), the layout (how data is arranged or divided across columns) or orientation (which are columns and which are rows) of the data in the Omniscope file. Omniscope offers many powerful data manipulation features to help you make these changes. These modifications are internal to Omniscope and some changes (such as re-naming and hiding) can survive refreshing from the original linked source. Other data modification operations must be repeated after each refresh if the source data layout or orientation cannot be changed.

Warning: Omniscope does not yet support partial refresh of only certain columns from linked data sources. If you add columns which are not present in the original linked data source (such as map coordinates or image references) to your Omniscope file, these columns will be lost or overwritten if you need to refresh from source. To preserve your added data, keep all columns not found in the source file in a separate merge file, with a common column of references so you can join the files together after each refresh. For more information, see Refreshing Data and Merging Data.

Managing Fields (columns)

Omniscope permits you to add, remove, hide and rename fields (columns) and to convert field data types using the Edit > Manage fields dialog. Database field names are often not self-explanatory, so renaming some fields is often a good idea, as is hiding columns you use, but not displayed to users of your file. Removing columns neither you nor your users will need will make your file smaller, but refreshing from source will restore the removed columns.

 

 

If you wish to replace a string of text in one or more columns with a different string, you can use the Replace within values option. If you want to calculate (and re-calculate) results in a column, perhaps applying additional logic tests, you can convert the column into a Formula field. For more information, see using Edit > Manage Fields.

Managing Values within fields

Data is imported from source may have either too much or too little information in each cell. If there is too much (first name, middle name and last name in the same cell), you may want to split the values from one column across several new columns. If there is too little (the first 4 digits of a post code in one column and the rest in another), you may wish to collapse the values in multiple columns into a single column. Sometimes, you may want to add a prefix or suffix to all the values in a column.

 

 

The Table View Tools sub-menu contains Collapse values (reduce to one column), two kinds of Expand values (spread across more than one column), and Append/Prepend text to values options which allow you to change the layout of your data across columns, or add defined prefixes or suffixes to values in selected columns. For more information, see Using the Table View.

International issues

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. For some combinations of settings and data formats, Omniscope cannot reliably detect the situation automatically.

 

.

 

If you find your data opens incorrectly and your fields are not correctly structured, your numbers have the wrong decimal place, etc. consult the File > Open file...>Open Data Set wizard page, which contains options to help with some common issues. For more information, see International issues.


Specifying custom date formats

Omniscope supports Date & Time data typing. Most common Date & Time formats are recognised automatically on import. If you create a new date field (column), or Omniscope does not recognise the format in your imported data set, you may be asked to provide guidance on interpreting the format, and to specify how the imported values should be displayed. The Date & Time formatting wizard will appear, or can be accessed from the Edit > Manage Fields dialog whenever changing a data type to Date & Time:

 

 

A date format is a sequence of case-sensitive characters describing the format of date/time values, not the dates themselves. For example, to show a dates such as "16-Mar-2002" you would specify the date format "dd-MMM-yyyy" in Omniscope. You can specify a wide range of formats, including days of week and time zones. For more detail and complete discussion of date and time formatting options, see Dates & Times.


Tokenized data- multiple values per cell

Sometimes, more than one value is associated with certain attributes of a record. For example, shoes can be available in more than one size, or you may have more than one image associated with a house (or whatever). Items available in more than one size, or with more than one associated image are examples of many-to-one relationships. Omniscope handles these kinds of relationships with a data subtype for Text and Category data fields called 'Tokenized'. In the example below, each record (row) is a pair of shoes, each of which is available in more than one size.

 

 

By declaring the filed (column) 'Size' to be tokenized, we can enter more than one size in the cell, divided by commas (or any separator you choose). Users of this file can specify their shoe size, and Omniscope will show only those records available in that size. For more detail, see Using Tokenized data.

Adding map coordinates

There are currently three ways to add geographic decimal coordinate (longitude and latitude) columns to your data for map displays. One option is to locate your records in Omniscope using the free Visokio world, country and city maps- just place the markers manually to generate the coordinates automatically as shown below (see the tutorial on Using Maps).

 

 

Alternatively, you can also look up missing coordinates using online sources such as Google Earth (and often Wikipedia), both of which can be integrated into Omniscope work flow as web services links. Just look up the missing values, then type or cut-and-paste them into Omniscope, copying the same values down for all the records in the same location.

If you have county or city names in your file, you can also merge geographic coordinate columns into your Omniscope data automatically using a merge file. To merge in coordinate columns for capital cities or geographic centres of countries, we supply a free 'By Countries' merge file containing these columns. We also supply a free 'By Cities' file containing coordinates for about 60,000 of the world's largest cities. Free merge files 'By Post codes' are available for the UK and the U.S., and an increasing number of other countries. Other free and licensed reference merge files may be available from other suppliers in future.

To learn more, see the User Guide section on Using the Map View, and the Knowledge Base sections on Maps & Coordinates.

 

Data Orientation- Time series

Omniscope processes repeated observations of values over time in vertical columns, rather than horizontal rows often used in spreadsheets. In the example of a time series data layout below, we have various bonds, each with a reference ISIN identifier in the first column. We also have repeated observations of Dates and Values (Price/Yield) over time entered vertically down the Date and Values columns. Each record (row) in the data is therefore a separate observation of the Values (Price/Yield) on a given Date repeated over time 'vertically' in separate rows:

 

 

Time series data layout in Omniscope requires at least one field (column) with a natural order, such as Date, and one or more values columns 'Price', 'Yield', etc. for repeated observations of values that make up the time series. In addition, to have multiple curves on one graph, there should be a Category field (with less than about 200-250 unique values) which contains the names of each curve to be drawn. In this example, we have many observations, but only 9 individual ISINs (bonds), so the curves can be plotted by the Category 'ISIN' reference field as shown in the example above. Don't worry about the apparent repetition in the data values. Outside of the Table View, Omniscope will render this invisible to the users of your files. For more information, see Displaying Time Series .

If your data is arranged differently from the example above, (e.g. 'horizontally' with the dates as columns and each cell in the row representing an observation over time) you may want to use the the tools available under Edit > De-/Re-Pivot on the Main Toolbar to transform your data set to the correct 'vertical' orientation in Omniscope (see below).

Changing Data orientation using De-Pivot/Re-Pivot

Omniscope provides powerful tools to change the orientation of the data from rows to columns, or from columns back to rows. This can be useful when working with data in Omniscope, and also to change the orientation of data being exported from Omniscope to other applications.

 

 

For more information, see Using De/Re-Pivot

 

Merging Columns and Rows from other files

Omniscope enables you to assemble data sets from multiple sources by merging, adding either more columns or more rows to your Omniscope data sets. You can merge data from other .IOK files, or from .XLS, .CSV, .TSV data files, or from database views/tables using the Merge Data wizard accessed from File > Import to current file > Merge data from another file:

 

 

Merges can be either a 'Join' where new columns are added to existing data using values from a common column (one to one, one to many or many to one relationship), or a 'Concatenate' where new records are added to existing columns (column names must be the same). Joins can use multiple criteria, and you can choose to import non-matching records, etc. For more information, see Using the Merge Data wizard.

Back to Configuring your Data


User Guide Top

Tokenized Data

Tokenized Data

Sometimes, more than one value is associated with certain attributes of a record.  For example, shoes can be available in more than one size, or you may have more than one image associated with with a house (or whatever). Shoe sizes and multiple images of a house are examples of many-to-one relationships.  Omniscope handles these kinds of relationships using a data subtype for Text and Category fields (columns) called 'Tokenized'.

When you declare a Text or Category data type to be 'Tokenized,' it means each cell in a field can contain more than one value, i.e. multiple "tokens" separated by a character you decide.  The default separator is a comma, but you can choose to use a space to separate words, or an unusual character such as a backslash if you need to use commas within your values.

The example below (you can download a copy of this example file here) is a shoe store data set with each a record corresponding to a pair of shoes, and a 'Size' field containing size numbers in stock (38, 39, 40, 41 etc.). The 'Size' field has been declared a Category field since it contains only a few values, and since the size numbers are treated as text, not numbers for calculations. 

 

 

Using Edit > Manage fields > Configure > Field options, we have set the data sub-type of the 'Size' Category to be 'Tokenized Category' with the default comma separator  dividing the values within the cells.  We then check the data to ensure that each available shoe size is entered in the 'Size' column with a comma separator as shown in the Table View above.

We can quickly check that all values have been entered correctly in the Side Bar query device for 'Size', each size should appear separately. In the example below, the user has set filters to display only shoes available in sizes 39 and 40.

Notice that in the Chart View, the highlighting for a specific pair of shoes available in 39 or 40 (or both) still shows the full range of sizes available.  This also affects other views that display breakdowns of Tokenized Categories, such as the Pie and Tile Views.

 

 

If there were multiple images for each pair of shoes, we would have done the same thing in the 'Photos'  image references field (column), so that we could relate more than one image to each pair of shoes, and display the multiple images in the Slideshow window.

Back to Configure your Data


User Guide Top

Time Series

Time Series Data Layout

Omniscope makes use of repeated observations over time in vertical rows, rather than horizontal layouts often used in spreadsheets. To create a multi-line time series, in Omniscope, put your data in the following 'vertical' format:

 

In this example of a time series, we have 5 companies "A" to "E" with historic share prices for each month. Each record in the data file is a price/time point for a company.

The Company field contains Category values correlating to different lines in the time series. Let's call this our Category field.

The Month field contains Date and Time values representing the time part of the time series, along the X axis. Let's call this our Time field.

The Price field contains quantitative Decimal number values for the Y axis. Let's call this our Value field.

Don't worry about the vertical repetition in the data...this will be invisible in all views except the Table View and not evident in the time series reports you configure.

 

Check your data types- After importing your data, make sure the Time (here Month) and Value (here Price) fields are the correct format. They must be numeric (decimal or integer), or dates, shown by the red to green colour gradation. Also make sure the Category field is of type Category, shown by the variety of different colours. You can convert data from one type to the other by right-clicking the column header in the Table View and choosing Convert field data type.

My data goes the other way!

Sometimes source data is laid out horizontally when Omniscope would manage it better vertically (e.g. time series), and vice-versa. Sometimes data needs to be exported from Omniscope transposed to an orientation different from that used in Omniscope reports. To avoid the time consuming process of changing the orientation of data from horizontal to vertical (row becomes column) or vertical to horizontal (column becomes row), Omniscope has both a De-pivot and Re-pivot function. Use of these functions is discussed in more detail here.

 

For a continuation on displaying line graphs like time series, see the the Graph View section displaying time series.

 

Back to Configure your data


User Guide Top

Dates&Times

Working with Dates & Times

Omniscope supports Date & Time data typing. Most common Date & Time formats are recognised automatically on import. If you create a new field (column) of this type, or Omniscope does not recognise the format in your imported data set, you may be asked to provide guidance on interpreting the format, and to specify how the imported values should be displayed. The Date & Time formatting wizard will appear, or can be accessed from the Edit > Manage Fields dialog whenever changing a data type to Date & Time:

 

 

Use the Date & Time formatting wizard if Omniscope needs help detecting the format of existing data, and to change that column's Date & Time display format to another. If you specify the time zone, it is important to specify the time zone and daylight-savings time settings of the database server recording the data, which may be different from your own. It is possible for server clocks not respecting daylight savings time to record data inconsistent with the time zone setting you select. (See below for further discussion of time zone and Daylight Savings Time-DST issues).

WARNING: When specifying date formats, make sure your data column is uniform. For example, if some cell values have Hours:Minutes:Seconds after the date, and you want to preserve this format in Omniscope, make sure that ALL cell values in that field have entries for Hours:Minutes:Seconds. If necessary, you can pad them out with all zero values like this: 00:00:00. Also, if you are using Date & Time fields as criteria for Omniscope merge file joins, make sure the fields are set to exactly the same format. If you intend to use AM/PM please make sure that your time is in 12 hour clock rather than in 24 hour clock format.


Help With Date Formats

A date format is a sequence of case-sensitive characters describing the format of date/time values. For example, to show your dates as "16-Mar-2002" you would use the date format "dd-MMM-yyyy". You can use any punctuation, but letters must be in one of the valid patterns of characters listed below:

SymbolMeaningExamplesNotes
yyyyYear2002, 53, 1997, 500 BCLiteral year values, where "53" and "1066" will mean the years 53 and 1066 AD, and "200 BC" means the year 200 BC.
yyYear02, 53, 97Two-digit years, with Y2K fix, where "53" and "10" will mean the years 1953 and 2010. Assumes any two-digit years fall within the last 80 years or next 20 years.
w
Week1, 3, 52
Week in year
MMMMMonthMarch, DecemberFull month name
MMMMonthMar, DecAbbreviated month name
MMMonth03, 12Two-digit month number, padded with zero
MMonth3, 12One- or two-digit month number, no padding
ddDay of month03, 16Two-digit day in month, padded with zero
dDay of month3, 16One- or two-digit day in month, no padding
EEEEWeekdayTuesdayFull name of day in week
EEEWeekdayTueAbbreviated name of day in week
SymbolMeaningExamplesNotes
aaAM/PMAM, PMUse aa for the AM/PM marker
HHHour (24)00, 07, 15, 23Hour of day in 24-hour clock, from 0 to 23, padded with zero
HHour (24)0, 7, 15, 23Hour of day in 24-hour clock, from 0 to 23, not padded
hhHour (12)01, 07, 11, 12Hour of day in 12-hour clock, from 1 to 12, padded with zero
hHour (12)1, 7, 11, 12Hour of day in 12-hour clock, from 1 to 12, not padded
mmMinutes00, 09, 23, 59Minutes past the hour, padded with zero
mMinutes0, 9, 23, 59Minutes past the hour, not padded
ssSeconds00, 09, 23, 59Seconds, padded with zero
sSeconds0, 9, 23, 59Seconds, not padded
SSSMilliseconds000, 009, 023, 595Milliseconds, padded with zero
SMilliseconds0, 9, 23, 595Milliseconds, not padded

Example patterns:

dd-MM-yy for values like: 21-11-99 meaning 21-11-1999
yyyy.MM.dd for values like: 2001.07.04 
yyyy.MM.dd HH:mm for values like: 2001.07.04 23:55 
EEE h:mm a for values like: Sat 9:33 PM 

For a further information see the full Java documentation, including additional date pattern symbols such as "D" for "day of year".

Time Zone Issues

Databases record data using the time zone specified for that database. The database could be located anywhere in the world. In addition, the database may or may not reflect daylight savings time adjustments, even locally. If the data in the data set does not reflect daylight savings time, but runs on GMT, and you select BST British summer time as a time zone for your data, Omniscope (and Java) will report invalid dates/times for some records. This occurs when daylight savings time adjustments 'skip over' one hour after midnight on specific dates. To fix this problem, you must isolate the offending times, and manually advance them by 1 hour.

 

Back to Configure your Data

 


User Guide Top

International

Importing International Data

Differences in formatting of data for presentation around the world can affect data import and display in Omniscope. Many international issues affecting data import have been addressed in recent versions, all of which are free upgrades. If you are experiencing problems with dates, thousands separators, etc., please ensure you are running version 2.2 or better.

Common issues

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 you find your data opens incorrectly and your fields are not correctly structured, your numbers have the wrong decimal place, etc. consult the File > Open file...Open Data Set wizard page, which contains options to help with some common issues further described below:

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, 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 Data Import wizard Customise data import dialog to change the Separator character to a semicolon " ; ".

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 Edit > Manage fields dialog. For more information on formatting dates and times and managing time zones, see the section on Dates & Times.

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 Open Data Set dialog. All fields will open as Category or Text data and their text values will be preserved. You can then use Edit > Manage fields to configure each field (column) as you would like it to display.

Back to Configure your Data


User Guide Top