About releases
From time to time we release a new version of CubeViz. In each version we focused on few parts to enhance. Here you will find general information about every major release. Please read page Upgrade an existing installation, if you plan to upgrade your current version.
This release is the result of the master thesis from Konrad Abicht, the head developer of CubeViz. The major issue was to provide an user interface to merge two data sets for later comparison. Furthermore, the legend and visualization part of CubeViz was heavily reworked to provide more information about the data itself.
The Compare user interface provides an overview about two previously selected data sets. There are several statistics about the measure values and general information about the contained DataCube information itself. Additionally, below this screen there is an area for value normalization and clustering too. The first one means, that you be able to adapt the values of all observations by set a specific formula. The last one is a certain user interface to manually create clusters of the measure values.
Improved sort functionality, more information and and the possibility to temporary change measure values are just a few of the new features. The data selection part of the legend was also reworked.
Jump to:
- Solved issues in this release
- Download page
Improving performance was the biggest issue. The developers of OntoWiki and Erfurt worked hard to speed up the Object- and QueryCache as well as the TitleHelper. Because of that, CubeViz now relies more on these technologies to handle database queries and store results. That means, CubeViz reuses results as much as possible which partly (dramatically) decreases the number of database queries.
Jump to:
- Solved issues in this release
- Download page
In this release we concentrated us on a few particular features:
- Support for materialized slice and dice
- Add an analyze tool to get an overview about general information of a selected DataCube plus integration of integrity constraints (addresses criteria what a well-formed data cube is: http://www.w3.org/TR/vocab-data-cube/#wf-rules)
- Export in various formats, for the moment RDF/Turtle and CSV are supported!
Here a screenshot containing UI-parts of all these features:
Do not let yourself fooled, we named the slice-and-dice field dataset filter because its more intuitive as materialized slices.
Jump to:
- Solved issues in this release
- Download page
First, we concentrated us on a fully translation. From now on CubeViz is fully translated and can be easily extend to further languages. After that we heavily face lift the left sidebar.
On the image you have both left the old one and right the new one. Our intention was to improve the overview about the selection itself as well as show as much information about the different kinds of the configuration, for instance label and description for each entry. Furthermore we use the dialog you already know from the component element selection for the dataset, attribute and measurement selection as well. You read it right, its additional possible to select between different attributes and measures.
These small icons you see in the new sidebar are from the Semicon project!
Jump to:
- Solved issues in this release
All user interface parts were visually reworked to improve the user experience. For that, we added a couple of icons, click to see help texts or meta data about the related resource. Another change was restructuring the user interface and add new items, for instance sort buttons (sort by alphabet or check status) in component dialog. Additionally we added a legend at the bottom of the visualization to let the user see, what the selected configuration is. There are information about the component elements itself, but also for the retrieved observations.
Furthermore it's now possible to remember both the selected cube configuration and visualization settings. For that we use two independent hashes, and two different files.
And there is now a more or less complete test suite on server- and client side.
Here and here are lists of all solved issues in this milestone.
Major topic was to rewrite the code to make it easier to adapt for further improvements. For that, we used TypeScript to write our JavaScript code. It is a new technology and language developed by Microsoft which contains JavaScript as a subset and provides a couple of really usefully features, for instance a clean class handling: hierarchies, extends, interfaces, no Object shoving anymore! We used that to create a couple of classes to handle our communication with the server. DataSet.ts is one of these and loads datasets for a given data structure definition.
Furthermore we added a chart selector to the user interface. With that you are able to switch between different visualizations for the same bunch of data.
Here is a list of all solved issues in this milestone.