InfoVis:Wiki - User contributions [en]

File:InfoVis Gruppe10 Aufgabe3 Prototype2.jpg

2006-01-08T14:46:53Z

UE-InfoVis0506 0027476: /* Source */

== Summary ==
Screenshot of prototype v2
== Copyright status ==
Open Source
== Source ==
[Kals, Minarik, Sahin, Slabschi, 2005]

File:InfoVis Gruppe10 Aufgabe3 Prototype2.jpg

2006-01-08T14:46:26Z

UE-InfoVis0506 0027476: Screenshot of prototype v2

== Summary ==
Screenshot of prototype v2
== Copyright status ==
Open Source
== Source ==
Stefan Kals

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 10 - Aufgabe 3 - Prototyp

2006-01-08T14:45:19Z

UE-InfoVis0506 0027476: /* Screenshot */

== Short Task Description ==

What we had to do in our project was to visualize data from MP3 music files. We use the so called ID3 Tags to get all the interesting attributes like: song title, album title, genre, year and so on. For getting all this information out of the songs, we decided to use iTunes, because this software saves all the songs on the computer in one file. It's a xml file that holds all the informations for each song.

There is also other data saved with each song when using iTunes. Namely the date when the song was added to the library, the date when it was last played and a rating given by the user between 0 and 5 stars. As we are doing Information Visualization a main task was to give the tool an explorative touch, so that the user can find and explore his music using totally new ways which have not been implemented in common tools on the market.

== Implementation Description ==

The prototype that we implemented of course doesn't has all the functionality we described in our concept but we tried to make clear what we wanted to achieve. The program consists of a main window and three other windows. In the main window there are two axis, one showing years and the other showing genres. The boxes on the crossings stand for the songs that were published in the given year and fall into the given genre.

The size of the box indicates the number of songs within and the color (more or less saturated in red) accounts for the rating. The better the rating, the higher the saturation. If you klick on such a box, more details of these songs are shown in the other windows. In the lower right window you can see a statistic view about how the selected songs are rated. In the lower left window the matching artists and albums are listed. In this prototype no pictures but only a list of artists and albums are shown unlike on the concept screenshot. The upper right window is also just faked and without functionality.

== Used Libraries ==

* mytunes
mytunes is a Java Package that makes it possible to get all the data from the iTunes Library xml file to the Java Sandbox. It makes the working with the xml file a lot easier, so you don't have to bother with xml parsing.

* AbsoluteLayout
Java Package that allows to use an absolute layout. This package is provided with NetBeans.

== Screenshot ==

[[Image:InfoVis_Gruppe10_Aufgabe3_Prototype2.jpg|none|thumb|500px|none|Screenshot of prototype v2]]

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 10 - Aufgabe 3 - Prototyp

2005-12-20T20:43:31Z

UE-InfoVis0506 0027476: /* Used Libraries */

== Prototype ==

Downloadlink: ...todo...

== Short Task Description ==

What we had to do in our project was to visualize data from MP3 music files. We use the so called ID3 Tags to get all the interesting attributes like: song title, album title, genre, year and so on. For getting all this information out of the songs, we decided to use iTunes, because this software saves all the songs on the computer in one file. It's a xml file that holds all the informations for each song.

There is also other data saved with each song when using iTunes. Namely the date when the song was added to the library, the date when it was last played and a rating given by the user between 0 and 5 stars. As we are doing Information Visualization a main task was to give the tool an explorative touch, so that the user can find and explore his music using totally new ways which have not been implemented in common tools on the market.

== Implementation Description ==

The prototype that we implemented of course doesn't has all the functionality we described in our concept but we tried to make clear what we wanted to achieve. The program consists of a main window and three other windows. In the main window there are two axis, one showing years and the other showing genres. The boxes on the crossings stand for the songs that were published in the given year and fall into the given genre.

The size of the box indicates the number of songs within and the color (more or less saturated in red) accounts for the rating. The better the rating, the higher the saturation. If you klick on such a box, more details of these songs are shown in the other windows. In the lower right window you can see a statistic view about how the selected songs are rated. In the lower left window the matching artists and albums are listed. In this prototype no pictures but only a list of artists and albums are shown unlike on the concept screenshot. The upper right window is also just faked and without functionality.

== Used Libraries ==

* mytunes
mytunes is a Java Package that makes it possible to get all the data from the iTunes Library xml file to the Java Sandbox. It makes the working with the xml file a lot easier, so you don't have to bother with xml parsing.

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 10 - Aufgabe 3 - Prototyp

2005-12-20T20:43:06Z

UE-InfoVis0506 0027476: /* Implementation Description */

== Prototype ==

Downloadlink: ...todo...

== Short Task Description ==

What we had to do in our project was to visualize data from MP3 music files. We use the so called ID3 Tags to get all the interesting attributes like: song title, album title, genre, year and so on. For getting all this information out of the songs, we decided to use iTunes, because this software saves all the songs on the computer in one file. It's a xml file that holds all the informations for each song.

There is also other data saved with each song when using iTunes. Namely the date when the song was added to the library, the date when it was last played and a rating given by the user between 0 and 5 stars. As we are doing Information Visualization a main task was to give the tool an explorative touch, so that the user can find and explore his music using totally new ways which have not been implemented in common tools on the market.

== Implementation Description ==

The prototype that we implemented of course doesn't has all the functionality we described in our concept but we tried to make clear what we wanted to achieve. The program consists of a main window and three other windows. In the main window there are two axis, one showing years and the other showing genres. The boxes on the crossings stand for the songs that were published in the given year and fall into the given genre.

The size of the box indicates the number of songs within and the color (more or less saturated in red) accounts for the rating. The better the rating, the higher the saturation. If you klick on such a box, more details of these songs are shown in the other windows. In the lower right window you can see a statistic view about how the selected songs are rated. In the lower left window the matching artists and albums are listed. In this prototype no pictures but only a list of artists and albums are shown unlike on the concept screenshot. The upper right window is also just faked and without functionality.

== Used Libraries ==

* mytunes
mytunes is a Java Package that makes it possible to get all the data from the iTunes Library xml file to the Java Sandbox. It makes the work with with the xml file a lot easier, for you don't have to bother with xml parsing.

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 10 - Aufgabe 3 - Prototyp

2005-12-20T20:40:02Z

UE-InfoVis0506 0027476: /* Short Task Description */

== Prototype ==

Downloadlink: ...todo...

== Short Task Description ==

What we had to do in our project was to visualize data from MP3 music files. We use the so called ID3 Tags to get all the interesting attributes like: song title, album title, genre, year and so on. For getting all this information out of the songs, we decided to use iTunes, because this software saves all the songs on the computer in one file. It's a xml file that holds all the informations for each song.

There is also other data saved with each song when using iTunes. Namely the date when the song was added to the library, the date when it was last played and a rating given by the user between 0 and 5 stars. As we are doing Information Visualization a main task was to give the tool an explorative touch, so that the user can find and explore his music using totally new ways which have not been implemented in common tools on the market.

== Implementation Description ==

The prototyp that we did of course doesn't have all the functionality we described in our concept but we tried to make clear what we wanted to achieve. The program consists of a main Window and three other windows. In the main window there are two axis, one showing years and the other showing genres. The boxes on the crossings stand for the songs that were published in the given year and fall into the given genre.

The size of the Box accounts for the number of songs and the color (more or less saturated red) accounts for the rating. The better the rating, the higher the saturation. If you klick on such a box, more details of these songs are shown in the other windows. In the lower right window you can see more detailed how the songs are rated. In the lower right window the artist and albums are listed. But there are no pictures, like we used them in the concept screenshot, it's just a list. The upper right window is also just faked and without pictures and you also can't play the songs with the buttons.

== Used Libraries ==

* mytunes
mytunes is a Java Package that makes it possible to get all the data from the iTunes Library xml file to the Java Sandbox. It makes the work with with the xml file a lot easier, for you don't have to bother with xml parsing.

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 10 - Aufgabe 3 - Prototyp

2005-12-20T20:35:29Z

UE-InfoVis0506 0027476: /* Used Libraries */

== Prototype ==

Downloadlink: ...todo...

== Short Task Description ==

What we had to do in our project was to visualize data from MP3 music files. We use the so called ID3 Tags to get all the interesting attributes like: song title, album title, genre, year and so on. For getting all this information out of the songs, we decided to use iTunes, because this software saves all the songs on the computer in one file. It's a xml file that holds all the informations for each song.

There is also other data saved with each song, when you are using iTunes. Namely the date when the song was added to the library, the date when it was last played and a rating given by the user between 0 and 5 stars. As we are doing Information Visualization a main task was to give the tool an explorative touch, so that the user can find and explore his music using totally new ways which were not possible before.

== Implementation Description ==

The prototyp that we did of course doesn't have all the functionality we described in our concept but we tried to make clear what we wanted to achieve. The program consists of a main Window and three other windows. In the main window there are two axis, one showing years and the other showing genres. The boxes on the crossings stand for the songs that were published in the given year and fall into the given genre.

The size of the Box accounts for the number of songs and the color (more or less saturated red) accounts for the rating. The better the rating, the higher the saturation. If you klick on such a box, more details of these songs are shown in the other windows. In the lower right window you can see more detailed how the songs are rated. In the lower right window the artist and albums are listed. But there are no pictures, like we used them in the concept screenshot, it's just a list. The upper right window is also just faked and without pictures and you also can't play the songs with the buttons.

== Used Libraries ==

* mytunes
mytunes is a Java Package that makes it possible to get all the data from the iTunes Library xml file to the Java Sandbox. It makes the work with with the xml file a lot easier, for you don't have to bother with xml parsing.

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 10 - Aufgabe 3 - Prototyp

2005-12-20T20:35:22Z

UE-InfoVis0506 0027476: /* Used Libraries */

== Prototype ==

Downloadlink: ...todo...

== Short Task Description ==

What we had to do in our project was to visualize data from MP3 music files. We use the so called ID3 Tags to get all the interesting attributes like: song title, album title, genre, year and so on. For getting all this information out of the songs, we decided to use iTunes, because this software saves all the songs on the computer in one file. It's a xml file that holds all the informations for each song.

There is also other data saved with each song, when you are using iTunes. Namely the date when the song was added to the library, the date when it was last played and a rating given by the user between 0 and 5 stars. As we are doing Information Visualization a main task was to give the tool an explorative touch, so that the user can find and explore his music using totally new ways which were not possible before.

== Implementation Description ==

The prototyp that we did of course doesn't have all the functionality we described in our concept but we tried to make clear what we wanted to achieve. The program consists of a main Window and three other windows. In the main window there are two axis, one showing years and the other showing genres. The boxes on the crossings stand for the songs that were published in the given year and fall into the given genre.

The size of the Box accounts for the number of songs and the color (more or less saturated red) accounts for the rating. The better the rating, the higher the saturation. If you klick on such a box, more details of these songs are shown in the other windows. In the lower right window you can see more detailed how the songs are rated. In the lower right window the artist and albums are listed. But there are no pictures, like we used them in the concept screenshot, it's just a list. The upper right window is also just faked and without pictures and you also can't play the songs with the buttons.

== Used Libraries ==

- mytunes<br>
mytunes is a Java Package that makes it possible to get all the data from the iTunes Library xml file to the Java Sandbox. It makes the work with with the xml file a lot easier, for you don't have to bother with xml parsing.

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 10 - Aufgabe 3

2005-12-20T20:35:11Z

UE-InfoVis0506 0027476: /* MP3 Archive Visualization */

== MP3 Archive Visualization ==

* [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 10 - Aufgabe 3 - Design|Design]]
* [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 10 - Aufgabe 3 - Prototyp|Prototype]]

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 10 - Aufgabe 3 - Prototyp

2005-12-20T20:32:06Z

UE-InfoVis0506 0027476: /* Prototype */

== Prototype ==

Downloadlink: ...todo...

== Short Task Description ==

What we had to do in our project was to visualize data from MP3 music files. We use the so called ID3 Tags to get all the interesting attributes like: song title, album title, genre, year and so on. For getting all this information out of the songs, we decided to use iTunes, because this software saves all the songs on the computer in one file. It's a xml file that holds all the informations for each song.

There is also other data saved with each song, when you are using iTunes. Namely the date when the song was added to the library, the date when it was last played and a rating given by the user between 0 and 5 stars. As we are doing Information Visualization a main task was to give the tool an explorative touch, so that the user can find and explore his music using totally new ways which were not possible before.

== Implementation Description ==

The prototyp that we did of course doesn't have all the functionality we described in our concept but we tried to make clear what we wanted to achieve. The program consists of a main Window and three other windows. In the main window there are two axis, one showing years and the other showing genres. The boxes on the crossings stand for the songs that were published in the given year and fall into the given genre.

The size of the Box accounts for the number of songs and the color (more or less saturated red) accounts for the rating. The better the rating, the higher the saturation. If you klick on such a box, more details of these songs are shown in the other windows. In the lower right window you can see more detailed how the songs are rated. In the lower right window the artist and albums are listed. But there are no pictures, like we used them in the concept screenshot, it's just a list. The upper right window is also just faked and without pictures and you also can't play the songs with the buttons.

== Used Libraries ==

"mytunes"
mytunes is a Java Package that makes it possible to get all the data from the iTunes Library xml file to the Java Sandbox. It makes the work with with the xml file a lot easier, for you don't have to bother with xml parsing.

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 10 - Aufgabe 3 - Prototyp

2005-12-20T20:31:01Z

UE-InfoVis0506 0027476: /* Prototyp */

== Prototype ==

== Short Task Description ==

What we had to do in our project was to visualize data from MP3 music files. We use the so called ID3 Tags to get all the interesting attributes like: song title, album title, genre, year and so on. For getting all this information out of the songs, we decided to use iTunes, because this software saves all the songs on the computer in one file. It's a xml file that holds all the informations for each song.

There is also other data saved with each song, when you are using iTunes. Namely the date when the song was added to the library, the date when it was last played and a rating given by the user between 0 and 5 stars. As we are doing Information Visualization a main task was to give the tool an explorative touch, so that the user can find and explore his music using totally new ways which were not possible before.

== Implementation Description ==

The prototyp that we did of course doesn't have all the functionality we described in our concept but we tried to make clear what we wanted to achieve. The program consists of a main Window and three other windows. In the main window there are two axis, one showing years and the other showing genres. The boxes on the crossings stand for the songs that were published in the given year and fall into the given genre.

The size of the Box accounts for the number of songs and the color (more or less saturated red) accounts for the rating. The better the rating, the higher the saturation. If you klick on such a box, more details of these songs are shown in the other windows. In the lower right window you can see more detailed how the songs are rated. In the lower right window the artist and albums are listed. But there are no pictures, like we used them in the concept screenshot, it's just a list. The upper right window is also just faked and without pictures and you also can't play the songs with the buttons.

== Used Libraries ==

"mytunes"
mytunes is a Java Package that makes it possible to get all the data from the iTunes Library xml file to the Java Sandbox. It makes the work with with the xml file a lot easier, for you don't have to bother with xml parsing.

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 10 - Aufgabe 3 - Design

2005-11-22T22:36:50Z

UE-InfoVis0506 0027476: /* What should be achieved with the visualisation? */

== Application Area and given Dataset ==

=== Application Area Analysis ===

The application area for this task is to visualize a music archive with the data provided by ID3/iTunes tags. These tags include information such as songname, artist, year, album and so on. The challenge in visualizing this information is to select suitable attributes for being used in relation to each other because of the high number of discreet and "organizational" attributes.

=== Dataset Analysis ===

{|
|- style="background:#e0e0e0"
!Attribute
!Data type
!Description
|- style="background:#eeeeee"
|Name
|Discreet
|Song title
|-
|Artist
|Discreet
|Artist name
|- style="background:#eeeeee"
|Album
|Discreet
|Album name
|-
|Genre
|Nominal
|Genre the song belongs to
|- style="background:#eeeeee"
|Composer
|Discreet
|The composer of the song
|-
|Size
|Ordinal
|The file size
|- style="background:#eeeeee"
|Total time
|Ordinal
|The total time of the song
|-
|Disc number
|Ordinal
|Number of the disc
|- style="background:#eeeeee"
|Disc count
|Ordinal
|Total number of discs
|-
|Track number
|Ordinal
|Track number of this song on the disc
|- style="background:#eeeeee"
|Track count
|Ordinal
|Total number of tracks on the disc
|-
|Year
|Ordinal
|Year of origin
|- style="background:#eeeeee"
|Date Modified
|Ordinal
|Date of modification
|-
|Date added
|Ordinal
|Date when song was added to archive
|- style="background:#eeeeee"
|Bit rate
|Ordinal
|Bit rate of song (e.g. 128kbit/s)
|-
|Sample rate
|Ordinal
|Sample rate of song (e.g. 44100Hz)
|- style="background:#eeeeee"
|Play count
|Ordinal
|Number of time the song was played
|-
|Play date
|Ordinal
|Date of last play
|- style="background:#eeeeee"
|Play date UTC
|Ordinal
|Date of last play in [http://en.wikipedia.org/wiki/UTC UTC]
|-
|Location
|Discreet
|File location
|- style="background:#eeeeee"
|Kind
|Nominal
|Kind of file (e.g. MPEG audio file)
|-
|Rating
|Ordinal
|Personal rating (1-5 stars)
|}

One data record consists of a concatenation of attributes listed in the table above. Those attributes are all 1-dimensional. A data record contains only necessary attributes or attributes with data.

== Target Group Analysis ==

=== Who should use this visualation technique? ===

The visualisation of our concept is mainly designed for people collecting mp3s and musicians who like to use creative and new ways for finding songs to play in their music archive they won't find in the usual tools. Moreover it's for people who like to explore their music collection using different approaches. This will fit the exploring character of information visualisation.

Our visualisation will make it possible to browse through the music collection in different ways than what iTunes offers. It's meant for people who want to find music to play, e.g. songs they didn't listen to for a long time. They will see from which period the songs are, which genre they fall into and how they have been rated. This is a different starting point than usual approaches and will allow the user to potentially find other music than without it.

The people that will use our tool are familiar with the internet and use it quite often. Moreover they are using their computer a lot at home and have their pc or mac in the living room where it is not only used for work, but also as multimedia station. That means they play video, music and watch TV with their computer.

This group is specially interested in music and is buying songs over the internet and not buying music CD's frequently anymore. If they buy a CD they rip the content onto the PC to have it in their music library.

=== What are the special interests of our target group? ===

Probably our target group is quite young, probably creative and they potentially have some sort of interest in exploring data visualisations in alternative ways. As can be assumed by analyzing iTunes, the target group likes nice and neat design, cool features and gimmicks. They probably use the visualisation mainly for playing around with their music collection.

Our target group has more interest in mp3s than they have in buying CDs and playing them in their CD player. They have all their music stored on their computer and want to have many possibilities to browse through their collection. They are looking for new ways of finding music so that they can listen to the music they like and the music matching upcoming emotions at every point of time. Instead of manually choosing a music CD they want to use a tool to help them selecting music out of their archive that suits their mood.

=== Are there any known / often used Methods / Visualisation Techniques? ===

Up to now there are no real visualisation techniques in the area of music players like iTunes. The only visualisation technique that can be found on most music tools is the sound visualisation of a playing song, implemented as frequency response or graphical art responding to the music progress.

For representing the songs of a library, ususally lists or tables are used. List-like and tabular approaches can not really be considered as graphic visualisation - they just are textual representations of the data that the user can read and use. Especially in iTunes the possibilities of combining different ID3 attributes to get a filtered playlist are vast. The user is for example able to choose only songs from 1980 to 1984 that are in the rock genre, have a rating between 1 and 3 stars and are not from Guns n' Roses. So you can do quite a lot of things with it, but there is no visualisation behind it. You can choose all that, but you can not choose it graphically which can make this much easier, faster, or just more interesting.

== Purpose of the Visualisation ==

=== What should be achieved with the visualisation? ===

* An expressive and effective representation of the data records and contained information enabling users to gain an overview of the music in the library as fast as possible using this visualization.
* An explorative visualisation of the data records. A good presentation of the contained information helps users to obtain information better.
* A new approach for finding music to play by bringing genre, year of creation, rating and size of the data set into relation.

=== Which tasks should be solved? ===

Using the nowadays available music library tools is effective and suitable for standard tasks like the following ones most of the time:
* Searching for music by textual fields like artist, album, genre etc.
* Filtering lists of music by selecting criteria on different attributes
* Ordering lists of music by different attributes
* Scrolling through lists of different items searching for songs that will be played next

All these standard tasks are more or less well known nowadays and implemented into most of the modern music libraries. Interestingly indeed is the fact that there are so much more approaches on finding music using alternative ways that have not been designed or implemented even after years like the following:
* Computer-aided decision of music to play based on user behavior (music types often skipped quickly, music types often played loud...)
* Graphical representations of relational visualisations of the music archive

This second task was being analyzed for the design of the here discussed visualisation trying to solve the following tasks:
* Representing a quick overview of the different types of music in the archive
* Guiding the user to good rated music using color coding
* Marking different sized song groups using different sizes of the representing graphic objects (boxes)
* Providing a focused view for selected music groups using a multi-view window layout
* Giving statistical information on selected music groups via a separated but linked window of the rating-distribution of the selected music group
* Filtering the representation by selecting range and scale

=== Questions that can be solved using this Visualisation ===

* Which Jazz songs of the 80's do I have im my library, how have I evaluated them in average?
* How many songs of one special genre of one special year do I have?
* How do I have them rated?
* Which albums do I have of a selected genre and year of publishing?
* Which songs are included on an album?
* How often do I have played a song?
* When did I last play a song?
* Of which genre and how old are most of the songs in my archive?
* Which genre do I like (which genre is best rated)?
* Selecting genre and year/decade, which alternative music do i find to one other?
* Which albums match each other in terms of genre and age?

== Designproposal ==

=== Which kinds of Visualisation should be used? ===
The actually existing music library systems mostly don't really visualize the contained music using its attributes but simply use lists of items (artists, albums, songs, playlists...). While this concept is easily understandable for the end-user it only allows for simple browsing using the following techniques:

* Searching for specific artists, albums, titles and so on.
* Filtering the list by choosing ranges or values for some attributes
* Sorting the list by different attributes
* Scrolling the list up and down

Some attributes of song items like artist, album and title are of hierarchical character and therefore suited mainly for being displayed in a list or being used for browsing in multi-step lists. One example of such a multi-step list is the media library in [http://www.winamp.com Winamp]: After selecting an artist in the first list, the second list gets filled with the available albums of this artist. Selecting an album fills the next list with the associated songs of this album and so on.

While hierarchical attributes can be considered essential and are very useful for a multi-level selection process or direct textual searching/filtering, they only can be used if the user exactly knows what he or she wants to listen to. In opposite users often want to listen to randomly chosen or special pattern matching song lists like "My Top 10 Most Played Ones".

Considering these facts we chose other criteria than hierachical attributes of music items for creating new concepts of how to find interesting music without exactly knowning what to listen to. Using attributes like genre, year of creation, rating, playcount and date of last play different approaches of browsing music came up to our minds.

=== Visual Mapping ===
In the context of this task a "Music Type Selection" browsing approach was chosen for being designed in detail and worked out as a prototype. This approach uses the following visual mapping:
* The approach bases on a 2D diagram containing:
** The year of creation on the x-axis
** The genre on the y-axis
Using this grid groups of similar music with respect to genre and year are getting plotted into the diagram as filled boxes. Additionally another two attributes are being mapped:
* The absolute number of songs within a specific group is mapped as the size of the box.
* The mean rating of all songs within this group is mapped as the intensity of the color used for filling the boxes.

=== Used Techniques / Applied Principles ===

* Focus & Context: Tiled Multi-Level Browser (Slides 0, Page 16)
** Overview Window
** Zoomed Window
** Details On Demand Window
* Scatterplot (Slides 1, Page 1)
** This concept is used in the upper left window. On the x-axis the year of publishing is displayed and on the y-axis the genre.

* Dynamic Queries: live choosable sliders for attribute ranges (Slides 4, Page 8)
** This technique is used at the left 2 windows to slide the genre or the albums if there is not enough space available to display all at one.

* Linking & Brushing: Detail window containing rating distribution of selected songs (Slides 0, Page 25)
* Visual Encoding: volume and color (Slides 0, Page 27)
** With the color of the shapes the average rating is displayed (white: bad rating; red: best rating) and with the volume the number of songs.

=== Interaction ===

As you can see in the advanced [[Media:InfoVis_Gruppe10_Aufgabe3_Entwurf2.jpg|concept]] we have a multi windwow view. The starting point is in the big main window. In the beginning the other windows are empty. In the main part the user sees all the songs availible represented in boxes of different shade and size. It is possible to scale the x- and the y-axis to have a better overview, or to see the boxes larger. When he clicks at one of those boxes more detailed information will appear in the other windows. In the lower left window the user will see the different Artists that suited his selection. There will be one box for each artist containing all the albums of this artist that correspond with the users selection of genre and year. In the lower right window the user can see a more detailed view on the ratings of his selection. So the mean value is split up and one can see how many songs there are for each rating star. In the upper left window the first album of the first artist will be presented, showing the songs.

In the next step the user can interact in the three smaller windows to change the artist, the album, or choose only specific ratings. When the user clicks on a new album or artist the details in the upper right window will be updated. Moreover there is the possibility to choose only some of the ratings represented in the lower right window. For example only 4 to 5 stars. Then the songs in the upper right window will be updated correctly and only albums which contain songs with this rating will be shown in the lower left window.

=== Mockup(s) / Fake Screenshot(s) ===
[[Image:InfoVis_Gruppe10_Aufgabe3_Entwurf1.gif|none|thumb|500px|none|Simple "Music Type Selection" Concept]]
[[Image:InfoVis_Gruppe10_Aufgabe3_Entwurf2.jpg|none|thumb|561px|none|Advanced "Music Type Selection" Concept]]

File:Diagramm 04.png

2005-11-22T22:33:12Z

UE-InfoVis0506 0027476: /* Copyright status */

== Summary ==
Last Version. Now all points refinded.
== Copyright status ==
Open Source

== Source ==
[Kals, Minarik, Sahin, Slabschi, 2005]

File:Diagramm 04.png

2005-11-22T22:33:06Z

UE-InfoVis0506 0027476: /* Source */

== Summary ==
Last Version. Now all points refinded.
== Copyright status ==

== Source ==
[Kals, Minarik, Sahin, Slabschi, 2005]

File:InfoVis Gruppe10 Aufgabe3 Entwurf2.jpg

2005-11-22T22:32:51Z

UE-InfoVis0506 0027476: /* Summary */

== Summary ==
Advanced concept of the "Music Type Selection" visualisation

== Copyright status ==
Open Source
== Source ==
[Kals, Minarik, Sahin, Slabschi, 2005]

File:InfoVis Gruppe10 Aufgabe3 Entwurf1.gif

2005-11-22T22:32:23Z

UE-InfoVis0506 0027476: /* Source */

== Summary ==
Simple concept of the "Music Type Selection" visualisation

== Copyright status ==
Open Source
== Source ==
[Kals, Minarik, Sahin, Slabschi, 2005]

File:InfoVis Gruppe10 Aufgabe3 Entwurf1.gif

2005-11-22T22:32:18Z

UE-InfoVis0506 0027476: /* Summary */

== Summary ==
Simple concept of the "Music Type Selection" visualisation

== Copyright status ==
Open Source
== Source ==
Stefan Kals, Gruppe 10

File:InfoVis Gruppe10 Aufgabe3 Entwurf2.jpg

2005-11-22T22:31:57Z

UE-InfoVis0506 0027476: /* Source */

== Summary ==
New concept for the genre/year visualisation
== Copyright status ==
Open Source
== Source ==
[Kals, Minarik, Sahin, Slabschi, 2005]

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 10 - Aufgabe 3 - Design

2005-11-22T22:28:03Z

UE-InfoVis0506 0027476: /* Interaction */

== Application Area and given Dataset ==

=== Application Area Analysis ===

The application area for this task is to visualize a music archive with the data provided by ID3/iTunes tags. These tags include information such as songname, artist, year, album and so on. The challenge in visualizing this information is to select suitable attributes for being used in relation to each other because of the high number of discreet and "organizational" attributes.

=== Dataset Analysis ===

{|
|- style="background:#e0e0e0"
!Attribute
!Data type
!Description
|- style="background:#eeeeee"
|Name
|Discreet
|Song title
|-
|Artist
|Discreet
|Artist name
|- style="background:#eeeeee"
|Album
|Discreet
|Album name
|-
|Genre
|Nominal
|Genre the song belongs to
|- style="background:#eeeeee"
|Composer
|Discreet
|The composer of the song
|-
|Size
|Ordinal
|The file size
|- style="background:#eeeeee"
|Total time
|Ordinal
|The total time of the song
|-
|Disc number
|Ordinal
|Number of the disc
|- style="background:#eeeeee"
|Disc count
|Ordinal
|Total number of discs
|-
|Track number
|Ordinal
|Track number of this song on the disc
|- style="background:#eeeeee"
|Track count
|Ordinal
|Total number of tracks on the disc
|-
|Year
|Ordinal
|Year of origin
|- style="background:#eeeeee"
|Date Modified
|Ordinal
|Date of modification
|-
|Date added
|Ordinal
|Date when song was added to archive
|- style="background:#eeeeee"
|Bit rate
|Ordinal
|Bit rate of song (e.g. 128kbit/s)
|-
|Sample rate
|Ordinal
|Sample rate of song (e.g. 44100Hz)
|- style="background:#eeeeee"
|Play count
|Ordinal
|Number of time the song was played
|-
|Play date
|Ordinal
|Date of last play
|- style="background:#eeeeee"
|Play date UTC
|Ordinal
|Date of last play in [http://en.wikipedia.org/wiki/UTC UTC]
|-
|Location
|Discreet
|File location
|- style="background:#eeeeee"
|Kind
|Nominal
|Kind of file (e.g. MPEG audio file)
|-
|Rating
|Ordinal
|Personal rating (1-5 stars)
|}

One data record consists of a concatenation of attributes listed in the table above. Those attributes are all 1-dimensional. A data record contains only necessary attributes or attributes with data.

== Target Group Analysis ==

=== Who should use this visualation technique? ===

The visualisation of our concept is mainly designed for people collecting mp3s and musicians who like to use creative and new ways for finding songs to play in their music archive they won't find in the usual tools. Moreover it's for people who like to explore their music collection using different approaches. This will fit the exploring character of information visualisation.

Our visualisation will make it possible to browse through the music collection in different ways than what iTunes offers. It's meant for people who want to find music to play, e.g. songs they didn't listen to for a long time. They will see from which period the songs are, which genre they fall into and how they have been rated. This is a different starting point than usual approaches and will allow the user to potentially find other music than without it.

The people that will use our tool are familiar with the internet and use it quite often. Moreover they are using their computer a lot at home and have their pc or mac in the living room where it is not only used for work, but also as multimedia station. That means they play video, music and watch TV with their computer.

This group is specially interested in music and is buying songs over the internet and not buying music CD's frequently anymore. If they buy a CD they rip the content onto the PC to have it in their music library.

=== What are the special interests of our target group? ===

Probably our target group is quite young, probably creative and they potentially have some sort of interest in exploring data visualisations in alternative ways. As can be assumed by analyzing iTunes, the target group likes nice and neat design, cool features and gimmicks. They probably use the visualisation mainly for playing around with their music collection.

Our target group has more interest in mp3s than they have in buying CDs and playing them in their CD player. They have all their music stored on their computer and want to have many possibilities to browse through their collection. They are looking for new ways of finding music so that they can listen to the music they like and the music matching upcoming emotions at every point of time. Instead of manually choosing a music CD they want to use a tool to help them selecting music out of their archive that suits their mood.

=== Are there any known / often used Methods / Visualisation Techniques? ===

Up to now there are no real visualisation techniques in the area of music players like iTunes. The only visualisation technique that can be found on most music tools is the sound visualisation of a playing song, implemented as frequency response or graphical art responding to the music progress.

For representing the songs of a library, ususally lists or tables are used. List-like and tabular approaches can not really be considered as graphic visualisation - they just are textual representations of the data that the user can read and use. Especially in iTunes the possibilities of combining different ID3 attributes to get a filtered playlist are vast. The user is for example able to choose only songs from 1980 to 1984 that are in the rock genre, have a rating between 1 and 3 stars and are not from Guns n' Roses. So you can do quite a lot of things with it, but there is no visualisation behind it. You can choose all that, but you can not choose it graphically which can make this much easier, faster, or just more interesting.

== Purpose of the Visualisation ==

=== What should be achieved with the visualisation? ===

* An expressive and effective representation of the data records and contained information enabling users to gain an overview of the music in the library as fast as possible using this visualization.
* An explorative visualisation of the data records. A good presentation of the contained information helps users to obtain information better.
* A new approach for finding music to play by bringing genre, year of creation, rating and size of the data set into relation

=== Which tasks should be solved? ===

Using the nowadays available music library tools is effective and suitable for standard tasks like the following ones most of the time:
* Searching for music by textual fields like artist, album, genre etc.
* Filtering lists of music by selecting criteria on different attributes
* Ordering lists of music by different attributes
* Scrolling through lists of different items searching for songs that will be played next

All these standard tasks are more or less well known nowadays and implemented into most of the modern music libraries. Interestingly indeed is the fact that there are so much more approaches on finding music using alternative ways that have not been designed or implemented even after years like the following:
* Computer-aided decision of music to play based on user behavior (music types often skipped quickly, music types often played loud...)
* Graphical representations of relational visualisations of the music archive

This second task was being analyzed for the design of the here discussed visualisation trying to solve the following tasks:
* Representing a quick overview of the different types of music in the archive
* Guiding the user to good rated music using color coding
* Marking different sized song groups using different sizes of the representing graphic objects (boxes)
* Providing a focused view for selected music groups using a multi-view window layout
* Giving statistical information on selected music groups via a separated but linked window of the rating-distribution of the selected music group
* Filtering the representation by selecting range and scale

=== Questions that can be solved using this Visualisation ===

* Which Jazz songs of the 80's do I have im my library, how have I evaluated them in average?
* How many songs of one special genre of one special year do I have?
* How do I have them rated?
* Which albums do I have of a selected genre and year of publishing?
* Which songs are included on an album?
* How often do I have played a song?
* When did I last play a song?
* Of which genre and how old are most of the songs in my archive?
* Which genre do I like (which genre is best rated)?
* Selecting genre and year/decade, which alternative music do i find to one other?
* Which albums match each other in terms of genre and age?

== Designproposal ==

=== Which kinds of Visualisation should be used? ===
The actually existing music library systems mostly don't really visualize the contained music using its attributes but simply use lists of items (artists, albums, songs, playlists...). While this concept is easily understandable for the end-user it only allows for simple browsing using the following techniques:

* Searching for specific artists, albums, titles and so on.
* Filtering the list by choosing ranges or values for some attributes
* Sorting the list by different attributes
* Scrolling the list up and down

Some attributes of song items like artist, album and title are of hierarchical character and therefore suited mainly for being displayed in a list or being used for browsing in multi-step lists. One example of such a multi-step list is the media library in [http://www.winamp.com Winamp]: After selecting an artist in the first list, the second list gets filled with the available albums of this artist. Selecting an album fills the next list with the associated songs of this album and so on.

While hierarchical attributes can be considered essential and are very useful for a multi-level selection process or direct textual searching/filtering, they only can be used if the user exactly knows what he or she wants to listen to. In opposite users often want to listen to randomly chosen or special pattern matching song lists like "My Top 10 Most Played Ones".

Considering these facts we chose other criteria than hierachical attributes of music items for creating new concepts of how to find interesting music without exactly knowning what to listen to. Using attributes like genre, year of creation, rating, playcount and date of last play different approaches of browsing music came up to our minds.

=== Visual Mapping ===
In the context of this task a "Music Type Selection" browsing approach was chosen for being designed in detail and worked out as a prototype. This approach uses the following visual mapping:
* The approach bases on a 2D diagram containing:
** The year of creation on the x-axis
** The genre on the y-axis
Using this grid groups of similar music with respect to genre and year are getting plotted into the diagram as filled boxes. Additionally another two attributes are being mapped:
* The absolute number of songs within a specific group is mapped as the size of the box.
* The mean rating of all songs within this group is mapped as the intensity of the color used for filling the boxes.

=== Used Techniques / Applied Principles ===

* Focus & Context: Tiled Multi-Level Browser (Slides 0, Page 16)
** Overview Window
** Zoomed Window
** Details On Demand Window
* Scatterplot (Slides 1, Page 1)
** This concept is used in the upper left window. On the x-axis the year of publishing is displayed and on the y-axis the genre.

* Dynamic Queries: live choosable sliders for attribute ranges (Slides 4, Page 8)
** This technique is used at the left 2 windows to slide the genre or the albums, if there is not enough space available to display all at one.

* Linking & Brushing: Detail window containing rating distribution of selected songs (Slides 0, Page 25)
* Visual Encoding: volume and color (Slides 0, Page 27)
** With the color of the shapes the average rating is displayed (white: bad rating; red: best rating) and with the volume the number of songs.

=== Interaction ===

As you can see in the advanced [[Media:InfoVis_Gruppe10_Aufgabe3_Entwurf2.jpg|concept]] we have a multi windwow view. The starting point is in the big main window. In the beginning the other windows are empty. In the main part the user sees all the songs availible represented in boxes of different shade and size. It is possible to scale the x- and the y-axis to have a better overview, or to see the boxes larger. When he clicks at one of those boxes more detailed information will appear in the other windows. In the lower left window the user will see the different Artists that suited his selection. There will be one box for each artist containing all the albums of this artist that correspond with the users selection of genre and year. In the lower right window the user can see a more detailed view on the ratings of his selection. So the mean value is split up and one can see how many songs there are for each rating star. In the upper left window the first album of the first artist will be presented, showing the songs.

In the next step the user can interact in the three smaller windows to change the artist, the album, or choose only specific ratings. When the user clicks on a new album or artist the details in the upper right window will be updated. Moreover there is the possibility to choose only some of the ratings represented in the lower right window. For example only 4 to 5 stars. Then the songs in the upper right window will be updated correctly and only albums which contain songs with this rating will be shown in the lower left window.

=== Mockup(s) / Fake Screenshot(s) ===
[[Image:InfoVis_Gruppe10_Aufgabe3_Entwurf1.gif|none|thumb|500px|none|Simple "Music Type Selection" Concept]]
[[Image:InfoVis_Gruppe10_Aufgabe3_Entwurf2.jpg|none|thumb|561px|none|Advanced "Music Type Selection" Concept]]

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 10 - Aufgabe 3 - Design

2005-11-22T22:27:37Z

UE-InfoVis0506 0027476: /* Mockup(s) / Fake Screenshot(s) */

== Application Area and given Dataset ==

=== Application Area Analysis ===

The application area for this task is to visualize a music archive with the data provided by ID3/iTunes tags. These tags include information such as songname, artist, year, album and so on. The challenge in visualizing this information is to select suitable attributes for being used in relation to each other because of the high number of discreet and "organizational" attributes.

=== Dataset Analysis ===

{|
|- style="background:#e0e0e0"
!Attribute
!Data type
!Description
|- style="background:#eeeeee"
|Name
|Discreet
|Song title
|-
|Artist
|Discreet
|Artist name
|- style="background:#eeeeee"
|Album
|Discreet
|Album name
|-
|Genre
|Nominal
|Genre the song belongs to
|- style="background:#eeeeee"
|Composer
|Discreet
|The composer of the song
|-
|Size
|Ordinal
|The file size
|- style="background:#eeeeee"
|Total time
|Ordinal
|The total time of the song
|-
|Disc number
|Ordinal
|Number of the disc
|- style="background:#eeeeee"
|Disc count
|Ordinal
|Total number of discs
|-
|Track number
|Ordinal
|Track number of this song on the disc
|- style="background:#eeeeee"
|Track count
|Ordinal
|Total number of tracks on the disc
|-
|Year
|Ordinal
|Year of origin
|- style="background:#eeeeee"
|Date Modified
|Ordinal
|Date of modification
|-
|Date added
|Ordinal
|Date when song was added to archive
|- style="background:#eeeeee"
|Bit rate
|Ordinal
|Bit rate of song (e.g. 128kbit/s)
|-
|Sample rate
|Ordinal
|Sample rate of song (e.g. 44100Hz)
|- style="background:#eeeeee"
|Play count
|Ordinal
|Number of time the song was played
|-
|Play date
|Ordinal
|Date of last play
|- style="background:#eeeeee"
|Play date UTC
|Ordinal
|Date of last play in [http://en.wikipedia.org/wiki/UTC UTC]
|-
|Location
|Discreet
|File location
|- style="background:#eeeeee"
|Kind
|Nominal
|Kind of file (e.g. MPEG audio file)
|-
|Rating
|Ordinal
|Personal rating (1-5 stars)
|}

One data record consists of a concatenation of attributes listed in the table above. Those attributes are all 1-dimensional. A data record contains only necessary attributes or attributes with data.

== Target Group Analysis ==

=== Who should use this visualation technique? ===

The visualisation of our concept is mainly designed for people collecting mp3s and musicians who like to use creative and new ways for finding songs to play in their music archive they won't find in the usual tools. Moreover it's for people who like to explore their music collection using different approaches. This will fit the exploring character of information visualisation.

Our visualisation will make it possible to browse through the music collection in different ways than what iTunes offers. It's meant for people who want to find music to play, e.g. songs they didn't listen to for a long time. They will see from which period the songs are, which genre they fall into and how they have been rated. This is a different starting point than usual approaches and will allow the user to potentially find other music than without it.

The people that will use our tool are familiar with the internet and use it quite often. Moreover they are using their computer a lot at home and have their pc or mac in the living room where it is not only used for work, but also as multimedia station. That means they play video, music and watch TV with their computer.

This group is specially interested in music and is buying songs over the internet and not buying music CD's frequently anymore. If they buy a CD they rip the content onto the PC to have it in their music library.

=== What are the special interests of our target group? ===

Probably our target group is quite young, probably creative and they potentially have some sort of interest in exploring data visualisations in alternative ways. As can be assumed by analyzing iTunes, the target group likes nice and neat design, cool features and gimmicks. They probably use the visualisation mainly for playing around with their music collection.

Our target group has more interest in mp3s than they have in buying CDs and playing them in their CD player. They have all their music stored on their computer and want to have many possibilities to browse through their collection. They are looking for new ways of finding music so that they can listen to the music they like and the music matching upcoming emotions at every point of time. Instead of manually choosing a music CD they want to use a tool to help them selecting music out of their archive that suits their mood.

=== Are there any known / often used Methods / Visualisation Techniques? ===

Up to now there are no real visualisation techniques in the area of music players like iTunes. The only visualisation technique that can be found on most music tools is the sound visualisation of a playing song, implemented as frequency response or graphical art responding to the music progress.

For representing the songs of a library, ususally lists or tables are used. List-like and tabular approaches can not really be considered as graphic visualisation - they just are textual representations of the data that the user can read and use. Especially in iTunes the possibilities of combining different ID3 attributes to get a filtered playlist are vast. The user is for example able to choose only songs from 1980 to 1984 that are in the rock genre, have a rating between 1 and 3 stars and are not from Guns n' Roses. So you can do quite a lot of things with it, but there is no visualisation behind it. You can choose all that, but you can not choose it graphically which can make this much easier, faster, or just more interesting.

== Purpose of the Visualisation ==

=== What should be achieved with the visualisation? ===

* An expressive and effective representation of the data records and contained information enabling users to gain an overview of the music in the library as fast as possible using this visualization.
* An explorative visualisation of the data records. A good presentation of the contained information helps users to obtain information better.
* A new approach for finding music to play by bringing genre, year of creation, rating and size of the data set into relation

=== Which tasks should be solved? ===

Using the nowadays available music library tools is effective and suitable for standard tasks like the following ones most of the time:
* Searching for music by textual fields like artist, album, genre etc.
* Filtering lists of music by selecting criteria on different attributes
* Ordering lists of music by different attributes
* Scrolling through lists of different items searching for songs that will be played next

All these standard tasks are more or less well known nowadays and implemented into most of the modern music libraries. Interestingly indeed is the fact that there are so much more approaches on finding music using alternative ways that have not been designed or implemented even after years like the following:
* Computer-aided decision of music to play based on user behavior (music types often skipped quickly, music types often played loud...)
* Graphical representations of relational visualisations of the music archive

This second task was being analyzed for the design of the here discussed visualisation trying to solve the following tasks:
* Representing a quick overview of the different types of music in the archive
* Guiding the user to good rated music using color coding
* Marking different sized song groups using different sizes of the representing graphic objects (boxes)
* Providing a focused view for selected music groups using a multi-view window layout
* Giving statistical information on selected music groups via a separated but linked window of the rating-distribution of the selected music group
* Filtering the representation by selecting range and scale

=== Questions that can be solved using this Visualisation ===

* Which Jazz songs of the 80's do I have im my library, how have I evaluated them in average?
* How many songs of one special genre of one special year do I have?
* How do I have them rated?
* Which albums do I have of a selected genre and year of publishing?
* Which songs are included on an album?
* How often do I have played a song?
* When did I last play a song?
* Of which genre and how old are most of the songs in my archive?
* Which genre do I like (which genre is best rated)?
* Selecting genre and year/decade, which alternative music do i find to one other?
* Which albums match each other in terms of genre and age?

== Designproposal ==

=== Which kinds of Visualisation should be used? ===
The actually existing music library systems mostly don't really visualize the contained music using its attributes but simply use lists of items (artists, albums, songs, playlists...). While this concept is easily understandable for the end-user it only allows for simple browsing using the following techniques:

* Searching for specific artists, albums, titles and so on.
* Filtering the list by choosing ranges or values for some attributes
* Sorting the list by different attributes
* Scrolling the list up and down

Some attributes of song items like artist, album and title are of hierarchical character and therefore suited mainly for being displayed in a list or being used for browsing in multi-step lists. One example of such a multi-step list is the media library in [http://www.winamp.com Winamp]: After selecting an artist in the first list, the second list gets filled with the available albums of this artist. Selecting an album fills the next list with the associated songs of this album and so on.

While hierarchical attributes can be considered essential and are very useful for a multi-level selection process or direct textual searching/filtering, they only can be used if the user exactly knows what he or she wants to listen to. In opposite users often want to listen to randomly chosen or special pattern matching song lists like "My Top 10 Most Played Ones".

Considering these facts we chose other criteria than hierachical attributes of music items for creating new concepts of how to find interesting music without exactly knowning what to listen to. Using attributes like genre, year of creation, rating, playcount and date of last play different approaches of browsing music came up to our minds.

=== Visual Mapping ===
In the context of this task a "Music Type Selection" browsing approach was chosen for being designed in detail and worked out as a prototype. This approach uses the following visual mapping:
* The approach bases on a 2D diagram containing:
** The year of creation on the x-axis
** The genre on the y-axis
Using this grid groups of similar music with respect to genre and year are getting plotted into the diagram as filled boxes. Additionally another two attributes are being mapped:
* The absolute number of songs within a specific group is mapped as the size of the box.
* The mean rating of all songs within this group is mapped as the intensity of the color used for filling the boxes.

=== Used Techniques / Applied Principles ===
TODO: this is a listing of used techniques only at the moment - detail and map to the implemented features
* Focus & Context: Tiled Multi-Level Browser (Slides 0, Page 16)
** Overview Window
** Zoomed Window
** Details On Demand Window
* Scatterplot (Slides 1, Page 1):
This concept is used in the upper left window. On the x-axis the year of publishing is displayed and on the y-axis the genre.
* Dynamic Queries: live choosable sliders for attribute ranges (Slides 4, Page 8): This technique is used at the left 2 windows to slide the genre or the albums, if there is not enough space available to display all at one.
* Linking & Brushing: Detail window containing rating distribution of selected songs (Slides 0, Page 25)
* Visual Encoding: volume and color (Slides 0, Page 27): With the color of the shapes the average rating is displayed (white: bad rating; red: best rating) and with the volume the number of songs.

=== Interaction ===

As you can see in our second [[Media:InfoVis_Gruppe10_Aufgabe3_Entwurf2.jpg|layout]] we have a multi windwow view. The starting point is in the big main window. In the beginning the other windows are empty. In the main part the user sees all the songs availible represented in boxes of different shade and size. It is possible to scale the x- and the y-axis to have a better overview, or to see the boxes larger. When he clicks at one of those boxes more detailed information will appear in the other windows. In the lower left window the user will see the different Artists that suited his selection. There will be one box for each artist containing all the albums of this artist that correspond with the users selection of genre and year. In the lower right window the user can see a more detailed view on the ratings of his selection. So the mean value is split up and one can see how many songs there are for each rating star. In the upper left window the first album of the first artist will be presented, showing the songs.

In the next step the user can interact in the three smaller windows to change the artist, the album, or choose only specific ratings. When the user clicks on a new album or artist the details in the upper right window will be updated. Moreover there is the possibility to choose only some of the ratings represented in the lower right window. For example only 4 to 5 stars. Then the songs in the upper right window will be updated correctly and only albums which contain songs with this rating will be shown in the lower left window.

=== Mockup(s) / Fake Screenshot(s) ===
[[Image:InfoVis_Gruppe10_Aufgabe3_Entwurf1.gif|none|thumb|500px|none|Simple "Music Type Selection" Concept]]
[[Image:InfoVis_Gruppe10_Aufgabe3_Entwurf2.jpg|none|thumb|561px|none|Advanced "Music Type Selection" Concept]]

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 10 - Aufgabe 3 - Design

2005-11-22T22:26:43Z

UE-InfoVis0506 0027476: /* Visual Mapping */

== Application Area and given Dataset ==

=== Application Area Analysis ===

The application area for this task is to visualize a music archive with the data provided by ID3/iTunes tags. These tags include information such as songname, artist, year, album and so on. The challenge in visualizing this information is to select suitable attributes for being used in relation to each other because of the high number of discreet and "organizational" attributes.

=== Dataset Analysis ===

{|
|- style="background:#e0e0e0"
!Attribute
!Data type
!Description
|- style="background:#eeeeee"
|Name
|Discreet
|Song title
|-
|Artist
|Discreet
|Artist name
|- style="background:#eeeeee"
|Album
|Discreet
|Album name
|-
|Genre
|Nominal
|Genre the song belongs to
|- style="background:#eeeeee"
|Composer
|Discreet
|The composer of the song
|-
|Size
|Ordinal
|The file size
|- style="background:#eeeeee"
|Total time
|Ordinal
|The total time of the song
|-
|Disc number
|Ordinal
|Number of the disc
|- style="background:#eeeeee"
|Disc count
|Ordinal
|Total number of discs
|-
|Track number
|Ordinal
|Track number of this song on the disc
|- style="background:#eeeeee"
|Track count
|Ordinal
|Total number of tracks on the disc
|-
|Year
|Ordinal
|Year of origin
|- style="background:#eeeeee"
|Date Modified
|Ordinal
|Date of modification
|-
|Date added
|Ordinal
|Date when song was added to archive
|- style="background:#eeeeee"
|Bit rate
|Ordinal
|Bit rate of song (e.g. 128kbit/s)
|-
|Sample rate
|Ordinal
|Sample rate of song (e.g. 44100Hz)
|- style="background:#eeeeee"
|Play count
|Ordinal
|Number of time the song was played
|-
|Play date
|Ordinal
|Date of last play
|- style="background:#eeeeee"
|Play date UTC
|Ordinal
|Date of last play in [http://en.wikipedia.org/wiki/UTC UTC]
|-
|Location
|Discreet
|File location
|- style="background:#eeeeee"
|Kind
|Nominal
|Kind of file (e.g. MPEG audio file)
|-
|Rating
|Ordinal
|Personal rating (1-5 stars)
|}

One data record consists of a concatenation of attributes listed in the table above. Those attributes are all 1-dimensional. A data record contains only necessary attributes or attributes with data.

== Target Group Analysis ==

=== Who should use this visualation technique? ===

The visualisation of our concept is mainly designed for people collecting mp3s and musicians who like to use creative and new ways for finding songs to play in their music archive they won't find in the usual tools. Moreover it's for people who like to explore their music collection using different approaches. This will fit the exploring character of information visualisation.

Our visualisation will make it possible to browse through the music collection in different ways than what iTunes offers. It's meant for people who want to find music to play, e.g. songs they didn't listen to for a long time. They will see from which period the songs are, which genre they fall into and how they have been rated. This is a different starting point than usual approaches and will allow the user to potentially find other music than without it.

The people that will use our tool are familiar with the internet and use it quite often. Moreover they are using their computer a lot at home and have their pc or mac in the living room where it is not only used for work, but also as multimedia station. That means they play video, music and watch TV with their computer.

This group is specially interested in music and is buying songs over the internet and not buying music CD's frequently anymore. If they buy a CD they rip the content onto the PC to have it in their music library.

=== What are the special interests of our target group? ===

Probably our target group is quite young, probably creative and they potentially have some sort of interest in exploring data visualisations in alternative ways. As can be assumed by analyzing iTunes, the target group likes nice and neat design, cool features and gimmicks. They probably use the visualisation mainly for playing around with their music collection.

Our target group has more interest in mp3s than they have in buying CDs and playing them in their CD player. They have all their music stored on their computer and want to have many possibilities to browse through their collection. They are looking for new ways of finding music so that they can listen to the music they like and the music matching upcoming emotions at every point of time. Instead of manually choosing a music CD they want to use a tool to help them selecting music out of their archive that suits their mood.

=== Are there any known / often used Methods / Visualisation Techniques? ===

Up to now there are no real visualisation techniques in the area of music players like iTunes. The only visualisation technique that can be found on most music tools is the sound visualisation of a playing song, implemented as frequency response or graphical art responding to the music progress.

For representing the songs of a library, ususally lists or tables are used. List-like and tabular approaches can not really be considered as graphic visualisation - they just are textual representations of the data that the user can read and use. Especially in iTunes the possibilities of combining different ID3 attributes to get a filtered playlist are vast. The user is for example able to choose only songs from 1980 to 1984 that are in the rock genre, have a rating between 1 and 3 stars and are not from Guns n' Roses. So you can do quite a lot of things with it, but there is no visualisation behind it. You can choose all that, but you can not choose it graphically which can make this much easier, faster, or just more interesting.

== Purpose of the Visualisation ==

=== What should be achieved with the visualisation? ===

* An expressive and effective representation of the data records and contained information enabling users to gain an overview of the music in the library as fast as possible using this visualization.
* An explorative visualisation of the data records. A good presentation of the contained information helps users to obtain information better.
* A new approach for finding music to play by bringing genre, year of creation, rating and size of the data set into relation

=== Which tasks should be solved? ===

Using the nowadays available music library tools is effective and suitable for standard tasks like the following ones most of the time:
* Searching for music by textual fields like artist, album, genre etc.
* Filtering lists of music by selecting criteria on different attributes
* Ordering lists of music by different attributes
* Scrolling through lists of different items searching for songs that will be played next

All these standard tasks are more or less well known nowadays and implemented into most of the modern music libraries. Interestingly indeed is the fact that there are so much more approaches on finding music using alternative ways that have not been designed or implemented even after years like the following:
* Computer-aided decision of music to play based on user behavior (music types often skipped quickly, music types often played loud...)
* Graphical representations of relational visualisations of the music archive

This second task was being analyzed for the design of the here discussed visualisation trying to solve the following tasks:
* Representing a quick overview of the different types of music in the archive
* Guiding the user to good rated music using color coding
* Marking different sized song groups using different sizes of the representing graphic objects (boxes)
* Providing a focused view for selected music groups using a multi-view window layout
* Giving statistical information on selected music groups via a separated but linked window of the rating-distribution of the selected music group
* Filtering the representation by selecting range and scale

=== Questions that can be solved using this Visualisation ===

* Which Jazz songs of the 80's do I have im my library, how have I evaluated them in average?
* How many songs of one special genre of one special year do I have?
* How do I have them rated?
* Which albums do I have of a selected genre and year of publishing?
* Which songs are included on an album?
* How often do I have played a song?
* When did I last play a song?
* Of which genre and how old are most of the songs in my archive?
* Which genre do I like (which genre is best rated)?
* Selecting genre and year/decade, which alternative music do i find to one other?
* Which albums match each other in terms of genre and age?

== Designproposal ==

=== Which kinds of Visualisation should be used? ===
The actually existing music library systems mostly don't really visualize the contained music using its attributes but simply use lists of items (artists, albums, songs, playlists...). While this concept is easily understandable for the end-user it only allows for simple browsing using the following techniques:

* Searching for specific artists, albums, titles and so on.
* Filtering the list by choosing ranges or values for some attributes
* Sorting the list by different attributes
* Scrolling the list up and down

Some attributes of song items like artist, album and title are of hierarchical character and therefore suited mainly for being displayed in a list or being used for browsing in multi-step lists. One example of such a multi-step list is the media library in [http://www.winamp.com Winamp]: After selecting an artist in the first list, the second list gets filled with the available albums of this artist. Selecting an album fills the next list with the associated songs of this album and so on.

While hierarchical attributes can be considered essential and are very useful for a multi-level selection process or direct textual searching/filtering, they only can be used if the user exactly knows what he or she wants to listen to. In opposite users often want to listen to randomly chosen or special pattern matching song lists like "My Top 10 Most Played Ones".

Considering these facts we chose other criteria than hierachical attributes of music items for creating new concepts of how to find interesting music without exactly knowning what to listen to. Using attributes like genre, year of creation, rating, playcount and date of last play different approaches of browsing music came up to our minds.

=== Visual Mapping ===
In the context of this task a "Music Type Selection" browsing approach was chosen for being designed in detail and worked out as a prototype. This approach uses the following visual mapping:
* The approach bases on a 2D diagram containing:
** The year of creation on the x-axis
** The genre on the y-axis
Using this grid groups of similar music with respect to genre and year are getting plotted into the diagram as filled boxes. Additionally another two attributes are being mapped:
* The absolute number of songs within a specific group is mapped as the size of the box.
* The mean rating of all songs within this group is mapped as the intensity of the color used for filling the boxes.

=== Used Techniques / Applied Principles ===
TODO: this is a listing of used techniques only at the moment - detail and map to the implemented features
* Focus & Context: Tiled Multi-Level Browser (Slides 0, Page 16)
** Overview Window
** Zoomed Window
** Details On Demand Window
* Scatterplot (Slides 1, Page 1): This concept is used in the upper left window. On the x-axis the year of publishing is displayed and on the y-axis the genre.
* Dynamic Queries: live choosable sliders for attribute ranges (Slides 4, Page 8): This technique is used at the left 2 windows to slide the genre or the albums, if there is not enough space available to display all at one.
* Linking & Brushing: Detail window containing rating distribution of selected songs (Slides 0, Page 25)
* Visual Encoding: volume and color (Slides 0, Page 27): With the color of the shapes the average rating is displayed (white: bad rating; red: best rating) and with the volume the number of songs.

=== Interaction ===

As you can see in our second [[Media:InfoVis_Gruppe10_Aufgabe3_Entwurf2.jpg|layout]] we have a multi windwow view. The starting point is in the big main window. In the beginning the other windows are empty. In the main part the user sees all the songs availible represented in boxes of different shade and size. It is possible to scale the x- and the y-axis to have a better overview, or to see the boxes larger. When he clicks at one of those boxes more detailed information will appear in the other windows. In the lower left window the user will see the different Artists that suited his selection. There will be one box for each artist containing all the albums of this artist that correspond with the users selection of genre and year. In the lower right window the user can see a more detailed view on the ratings of his selection. So the mean value is split up and one can see how many songs there are for each rating star. In the upper left window the first album of the first artist will be presented, showing the songs.

In the next step the user can interact in the three smaller windows to change the artist, the album, or choose only specific ratings. When the user clicks on a new album or artist the details in the upper right window will be updated. Moreover there is the possibility to choose only some of the ratings represented in the lower right window. For example only 4 to 5 stars. Then the songs in the upper right window will be updated correctly and only albums which contain songs with this rating will be shown in the lower left window.

=== Mockup(s) / Fake Screenshot(s) ===
[[Image:InfoVis_Gruppe10_Aufgabe3_Entwurf1.gif|none|thumb|500px|none|Entwurf 1]]
[[Image:InfoVis_Gruppe10_Aufgabe3_Entwurf2.jpg|none|thumb|561px|none|Entwurf 2]]

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 10 - Aufgabe 3 - Design

2005-11-22T22:26:21Z

UE-InfoVis0506 0027476: /* Which kinds of Visualisation should be used? */

== Application Area and given Dataset ==

=== Application Area Analysis ===

The application area for this task is to visualize a music archive with the data provided by ID3/iTunes tags. These tags include information such as songname, artist, year, album and so on. The challenge in visualizing this information is to select suitable attributes for being used in relation to each other because of the high number of discreet and "organizational" attributes.

=== Dataset Analysis ===

{|
|- style="background:#e0e0e0"
!Attribute
!Data type
!Description
|- style="background:#eeeeee"
|Name
|Discreet
|Song title
|-
|Artist
|Discreet
|Artist name
|- style="background:#eeeeee"
|Album
|Discreet
|Album name
|-
|Genre
|Nominal
|Genre the song belongs to
|- style="background:#eeeeee"
|Composer
|Discreet
|The composer of the song
|-
|Size
|Ordinal
|The file size
|- style="background:#eeeeee"
|Total time
|Ordinal
|The total time of the song
|-
|Disc number
|Ordinal
|Number of the disc
|- style="background:#eeeeee"
|Disc count
|Ordinal
|Total number of discs
|-
|Track number
|Ordinal
|Track number of this song on the disc
|- style="background:#eeeeee"
|Track count
|Ordinal
|Total number of tracks on the disc
|-
|Year
|Ordinal
|Year of origin
|- style="background:#eeeeee"
|Date Modified
|Ordinal
|Date of modification
|-
|Date added
|Ordinal
|Date when song was added to archive
|- style="background:#eeeeee"
|Bit rate
|Ordinal
|Bit rate of song (e.g. 128kbit/s)
|-
|Sample rate
|Ordinal
|Sample rate of song (e.g. 44100Hz)
|- style="background:#eeeeee"
|Play count
|Ordinal
|Number of time the song was played
|-
|Play date
|Ordinal
|Date of last play
|- style="background:#eeeeee"
|Play date UTC
|Ordinal
|Date of last play in [http://en.wikipedia.org/wiki/UTC UTC]
|-
|Location
|Discreet
|File location
|- style="background:#eeeeee"
|Kind
|Nominal
|Kind of file (e.g. MPEG audio file)
|-
|Rating
|Ordinal
|Personal rating (1-5 stars)
|}

One data record consists of a concatenation of attributes listed in the table above. Those attributes are all 1-dimensional. A data record contains only necessary attributes or attributes with data.

== Target Group Analysis ==

=== Who should use this visualation technique? ===

The visualisation of our concept is mainly designed for people collecting mp3s and musicians who like to use creative and new ways for finding songs to play in their music archive they won't find in the usual tools. Moreover it's for people who like to explore their music collection using different approaches. This will fit the exploring character of information visualisation.

Our visualisation will make it possible to browse through the music collection in different ways than what iTunes offers. It's meant for people who want to find music to play, e.g. songs they didn't listen to for a long time. They will see from which period the songs are, which genre they fall into and how they have been rated. This is a different starting point than usual approaches and will allow the user to potentially find other music than without it.

The people that will use our tool are familiar with the internet and use it quite often. Moreover they are using their computer a lot at home and have their pc or mac in the living room where it is not only used for work, but also as multimedia station. That means they play video, music and watch TV with their computer.

This group is specially interested in music and is buying songs over the internet and not buying music CD's frequently anymore. If they buy a CD they rip the content onto the PC to have it in their music library.

=== What are the special interests of our target group? ===

Probably our target group is quite young, probably creative and they potentially have some sort of interest in exploring data visualisations in alternative ways. As can be assumed by analyzing iTunes, the target group likes nice and neat design, cool features and gimmicks. They probably use the visualisation mainly for playing around with their music collection.

Our target group has more interest in mp3s than they have in buying CDs and playing them in their CD player. They have all their music stored on their computer and want to have many possibilities to browse through their collection. They are looking for new ways of finding music so that they can listen to the music they like and the music matching upcoming emotions at every point of time. Instead of manually choosing a music CD they want to use a tool to help them selecting music out of their archive that suits their mood.

=== Are there any known / often used Methods / Visualisation Techniques? ===

Up to now there are no real visualisation techniques in the area of music players like iTunes. The only visualisation technique that can be found on most music tools is the sound visualisation of a playing song, implemented as frequency response or graphical art responding to the music progress.

For representing the songs of a library, ususally lists or tables are used. List-like and tabular approaches can not really be considered as graphic visualisation - they just are textual representations of the data that the user can read and use. Especially in iTunes the possibilities of combining different ID3 attributes to get a filtered playlist are vast. The user is for example able to choose only songs from 1980 to 1984 that are in the rock genre, have a rating between 1 and 3 stars and are not from Guns n' Roses. So you can do quite a lot of things with it, but there is no visualisation behind it. You can choose all that, but you can not choose it graphically which can make this much easier, faster, or just more interesting.

== Purpose of the Visualisation ==

=== What should be achieved with the visualisation? ===

* An expressive and effective representation of the data records and contained information enabling users to gain an overview of the music in the library as fast as possible using this visualization.
* An explorative visualisation of the data records. A good presentation of the contained information helps users to obtain information better.
* A new approach for finding music to play by bringing genre, year of creation, rating and size of the data set into relation

=== Which tasks should be solved? ===

Using the nowadays available music library tools is effective and suitable for standard tasks like the following ones most of the time:
* Searching for music by textual fields like artist, album, genre etc.
* Filtering lists of music by selecting criteria on different attributes
* Ordering lists of music by different attributes
* Scrolling through lists of different items searching for songs that will be played next

All these standard tasks are more or less well known nowadays and implemented into most of the modern music libraries. Interestingly indeed is the fact that there are so much more approaches on finding music using alternative ways that have not been designed or implemented even after years like the following:
* Computer-aided decision of music to play based on user behavior (music types often skipped quickly, music types often played loud...)
* Graphical representations of relational visualisations of the music archive

This second task was being analyzed for the design of the here discussed visualisation trying to solve the following tasks:
* Representing a quick overview of the different types of music in the archive
* Guiding the user to good rated music using color coding
* Marking different sized song groups using different sizes of the representing graphic objects (boxes)
* Providing a focused view for selected music groups using a multi-view window layout
* Giving statistical information on selected music groups via a separated but linked window of the rating-distribution of the selected music group
* Filtering the representation by selecting range and scale

=== Questions that can be solved using this Visualisation ===

* Which Jazz songs of the 80's do I have im my library, how have I evaluated them in average?
* How many songs of one special genre of one special year do I have?
* How do I have them rated?
* Which albums do I have of a selected genre and year of publishing?
* Which songs are included on an album?
* How often do I have played a song?
* When did I last play a song?
* Of which genre and how old are most of the songs in my archive?
* Which genre do I like (which genre is best rated)?
* Selecting genre and year/decade, which alternative music do i find to one other?
* Which albums match each other in terms of genre and age?

== Designproposal ==

=== Which kinds of Visualisation should be used? ===
The actually existing music library systems mostly don't really visualize the contained music using its attributes but simply use lists of items (artists, albums, songs, playlists...). While this concept is easily understandable for the end-user it only allows for simple browsing using the following techniques:

* Searching for specific artists, albums, titles and so on.
* Filtering the list by choosing ranges or values for some attributes
* Sorting the list by different attributes
* Scrolling the list up and down

Some attributes of song items like artist, album and title are of hierarchical character and therefore suited mainly for being displayed in a list or being used for browsing in multi-step lists. One example of such a multi-step list is the media library in [http://www.winamp.com Winamp]: After selecting an artist in the first list, the second list gets filled with the available albums of this artist. Selecting an album fills the next list with the associated songs of this album and so on.

While hierarchical attributes can be considered essential and are very useful for a multi-level selection process or direct textual searching/filtering, they only can be used if the user exactly knows what he or she wants to listen to. In opposite users often want to listen to randomly chosen or special pattern matching song lists like "My Top 10 Most Played Ones".

Considering these facts we chose other criteria than hierachical attributes of music items for creating new concepts of how to find interesting music without exactly knowning what to listen to. Using attributes like genre, year of creation, rating, playcount and date of last play different approaches of browsing music came up to our minds.

=== Visual Mapping ===
In the context of this task the "Music Type Selection" (TODO: find a superior name) browsing approach was chosen for being designed in detail and worked out as a prototype. This approach uses the following visual mapping:
* The approach bases on a 2D diagram containing:
** The year of creation on the x-axis
** The genre on the y-axis
Using this grid groups of similar music with respect to genre and year are getting plotted into the diagram as filled boxes. Additionally another two attributes are being mapped:
* The absolute number of songs within a specific group is mapped as the size of the box.
* The mean rating of all songs within this group is mapped as the intensity of the color used for filling the boxes.

=== Used Techniques / Applied Principles ===
TODO: this is a listing of used techniques only at the moment - detail and map to the implemented features
* Focus & Context: Tiled Multi-Level Browser (Slides 0, Page 16)
** Overview Window
** Zoomed Window
** Details On Demand Window
* Scatterplot (Slides 1, Page 1): This concept is used in the upper left window. On the x-axis the year of publishing is displayed and on the y-axis the genre.
* Dynamic Queries: live choosable sliders for attribute ranges (Slides 4, Page 8): This technique is used at the left 2 windows to slide the genre or the albums, if there is not enough space available to display all at one.
* Linking & Brushing: Detail window containing rating distribution of selected songs (Slides 0, Page 25)
* Visual Encoding: volume and color (Slides 0, Page 27): With the color of the shapes the average rating is displayed (white: bad rating; red: best rating) and with the volume the number of songs.

=== Interaction ===

As you can see in our second [[Media:InfoVis_Gruppe10_Aufgabe3_Entwurf2.jpg|layout]] we have a multi windwow view. The starting point is in the big main window. In the beginning the other windows are empty. In the main part the user sees all the songs availible represented in boxes of different shade and size. It is possible to scale the x- and the y-axis to have a better overview, or to see the boxes larger. When he clicks at one of those boxes more detailed information will appear in the other windows. In the lower left window the user will see the different Artists that suited his selection. There will be one box for each artist containing all the albums of this artist that correspond with the users selection of genre and year. In the lower right window the user can see a more detailed view on the ratings of his selection. So the mean value is split up and one can see how many songs there are for each rating star. In the upper left window the first album of the first artist will be presented, showing the songs.

In the next step the user can interact in the three smaller windows to change the artist, the album, or choose only specific ratings. When the user clicks on a new album or artist the details in the upper right window will be updated. Moreover there is the possibility to choose only some of the ratings represented in the lower right window. For example only 4 to 5 stars. Then the songs in the upper right window will be updated correctly and only albums which contain songs with this rating will be shown in the lower left window.

=== Mockup(s) / Fake Screenshot(s) ===
[[Image:InfoVis_Gruppe10_Aufgabe3_Entwurf1.gif|none|thumb|500px|none|Entwurf 1]]
[[Image:InfoVis_Gruppe10_Aufgabe3_Entwurf2.jpg|none|thumb|561px|none|Entwurf 2]]

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 10 - Aufgabe 3 - Design

2005-11-22T22:03:52Z

UE-InfoVis0506 0027476: /* Questions that can be solved using this Visualisation */

== Application Area and given Dataset ==

=== Application Area Analysis ===

The application area for this task is to visualize a music archive with the data provided by ID3/iTunes tags. These tags include information such as songname, artist, year, album and so on. The challenge in visualizing this information is to select suitable attributes for being used in relation to each other because of the high number of discreet and "organizational" attributes.

=== Dataset Analysis ===

{|
|- style="background:#e0e0e0"
!Attribute
!Data type
!Description
|- style="background:#eeeeee"
|Name
|Discreet
|Song title
|-
|Artist
|Discreet
|Artist name
|- style="background:#eeeeee"
|Album
|Discreet
|Album name
|-
|Genre
|Nominal
|Genre the song belongs to
|- style="background:#eeeeee"
|Composer
|Discreet
|The composer of the song
|-
|Size
|Ordinal
|The file size
|- style="background:#eeeeee"
|Total time
|Ordinal
|The total time of the song
|-
|Disc number
|Ordinal
|Number of the disc
|- style="background:#eeeeee"
|Disc count
|Ordinal
|Total number of discs
|-
|Track number
|Ordinal
|Track number of this song on the disc
|- style="background:#eeeeee"
|Track count
|Ordinal
|Total number of tracks on the disc
|-
|Year
|Ordinal
|Year of origin
|- style="background:#eeeeee"
|Date Modified
|Ordinal
|Date of modification
|-
|Date added
|Ordinal
|Date when song was added to archive
|- style="background:#eeeeee"
|Bit rate
|Ordinal
|Bit rate of song (e.g. 128kbit/s)
|-
|Sample rate
|Ordinal
|Sample rate of song (e.g. 44100Hz)
|- style="background:#eeeeee"
|Play count
|Ordinal
|Number of time the song was played
|-
|Play date
|Ordinal
|Date of last play
|- style="background:#eeeeee"
|Play date UTC
|Ordinal
|Date of last play in [http://en.wikipedia.org/wiki/UTC UTC]
|-
|Location
|Discreet
|File location
|- style="background:#eeeeee"
|Kind
|Nominal
|Kind of file (e.g. MPEG audio file)
|-
|Rating
|Ordinal
|Personal rating (1-5 stars)
|}

One data record consists of a concatenation of attributes listed in the table above. Those attributes are all 1-dimensional. A data record contains only necessary attributes or attributes with data.

== Target Group Analysis ==

=== Who should use this visualation technique? ===

The visualisation of our concept is mainly designed for people collecting mp3s and musicians who like to use creative and new ways for finding songs to play in their music archive they won't find in the usual tools. Moreover it's for people who like to explore their music collection using different approaches. This will fit the exploring character of information visualisation.

Our visualisation will make it possible to browse through the music collection in different ways than what iTunes offers. It's meant for people who want to find music to play, e.g. songs they didn't listen to for a long time. They will see from which period the songs are, which genre they fall into and how they have been rated. This is a different starting point than usual approaches and will allow the user to potentially find other music than without it.

The people that will use our tool are familiar with the internet and use it quite often. Moreover they are using their computer a lot at home and have their pc or mac in the living room where it is not only used for work, but also as multimedia station. That means they play video, music and watch TV with their computer.

This group is specially interested in music and is buying songs over the internet and not buying music CD's frequently anymore. If they buy a CD they rip the content onto the PC to have it in their music library.

=== What are the special interests of our target group? ===

Probably our target group is quite young, probably creative and they potentially have some sort of interest in exploring data visualisations in alternative ways. As can be assumed by analyzing iTunes, the target group likes nice and neat design, cool features and gimmicks. They probably use the visualisation mainly for playing around with their music collection.

Our target group has more interest in mp3s than they have in buying CDs and playing them in their CD player. They have all their music stored on their computer and want to have many possibilities to browse through their collection. They are looking for new ways of finding music so that they can listen to the music they like and the music matching upcoming emotions at every point of time. Instead of manually choosing a music CD they want to use a tool to help them selecting music out of their archive that suits their mood.

=== Are there any known / often used Methods / Visualisation Techniques? ===

Up to now there are no real visualisation techniques in the area of music players like iTunes. The only visualisation technique that can be found on most music tools is the sound visualisation of a playing song, implemented as frequency response or graphical art responding to the music progress.

For representing the songs of a library, ususally lists or tables are used. List-like and tabular approaches can not really be considered as graphic visualisation - they just are textual representations of the data that the user can read and use. Especially in iTunes the possibilities of combining different ID3 attributes to get a filtered playlist are vast. The user is for example able to choose only songs from 1980 to 1984 that are in the rock genre, have a rating between 1 and 3 stars and are not from Guns n' Roses. So you can do quite a lot of things with it, but there is no visualisation behind it. You can choose all that, but you can not choose it graphically which can make this much easier, faster, or just more interesting.

== Purpose of the Visualisation ==

=== What should be achieved with the visualisation? ===

* An expressive and effective representation of the data records and contained information enabling users to gain an overview of the music in the library as fast as possible using this visualization.
* An explorative visualisation of the data records. A good presentation of the contained information helps users to obtain information better.
* A new approach for finding music to play by bringing genre, year of creation, rating and size of the data set into relation

=== Which tasks should be solved? ===

Using the nowadays available music library tools is effective and suitable for standard tasks like the following ones most of the time:
* Searching for music by textual fields like artist, album, genre etc.
* Filtering lists of music by selecting criteria on different attributes
* Ordering lists of music by different attributes
* Scrolling through lists of different items searching for songs that will be played next

All these standard tasks are more or less well known nowadays and implemented into most of the modern music libraries. Interestingly indeed is the fact that there are so much more approaches on finding music using alternative ways that have not been designed or implemented even after years like the following:
* Computer-aided decision of music to play based on user behavior (music types often skipped quickly, music types often played loud...)
* Graphical representations of relational visualisations of the music archive

This second task was being analyzed for the design of the here discussed visualisation trying to solve the following tasks:
* Representing a quick overview of the different types of music in the archive
* Guiding the user to good rated music using color coding
* Marking different sized song groups using different sizes of the representing graphic objects (boxes)
* Providing a focused view for selected music groups using a multi-view window layout
* Giving statistical information on selected music groups via a separated but linked window of the rating-distribution of the selected music group
* Filtering the representation by selecting range and scale

=== Questions that can be solved using this Visualisation ===

* Which Jazz songs of the 80's do I have im my library, how have I evaluated them in average?
* How many songs of one special genre of one special year do I have?
* How do I have them rated?
* Which albums do I have of a selected genre and year of publishing?
* Which songs are included on an album?
* How often do I have played a song?
* When did I last play a song?
* Of which genre and how old are most of the songs in my archive?
* Which genre do I like (which genre is best rated)?
* Selecting genre and year/decade, which alternative music do i find to one other?
* Which albums match each other in terms of genre and age?

== Designproposal ==

=== Which kinds of Visualisation should be used? ===
The actually existing music library systems mostly don't really visualize the contained music using its attributes but simply use lists of items (artists, albums, songs, playlists...). While this concept is easily understandable for the end-user it only allows for simple browsing using the following techniques:

* Searching for specific artists, albums, titles and so on.
* Filtering the list by choosing ranges or values for some attributes
* Sorting the list by different attributes
* Scrolling the list up and down

Some attributes of song items like artist, album and title are of hierarchical character and therefore suited mainly for being displayed in a list or being used for browsing in multi-step lists. One example of such a multi-step list is the media library in Winamp (TODO: cite): After selecting an artist in the first list, the second list gets filled with the available albums of this artist. Selecting an album fills the next list with the associated songs of this album and so on.

TODO: list the different types of attributes!

While hierarchical attributes can be considered essential and are very useful for a multi-level selection process or direct textual searching/filtering, they only can be used if the user exactly knows what he or she wants to listen to. In opposite users often want to listen to randomly chosen or special pattern matching song lists like "My Top 10 Most Played Ones".

Considering these facts we chose other criteria than hierachical attributes of music items for creating new concepts of how to find interesting music without exactly knowning what to listen to. Using attributes like genre, year of creation, rating, playcount and date of last play different approaches of browsing music came up to our minds.

=== Visual Mapping ===
In the context of this task the "Music Type Selection" (TODO: find a superior name) browsing approach was chosen for being designed in detail and worked out as a prototype. This approach uses the following visual mapping:
* The approach bases on a 2D diagram containing:
** The year of creation on the x-axis
** The genre on the y-axis
Using this grid groups of similar music with respect to genre and year are getting plotted into the diagram as filled boxes. Additionally another two attributes are being mapped:
* The absolute number of songs within a specific group is mapped as the size of the box.
* The mean rating of all songs within this group is mapped as the intensity of the color used for filling the boxes.

=== Used Techniques / Applied Principles ===
TODO: this is a listing of used techniques only at the moment - detail and map to the implemented features
* Focus & Context: Tiled Multi-Level Browser (Slides 0, Page 16)
** Overview Window
** Zoomed Window
** Details On Demand Window
* Scatterplot (Slides 1, Page 1) + Color and Shape concept: This concept is used in the upper left window. On the x-axis the year of publishing is displayed and on the y-axis the genre. With the color of the shapes the average rating is displayed (white: bad rating; red: best rating) and with the size the number of songs.
* Dynamic Queries: live choosable sliders for attribute ranges (Slides 4, Page 8): This technique is used at the left 2 windows to slide the genre or the albums, if there is not enough space available to display all at one.
* Linking & Brushing: Detail window containing rating distribution of selected songs (Slides 0, Page 25)
* Visual Encoding: volume, color

=== Interaction ===

As you can see in our second [[Media:InfoVis_Gruppe10_Aufgabe3_Entwurf2.jpg|layout]] we have a multi windwow view. The starting point is in the big main window. In the beginning the other windows are empty. In the main part the user sees all the songs availible represented in boxes of different shade and size. It is possible to scale the x- and the y-axis to have a better overview, or to see the boxes larger. When he clicks at one of those boxes more detailed information will appear in the other windows. In the lower left window the user will see the different Artists that suited his selection. There will be one box for each artist containing all the albums of this artist that correspond with the users selection of genre and year. In the lower right window the user can see a more detailed view on the ratings of his selection. So the mean value is split up and one can see how many songs there are for each rating star. In the upper left window the first album of the first artist will be presented, showing the songs.

In the next step the user can interact in the three smaller windows to change the artist, the album, or choose only specific ratings. When the user clicks on a new album or artist the details in the upper right window will be updated. Moreover there is the possibility to choose only some of the ratings represented in the lower right window. For example only 4 to 5 stars. Then the songs in the upper right window will be updated correctly and only albums which contain songs with this rating will be shown in the lower left window.

=== Mockup(s) / Fake Screenshot(s) ===
[[Image:InfoVis_Gruppe10_Aufgabe3_Entwurf1.gif|none|thumb|500px|none|Entwurf 1]]
[[Image:InfoVis_Gruppe10_Aufgabe3_Entwurf2.jpg|none|thumb|561px|none|Entwurf 2]]

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 10 - Aufgabe 3 - Design

2005-11-22T22:00:51Z

UE-InfoVis0506 0027476: /* Which tasks should be solved? */

== Application Area and given Dataset ==

=== Application Area Analysis ===

The application area for this task is to visualize a music archive with the data provided by ID3/iTunes tags. These tags include information such as songname, artist, year, album and so on. The challenge in visualizing this information is to select suitable attributes for being used in relation to each other because of the high number of discreet and "organizational" attributes.

=== Dataset Analysis ===

{|
|- style="background:#e0e0e0"
!Attribute
!Data type
!Description
|- style="background:#eeeeee"
|Name
|Discreet
|Song title
|-
|Artist
|Discreet
|Artist name
|- style="background:#eeeeee"
|Album
|Discreet
|Album name
|-
|Genre
|Nominal
|Genre the song belongs to
|- style="background:#eeeeee"
|Composer
|Discreet
|The composer of the song
|-
|Size
|Ordinal
|The file size
|- style="background:#eeeeee"
|Total time
|Ordinal
|The total time of the song
|-
|Disc number
|Ordinal
|Number of the disc
|- style="background:#eeeeee"
|Disc count
|Ordinal
|Total number of discs
|-
|Track number
|Ordinal
|Track number of this song on the disc
|- style="background:#eeeeee"
|Track count
|Ordinal
|Total number of tracks on the disc
|-
|Year
|Ordinal
|Year of origin
|- style="background:#eeeeee"
|Date Modified
|Ordinal
|Date of modification
|-
|Date added
|Ordinal
|Date when song was added to archive
|- style="background:#eeeeee"
|Bit rate
|Ordinal
|Bit rate of song (e.g. 128kbit/s)
|-
|Sample rate
|Ordinal
|Sample rate of song (e.g. 44100Hz)
|- style="background:#eeeeee"
|Play count
|Ordinal
|Number of time the song was played
|-
|Play date
|Ordinal
|Date of last play
|- style="background:#eeeeee"
|Play date UTC
|Ordinal
|Date of last play in [http://en.wikipedia.org/wiki/UTC UTC]
|-
|Location
|Discreet
|File location
|- style="background:#eeeeee"
|Kind
|Nominal
|Kind of file (e.g. MPEG audio file)
|-
|Rating
|Ordinal
|Personal rating (1-5 stars)
|}

One data record consists of a concatenation of attributes listed in the table above. Those attributes are all 1-dimensional. A data record contains only necessary attributes or attributes with data.

== Target Group Analysis ==

=== Who should use this visualation technique? ===

The visualisation of our concept is mainly designed for people collecting mp3s and musicians who like to use creative and new ways for finding songs to play in their music archive they won't find in the usual tools. Moreover it's for people who like to explore their music collection using different approaches. This will fit the exploring character of information visualisation.

Our visualisation will make it possible to browse through the music collection in different ways than what iTunes offers. It's meant for people who want to find music to play, e.g. songs they didn't listen to for a long time. They will see from which period the songs are, which genre they fall into and how they have been rated. This is a different starting point than usual approaches and will allow the user to potentially find other music than without it.

The people that will use our tool are familiar with the internet and use it quite often. Moreover they are using their computer a lot at home and have their pc or mac in the living room where it is not only used for work, but also as multimedia station. That means they play video, music and watch TV with their computer.

This group is specially interested in music and is buying songs over the internet and not buying music CD's frequently anymore. If they buy a CD they rip the content onto the PC to have it in their music library.

=== What are the special interests of our target group? ===

Probably our target group is quite young, probably creative and they potentially have some sort of interest in exploring data visualisations in alternative ways. As can be assumed by analyzing iTunes, the target group likes nice and neat design, cool features and gimmicks. They probably use the visualisation mainly for playing around with their music collection.

Our target group has more interest in mp3s than they have in buying CDs and playing them in their CD player. They have all their music stored on their computer and want to have many possibilities to browse through their collection. They are looking for new ways of finding music so that they can listen to the music they like and the music matching upcoming emotions at every point of time. Instead of manually choosing a music CD they want to use a tool to help them selecting music out of their archive that suits their mood.

=== Are there any known / often used Methods / Visualisation Techniques? ===

Up to now there are no real visualisation techniques in the area of music players like iTunes. The only visualisation technique that can be found on most music tools is the sound visualisation of a playing song, implemented as frequency response or graphical art responding to the music progress.

For representing the songs of a library, ususally lists or tables are used. List-like and tabular approaches can not really be considered as graphic visualisation - they just are textual representations of the data that the user can read and use. Especially in iTunes the possibilities of combining different ID3 attributes to get a filtered playlist are vast. The user is for example able to choose only songs from 1980 to 1984 that are in the rock genre, have a rating between 1 and 3 stars and are not from Guns n' Roses. So you can do quite a lot of things with it, but there is no visualisation behind it. You can choose all that, but you can not choose it graphically which can make this much easier, faster, or just more interesting.

== Purpose of the Visualisation ==

=== What should be achieved with the visualisation? ===

* An expressive and effective representation of the data records and contained information enabling users to gain an overview of the music in the library as fast as possible using this visualization.
* An explorative visualisation of the data records. A good presentation of the contained information helps users to obtain information better.
* A new approach for finding music to play by bringing genre, year of creation, rating and size of the data set into relation

=== Which tasks should be solved? ===

Using the nowadays available music library tools is effective and suitable for standard tasks like the following ones most of the time:
* Searching for music by textual fields like artist, album, genre etc.
* Filtering lists of music by selecting criteria on different attributes
* Ordering lists of music by different attributes
* Scrolling through lists of different items searching for songs that will be played next

All these standard tasks are more or less well known nowadays and implemented into most of the modern music libraries. Interestingly indeed is the fact that there are so much more approaches on finding music using alternative ways that have not been designed or implemented even after years like the following:
* Computer-aided decision of music to play based on user behavior (music types often skipped quickly, music types often played loud...)
* Graphical representations of relational visualisations of the music archive

This second task was being analyzed for the design of the here discussed visualisation trying to solve the following tasks:
* Representing a quick overview of the different types of music in the archive
* Guiding the user to good rated music using color coding
* Marking different sized song groups using different sizes of the representing graphic objects (boxes)
* Providing a focused view for selected music groups using a multi-view window layout
* Giving statistical information on selected music groups via a separated but linked window of the rating-distribution of the selected music group
* Filtering the representation by selecting range and scale

=== Questions that can be solved using this Visualisation ===

* Which Jazz songs of the 80's do I have im my library, how have I evaluated them in average?
* How many songs of a Genre of a year do I have?
* How do I have them rated?
* Which albums do I have of a selected Genre and Year of publishing?
* Which songs are included on an album?
* How often have I played a song ?
* When did I play last a song ?

== Designproposal ==

=== Which kinds of Visualisation should be used? ===
The actually existing music library systems mostly don't really visualize the contained music using its attributes but simply use lists of items (artists, albums, songs, playlists...). While this concept is easily understandable for the end-user it only allows for simple browsing using the following techniques:

* Searching for specific artists, albums, titles and so on.
* Filtering the list by choosing ranges or values for some attributes
* Sorting the list by different attributes
* Scrolling the list up and down

Some attributes of song items like artist, album and title are of hierarchical character and therefore suited mainly for being displayed in a list or being used for browsing in multi-step lists. One example of such a multi-step list is the media library in Winamp (TODO: cite): After selecting an artist in the first list, the second list gets filled with the available albums of this artist. Selecting an album fills the next list with the associated songs of this album and so on.

TODO: list the different types of attributes!

While hierarchical attributes can be considered essential and are very useful for a multi-level selection process or direct textual searching/filtering, they only can be used if the user exactly knows what he or she wants to listen to. In opposite users often want to listen to randomly chosen or special pattern matching song lists like "My Top 10 Most Played Ones".

Considering these facts we chose other criteria than hierachical attributes of music items for creating new concepts of how to find interesting music without exactly knowning what to listen to. Using attributes like genre, year of creation, rating, playcount and date of last play different approaches of browsing music came up to our minds.

=== Visual Mapping ===
In the context of this task the "Music Type Selection" (TODO: find a superior name) browsing approach was chosen for being designed in detail and worked out as a prototype. This approach uses the following visual mapping:
* The approach bases on a 2D diagram containing:
** The year of creation on the x-axis
** The genre on the y-axis
Using this grid groups of similar music with respect to genre and year are getting plotted into the diagram as filled boxes. Additionally another two attributes are being mapped:
* The absolute number of songs within a specific group is mapped as the size of the box.
* The mean rating of all songs within this group is mapped as the intensity of the color used for filling the boxes.

=== Used Techniques / Applied Principles ===
TODO: this is a listing of used techniques only at the moment - detail and map to the implemented features
* Focus & Context: Tiled Multi-Level Browser (Slides 0, Page 16)
** Overview Window
** Zoomed Window
** Details On Demand Window
* Scatterplot + Color and Shape concept
* Dynamic Queries: live choosable sliders for attribute ranges (Slides 4, Page 8)
* Linking & Brushing: Detail window containing rating distribution of selected songs (Slides 0, Page 25)
* Visual Encoding: volume, color

=== Interaction ===

As you can see in our second [[Media:InfoVis_Gruppe10_Aufgabe3_Entwurf2.jpg|layout]] we have a multi windwow view. The starting point is in the big main window. In the beginning the other windows are empty. In the main part the user sees all the songs availible represented in boxes of different shade and size. It is possible to scale the x- and the y-axis to have a better overview, or to see the boxes larger. When he clicks at one of those boxes more detailed information will appear in the other windows. In the lower left window the user will see the different Artists that suited his selection. There will be one box for each artist containing all the albums of this artist that correspond with the users selection of genre and year. In the lower right window the user can see a more detailed view on the ratings of his selection. So the mean value is split up and one can see how many songs there are for each rating star. In the upper left window the first album of the first artist will be presented, showing the songs.

In the next step the user can interact in the three smaller windows to change the artist, the album, or choose only specific ratings. When the user clicks on a new album or artist the details in the upper right window will be updated. Moreover there is the possibility to choose only some of the ratings represented in the lower right window. For example only 4 to 5 stars. Then the songs in the upper right window will be updated correctly and only albums which contain songs with this rating will be shown in the lower left window.

=== Mockup(s) / Fake Screenshot(s) ===
[[Image:InfoVis_Gruppe10_Aufgabe3_Entwurf1.gif|none|thumb|500px|none|Entwurf 1]]
[[Image:InfoVis_Gruppe10_Aufgabe3_Entwurf2.jpg|none|thumb|561px|none|Entwurf 2]]

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 10 - Aufgabe 3 - Design

2005-11-22T21:52:27Z

UE-InfoVis0506 0027476: /* What should be achieved with the Visualisation? */

== Application Area and given Dataset ==

=== Application Area Analysis ===

The application area for this task is to visualize a music archive with the data provided by ID3/iTunes tags. These tags include information such as songname, artist, year, album and so on. The challenge in visualizing this information is to select suitable attributes for being used in relation to each other because of the high number of discreet and "organizational" attributes.

=== Dataset Analysis ===

{|
|- style="background:#e0e0e0"
!Attribute
!Data type
!Description
|- style="background:#eeeeee"
|Name
|Discreet
|Song title
|-
|Artist
|Discreet
|Artist name
|- style="background:#eeeeee"
|Album
|Discreet
|Album name
|-
|Genre
|Nominal
|Genre the song belongs to
|- style="background:#eeeeee"
|Composer
|Discreet
|The composer of the song
|-
|Size
|Ordinal
|The file size
|- style="background:#eeeeee"
|Total time
|Ordinal
|The total time of the song
|-
|Disc number
|Ordinal
|Number of the disc
|- style="background:#eeeeee"
|Disc count
|Ordinal
|Total number of discs
|-
|Track number
|Ordinal
|Track number of this song on the disc
|- style="background:#eeeeee"
|Track count
|Ordinal
|Total number of tracks on the disc
|-
|Year
|Ordinal
|Year of origin
|- style="background:#eeeeee"
|Date Modified
|Ordinal
|Date of modification
|-
|Date added
|Ordinal
|Date when song was added to archive
|- style="background:#eeeeee"
|Bit rate
|Ordinal
|Bit rate of song (e.g. 128kbit/s)
|-
|Sample rate
|Ordinal
|Sample rate of song (e.g. 44100Hz)
|- style="background:#eeeeee"
|Play count
|Ordinal
|Number of time the song was played
|-
|Play date
|Ordinal
|Date of last play
|- style="background:#eeeeee"
|Play date UTC
|Ordinal
|Date of last play in [http://en.wikipedia.org/wiki/UTC UTC]
|-
|Location
|Discreet
|File location
|- style="background:#eeeeee"
|Kind
|Nominal
|Kind of file (e.g. MPEG audio file)
|-
|Rating
|Ordinal
|Personal rating (1-5 stars)
|}

One data record consists of a concatenation of attributes listed in the table above. Those attributes are all 1-dimensional. A data record contains only necessary attributes or attributes with data.

== Target Group Analysis ==

=== Who should use this visualation technique? ===

The visualisation of our concept is mainly designed for people collecting mp3s and musicians who like to use creative and new ways for finding songs to play in their music archive they won't find in the usual tools. Moreover it's for people who like to explore their music collection using different approaches. This will fit the exploring character of information visualisation.

Our visualisation will make it possible to browse through the music collection in different ways than what iTunes offers. It's meant for people who want to find music to play, e.g. songs they didn't listen to for a long time. They will see from which period the songs are, which genre they fall into and how they have been rated. This is a different starting point than usual approaches and will allow the user to potentially find other music than without it.

The people that will use our tool are familiar with the internet and use it quite often. Moreover they are using their computer a lot at home and have their pc or mac in the living room where it is not only used for work, but also as multimedia station. That means they play video, music and watch TV with their computer.

This group is specially interested in music and is buying songs over the internet and not buying music CD's frequently anymore. If they buy a CD they rip the content onto the PC to have it in their music library.

=== What are the special interests of our target group? ===

Probably our target group is quite young, probably creative and they potentially have some sort of interest in exploring data visualisations in alternative ways. As can be assumed by analyzing iTunes, the target group likes nice and neat design, cool features and gimmicks. They probably use the visualisation mainly for playing around with their music collection.

Our target group has more interest in mp3s than they have in buying CDs and playing them in their CD player. They have all their music stored on their computer and want to have many possibilities to browse through their collection. They are looking for new ways of finding music so that they can listen to the music they like and the music matching upcoming emotions at every point of time. Instead of manually choosing a music CD they want to use a tool to help them selecting music out of their archive that suits their mood.

=== Are there any known / often used Methods / Visualisation Techniques? ===

Up to now there are no real visualisation techniques in the area of music players like iTunes. The only visualisation technique that can be found on most music tools is the sound visualisation of a playing song, implemented as frequency response or graphical art responding to the music progress.

For representing the songs of a library, ususally lists or tables are used. List-like and tabular approaches can not really be considered as graphic visualisation - they just are textual representations of the data that the user can read and use. Especially in iTunes the possibilities of combining different ID3 attributes to get a filtered playlist are vast. The user is for example able to choose only songs from 1980 to 1984 that are in the rock genre, have a rating between 1 and 3 stars and are not from Guns n' Roses. So you can do quite a lot of things with it, but there is no visualisation behind it. You can choose all that, but you can not choose it graphically which can make this much easier, faster, or just more interesting.

== Purpose of the Visualisation ==

=== What should be achieved with the visualisation? ===

* An expressive and effective representation of the data records and contained information enabling users to gain an overview of the music in the library as fast as possible using this visualization.
* An explorative visualisation of the data records. A good presentation of the contained information helps users to obtain information better.
* A new approach for finding music to play by bringing genre, year of creation, rating and size of the data set into relation

=== Which tasks should be solved? ===

* current condition from information
* Visualization should be clear , Information is made more easily understandable.
* Data must be interpreted correct
* Information is explained by the best way user
* Restriction of the data . NOT "too much data , too little space".

=== Questions that can be solved using this Visualisation ===

* Which Jazz Songs of the 80's do I have in my archives, which I evaluated average?
* How many Songs do I have in Genre "Metal" in 2000 ?
* When did I play last "Shoot ME again" ?
* How often have I played Song "My World"?
* Which albums of Metallica do I have ?
* When was "Purify" created ?

----

* Which Jazz songs of the 80's do I have im my library, how have I evaluated them in average?
* How many songs of a Genre of a year do I have?
* How do I have them rated?
* Which albums do I have of a selected Genre and Year of publishing?
* Which songs are included on an album?

== Designproposal ==

=== Which kinds of Visualisation should be used? ===
The actually existing music library systems mostly don't really visualize the contained music using its attributes but simply use lists of items (artists, albums, songs, playlists...). While this concept is easily understandable for the end-user it only allows for simple browsing using the following techniques:

* Searching for specific artists, albums, titles and so on.
* Filtering the list by choosing ranges or values for some attributes
* Sorting the list by different attributes
* Scrolling the list up and down

Some attributes of song items like artist, album and title are of hierarchical character and therefore suited mainly for being displayed in a list or being used for browsing in multi-step lists. One example of such a multi-step list is the media library in Winamp (TODO: cite): After selecting an artist in the first list, the second list gets filled with the available albums of this artist. Selecting an album fills the next list with the associated songs of this album and so on.

TODO: list the different types of attributes!

While hierarchical attributes can be considered essential and are very useful for a multi-level selection process or direct textual searching/filtering, they only can be used if the user exactly knows what he or she wants to listen to. In opposite users often want to listen to randomly chosen or special pattern matching song lists like "My Top 10 Most Played Ones".

Considering these facts we chose other criteria than hierachical attributes of music items for creating new concepts of how to find interesting music without exactly knowning what to listen to. Using attributes like genre, year of creation, rating, playcount and date of last play different approaches of browsing music came up to our minds.

=== Visual Mapping ===
In the context of this task the "Music Type Selection" (TODO: find a superior name) browsing approach was chosen for being designed in detail and worked out as a prototype. This approach uses the following visual mapping:
* The approach bases on a 2D diagram containing:
** The year of creation on the x-axis
** The genre on the y-axis
Using this grid groups of similar music with respect to genre and year are getting plotted into the diagram as filled boxes. Additionally another two attributes are being mapped:
* The absolute number of songs within a specific group is mapped as the size of the box.
* The mean rating of all songs within this group is mapped as the intensity of the color used for filling the boxes.

=== Used Techniques / Applied Principles ===
TODO: this is a listing of used techniques only at the moment - detail and map to the implemented features
* Focus & Context: Tiled Multi-Level Browser (Slides 0, Page 16)
** Overview Window
** Zoomed Window
** Details On Demand Window
* Scatterplot + Color and Shape concept
* Dynamic Queries: live choosable sliders for attribute ranges (Slides 4, Page 8)
* Linking & Brushing: Detail window containing rating distribution of selected songs (Slides 0, Page 25)
* Visual Encoding: volume, color

=== Interaction ===

As you can see in our second [[Media:InfoVis_Gruppe10_Aufgabe3_Entwurf2.jpg|layout]] we have a multi windwow view. The starting point is in the big main window. In the beginning the other windows are empty. In the main part the user sees all the songs availible represented in boxes of different shade and size. It is possible to scale the x- and the y-axis to have a better overview, or to see the boxes larger. When he clicks at one of those boxes more detailed information will appear in the other windows. In the lower left window the user will see the different Artists that suited his selection. There will be one box for each artist containing all the albums of this artist that correspond with the users selection of genre and year. In the lower right window the user can see a more detailed view on the ratings of his selection. So the mean value is split up and one can see how many songs there are for each rating star. In the upper left window the first album of the first artist will be presented, showing the songs.

In the next step the user can interact in the three smaller windows to change the artist, the album, or choose only specific ratings. When the user clicks on a new album or artist the details in the upper right window will be updated. Moreover there is the possibility to choose only some of the ratings represented in the lower right window. For example only 4 to 5 stars. Then the songs in the upper right window will be updated correctly and only albums which contain songs with this rating will be shown in the lower left window.

=== Mockup(s) / Fake Screenshot(s) ===
[[Image:InfoVis_Gruppe10_Aufgabe3_Entwurf1.gif|none|thumb|500px|none|Entwurf 1]]
[[Image:InfoVis_Gruppe10_Aufgabe3_Entwurf2.jpg|none|thumb|561px|none|Entwurf 2]]

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 10 - Aufgabe 3 - Design

2005-11-22T21:47:51Z

UE-InfoVis0506 0027476: /* Are there any known / often used Methods / Visualisation Techniques? */

== Application Area and given Dataset ==

=== Application Area Analysis ===

The application area for this task is to visualize a music archive with the data provided by ID3/iTunes tags. These tags include information such as songname, artist, year, album and so on. The challenge in visualizing this information is to select suitable attributes for being used in relation to each other because of the high number of discreet and "organizational" attributes.

=== Dataset Analysis ===

{|
|- style="background:#e0e0e0"
!Attribute
!Data type
!Description
|- style="background:#eeeeee"
|Name
|Discreet
|Song title
|-
|Artist
|Discreet
|Artist name
|- style="background:#eeeeee"
|Album
|Discreet
|Album name
|-
|Genre
|Nominal
|Genre the song belongs to
|- style="background:#eeeeee"
|Composer
|Discreet
|The composer of the song
|-
|Size
|Ordinal
|The file size
|- style="background:#eeeeee"
|Total time
|Ordinal
|The total time of the song
|-
|Disc number
|Ordinal
|Number of the disc
|- style="background:#eeeeee"
|Disc count
|Ordinal
|Total number of discs
|-
|Track number
|Ordinal
|Track number of this song on the disc
|- style="background:#eeeeee"
|Track count
|Ordinal
|Total number of tracks on the disc
|-
|Year
|Ordinal
|Year of origin
|- style="background:#eeeeee"
|Date Modified
|Ordinal
|Date of modification
|-
|Date added
|Ordinal
|Date when song was added to archive
|- style="background:#eeeeee"
|Bit rate
|Ordinal
|Bit rate of song (e.g. 128kbit/s)
|-
|Sample rate
|Ordinal
|Sample rate of song (e.g. 44100Hz)
|- style="background:#eeeeee"
|Play count
|Ordinal
|Number of time the song was played
|-
|Play date
|Ordinal
|Date of last play
|- style="background:#eeeeee"
|Play date UTC
|Ordinal
|Date of last play in [http://en.wikipedia.org/wiki/UTC UTC]
|-
|Location
|Discreet
|File location
|- style="background:#eeeeee"
|Kind
|Nominal
|Kind of file (e.g. MPEG audio file)
|-
|Rating
|Ordinal
|Personal rating (1-5 stars)
|}

One data record consists of a concatenation of attributes listed in the table above. Those attributes are all 1-dimensional. A data record contains only necessary attributes or attributes with data.

== Target Group Analysis ==

=== Who should use this visualation technique? ===

The visualisation of our concept is mainly designed for people collecting mp3s and musicians who like to use creative and new ways for finding songs to play in their music archive they won't find in the usual tools. Moreover it's for people who like to explore their music collection using different approaches. This will fit the exploring character of information visualisation.

Our visualisation will make it possible to browse through the music collection in different ways than what iTunes offers. It's meant for people who want to find music to play, e.g. songs they didn't listen to for a long time. They will see from which period the songs are, which genre they fall into and how they have been rated. This is a different starting point than usual approaches and will allow the user to potentially find other music than without it.

The people that will use our tool are familiar with the internet and use it quite often. Moreover they are using their computer a lot at home and have their pc or mac in the living room where it is not only used for work, but also as multimedia station. That means they play video, music and watch TV with their computer.

This group is specially interested in music and is buying songs over the internet and not buying music CD's frequently anymore. If they buy a CD they rip the content onto the PC to have it in their music library.

=== What are the special interests of our target group? ===

Probably our target group is quite young, probably creative and they potentially have some sort of interest in exploring data visualisations in alternative ways. As can be assumed by analyzing iTunes, the target group likes nice and neat design, cool features and gimmicks. They probably use the visualisation mainly for playing around with their music collection.

Our target group has more interest in mp3s than they have in buying CDs and playing them in their CD player. They have all their music stored on their computer and want to have many possibilities to browse through their collection. They are looking for new ways of finding music so that they can listen to the music they like and the music matching upcoming emotions at every point of time. Instead of manually choosing a music CD they want to use a tool to help them selecting music out of their archive that suits their mood.

=== Are there any known / often used Methods / Visualisation Techniques? ===

Up to now there are no real visualisation techniques in the area of music players like iTunes. The only visualisation technique that can be found on most music tools is the sound visualisation of a playing song, implemented as frequency response or graphical art responding to the music progress.

For representing the songs of a library, ususally lists or tables are used. List-like and tabular approaches can not really be considered as graphic visualisation - they just are textual representations of the data that the user can read and use. Especially in iTunes the possibilities of combining different ID3 attributes to get a filtered playlist are vast. The user is for example able to choose only songs from 1980 to 1984 that are in the rock genre, have a rating between 1 and 3 stars and are not from Guns n' Roses. So you can do quite a lot of things with it, but there is no visualisation behind it. You can choose all that, but you can not choose it graphically which can make this much easier, faster, or just more interesting.

== Purpose of the Visualisation ==

=== What should be achieved with the Visualisation? ===

* a expressive and effective representation of the data records and contained information so that user can see with this visualization as fast as possible overview of the data and contained information.
* Exploration visualisation on the data record . Good presentation of information, because users can obtain information with visualisation better.
* semantic information from data
* Data condensation , so that complex information can be well observed.

=== Which tasks should be solved? ===

* current condition from information
* Visualization should be clear , Information is made more easily understandable.
* Data must be interpreted correct
* Information is explained by the best way user
* Restriction of the data . NOT "too much data , too little space".

=== Questions that can be solved using this Visualisation ===

* Which Jazz Songs of the 80's do I have in my archives, which I evaluated average?
* How many Songs do I have in Genre "Metal" in 2000 ?
* When did I play last "Shoot ME again" ?
* How often have I played Song "My World"?
* Which albums of Metallica do I have ?
* When was "Purify" created ?

----

* Which Jazz songs of the 80's do I have im my library, how have I evaluated them in average?
* How many songs of a Genre of a year do I have?
* How do I have them rated?
* Which albums do I have of a selected Genre and Year of publishing?
* Which songs are included on an album?

== Designproposal ==

=== Which kinds of Visualisation should be used? ===
The actually existing music library systems mostly don't really visualize the contained music using its attributes but simply use lists of items (artists, albums, songs, playlists...). While this concept is easily understandable for the end-user it only allows for simple browsing using the following techniques:

* Searching for specific artists, albums, titles and so on.
* Filtering the list by choosing ranges or values for some attributes
* Sorting the list by different attributes
* Scrolling the list up and down

Some attributes of song items like artist, album and title are of hierarchical character and therefore suited mainly for being displayed in a list or being used for browsing in multi-step lists. One example of such a multi-step list is the media library in Winamp (TODO: cite): After selecting an artist in the first list, the second list gets filled with the available albums of this artist. Selecting an album fills the next list with the associated songs of this album and so on.

TODO: list the different types of attributes!

While hierarchical attributes can be considered essential and are very useful for a multi-level selection process or direct textual searching/filtering, they only can be used if the user exactly knows what he or she wants to listen to. In opposite users often want to listen to randomly chosen or special pattern matching song lists like "My Top 10 Most Played Ones".

Considering these facts we chose other criteria than hierachical attributes of music items for creating new concepts of how to find interesting music without exactly knowning what to listen to. Using attributes like genre, year of creation, rating, playcount and date of last play different approaches of browsing music came up to our minds.

=== Visual Mapping ===
In the context of this task the "Music Type Selection" (TODO: find a superior name) browsing approach was chosen for being designed in detail and worked out as a prototype. This approach uses the following visual mapping:
* The approach bases on a 2D diagram containing:
** The year of creation on the x-axis
** The genre on the y-axis
Using this grid groups of similar music with respect to genre and year are getting plotted into the diagram as filled boxes. Additionally another two attributes are being mapped:
* The absolute number of songs within a specific group is mapped as the size of the box.
* The mean rating of all songs within this group is mapped as the intensity of the color used for filling the boxes.

=== Used Techniques / Applied Principles ===
TODO: this is a listing of used techniques only at the moment - detail and map to the implemented features
* Focus & Context: Tiled Multi-Level Browser (Slides 0, Page 16)
** Overview Window
** Zoomed Window
** Details On Demand Window
* Scatterplot + Color and Shape concept
* Dynamic Queries: live choosable sliders for attribute ranges (Slides 4, Page 8)
* Linking & Brushing: Detail window containing rating distribution of selected songs (Slides 0, Page 25)
* Visual Encoding: volume, color

=== Interaction ===

As you can see in our second [[Media:InfoVis_Gruppe10_Aufgabe3_Entwurf2.jpg|layout]] we have a multi windwow view. The starting point is in the big main window. In the beginning the other windows are empty. In the main part the user sees all the songs availible represented in boxes of different shade and size. It is possible to scale the x- and the y-axis to have a better overview, or to see the boxes larger. When he clicks at one of those boxes more detailed information will appear in the other windows. In the lower left window the user will see the different Artists that suited his selection. There will be one box for each artist containing all the albums of this artist that correspond with the users selection of genre and year. In the lower right window the user can see a more detailed view on the ratings of his selection. So the mean value is split up and one can see how many songs there are for each rating star. In the upper left window the first album of the first artist will be presented, showing the songs.

In the next step the user can interact in the three smaller windows to change the artist, the album, or choose only specific ratings. When the user clicks on a new album or artist the details in the upper right window will be updated. Moreover there is the possibility to choose only some of the ratings represented in the lower right window. For example only 4 to 5 stars. Then the songs in the upper right window will be updated correctly and only albums which contain songs with this rating will be shown in the lower left window.

=== Mockup(s) / Fake Screenshot(s) ===
[[Image:InfoVis_Gruppe10_Aufgabe3_Entwurf1.gif|none|thumb|500px|none|Entwurf 1]]
[[Image:InfoVis_Gruppe10_Aufgabe3_Entwurf2.jpg|none|thumb|561px|none|Entwurf 2]]

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 10 - Aufgabe 3 - Design

2005-11-22T21:43:20Z

UE-InfoVis0506 0027476: /* What are the special interests of our target group? */

== Application Area and given Dataset ==

=== Application Area Analysis ===

The application area for this task is to visualize a music archive with the data provided by ID3/iTunes tags. These tags include information such as songname, artist, year, album and so on. The challenge in visualizing this information is to select suitable attributes for being used in relation to each other because of the high number of discreet and "organizational" attributes.

=== Dataset Analysis ===

{|
|- style="background:#e0e0e0"
!Attribute
!Data type
!Description
|- style="background:#eeeeee"
|Name
|Discreet
|Song title
|-
|Artist
|Discreet
|Artist name
|- style="background:#eeeeee"
|Album
|Discreet
|Album name
|-
|Genre
|Nominal
|Genre the song belongs to
|- style="background:#eeeeee"
|Composer
|Discreet
|The composer of the song
|-
|Size
|Ordinal
|The file size
|- style="background:#eeeeee"
|Total time
|Ordinal
|The total time of the song
|-
|Disc number
|Ordinal
|Number of the disc
|- style="background:#eeeeee"
|Disc count
|Ordinal
|Total number of discs
|-
|Track number
|Ordinal
|Track number of this song on the disc
|- style="background:#eeeeee"
|Track count
|Ordinal
|Total number of tracks on the disc
|-
|Year
|Ordinal
|Year of origin
|- style="background:#eeeeee"
|Date Modified
|Ordinal
|Date of modification
|-
|Date added
|Ordinal
|Date when song was added to archive
|- style="background:#eeeeee"
|Bit rate
|Ordinal
|Bit rate of song (e.g. 128kbit/s)
|-
|Sample rate
|Ordinal
|Sample rate of song (e.g. 44100Hz)
|- style="background:#eeeeee"
|Play count
|Ordinal
|Number of time the song was played
|-
|Play date
|Ordinal
|Date of last play
|- style="background:#eeeeee"
|Play date UTC
|Ordinal
|Date of last play in [http://en.wikipedia.org/wiki/UTC UTC]
|-
|Location
|Discreet
|File location
|- style="background:#eeeeee"
|Kind
|Nominal
|Kind of file (e.g. MPEG audio file)
|-
|Rating
|Ordinal
|Personal rating (1-5 stars)
|}

One data record consists of a concatenation of attributes listed in the table above. Those attributes are all 1-dimensional. A data record contains only necessary attributes or attributes with data.

== Target Group Analysis ==

=== Who should use this visualation technique? ===

The visualisation of our concept is mainly designed for people collecting mp3s and musicians who like to use creative and new ways for finding songs to play in their music archive they won't find in the usual tools. Moreover it's for people who like to explore their music collection using different approaches. This will fit the exploring character of information visualisation.

Our visualisation will make it possible to browse through the music collection in different ways than what iTunes offers. It's meant for people who want to find music to play, e.g. songs they didn't listen to for a long time. They will see from which period the songs are, which genre they fall into and how they have been rated. This is a different starting point than usual approaches and will allow the user to potentially find other music than without it.

The people that will use our tool are familiar with the internet and use it quite often. Moreover they are using their computer a lot at home and have their pc or mac in the living room where it is not only used for work, but also as multimedia station. That means they play video, music and watch TV with their computer.

This group is specially interested in music and is buying songs over the internet and not buying music CD's frequently anymore. If they buy a CD they rip the content onto the PC to have it in their music library.

=== What are the special interests of our target group? ===

Probably our target group is quite young, probably creative and they potentially have some sort of interest in exploring data visualisations in alternative ways. As can be assumed by analyzing iTunes, the target group likes nice and neat design, cool features and gimmicks. They probably use the visualisation mainly for playing around with their music collection.

Our target group has more interest in mp3s than they have in buying CDs and playing them in their CD player. They have all their music stored on their computer and want to have many possibilities to browse through their collection. They are looking for new ways of finding music so that they can listen to the music they like and the music matching upcoming emotions at every point of time. Instead of manually choosing a music CD they want to use a tool to help them selecting music out of their archive that suits their mood.

=== Are there any known / often used Methods / Visualisation Techniques? ===

Up to now there are no real visualisation techniques in the area of music players like iTunes. The only visualisation techniques can be found at the playback time of a song, when the music itself is visualised.

For representing the Songs of a library ususally lists or tables are used. That means this is not a real graphic visualisation, it's just a representation of the data, that the user can read and use to make for example playlists. Especially in iTunes the possibilities of combining many ID3 attributes to get a playlist are vast. You can for example say you want only songs from 1980 to 1984, that are in the rock genre, that have a rating between 1 and 3 stars, and are not from Guns n' Roses. So you can do quite a lot of things with it, but there is no visualisation behind it. You can choose all that, but you can not choose it graphically which can make this much easier, faster, or just more interessting.

== Purpose of the Visualisation ==

=== What should be achieved with the Visualisation? ===

* a expressive and effective representation of the data records and contained information so that user can see with this visualization as fast as possible overview of the data and contained information.
* Exploration visualisation on the data record . Good presentation of information, because users can obtain information with visualisation better.
* semantic information from data
* Data condensation , so that complex information can be well observed.

=== Which tasks should be solved? ===

* current condition from information
* Visualization should be clear , Information is made more easily understandable.
* Data must be interpreted correct
* Information is explained by the best way user
* Restriction of the data . NOT "too much data , too little space".

=== Questions that can be solved using this Visualisation ===

* Which Jazz Songs of the 80's do I have in my archives, which I evaluated average?
* How many Songs do I have in Genre "Metal" in 2000 ?
* When did I play last "Shoot ME again" ?
* How often have I played Song "My World"?
* Which albums of Metallica do I have ?
* When was "Purify" created ?

----

* Which Jazz songs of the 80's do I have im my library, how have I evaluated them in average?
* How many songs of a Genre of a year do I have?
* How do I have them rated?
* Which albums do I have of a selected Genre and Year of publishing?
* Which songs are included on an album?

== Designproposal ==

=== Which kinds of Visualisation should be used? ===
The actually existing music library systems mostly don't really visualize the contained music using its attributes but simply use lists of items (artists, albums, songs, playlists...). While this concept is easily understandable for the end-user it only allows for simple browsing using the following techniques:

* Searching for specific artists, albums, titles and so on.
* Filtering the list by choosing ranges or values for some attributes
* Sorting the list by different attributes
* Scrolling the list up and down

Some attributes of song items like artist, album and title are of hierarchical character and therefore suited mainly for being displayed in a list or being used for browsing in multi-step lists. One example of such a multi-step list is the media library in Winamp (TODO: cite): After selecting an artist in the first list, the second list gets filled with the available albums of this artist. Selecting an album fills the next list with the associated songs of this album and so on.

TODO: list the different types of attributes!

While hierarchical attributes can be considered essential and are very useful for a multi-level selection process or direct textual searching/filtering, they only can be used if the user exactly knows what he or she wants to listen to. In opposite users often want to listen to randomly chosen or special pattern matching song lists like "My Top 10 Most Played Ones".

Considering these facts we chose other criteria than hierachical attributes of music items for creating new concepts of how to find interesting music without exactly knowning what to listen to. Using attributes like genre, year of creation, rating, playcount and date of last play different approaches of browsing music came up to our minds.

=== Visual Mapping ===
In the context of this task the "Music Type Selection" (TODO: find a superior name) browsing approach was chosen for being designed in detail and worked out as a prototype. This approach uses the following visual mapping:
* The approach bases on a 2D diagram containing:
** The year of creation on the x-axis
** The genre on the y-axis
Using this grid groups of similar music with respect to genre and year are getting plotted into the diagram as filled boxes. Additionally another two attributes are being mapped:
* The absolute number of songs within a specific group is mapped as the size of the box.
* The mean rating of all songs within this group is mapped as the intensity of the color used for filling the boxes.

=== Used Techniques / Applied Principles ===
TODO: this is a listing of used techniques only at the moment - detail and map to the implemented features
* Focus & Context: Tiled Multi-Level Browser (Slides 0, Page 16)
** Overview Window
** Zoomed Window
** Details On Demand Window
* Scatterplot + Color and Shape concept
* Dynamic Queries: live choosable sliders for attribute ranges (Slides 4, Page 8)
* Linking & Brushing: Detail window containing rating distribution of selected songs (Slides 0, Page 25)
* Visual Encoding: volume, color

=== Interaction ===

As you can see in our second [[Media:InfoVis_Gruppe10_Aufgabe3_Entwurf2.jpg|layout]] we have a multi windwow view. The starting point is in the big main window. In the beginning the other windows are empty. In the main part the user sees all the songs availible represented in boxes of different shade and size. It is possible to scale the x- and the y-axis to have a better overview, or to see the boxes larger. When he clicks at one of those boxes more detailed information will appear in the other windows. In the lower left window the user will see the different Artists that suited his selection. There will be one box for each artist containing all the albums of this artist that correspond with the users selection of genre and year. In the lower right window the user can see a more detailed view on the ratings of his selection. So the mean value is split up and one can see how many songs there are for each rating star. In the upper left window the first album of the first artist will be presented, showing the songs.

In the next step the user can interact in the three smaller windows to change the artist, the album, or choose only specific ratings. When the user clicks on a new album or artist the details in the upper right window will be updated. Moreover there is the possibility to choose only some of the ratings represented in the lower right window. For example only 4 to 5 stars. Then the songs in the upper right window will be updated correctly and only albums which contain songs with this rating will be shown in the lower left window.

=== Mockup(s) / Fake Screenshot(s) ===
[[Image:InfoVis_Gruppe10_Aufgabe3_Entwurf1.gif|none|thumb|500px|none|Entwurf 1]]
[[Image:InfoVis_Gruppe10_Aufgabe3_Entwurf2.jpg|none|thumb|561px|none|Entwurf 2]]

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 10 - Aufgabe 3 - Design

2005-11-22T21:39:31Z

UE-InfoVis0506 0027476: /* Who should use this visualation technique? */

== Application Area and given Dataset ==

=== Application Area Analysis ===

The application area for this task is to visualize a music archive with the data provided by ID3/iTunes tags. These tags include information such as songname, artist, year, album and so on. The challenge in visualizing this information is to select suitable attributes for being used in relation to each other because of the high number of discreet and "organizational" attributes.

=== Dataset Analysis ===

{|
|- style="background:#e0e0e0"
!Attribute
!Data type
!Description
|- style="background:#eeeeee"
|Name
|Discreet
|Song title
|-
|Artist
|Discreet
|Artist name
|- style="background:#eeeeee"
|Album
|Discreet
|Album name
|-
|Genre
|Nominal
|Genre the song belongs to
|- style="background:#eeeeee"
|Composer
|Discreet
|The composer of the song
|-
|Size
|Ordinal
|The file size
|- style="background:#eeeeee"
|Total time
|Ordinal
|The total time of the song
|-
|Disc number
|Ordinal
|Number of the disc
|- style="background:#eeeeee"
|Disc count
|Ordinal
|Total number of discs
|-
|Track number
|Ordinal
|Track number of this song on the disc
|- style="background:#eeeeee"
|Track count
|Ordinal
|Total number of tracks on the disc
|-
|Year
|Ordinal
|Year of origin
|- style="background:#eeeeee"
|Date Modified
|Ordinal
|Date of modification
|-
|Date added
|Ordinal
|Date when song was added to archive
|- style="background:#eeeeee"
|Bit rate
|Ordinal
|Bit rate of song (e.g. 128kbit/s)
|-
|Sample rate
|Ordinal
|Sample rate of song (e.g. 44100Hz)
|- style="background:#eeeeee"
|Play count
|Ordinal
|Number of time the song was played
|-
|Play date
|Ordinal
|Date of last play
|- style="background:#eeeeee"
|Play date UTC
|Ordinal
|Date of last play in [http://en.wikipedia.org/wiki/UTC UTC]
|-
|Location
|Discreet
|File location
|- style="background:#eeeeee"
|Kind
|Nominal
|Kind of file (e.g. MPEG audio file)
|-
|Rating
|Ordinal
|Personal rating (1-5 stars)
|}

One data record consists of a concatenation of attributes listed in the table above. Those attributes are all 1-dimensional. A data record contains only necessary attributes or attributes with data.

== Target Group Analysis ==

=== Who should use this visualation technique? ===

The visualisation of our concept is mainly designed for people collecting mp3s and musicians who like to use creative and new ways for finding songs to play in their music archive they won't find in the usual tools. Moreover it's for people who like to explore their music collection using different approaches. This will fit the exploring character of information visualisation.

Our visualisation will make it possible to browse through the music collection in different ways than what iTunes offers. It's meant for people who want to find music to play, e.g. songs they didn't listen to for a long time. They will see from which period the songs are, which genre they fall into and how they have been rated. This is a different starting point than usual approaches and will allow the user to potentially find other music than without it.

The people that will use our tool are familiar with the internet and use it quite often. Moreover they are using their computer a lot at home and have their pc or mac in the living room where it is not only used for work, but also as multimedia station. That means they play video, music and watch TV with their computer.

This group is specially interested in music and is buying songs over the internet and not buying music CD's frequently anymore. If they buy a CD they rip the content onto the PC to have it in their music library.

=== What are the special interests of our target group? ===

I think our target group is quite young, probably creative and I suppose they have some sort of interest in playing around with things a bit. As we are analysing iTunes the target group likes nice and neat design, cool tools, cool features and gimmicks. They should use the visualisation mainly for playing around with their music collection.

Our target group has more interesst in mp3s than they have in buying CDs and playing them from their CD player. They have all their music stored on their computer and want to have many possibilities to browse through their collection. They are looking for new ways of finding music so that they can listen to they music they like and the music they feel for in the moment. Instead of putting a CD into the HiFi set they want to see what they have in their collection that suits their mood.

=== Are there any known / often used Methods / Visualisation Techniques? ===

Up to now there are no real visualisation techniques in the area of music players like iTunes. The only visualisation techniques can be found at the playback time of a song, when the music itself is visualised.

For representing the Songs of a library ususally lists or tables are used. That means this is not a real graphic visualisation, it's just a representation of the data, that the user can read and use to make for example playlists. Especially in iTunes the possibilities of combining many ID3 attributes to get a playlist are vast. You can for example say you want only songs from 1980 to 1984, that are in the rock genre, that have a rating between 1 and 3 stars, and are not from Guns n' Roses. So you can do quite a lot of things with it, but there is no visualisation behind it. You can choose all that, but you can not choose it graphically which can make this much easier, faster, or just more interessting.

== Purpose of the Visualisation ==

=== What should be achieved with the Visualisation? ===

* a expressive and effective representation of the data records and contained information so that user can see with this visualization as fast as possible overview of the data and contained information.
* Exploration visualisation on the data record . Good presentation of information, because users can obtain information with visualisation better.
* semantic information from data
* Data condensation , so that complex information can be well observed.

=== Which tasks should be solved? ===

* current condition from information
* Visualization should be clear , Information is made more easily understandable.
* Data must be interpreted correct
* Information is explained by the best way user
* Restriction of the data . NOT "too much data , too little space".

=== Questions that can be solved using this Visualisation ===

* Which Jazz Songs of the 80's do I have in my archives, which I evaluated average?
* How many Songs do I have in Genre "Metal" in 2000 ?
* When did I play last "Shoot ME again" ?
* How often have I played Song "My World"?
* Which albums of Metallica do I have ?
* When was "Purify" created ?

----

* Which Jazz songs of the 80's do I have im my library, how have I evaluated them in average?
* How many songs of a Genre of a year do I have?
* How do I have them rated?
* Which albums do I have of a selected Genre and Year of publishing?
* Which songs are included on an album?

== Designproposal ==

=== Which kinds of Visualisation should be used? ===
The actually existing music library systems mostly don't really visualize the contained music using its attributes but simply use lists of items (artists, albums, songs, playlists...). While this concept is easily understandable for the end-user it only allows for simple browsing using the following techniques:

* Searching for specific artists, albums, titles and so on.
* Filtering the list by choosing ranges or values for some attributes
* Sorting the list by different attributes
* Scrolling the list up and down

Some attributes of song items like artist, album and title are of hierarchical character and therefore suited mainly for being displayed in a list or being used for browsing in multi-step lists. One example of such a multi-step list is the media library in Winamp (TODO: cite): After selecting an artist in the first list, the second list gets filled with the available albums of this artist. Selecting an album fills the next list with the associated songs of this album and so on.

TODO: list the different types of attributes!

While hierarchical attributes can be considered essential and are very useful for a multi-level selection process or direct textual searching/filtering, they only can be used if the user exactly knows what he or she wants to listen to. In opposite users often want to listen to randomly chosen or special pattern matching song lists like "My Top 10 Most Played Ones".

Considering these facts we chose other criteria than hierachical attributes of music items for creating new concepts of how to find interesting music without exactly knowning what to listen to. Using attributes like genre, year of creation, rating, playcount and date of last play different approaches of browsing music came up to our minds.

=== Visual Mapping ===
In the context of this task the "Music Type Selection" (TODO: find a superior name) browsing approach was chosen for being designed in detail and worked out as a prototype. This approach uses the following visual mapping:
* The approach bases on a 2D diagram containing:
** The year of creation on the x-axis
** The genre on the y-axis
Using this grid groups of similar music with respect to genre and year are getting plotted into the diagram as filled boxes. Additionally another two attributes are being mapped:
* The absolute number of songs within a specific group is mapped as the size of the box.
* The mean rating of all songs within this group is mapped as the intensity of the color used for filling the boxes.

=== Used Techniques / Applied Principles ===
TODO: this is a listing of used techniques only at the moment - detail and map to the implemented features
* Focus & Context: Tiled Multi-Level Browser (Slides 0, Page 16)
** Overview Window
** Zoomed Window
** Details On Demand Window
* Scatterplot + Color and Shape concept
* Dynamic Queries: live choosable sliders for attribute ranges (Slides 4, Page 8)
* Linking & Brushing: Detail window containing rating distribution of selected songs (Slides 0, Page 25)
* Visual Encoding: volume, color

=== Interaction ===

As you can see in our second [[Media:InfoVis_Gruppe10_Aufgabe3_Entwurf2.jpg|layout]] we have a multi windwow view. The starting point is in the big main window. In the beginning the other windows are empty. In the main part the user sees all the songs availible represented in boxes of different shade and size. It is possible to scale the x- and the y-axis to have a better overview, or to see the boxes larger. When he clicks at one of those boxes more detailed information will appear in the other windows. In the lower left window the user will see the different Artists that suited his selection. There will be one box for each artist containing all the albums of this artist that correspond with the users selection of genre and year. In the lower right window the user can see a more detailed view on the ratings of his selection. So the mean value is split up and one can see how many songs there are for each rating star. In the upper left window the first album of the first artist will be presented, showing the songs.

In the next step the user can interact in the three smaller windows to change the artist, the album, or choose only specific ratings. When the user clicks on a new album or artist the details in the upper right window will be updated. Moreover there is the possibility to choose only some of the ratings represented in the lower right window. For example only 4 to 5 stars. Then the songs in the upper right window will be updated correctly and only albums which contain songs with this rating will be shown in the lower left window.

=== Mockup(s) / Fake Screenshot(s) ===
[[Image:InfoVis_Gruppe10_Aufgabe3_Entwurf1.gif|none|thumb|500px|none|Entwurf 1]]
[[Image:InfoVis_Gruppe10_Aufgabe3_Entwurf2.jpg|none|thumb|561px|none|Entwurf 2]]

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 10 - Aufgabe 3 - Design

2005-11-22T21:37:31Z

UE-InfoVis0506 0027476: /* Who should use this visualation technique? */

== Application Area and given Dataset ==

=== Application Area Analysis ===

The application area for this task is to visualize a music archive with the data provided by ID3/iTunes tags. These tags include information such as songname, artist, year, album and so on. The challenge in visualizing this information is to select suitable attributes for being used in relation to each other because of the high number of discreet and "organizational" attributes.

=== Dataset Analysis ===

{|
|- style="background:#e0e0e0"
!Attribute
!Data type
!Description
|- style="background:#eeeeee"
|Name
|Discreet
|Song title
|-
|Artist
|Discreet
|Artist name
|- style="background:#eeeeee"
|Album
|Discreet
|Album name
|-
|Genre
|Nominal
|Genre the song belongs to
|- style="background:#eeeeee"
|Composer
|Discreet
|The composer of the song
|-
|Size
|Ordinal
|The file size
|- style="background:#eeeeee"
|Total time
|Ordinal
|The total time of the song
|-
|Disc number
|Ordinal
|Number of the disc
|- style="background:#eeeeee"
|Disc count
|Ordinal
|Total number of discs
|-
|Track number
|Ordinal
|Track number of this song on the disc
|- style="background:#eeeeee"
|Track count
|Ordinal
|Total number of tracks on the disc
|-
|Year
|Ordinal
|Year of origin
|- style="background:#eeeeee"
|Date Modified
|Ordinal
|Date of modification
|-
|Date added
|Ordinal
|Date when song was added to archive
|- style="background:#eeeeee"
|Bit rate
|Ordinal
|Bit rate of song (e.g. 128kbit/s)
|-
|Sample rate
|Ordinal
|Sample rate of song (e.g. 44100Hz)
|- style="background:#eeeeee"
|Play count
|Ordinal
|Number of time the song was played
|-
|Play date
|Ordinal
|Date of last play
|- style="background:#eeeeee"
|Play date UTC
|Ordinal
|Date of last play in [http://en.wikipedia.org/wiki/UTC UTC]
|-
|Location
|Discreet
|File location
|- style="background:#eeeeee"
|Kind
|Nominal
|Kind of file (e.g. MPEG audio file)
|-
|Rating
|Ordinal
|Personal rating (1-5 stars)
|}

One data record consists of a concatenation of attributes listed in the table above. Those attributes are all 1-dimensional. A data record contains only necessary attributes or attributes with data.

== Target Group Analysis ==

=== Who should use this visualation technique? ===

The visualisation of our concept is mainly designed for people collecting mp3s and musicians who like to use creative and new ways for finding songs to play in their music archive they won't find in the usual tools. Moreover it's for people who like to explore their music collection using different approaches. This will fit the exploring character of information visualisation.

Our visualisation will make it possible to browse through the music collection in different ways than what iTunes offers. It's meant for people who want to find music to play, e.g. songs they didn't listen to for a long time. They will see from which period the songs are, which genre they fall into and how they have been rated. This is a different starting point than usual approaches and will allow the user to potentially find other music than without it.

The people that will use our tool are familiar with the internet and use it quite often. Moreover they are using their computer a lot at home and have their pc or mac in the living room where it is not only used for work, but also as multimedia station. That means they play video, music and watch TV with their computer.

They are also interessted in music and they are buying the music from the internet and not buying the songs on a CD. If they buy a CD they rip the content on the pc to have it in their music library.

=== What are the special interests of our target group? ===

I think our target group is quite young, probably creative and I suppose they have some sort of interest in playing around with things a bit. As we are analysing iTunes the target group likes nice and neat design, cool tools, cool features and gimmicks. They should use the visualisation mainly for playing around with their music collection.

Our target group has more interesst in mp3s than they have in buying CDs and playing them from their CD player. They have all their music stored on their computer and want to have many possibilities to browse through their collection. They are looking for new ways of finding music so that they can listen to they music they like and the music they feel for in the moment. Instead of putting a CD into the HiFi set they want to see what they have in their collection that suits their mood.

=== Are there any known / often used Methods / Visualisation Techniques? ===

Up to now there are no real visualisation techniques in the area of music players like iTunes. The only visualisation techniques can be found at the playback time of a song, when the music itself is visualised.

For representing the Songs of a library ususally lists or tables are used. That means this is not a real graphic visualisation, it's just a representation of the data, that the user can read and use to make for example playlists. Especially in iTunes the possibilities of combining many ID3 attributes to get a playlist are vast. You can for example say you want only songs from 1980 to 1984, that are in the rock genre, that have a rating between 1 and 3 stars, and are not from Guns n' Roses. So you can do quite a lot of things with it, but there is no visualisation behind it. You can choose all that, but you can not choose it graphically which can make this much easier, faster, or just more interessting.

== Purpose of the Visualisation ==

=== What should be achieved with the Visualisation? ===

* a expressive and effective representation of the data records and contained information so that user can see with this visualization as fast as possible overview of the data and contained information.
* Exploration visualisation on the data record . Good presentation of information, because users can obtain information with visualisation better.
* semantic information from data
* Data condensation , so that complex information can be well observed.

=== Which tasks should be solved? ===

* current condition from information
* Visualization should be clear , Information is made more easily understandable.
* Data must be interpreted correct
* Information is explained by the best way user
* Restriction of the data . NOT "too much data , too little space".

=== Questions that can be solved using this Visualisation ===

* Which Jazz Songs of the 80's do I have in my archives, which I evaluated average?
* How many Songs do I have in Genre "Metal" in 2000 ?
* When did I play last "Shoot ME again" ?
* How often have I played Song "My World"?
* Which albums of Metallica do I have ?
* When was "Purify" created ?

----

* Which Jazz songs of the 80's do I have im my library, how have I evaluated them in average?
* How many songs of a Genre of a year do I have?
* How do I have them rated?
* Which albums do I have of a selected Genre and Year of publishing?
* Which songs are included on an album?

== Designproposal ==

=== Which kinds of Visualisation should be used? ===
The actually existing music library systems mostly don't really visualize the contained music using its attributes but simply use lists of items (artists, albums, songs, playlists...). While this concept is easily understandable for the end-user it only allows for simple browsing using the following techniques:

* Searching for specific artists, albums, titles and so on.
* Filtering the list by choosing ranges or values for some attributes
* Sorting the list by different attributes
* Scrolling the list up and down

Some attributes of song items like artist, album and title are of hierarchical character and therefore suited mainly for being displayed in a list or being used for browsing in multi-step lists. One example of such a multi-step list is the media library in Winamp (TODO: cite): After selecting an artist in the first list, the second list gets filled with the available albums of this artist. Selecting an album fills the next list with the associated songs of this album and so on.

TODO: list the different types of attributes!

While hierarchical attributes can be considered essential and are very useful for a multi-level selection process or direct textual searching/filtering, they only can be used if the user exactly knows what he or she wants to listen to. In opposite users often want to listen to randomly chosen or special pattern matching song lists like "My Top 10 Most Played Ones".

Considering these facts we chose other criteria than hierachical attributes of music items for creating new concepts of how to find interesting music without exactly knowning what to listen to. Using attributes like genre, year of creation, rating, playcount and date of last play different approaches of browsing music came up to our minds.

=== Visual Mapping ===
In the context of this task the "Music Type Selection" (TODO: find a superior name) browsing approach was chosen for being designed in detail and worked out as a prototype. This approach uses the following visual mapping:
* The approach bases on a 2D diagram containing:
** The year of creation on the x-axis
** The genre on the y-axis
Using this grid groups of similar music with respect to genre and year are getting plotted into the diagram as filled boxes. Additionally another two attributes are being mapped:
* The absolute number of songs within a specific group is mapped as the size of the box.
* The mean rating of all songs within this group is mapped as the intensity of the color used for filling the boxes.

=== Used Techniques / Applied Principles ===
TODO: this is a listing of used techniques only at the moment - detail and map to the implemented features
* Focus & Context: Tiled Multi-Level Browser (Slides 0, Page 16)
** Overview Window
** Zoomed Window
** Details On Demand Window
* Scatterplot + Color and Shape concept
* Dynamic Queries: live choosable sliders for attribute ranges (Slides 4, Page 8)
* Linking & Brushing: Detail window containing rating distribution of selected songs (Slides 0, Page 25)
* Visual Encoding: volume, color

=== Interaction ===

As you can see in our second [[Media:InfoVis_Gruppe10_Aufgabe3_Entwurf2.jpg|layout]] we have a multi windwow view. The starting point is in the big main window. In the beginning the other windows are empty. In the main part the user sees all the songs availible represented in boxes of different shade and size. It is possible to scale the x- and the y-axis to have a better overview, or to see the boxes larger. When he clicks at one of those boxes more detailed information will appear in the other windows. In the lower left window the user will see the different Artists that suited his selection. There will be one box for each artist containing all the albums of this artist that correspond with the users selection of genre and year. In the lower right window the user can see a more detailed view on the ratings of his selection. So the mean value is split up and one can see how many songs there are for each rating star. In the upper left window the first album of the first artist will be presented, showing the songs.

In the next step the user can interact in the three smaller windows to change the artist, the album, or choose only specific ratings. When the user clicks on a new album or artist the details in the upper right window will be updated. Moreover there is the possibility to choose only some of the ratings represented in the lower right window. For example only 4 to 5 stars. Then the songs in the upper right window will be updated correctly and only albums which contain songs with this rating will be shown in the lower left window.

=== Mockup(s) / Fake Screenshot(s) ===
[[Image:InfoVis_Gruppe10_Aufgabe3_Entwurf1.gif|none|thumb|500px|none|Entwurf 1]]
[[Image:InfoVis_Gruppe10_Aufgabe3_Entwurf2.jpg|none|thumb|561px|none|Entwurf 2]]

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 10 - Aufgabe 3 - Design

2005-11-22T21:31:26Z

UE-InfoVis0506 0027476: /* Who should use this visualation technique? */

== Application Area and given Dataset ==

=== Application Area Analysis ===

The application area for this task is to visualize a music archive with the data provided by ID3/iTunes tags. These tags include information such as songname, artist, year, album and so on. The challenge in visualizing this information is to select suitable attributes for being used in relation to each other because of the high number of discreet and "organizational" attributes.

=== Dataset Analysis ===

{|
|- style="background:#e0e0e0"
!Attribute
!Data type
!Description
|- style="background:#eeeeee"
|Name
|Discreet
|Song title
|-
|Artist
|Discreet
|Artist name
|- style="background:#eeeeee"
|Album
|Discreet
|Album name
|-
|Genre
|Nominal
|Genre the song belongs to
|- style="background:#eeeeee"
|Composer
|Discreet
|The composer of the song
|-
|Size
|Ordinal
|The file size
|- style="background:#eeeeee"
|Total time
|Ordinal
|The total time of the song
|-
|Disc number
|Ordinal
|Number of the disc
|- style="background:#eeeeee"
|Disc count
|Ordinal
|Total number of discs
|-
|Track number
|Ordinal
|Track number of this song on the disc
|- style="background:#eeeeee"
|Track count
|Ordinal
|Total number of tracks on the disc
|-
|Year
|Ordinal
|Year of origin
|- style="background:#eeeeee"
|Date Modified
|Ordinal
|Date of modification
|-
|Date added
|Ordinal
|Date when song was added to archive
|- style="background:#eeeeee"
|Bit rate
|Ordinal
|Bit rate of song (e.g. 128kbit/s)
|-
|Sample rate
|Ordinal
|Sample rate of song (e.g. 44100Hz)
|- style="background:#eeeeee"
|Play count
|Ordinal
|Number of time the song was played
|-
|Play date
|Ordinal
|Date of last play
|- style="background:#eeeeee"
|Play date UTC
|Ordinal
|Date of last play in [http://en.wikipedia.org/wiki/UTC UTC]
|-
|Location
|Discreet
|File location
|- style="background:#eeeeee"
|Kind
|Nominal
|Kind of file (e.g. MPEG audio file)
|-
|Rating
|Ordinal
|Personal rating (1-5 stars)
|}

One data record consists of a concatenation of attributes listed in the table above. Those attributes are all 1-dimensional. A data record contains only necessary attributes or attributes with data.

== Target Group Analysis ==

=== Who should use this visualation technique? ===

The visualisation of our concept is mainly designed for people collecting mp3s and musicians who like to use creative and new ways for finding songs to play in their music archive they won't find in the usual tools. Moreover it's for people who like to explore their music collection using different approaches. This will fit the exploring character of information visualisation.

Our visualisation will make it possible to browse through the music collection in different ways than what iTunes offers. It's meant for people who want to find music to play, e.g. songs they didn't listen to for a long time. They will see from which period the songs are, which genre they fall into and how they have been rated. This is a different starting point than usual approaches and will allow the user to probably find other music, than without the tool.

The people that will use our tool are familiar with the internet and use it quite often. Moreover they are using their computer a lot at home and have their pc or mac in the living room where it is not only used to work, but also as multimedia station. That means they play video, music and watch TV with their computer.

They are also interessted in music and they are buying the music from the internet and not buying the songs on a CD. If they buy a CD they rip the content on the pc to have it in their music library.

=== What are the special interests of our target group? ===

I think our target group is quite young, probably creative and I suppose they have some sort of interest in playing around with things a bit. As we are analysing iTunes the target group likes nice and neat design, cool tools, cool features and gimmicks. They should use the visualisation mainly for playing around with their music collection.

Our target group has more interesst in mp3s than they have in buying CDs and playing them from their CD player. They have all their music stored on their computer and want to have many possibilities to browse through their collection. They are looking for new ways of finding music so that they can listen to they music they like and the music they feel for in the moment. Instead of putting a CD into the HiFi set they want to see what they have in their collection that suits their mood.

=== Are there any known / often used Methods / Visualisation Techniques? ===

Up to now there are no real visualisation techniques in the area of music players like iTunes. The only visualisation techniques can be found at the playback time of a song, when the music itself is visualised.

For representing the Songs of a library ususally lists or tables are used. That means this is not a real graphic visualisation, it's just a representation of the data, that the user can read and use to make for example playlists. Especially in iTunes the possibilities of combining many ID3 attributes to get a playlist are vast. You can for example say you want only songs from 1980 to 1984, that are in the rock genre, that have a rating between 1 and 3 stars, and are not from Guns n' Roses. So you can do quite a lot of things with it, but there is no visualisation behind it. You can choose all that, but you can not choose it graphically which can make this much easier, faster, or just more interessting.

== Purpose of the Visualisation ==

=== What should be achieved with the Visualisation? ===

* a expressive and effective representation of the data records and contained information so that user can see with this visualization as fast as possible overview of the data and contained information.
* Exploration visualisation on the data record . Good presentation of information, because users can obtain information with visualisation better.
* semantic information from data
* Data condensation , so that complex information can be well observed.

=== Which tasks should be solved? ===

* current condition from information
* Visualization should be clear , Information is made more easily understandable.
* Data must be interpreted correct
* Information is explained by the best way user
* Restriction of the data . NOT "too much data , too little space".

=== Questions that can be solved using this Visualisation ===

* Which Jazz Songs of the 80's do I have in my archives, which I evaluated average?
* How many Songs do I have in Genre "Metal" in 2000 ?
* When did I play last "Shoot ME again" ?
* How often have I played Song "My World"?
* Which albums of Metallica do I have ?
* When was "Purify" created ?

== Designproposal ==

=== Which kinds of Visualisation should be used? ===
The actually existing music library systems mostly don't really visualize the contained music using its attributes but simply use lists of items (artists, albums, songs, playlists...). While this concept is easily understandable for the end-user it only allows for simple browsing using the following techniques:

* Searching for specific artists, albums, titles and so on.
* Filtering the list by choosing ranges or values for some attributes
* Sorting the list by different attributes
* Scrolling the list up and down

Some attributes of song items like artist, album and title are of hierarchical character and therefore suited mainly for being displayed in a list or being used for browsing in multi-step lists. One example of such a multi-step list is the media library in Winamp (TODO: cite): After selecting an artist in the first list, the second list gets filled with the available albums of this artist. Selecting an album fills the next list with the associated songs of this album and so on.

TODO: list the different types of attributes!

While hierarchical attributes can be considered essential and are very useful for a multi-level selection process or direct textual searching/filtering, they only can be used if the user exactly knows what he or she wants to listen to. In opposite users often want to listen to randomly chosen or special pattern matching song lists like "My Top 10 Most Played Ones".

Considering these facts we chose other criteria than hierachical attributes of music items for creating new concepts of how to find interesting music without exactly knowning what to listen to. Using attributes like genre, year of creation, rating, playcount and date of last play different approaches of browsing music came up to our minds.

=== Visual Mapping ===
In the context of this task the "Music Type Selection" (TODO: find a superior name) browsing approach was chosen for being designed in detail and worked out as a prototype. This approach uses the following visual mapping:
* The approach bases on a 2D diagram containing:
** The year of creation on the x-axis
** The genre on the y-axis
Using this grid groups of similar music with respect to genre and year are getting plotted into the diagram as filled boxes. Additionally another two attributes are being mapped:
* The absolute number of songs within a specific group is mapped as the size of the box.
* The mean rating of all songs within this group is mapped as the intensity of the color used for filling the boxes.

=== Used Techniques / Applied Principles ===
TODO: this is a listing of used techniques only at the moment - detail and map to the implemented features
* Focus & Context: Tiled Multi-Level Browser (Slides 0, Page 16)
** Overview Window
** Zoomed Window
** Details On Demand Window
* Scatterplot + Color and Shape concept
* Dynamic Queries: live choosable sliders for attribute ranges (Slides 4, Page 8)
* Linking & Brushing: Detail window containing rating distribution of selected songs (Slides 0, Page 25)
* Visual Encoding: volume, color

=== Interaction ===

As you can see in our second [[Media:InfoVis_Gruppe10_Aufgabe3_Entwurf2.jpg|layout]] we have a multi windwow view. The starting point is in the big main window. In the beginning the other windows are empty. In the main part the user sees all the songs availible represented in boxes of different shade and size. It is possible to scale the x- and the y-axis to have a better overview, or to see the boxes larger. When he clicks at one of those boxes more detailed information will appear in the other windows. In the lower left window the user will see the different Artists that suited his selection. There will be one box for each artist containing all the albums of this artist that correspond with the users selection of genre and year. In the lower right window the user can see a more detailed view on the ratings of his selection. So the mean value is split up and one can see how many songs there are for each rating star. In the upper left window the first album of the first artist will be presented, showing the songs.

In the next step the user can interact in the three smaller windows to change the artist, the album, or choose only specific ratings. When the user clicks on a new album or artist the details in the upper right window will be updated. Moreover there is the possibility to choose only some of the ratings represented in the lower right window. For example only 4 to 5 stars. Then the songs in the upper right window will be updated correctly and only albums which contain songs with this rating will be shown in the lower left window.

=== Mockup(s) / Fake Screenshot(s) ===
[[Image:InfoVis_Gruppe10_Aufgabe3_Entwurf1.gif|none|thumb|500px|none|Entwurf 1]]
[[Image:InfoVis_Gruppe10_Aufgabe3_Entwurf2.jpg|none|thumb|561px|none|Entwurf 2]]

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 10 - Aufgabe 3 - Design

2005-11-22T21:30:28Z

UE-InfoVis0506 0027476: /* Who should use this visualation technique? */

== Application Area and given Dataset ==

=== Application Area Analysis ===

The application area for this task is to visualize a music archive with the data provided by ID3/iTunes tags. These tags include information such as songname, artist, year, album and so on. The challenge in visualizing this information is to select suitable attributes for being used in relation to each other because of the high number of discreet and "organizational" attributes.

=== Dataset Analysis ===

{|
|- style="background:#e0e0e0"
!Attribute
!Data type
!Description
|- style="background:#eeeeee"
|Name
|Discreet
|Song title
|-
|Artist
|Discreet
|Artist name
|- style="background:#eeeeee"
|Album
|Discreet
|Album name
|-
|Genre
|Nominal
|Genre the song belongs to
|- style="background:#eeeeee"
|Composer
|Discreet
|The composer of the song
|-
|Size
|Ordinal
|The file size
|- style="background:#eeeeee"
|Total time
|Ordinal
|The total time of the song
|-
|Disc number
|Ordinal
|Number of the disc
|- style="background:#eeeeee"
|Disc count
|Ordinal
|Total number of discs
|-
|Track number
|Ordinal
|Track number of this song on the disc
|- style="background:#eeeeee"
|Track count
|Ordinal
|Total number of tracks on the disc
|-
|Year
|Ordinal
|Year of origin
|- style="background:#eeeeee"
|Date Modified
|Ordinal
|Date of modification
|-
|Date added
|Ordinal
|Date when song was added to archive
|- style="background:#eeeeee"
|Bit rate
|Ordinal
|Bit rate of song (e.g. 128kbit/s)
|-
|Sample rate
|Ordinal
|Sample rate of song (e.g. 44100Hz)
|- style="background:#eeeeee"
|Play count
|Ordinal
|Number of time the song was played
|-
|Play date
|Ordinal
|Date of last play
|- style="background:#eeeeee"
|Play date UTC
|Ordinal
|Date of last play in [http://en.wikipedia.org/wiki/UTC UTC]
|-
|Location
|Discreet
|File location
|- style="background:#eeeeee"
|Kind
|Nominal
|Kind of file (e.g. MPEG audio file)
|-
|Rating
|Ordinal
|Personal rating (1-5 stars)
|}

One data record consists of a concatenation of attributes listed in the table above. Those attributes are all 1-dimensional. A data record contains only necessary attributes or attributes with data.

== Target Group Analysis ==

=== Who should use this visualation technique? ===

The visualisation of our concept is mainly designed for people collecting mp3s and musicians who like to use creative and new ways for finding songs to play in their music archive they won't find in the usual tools. Moreover it's for people who like to explore their music collection using different approaches. This will fit the exploring character of information visualisation.

Our visualisation will make it possible to browse through the music collection in different ways than what iTunes offers. It's meant for people who want to find music to play, e.g. songs they didn't listen to for a long time. They will see from wich period the songs are, which genre they fall into and how they have been rated. This is a different starting point than usual and will allow the user to probably find other music, than without the tool.

The people that will use our tool are familiar with the internet and use it quite often. Moreover they are using their computer a lot at home and have their pc or mac in the living room where it is not only used to work, but also as multimedia station. That means they play video, music and watch TV with their computer.

They are also interessted in music and they are buying the music from the internet and not buying the songs on a CD. If they buy a CD they rip the content on the pc to have it in their music library.

=== What are the special interests of our target group? ===

I think our target group is quite young, probably creative and I suppose they have some sort of interest in playing around with things a bit. As we are analysing iTunes the target group likes nice and neat design, cool tools, cool features and gimmicks. They should use the visualisation mainly for playing around with their music collection.

Our target group has more interesst in mp3s than they have in buying CDs and playing them from their CD player. They have all their music stored on their computer and want to have many possibilities to browse through their collection. They are looking for new ways of finding music so that they can listen to they music they like and the music they feel for in the moment. Instead of putting a CD into the HiFi set they want to see what they have in their collection that suits their mood.

=== Are there any known / often used Methods / Visualisation Techniques? ===

Up to now there are no real visualisation techniques in the area of music players like iTunes. The only visualisation techniques can be found at the playback time of a song, when the music itself is visualised.

For representing the Songs of a library ususally lists or tables are used. That means this is not a real graphic visualisation, it's just a representation of the data, that the user can read and use to make for example playlists. Especially in iTunes the possibilities of combining many ID3 attributes to get a playlist are vast. You can for example say you want only songs from 1980 to 1984, that are in the rock genre, that have a rating between 1 and 3 stars, and are not from Guns n' Roses. So you can do quite a lot of things with it, but there is no visualisation behind it. You can choose all that, but you can not choose it graphically which can make this much easier, faster, or just more interessting.

== Purpose of the Visualisation ==

=== What should be achieved with the Visualisation? ===

* a expressive and effective representation of the data records and contained information so that user can see with this visualization as fast as possible overview of the data and contained information.
* Exploration visualisation on the data record . Good presentation of information, because users can obtain information with visualisation better.
* semantic information from data
* Data condensation , so that complex information can be well observed.

=== Which tasks should be solved? ===

* current condition from information
* Visualization should be clear , Information is made more easily understandable.
* Data must be interpreted correct
* Information is explained by the best way user
* Restriction of the data . NOT "too much data , too little space".

=== Questions that can be solved using this Visualisation ===

* Which Jazz Songs of the 80's do I have in my archives, which I evaluated average?
* How many Songs do I have in Genre "Metal" in 2000 ?
* When did I play last "Shoot ME again" ?
* How often have I played Song "My World"?
* Which albums of Metallica do I have ?
* When was "Purify" created ?

== Designproposal ==

=== Which kinds of Visualisation should be used? ===
The actually existing music library systems mostly don't really visualize the contained music using its attributes but simply use lists of items (artists, albums, songs, playlists...). While this concept is easily understandable for the end-user it only allows for simple browsing using the following techniques:

* Searching for specific artists, albums, titles and so on.
* Filtering the list by choosing ranges or values for some attributes
* Sorting the list by different attributes
* Scrolling the list up and down

Some attributes of song items like artist, album and title are of hierarchical character and therefore suited mainly for being displayed in a list or being used for browsing in multi-step lists. One example of such a multi-step list is the media library in Winamp (TODO: cite): After selecting an artist in the first list, the second list gets filled with the available albums of this artist. Selecting an album fills the next list with the associated songs of this album and so on.

TODO: list the different types of attributes!

While hierarchical attributes can be considered essential and are very useful for a multi-level selection process or direct textual searching/filtering, they only can be used if the user exactly knows what he or she wants to listen to. In opposite users often want to listen to randomly chosen or special pattern matching song lists like "My Top 10 Most Played Ones".

Considering these facts we chose other criteria than hierachical attributes of music items for creating new concepts of how to find interesting music without exactly knowning what to listen to. Using attributes like genre, year of creation, rating, playcount and date of last play different approaches of browsing music came up to our minds.

=== Visual Mapping ===
In the context of this task the "Music Type Selection" (TODO: find a superior name) browsing approach was chosen for being designed in detail and worked out as a prototype. This approach uses the following visual mapping:
* The approach bases on a 2D diagram containing:
** The year of creation on the x-axis
** The genre on the y-axis
Using this grid groups of similar music with respect to genre and year are getting plotted into the diagram as filled boxes. Additionally another two attributes are being mapped:
* The absolute number of songs within a specific group is mapped as the size of the box.
* The mean rating of all songs within this group is mapped as the intensity of the color used for filling the boxes.

=== Used Techniques / Applied Principles ===
TODO: this is a listing of used techniques only at the moment - detail and map to the implemented features
* Focus & Context: Tiled Multi-Level Browser (Slides 0, Page 16)
** Overview Window
** Zoomed Window
** Details On Demand Window
* Scatterplot + Color and Shape concept
* Dynamic Queries: live choosable sliders for attribute ranges (Slides 4, Page 8)
* Linking & Brushing: Detail window containing rating distribution of selected songs (Slides 0, Page 25)
* Visual Encoding: volume, color

=== Interaction ===

As you can see in our second [[Media:InfoVis_Gruppe10_Aufgabe3_Entwurf2.jpg|layout]] we have a multi windwow view. The starting point is in the big main window. In the beginning the other windows are empty. In the main part the user sees all the songs availible represented in boxes of different shade and size. It is possible to scale the x- and the y-axis to have a better overview, or to see the boxes larger. When he clicks at one of those boxes more detailed information will appear in the other windows. In the lower left window the user will see the different Artists that suited his selection. There will be one box for each artist containing all the albums of this artist that correspond with the users selection of genre and year. In the lower right window the user can see a more detailed view on the ratings of his selection. So the mean value is split up and one can see how many songs there are for each rating star. In the upper left window the first album of the first artist will be presented, showing the songs.

In the next step the user can interact in the three smaller windows to change the artist, the album, or choose only specific ratings. When the user clicks on a new album or artist the details in the upper right window will be updated. Moreover there is the possibility to choose only some of the ratings represented in the lower right window. For example only 4 to 5 stars. Then the songs in the upper right window will be updated correctly and only albums which contain songs with this rating will be shown in the lower left window.

=== Mockup(s) / Fake Screenshot(s) ===
[[Image:InfoVis_Gruppe10_Aufgabe3_Entwurf1.gif|none|thumb|500px|none|Entwurf 1]]
[[Image:InfoVis_Gruppe10_Aufgabe3_Entwurf2.jpg|none|thumb|561px|none|Entwurf 2]]

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 10 - Aufgabe 3 - Design

2005-11-22T21:27:35Z

UE-InfoVis0506 0027476: /* Application Area Analysis */

== Application Area and given Dataset ==

=== Application Area Analysis ===

The application area for this task is to visualize a music archive with the data provided by ID3/iTunes tags. These tags include information such as songname, artist, year, album and so on. The challenge in visualizing this information is to select suitable attributes for being used in relation to each other because of the high number of discreet and "organizational" attributes.

=== Dataset Analysis ===

{|
|- style="background:#e0e0e0"
!Attribute
!Data type
!Description
|- style="background:#eeeeee"
|Name
|Discreet
|Song title
|-
|Artist
|Discreet
|Artist name
|- style="background:#eeeeee"
|Album
|Discreet
|Album name
|-
|Genre
|Nominal
|Genre the song belongs to
|- style="background:#eeeeee"
|Composer
|Discreet
|The composer of the song
|-
|Size
|Ordinal
|The file size
|- style="background:#eeeeee"
|Total time
|Ordinal
|The total time of the song
|-
|Disc number
|Ordinal
|Number of the disc
|- style="background:#eeeeee"
|Disc count
|Ordinal
|Total number of discs
|-
|Track number
|Ordinal
|Track number of this song on the disc
|- style="background:#eeeeee"
|Track count
|Ordinal
|Total number of tracks on the disc
|-
|Year
|Ordinal
|Year of origin
|- style="background:#eeeeee"
|Date Modified
|Ordinal
|Date of modification
|-
|Date added
|Ordinal
|Date when song was added to archive
|- style="background:#eeeeee"
|Bit rate
|Ordinal
|Bit rate of song (e.g. 128kbit/s)
|-
|Sample rate
|Ordinal
|Sample rate of song (e.g. 44100Hz)
|- style="background:#eeeeee"
|Play count
|Ordinal
|Number of time the song was played
|-
|Play date
|Ordinal
|Date of last play
|- style="background:#eeeeee"
|Play date UTC
|Ordinal
|Date of last play in [http://en.wikipedia.org/wiki/UTC UTC]
|-
|Location
|Discreet
|File location
|- style="background:#eeeeee"
|Kind
|Nominal
|Kind of file (e.g. MPEG audio file)
|-
|Rating
|Ordinal
|Personal rating (1-5 stars)
|}

One data record consists of a concatenation of attributes listed in the table above. Those attributes are all 1-dimensional. A data record contains only necessary attributes or attributes with data.

== Target Group Analysis ==

=== Who should use this visualation technique? ===

The visualisation is mainly meant for people collecting mp3s or for musicians who like to see some nice information they won't find in the usual representations. Moreover it's for people who like to explore their music collection under different standpoints. This will fit the exploring character of information visualisation.

Our visualisation tool will make it possible to browse through the music collection in different ways than what iTunes offers. It's meant for people who want to find some music, they for example didn't listen to for a long time. They will see from wich period the songs are, which genre they fall into and how they have been rated. This is a different starting point than usual and will allow the user to probably find other music, than without the tool.

The people that will use our tool are familiar with the internet and use it quite often. Moreover they are using their computer a lot at home and have their pc or mac in the living room where it is not only used to work, but also as multimedia station. That means they play video, music and watch TV with their computer.

They are also interessted in music and they are buying the music from the internet and not buying the songs on a CD. If they buy a CD they rip the content on the pc to have it in their music library.

=== What are the special interests of our target group? ===

I think our target group is quite young, probably creative and I suppose they have some sort of interest in playing around with things a bit. As we are analysing iTunes the target group likes nice and neat design, cool tools, cool features and gimmicks. They should use the visualisation mainly for playing around with their music collection.

Our target group has more interesst in mp3s than they have in buying CDs and playing them from their CD player. They have all their music stored on their computer and want to have many possibilities to browse through their collection. They are looking for new ways of finding music so that they can listen to they music they like and the music they feel for in the moment. Instead of putting a CD into the HiFi set they want to see what they have in their collection that suits their mood.

=== Are there any known / often used Methods / Visualisation Techniques? ===

Up to now there are no real visualisation techniques in the area of music players like iTunes. The only visualisation techniques can be found at the playback time of a song, when the music itself is visualised.

For representing the Songs of a library ususally lists or tables are used. That means this is not a real graphic visualisation, it's just a representation of the data, that the user can read and use to make for example playlists. Especially in iTunes the possibilities of combining many ID3 attributes to get a playlist are vast. You can for example say you want only songs from 1980 to 1984, that are in the rock genre, that have a rating between 1 and 3 stars, and are not from Guns n' Roses. So you can do quite a lot of things with it, but there is no visualisation behind it. You can choose all that, but you can not choose it graphically which can make this much easier, faster, or just more interessting.

== Purpose of the Visualisation ==

=== What should be achieved with the Visualisation? ===

* a expressive and effective representation of the data records and contained information so that user can see with this visualization as fast as possible overview of the data and contained information.
* Exploration visualisation on the data record . Good presentation of information, because users can obtain information with visualisation better.
* semantic information from data
* Data condensation , so that complex information can be well observed.

=== Which tasks should be solved? ===

* current condition from information
* Visualization should be clear , Information is made more easily understandable.
* Data must be interpreted correct
* Information is explained by the best way user
* Restriction of the data . NOT "too much data , too little space".

=== Questions that can be solved using this Visualisation ===

* Which Jazz Songs of the 80's do I have in my archives, which I evaluated average?
* How many Songs do I have in Genre "Metal" in 2000 ?
* When did I play last "Shoot ME again" ?
* How often have I played Song "My World"?
* Which albums of Metallica do I have ?

== Designproposal ==

=== Which kinds of Visualisation should be used? ===
The actually existing music library systems mostly don't really visualize the contained music using its attributes but simply use lists of items (artists, albums, songs, playlists...). While this concept is easily understandable for the end-user it only allows for simple browsing using the following techniques:

* Searching for specific artists, albums, titles and so on.
* Filtering the list by choosing ranges or values for some attributes
* Sorting the list by different attributes
* Scrolling the list up and down

Some attributes of song items like artist, album and title are of hierarchical character and therefore suited mainly for being displayed in a list or being used for browsing in multi-step lists. One example of such a multi-step list is the media library in Winamp (TODO: cite): After selecting an artist in the first list, the second list gets filled with the available albums of this artist. Selecting an album fills the next list with the associated songs of this album and so on.

TODO: list the different types of attributes!

While hierarchical attributes can be considered essential and are very useful for a multi-level selection process or direct textual searching/filtering, they only can be used if the user exactly knows what he or she wants to listen to. In opposite users often want to listen to randomly chosen or special pattern matching song lists like "My Top 10 Most Played Ones".

Considering these facts we chose other criteria than hierachical attributes of music items for creating new concepts of how to find interesting music without exactly knowning what to listen to. Using attributes like genre, year of creation, rating, playcount and date of last play different approaches of browsing music came up to our minds.

=== Visual Mapping ===
In the context of this task the "Music Type Selection" (TODO: find a superior name) browsing approach was chosen for being designed in detail and worked out as a prototype. This approach uses the following visual mapping:
* The approach bases on a 2D diagram containing:
** The year of creation on the x-axis
** The genre on the y-axis
Using this grid groups of similar music with respect to genre and year are getting plotted into the diagram as filled boxes. Additionally another two attributes are being mapped:
* The absolute number of songs within a specific group is mapped as the size of the box.
* The mean rating of all songs within this group is mapped as the intensity of the color used for filling the boxes.

=== Used Techniques / Applied Principles ===
TODO: this is a listing of used techniques only at the moment - detail and map to the implemented features
* Focus & Context: Tiled Multi-Level Browser (Slides 0, Page 16)
** Overview Window
** Zoomed Window
** Details On Demand Window
* Scatterplot + Color and Shape concept
* Dynamic Queries: live choosable sliders for attribute ranges (Slides 4, Page 8)
* Linking & Brushing: Detail window containing rating distribution of selected songs (Slides 0, Page 25)
* Visual Encoding: volume, color

=== Interaction ===

As you can see in our second [[Media:InfoVis_Gruppe10_Aufgabe3_Entwurf2.jpg|layout]] we have a multi windwow view. The starting point is in the big main window. In the beginning the other windows are empty. In the main part the user sees all the songs availible represented in boxes of different shade and size. It is possible to scale the x- and the y-axis to have a better overview, or to see the boxes larger. When he clicks at one of those boxes more detailed information will appear in the other windows. In the lower left window the user will see the different Artists that suited his selection. There will be one box for each artist containing all the albums of this artist that correspond with the users selection of genre and year. In the lower right window the user can see a more detailed view on the ratings of his selection. So the mean value is split up and one can see how many songs there are for each rating star. In the upper left window the first album of the first artist will be presented, showing the songs.

In the next step the user can interact in the three smaller windows to change the artist, the album, or choose only specific ratings. When the user clicks on a new album or artist the details in the upper right window will be updated. Moreover there is the possibility to choose only some of the ratings represented in the lower right window. For example only 4 to 5 stars. Then the songs in the upper right window will be updated correctly and only albums which contain songs with this rating will be shown in the lower left window.

=== Mockup(s) / Fake Screenshot(s) ===
[[Image:InfoVis_Gruppe10_Aufgabe3_Entwurf1.gif|none|thumb|500px|none|Entwurf 1]]
[[Image:InfoVis_Gruppe10_Aufgabe3_Entwurf2.jpg|none|thumb|561px|none|Entwurf 2]]

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 10 - Aufgabe 3 - Design

2005-11-22T20:28:17Z

UE-InfoVis0506 0027476: /* Interaction */

== Application Area and given Dataset ==

=== Application Area Analysis ===

The application area for this task is to visualize a music archive with the data provided by ID3/iTunes tags. These tags include information about songname, artist, year, album,... The challenge in visualizing this information is to select "good" attributes that can be brought into relation, because of the high number of discreet and "organizational" attributes.

=== Dataset Analysis ===

{|
|- style="background:#e0e0e0"
!Attribute
!Data type
!Description
|- style="background:#eeeeee"
|Name
|Discreet
|Song title
|-
|Artist
|Discreet
|Artist name
|- style="background:#eeeeee"
|Album
|Discreet
|Album name
|-
|Genre
|Nominal
|Genre the song belongs to
|- style="background:#eeeeee"
|Composer
|Discreet
|The composer of the song
|-
|Size
|Ordinal
|The file size
|- style="background:#eeeeee"
|Total time
|Ordinal
|The total time of the song
|-
|Disc number
|Ordinal
|Number of the disc
|- style="background:#eeeeee"
|Disc count
|Ordinal
|Total number of discs
|-
|Track number
|Ordinal
|Track number of this song on the disc
|- style="background:#eeeeee"
|Track count
|Ordinal
|Total number of tracks on the disc
|-
|Year
|Ordinal
|Year of origin
|- style="background:#eeeeee"
|Date Modified
|Ordinal
|Date of modification
|-
|Date added
|Ordinal
|Date when song was added to archive
|- style="background:#eeeeee"
|Bit rate
|Ordinal
|Bit rate of song (e.g. 128kbit/s)
|-
|Sample rate
|Ordinal
|Sample rate of song (e.g. 44100Hz)
|- style="background:#eeeeee"
|Play count
|Ordinal
|Number of time the song was played
|-
|Play date
|Ordinal
|Date of last play
|- style="background:#eeeeee"
|Play date UTC
|Ordinal
|Date of last play in [http://en.wikipedia.org/wiki/UTC UTC]
|-
|Location
|Discreet
|File location
|- style="background:#eeeeee"
|Kind
|Nominal
|Kind of file (e.g. MPEG audio file)
|-
|Rating
|Ordinal
|Personal rating (1-5 stars)
|}

One data record consists of a concatenation of attributes listed in the table above. Those attributes are all 1-dimensional. A data record contains only necessary attributes or attributes with data.

== Target Group Analysis ==

=== Who should use this visualation technique? ===

The visualisation is mainly meant for people collecting mp3s or for musicians who like to see some nice information they won't find in the usual representations. Moreover it's for people who like to explore their music collection under different standpoints. This will fit the exploring character of information visualisation.

Our visualisation tool will make it possible to browse through the music collection in different ways than what iTunes offers. It's meant for people who want to find some music, they for example didn't listen to for a long time. They will see from wich period the songs are, which genre they fall into and how they have been rated. This is a different starting point than usual and will allow the user to probably find other music, than without the tool.

The people that will use our tool are familiar with the internet and use it quite often. Moreover they are using their computer a lot at home and have their pc or mac in the living room where it is not only used to work, but also as multimedia station. That means they play video, music and watch TV with their computer.

They are also interessted in music and they are buying the music from the internet and not buying the songs on a CD. If they buy a CD they rip the content on the pc to have it in their music library.

=== What are the special interests of our target group? ===

I think our target group is quite young, probably creative and I suppose they have some sort of interest in playing around with things a bit. As we are analysing iTunes the target group likes nice and neat design, cool tools, cool features and gimmicks. They should use the visualisation mainly for playing around with their music collection.

Our target group has more interesst in mp3s than they have in buying CDs and playing them from their CD player. They have all their music stored on their computer and want to have many possibilities to browse through their collection. They are looking for new ways of finding music so that they can listen to they music they like and the music they feel for in the moment. Instead of putting a CD into the HiFi set they want to see what they have in their collection that suits their mood.

=== Are there any known / often used Methods / Visualisation Techniques? ===

Up to now there are no real visualisation techniques in the area of music players like iTunes. The only visualisation techniques can be found at the playback time of a song, when the music itself is visualised.

For representing the Songs of a library ususally lists or tables are used. That means this is not a real graphic visualisation, it's just a representation of the data, that the user can read and use to make for example playlists. Especially in iTunes the possibilities of combining many ID3 attributes to get a playlist are vast. You can for example say you want only songs from 1980 to 1984, that are in the rock genre, that have a rating between 1 and 3 stars, and are not from Guns n' Roses. So you can do quite a lot of things with it, but there is no visualisation behind it. You can choose all that, but you can not choose it graphically which can make this much easier, faster, or just more interessting.

== Purpose of the Visualisation ==

=== What should be achieved with the Visualisation? ===

* a expressive and effective representation of the data records and contained information so that user can see with this visualization as fast as possible overview of the data and contained information.
* Exploration visualisation on the data record . Good presentation of information, because users can obtain information with visualisation better.
* semantic information from data
* Data condensation , so that complex information can be well observed.

=== Which tasks should be solved? ===

* current condition from information
* Visualization should be clear , Information is made more easily understandable.
* Data must be interpreted correct
* Information is explained by the best way user
* Restriction of the data . NOT "too much data , too little space".

=== Questions that can be solved using this Visualisation ===

* Is there a certain structure classification of the data?
* Are Information understandable?
* Are Information clarified essential?
* Is Color used purposefully ?

== Designproposal ==

=== Which kinds of Visualisation should be used? ===
The actually existing music library systems mostly don't really visualize the contained music using its attributes but simply use lists of items (artists, albums, songs, playlists...). While this concept is easily understandable for the end-user it only allows for simple browsing using the following techniques:

* Searching for specific artists, albums, titles and so on.
* Filtering the list by choosing ranges or values for some attributes
* Sorting the list by different attributes
* Scrolling the list up and down

Some attributes of song items like artist, album and title are of hierarchical character and therefore suited mainly for being displayed in a list or being used for browsing in multi-step lists. One example of such a multi-step list is the media library in Winamp (TODO: cite): After selecting an artist in the first list, the second list gets filled with the available albums of this artist. Selecting an album fills the next list with the associated songs of this album and so on.

TODO: list the different types of attributes!

While hierarchical attributes can be considered essential and are very useful for a multi-level selection process or direct textual searching/filtering, they only can be used if the user exactly knows what he or she wants to listen to. In opposite users often want to listen to randomly chosen or special pattern matching song lists like "My Top 10 Most Played Ones".

Considering these facts we chose other criteria than hierachical attributes of music items for creating new concepts of how to find interesting music without exactly knowning what to listen to. Using attributes like genre, year of creation, rating, playcount and date of last play different approaches of browsing music came up to our minds.

=== Visual Mapping ===
In the context of this task the "Music Type Selection" (TODO: find a superior name) browsing approach was chosen for being designed in detail and worked out as a prototype. This approach uses the following visual mapping:
* The approach bases on a 2D diagram containing:
** The year of creation on the x-axis
** The genre on the y-axis
Using this grid groups of similar music with respect to genre and year are getting plotted into the diagram as filled boxes. Additionally another two attributes are being mapped:
* The absolute number of songs within a specific group is mapped as the size of the box.
* The mean rating of all songs within this group is mapped as the intensity of the color used for filling the boxes.

=== Used Techniques / Applied Principles ===
TODO: this is a listing of used techniques only at the moment - detail and map to the implemented features
* Focus & Context: Tiled Multi-Level Browser (Slides 0, Page 16)
** Overview Window
** Zoomed Window
** Details On Demand Window
* Scatterplot + Color and Shape concept
* Dynamic Queries: live choosable sliders for attribute ranges (Slides 4, Page 8)
* Linking & Brushing: Detail window containing rating distribution of selected songs (Slides 0, Page 25)
* Visual Encoding: volume, color

=== Interaction ===

As you can see in our second [[Media:InfoVis_Gruppe10_Aufgabe3_Entwurf2.jpg|layout]] we have a multi windwow view. The starting point is in the big main window. In the beginning the other windwos are empty. In the main part the user sees all the songs availible represented in boxes of different shade and size. It is possible to scale the x- and the y-axis to have a better overview, or to see the boxes larger. When he clicks at one of those boxes more detailed information will appear in the other windows. In the lower left window the user will see the different Artists that suited his selection. There will be one box for each artist containing all the albums of this artist that correspond with the users selection of genre and year. In the lower right window the user can see a more detailed view on the ratings of his selection. So the mean value is split up and one can see how many songs there are for each rating star. In the upper left window the first album of the first artist will be presented, showing the songs.

In the next step the user can interact in the three smaller windows to change the artist, the album, or choose only specific ratings. When the user clicks on a new album or artist the details in the upper right window will be updated. Moreover there is the possibility to choose only some of the ratings represented in the lower right window. For example only 4 to 5 stars. Then the songs in the upper right window will be updated correctly and only albums which contain songs with this rating will be shown in the lower left window.

=== Mockup(s) / Fake Screenshot(s) ===
[[Image:InfoVis_Gruppe10_Aufgabe3_Entwurf1.gif|none|thumb|500px|none|Entwurf 1]]
[[Image:InfoVis_Gruppe10_Aufgabe3_Entwurf2.jpg|none|thumb|561px|none|Entwurf 2]]

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 10 - Aufgabe 3 - Design

2005-11-21T09:05:21Z

UE-InfoVis0506 0027476: /* Which kinds of Visualisation should be used? */

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 10 - Aufgabe 3 - Design

2005-11-21T07:30:20Z

UE-InfoVis0506 0027476: /* Mockup(s) / Fake Screenshot(s) */

File:InfoVis Gruppe10 Aufgabe3 Entwurf2.jpg

2005-11-21T07:29:46Z

UE-InfoVis0506 0027476: New concept for the genre/year visualisation

== Summary ==
New concept for the genre/year visualisation
== Copyright status ==
Open Source
== Source ==
Stefan Kals, Gruppe 10

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 10 - Aufgabe 3 - Design

2005-11-16T19:04:02Z

UE-InfoVis0506 0027476: /* Mockup(s) / Fake Screenshot(s) */

== Application Area and given Dataset ==

=== Application Area Analysis ===

=== Dataset Analysis ===

* Name:
* Artist:
* Composer:
* Album:
* Genre:
* Kind:
* Size:
* Total Time:
* Disc Number:
* Disc Count:
* Track Number:
* Track Count:
* Year:
* Date Modified:
* Date Added:
* Bit Rate:
* Sample Rate:
* Play Count:
* Play Date:
* Play Date UTC:
* Location:
* File Folder Count:
* Library Folder Count:

== Target Group Analysis ==

=== Who should use this visualation technique? ===

The visualisation is mainly meant for people collecting mp3s or for musicians who like to see some nice information they won't find in the usual representations. Moreover it's for people who like to explore their music collection under different standpoints. This will fit the exploring character of information visualisation.

=== What are the special interests of our target group? ===

I think our target group is quite young, probably creative and I suppose they have some sort of interest in playing around with things a bit. As we are analysing iTunes the target group likes nice and neat design, cool tools, cool features and gimmicks. They should use the visualisation mainly for playing around with their music collection.

=== Are there any known / often used Methods / Visualisationtechniques? ===

== Purpose of the Visualisation ==

=== What should be achieved with the Visualisation? ===

=== Which tasks should be solved? ===

Warum haben wir nur wenige Datensätze heraus genommen?

=== Questions that can be solved using this Visualisation ===

== Designproposal ==

=== Which kinds of Visualisation should be used? ===

=== Visual Mapping ===

=== Used Techniques / Applied Principles ===

=== Interaction ===

=== Mockup(s) / Fake Screenshot(s) ===
[[Image:InfoVis_Gruppe10_Aufgabe3_Entwurf1.gif|none|thumb|600px|none|Entwurf 1]]

File:InfoVis Gruppe10 Aufgabe3 Entwurf1.gif

2005-11-16T19:03:20Z

UE-InfoVis0506 0027476: Entwurf 1 "Screenshot"

== Summary ==
Entwurf 1 "Screenshot"
== Copyright status ==
Open Source
== Source ==
Stefan Kals, Gruppe 10

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 10 - Aufgabe 2

2005-11-03T21:29:03Z

UE-InfoVis0506 0027476: /* Preattentive Processing */

== Poor Graphic ==
[[Image:Friendly02doctors.gif|none|thumb|413px|Incomes of Doctors Vs. Other Professionals]]

== Drawbacks ==

The first step in the process of creating a better version of the provided graphic was the detailed analysis of the graphic and its drawbacks considering the discussed design principles.

=== [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G3 - Aufgabe 1 - Preattentive Processing|Preattentive Processing]] ===

Through the very bad Data-Ink-Ratio and lot of Chart Junk the Preattentive Processing [Healey et al., 1996] is heavily affected:

* The embedded bodies/heads of doctors and other professionals distract the viewer's eyes from the main information. Thus it is hard for the first-time viewer to quickly understand the information content of the diagram.

* The descriptions of the both data samples (Office-based nonsalaried physicians versus Male professional technical and kindred workers) are not clearly placed in the graphics and cannot be preattentively associated to the data series.

* Especially the data series of the technical workers is not really presented by clear data bars because of the worker pictures on top using the same color as the bars (both black). Thus the different salary values can optically not clearely be compared against each other.

=== [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G4 - Aufgabe 1 - Lie Factor|Lie Factor]] ===

Edward Tufte states the principle that "The representation of numbers, as physically measured on the surface of the graphic itself, should be directly proportional to the quantities represented" [Tufte, 1991]

This principle is definitly violated in the provided graphic because of the following facts:

* The provided original graphic heavily uses changes in the continuity of the time scale. While in the beginning of the time scale jumps of up to 8-9 years occur between two salary values, the last five salary values differ only by 1 year anymore.

* As seen in the redesigned graphic using a linear time-scale the original graphic uses the Lie Factor to hide the fact that the distributions of the salaries are exponential not nearly linear as the viewer guesses by looking at the original graphic.

* By changing the time scale multiple times within the same diagram, the viewer is confused and is potentially not able to directly discover the lie.

=== [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G8 - Aufgabe 1 - Chart Junk|Chart Junk]] ===

Edward Tufte comments the principle of Chart Junk as follows: "The interior decoration of graphics generates a lot of ink which does not tell the viewer anything new." [Tufte, 1991]

The provided graphic does contain a lot of ink not telling the viewer anything new:

* The embedded stilistic pictures of doctors and other professionals are really unnecessary Chart Junk.

* The time scale is labeled with full year marks. This can be reduced to only using the last two digits as the first two ones don't change over the whole time-scale.

* The black background of the technical workers data series is making it more difficult for the viewer to recognize the presented information.

=== [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 01 - Aufgabe 1 - Data-Ink Ratio|Data-Ink Ratio]] ===

* A lot of color is used just for separating the two data series from each other.

* As mentioned above, the stilistic pictures of doctors and other professionals add a high amount of ink to the diagram which do not contain much additional information.

=== [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 09 - Aufgabe 1 - Color Coding / Color|Color Coding / Color]] ===

* The use of few colors for clearly separating the different data series within the same diagram makes sense. The provided graphic uses black and white for the two data series which results in a graphic with high contrast. The drawback of this approach is that the viewer is distracted from recognizing the main content information to the contrast spots which do not contain the real information.

=== [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 01 - Aufgabe 1 - Aesthetic-Usability Effect|Aesthetic-Usability Effect]] ===

Donny Truong describes the Aesthetic-Usability Effect as follows: "Aesthetic designs are perceived as easier to use than less-aesthetic designs. Aesthetic designs also foster positive relationships with people, making them more tolerant of problems with a design." [Truong, 2005]

The following comments on the provided graphic affect this effect:

* The heavy use of Chart Junk and the high Lie Factor lead to a diagram with a low usability.

* By using only black & white as "colors", the recognition of the information content is complicated for the viewer and directly degrades the aestetic approach of the graphic.

== Improvements ==

* A linear time scale was used to provide a clear basis for understanding the information content of the diagram to the viewer.

* Through the use of a linear time scale the non-linear but exponential growth of the salaries were presented to the viewer.

* Additional usage of a line chart leads to a better visualisation of the higher growth of doctors salary.

* Removal of the Chart Junk (mainly the pictures of doctors and other professionals and 4-digit years) which results in a better data-ink-ratio.

* Grouping of the legend into a single block for providing the viewer with better understandable and quicker recognizable data series association.

* Adding a y-axis scale on both sides for fast salary estimation within the diagram because of the high width of the new graphic.

* Improval of the Aesthetic-Usability Effect due to usage of two easily distinguishable colors.

== Redesigned Graphic ==
[[Image:Diagramm 02.png|none|thumb|600px|none|Redesigned Graphic]]

= Resources =

[Healey et al., 1996] Christopher G. Healey, Kellog S. Booth and James T. Enns. High-Speed Visual Estimation Using Preattentive Processing. The University of British Columbia, June 1996. http://www.csc.ncsu.edu/faculty/healey/download/tochi.96.pdf

[Tufte, 1991] Edward Tufte, ''The Visual Display of Quantitative Information'', Second Edition, Graphics Press, USA, 1991.

[Truong, 2005] Donny Truong, ''Universal Principles of design''. Access Date: 3. November 2005
http://www.visualgui.com/index.php?p=1

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 10 - Aufgabe 2

2005-11-03T21:28:56Z

UE-InfoVis0506 0027476: /* Resources */

== Poor Graphic ==
[[Image:Friendly02doctors.gif|none|thumb|413px|Incomes of Doctors Vs. Other Professionals]]

== Drawbacks ==

The first step in the process of creating a better version of the provided graphic was the detailed analysis of the graphic and its drawbacks considering the discussed design principles.

=== [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G3 - Aufgabe 1 - Preattentive Processing|Preattentive Processing]] ===

Through the very bad Data-Ink-Ratio and lot of Chart Junk the Preattentive Processing [Healey et al., 2005] is heavily affected:

* The embedded bodies/heads of doctors and other professionals distract the viewer's eyes from the main information. Thus it is hard for the first-time viewer to quickly understand the information content of the diagram.

* The descriptions of the both data samples (Office-based nonsalaried physicians versus Male professional technical and kindred workers) are not clearly placed in the graphics and cannot be preattentively associated to the data series.

* Especially the data series of the technical workers is not really presented by clear data bars because of the worker pictures on top using the same color as the bars (both black). Thus the different salary values can optically not clearely be compared against each other.

=== [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G4 - Aufgabe 1 - Lie Factor|Lie Factor]] ===

Edward Tufte states the principle that "The representation of numbers, as physically measured on the surface of the graphic itself, should be directly proportional to the quantities represented" [Tufte, 1991]

This principle is definitly violated in the provided graphic because of the following facts:

* The provided original graphic heavily uses changes in the continuity of the time scale. While in the beginning of the time scale jumps of up to 8-9 years occur between two salary values, the last five salary values differ only by 1 year anymore.

* As seen in the redesigned graphic using a linear time-scale the original graphic uses the Lie Factor to hide the fact that the distributions of the salaries are exponential not nearly linear as the viewer guesses by looking at the original graphic.

* By changing the time scale multiple times within the same diagram, the viewer is confused and is potentially not able to directly discover the lie.

=== [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G8 - Aufgabe 1 - Chart Junk|Chart Junk]] ===

Edward Tufte comments the principle of Chart Junk as follows: "The interior decoration of graphics generates a lot of ink which does not tell the viewer anything new." [Tufte, 1991]

The provided graphic does contain a lot of ink not telling the viewer anything new:

* The embedded stilistic pictures of doctors and other professionals are really unnecessary Chart Junk.

* The time scale is labeled with full year marks. This can be reduced to only using the last two digits as the first two ones don't change over the whole time-scale.

* The black background of the technical workers data series is making it more difficult for the viewer to recognize the presented information.

=== [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 01 - Aufgabe 1 - Data-Ink Ratio|Data-Ink Ratio]] ===

* A lot of color is used just for separating the two data series from each other.

* As mentioned above, the stilistic pictures of doctors and other professionals add a high amount of ink to the diagram which do not contain much additional information.

=== [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 09 - Aufgabe 1 - Color Coding / Color|Color Coding / Color]] ===

* The use of few colors for clearly separating the different data series within the same diagram makes sense. The provided graphic uses black and white for the two data series which results in a graphic with high contrast. The drawback of this approach is that the viewer is distracted from recognizing the main content information to the contrast spots which do not contain the real information.

=== [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 01 - Aufgabe 1 - Aesthetic-Usability Effect|Aesthetic-Usability Effect]] ===

Donny Truong describes the Aesthetic-Usability Effect as follows: "Aesthetic designs are perceived as easier to use than less-aesthetic designs. Aesthetic designs also foster positive relationships with people, making them more tolerant of problems with a design." [Truong, 2005]

The following comments on the provided graphic affect this effect:

* The heavy use of Chart Junk and the high Lie Factor lead to a diagram with a low usability.

* By using only black & white as "colors", the recognition of the information content is complicated for the viewer and directly degrades the aestetic approach of the graphic.

== Improvements ==

* A linear time scale was used to provide a clear basis for understanding the information content of the diagram to the viewer.

* Through the use of a linear time scale the non-linear but exponential growth of the salaries were presented to the viewer.

* Additional usage of a line chart leads to a better visualisation of the higher growth of doctors salary.

* Removal of the Chart Junk (mainly the pictures of doctors and other professionals and 4-digit years) which results in a better data-ink-ratio.

* Grouping of the legend into a single block for providing the viewer with better understandable and quicker recognizable data series association.

* Adding a y-axis scale on both sides for fast salary estimation within the diagram because of the high width of the new graphic.

* Improval of the Aesthetic-Usability Effect due to usage of two easily distinguishable colors.

== Redesigned Graphic ==
[[Image:Diagramm 02.png|none|thumb|600px|none|Redesigned Graphic]]

= Resources =

[Healey et al., 1996] Christopher G. Healey, Kellog S. Booth and James T. Enns. High-Speed Visual Estimation Using Preattentive Processing. The University of British Columbia, June 1996. http://www.csc.ncsu.edu/faculty/healey/download/tochi.96.pdf

[Tufte, 1991] Edward Tufte, ''The Visual Display of Quantitative Information'', Second Edition, Graphics Press, USA, 1991.

[Truong, 2005] Donny Truong, ''Universal Principles of design''. Access Date: 3. November 2005
http://www.visualgui.com/index.php?p=1

Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 10 - Aufgabe 2

2005-11-03T21:28:35Z

UE-InfoVis0506 0027476: /* Resources */

== Poor Graphic ==
[[Image:Friendly02doctors.gif|none|thumb|413px|Incomes of Doctors Vs. Other Professionals]]

== Drawbacks ==

The first step in the process of creating a better version of the provided graphic was the detailed analysis of the graphic and its drawbacks considering the discussed design principles.

=== [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G3 - Aufgabe 1 - Preattentive Processing|Preattentive Processing]] ===

Through the very bad Data-Ink-Ratio and lot of Chart Junk the Preattentive Processing [Healey et al., 2005] is heavily affected:

* The embedded bodies/heads of doctors and other professionals distract the viewer's eyes from the main information. Thus it is hard for the first-time viewer to quickly understand the information content of the diagram.

* The descriptions of the both data samples (Office-based nonsalaried physicians versus Male professional technical and kindred workers) are not clearly placed in the graphics and cannot be preattentively associated to the data series.

* Especially the data series of the technical workers is not really presented by clear data bars because of the worker pictures on top using the same color as the bars (both black). Thus the different salary values can optically not clearely be compared against each other.

=== [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G4 - Aufgabe 1 - Lie Factor|Lie Factor]] ===

Edward Tufte states the principle that "The representation of numbers, as physically measured on the surface of the graphic itself, should be directly proportional to the quantities represented" [Tufte, 1991]

This principle is definitly violated in the provided graphic because of the following facts:

* The provided original graphic heavily uses changes in the continuity of the time scale. While in the beginning of the time scale jumps of up to 8-9 years occur between two salary values, the last five salary values differ only by 1 year anymore.

* As seen in the redesigned graphic using a linear time-scale the original graphic uses the Lie Factor to hide the fact that the distributions of the salaries are exponential not nearly linear as the viewer guesses by looking at the original graphic.

* By changing the time scale multiple times within the same diagram, the viewer is confused and is potentially not able to directly discover the lie.

=== [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G8 - Aufgabe 1 - Chart Junk|Chart Junk]] ===

Edward Tufte comments the principle of Chart Junk as follows: "The interior decoration of graphics generates a lot of ink which does not tell the viewer anything new." [Tufte, 1991]

The provided graphic does contain a lot of ink not telling the viewer anything new:

* The embedded stilistic pictures of doctors and other professionals are really unnecessary Chart Junk.

* The time scale is labeled with full year marks. This can be reduced to only using the last two digits as the first two ones don't change over the whole time-scale.

* The black background of the technical workers data series is making it more difficult for the viewer to recognize the presented information.

=== [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 01 - Aufgabe 1 - Data-Ink Ratio|Data-Ink Ratio]] ===

* A lot of color is used just for separating the two data series from each other.

* As mentioned above, the stilistic pictures of doctors and other professionals add a high amount of ink to the diagram which do not contain much additional information.

=== [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 09 - Aufgabe 1 - Color Coding / Color|Color Coding / Color]] ===

* The use of few colors for clearly separating the different data series within the same diagram makes sense. The provided graphic uses black and white for the two data series which results in a graphic with high contrast. The drawback of this approach is that the viewer is distracted from recognizing the main content information to the contrast spots which do not contain the real information.

=== [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 01 - Aufgabe 1 - Aesthetic-Usability Effect|Aesthetic-Usability Effect]] ===

Donny Truong describes the Aesthetic-Usability Effect as follows: "Aesthetic designs are perceived as easier to use than less-aesthetic designs. Aesthetic designs also foster positive relationships with people, making them more tolerant of problems with a design." [Truong, 2005]

The following comments on the provided graphic affect this effect:

* The heavy use of Chart Junk and the high Lie Factor lead to a diagram with a low usability.

* By using only black & white as "colors", the recognition of the information content is complicated for the viewer and directly degrades the aestetic approach of the graphic.

== Improvements ==

* A linear time scale was used to provide a clear basis for understanding the information content of the diagram to the viewer.

* Through the use of a linear time scale the non-linear but exponential growth of the salaries were presented to the viewer.

* Additional usage of a line chart leads to a better visualisation of the higher growth of doctors salary.

* Removal of the Chart Junk (mainly the pictures of doctors and other professionals and 4-digit years) which results in a better data-ink-ratio.

* Grouping of the legend into a single block for providing the viewer with better understandable and quicker recognizable data series association.

* Adding a y-axis scale on both sides for fast salary estimation within the diagram because of the high width of the new graphic.

* Improval of the Aesthetic-Usability Effect due to usage of two easily distinguishable colors.

== Redesigned Graphic ==
[[Image:Diagramm 02.png|none|thumb|600px|none|Redesigned Graphic]]

= Resources =

[Healey et al., 2005] Christopher G. Healey, Kellog S. Booth and James T. Enns. High-Speed Visual Estimation Using Preattentive Processing. The University of British Columbia, June 1996. http://www.csc.ncsu.edu/faculty/healey/download/tochi.96.pdf

[Tufte, 1991] Edward Tufte, ''The Visual Display of Quantitative Information'', Second Edition, Graphics Press, USA, 1991.

[Truong, 2005] Donny Truong, ''Universal Principles of design''. Access Date: 3. November 2005
http://www.visualgui.com/index.php?p=1

File:Grid based audi-small.jpg

2005-11-03T20:05:54Z

UE-InfoVis0506 0027476: /* Source */

== Summary ==
An exemplary grid based web page layout using a clear structured navigation and grouped image and text blocks.
== Copyright status ==
Audi (Nederland), http://www.audi.nl
== Source ==

[Welie, 2005] Martijn van Welie, Patterns in Interaction Design, Retrieved at October 25, 2005. http://www.welie.com

File:Grid based abn-small.jpg

2005-11-03T20:05:41Z

UE-InfoVis0506 0027476: /* Source */

== Summary ==
In this example from the Abn-Amro shop you can see a not strict modular grid, but a grid defining some columns, margins and horizontal evenly spaced guides.
== Copyright status ==

== Source ==

[Welie, 2005] Martijn van Welie, Patterns in Interaction Design, Retrieved at October 25, 2005. http://www.welie.com

File:Cover-fall-2003-lg.gif

2005-11-03T20:05:07Z

UE-InfoVis0506 0027476: /* Source */

== Summary ==
The Cover of the Carleton Univerity Magazine which illustrates the ''Grid Based Layout''.

== Source ==

[Carleton, 2003] Cover of Carleton University magazine. Retrieved at: October 24, 2005.
http://magazine.carleton.ca/2003_Fall/1154.htm

File:Grid based hinum1.gif

2005-11-03T20:04:25Z

UE-InfoVis0506 0027476: /* Source */

== Summary ==
Two examples for grid based design. The upper images are the grid designs, the lower images show the resulting layout.

== Copyright status ==

== Source ==

[Hinum, 2004] Klaus Hinum, Master's Thesis about Human centred Design for Graphical User Interfaces, February 2004.

File:Sechs1.png

2005-11-03T20:03:50Z

UE-InfoVis0506 0027476: /* Source */

== Summary ==

== Copyright status ==

== Source ==

[Phillips, 2005] Richard Phillips, Retrieved at October 29, 2005. http://richardphillips.org.uk/maps/symbols.html#ge

File:Fünfte1.png

2005-11-03T20:03:41Z

UE-InfoVis0506 0027476: /* Source */

== Summary ==

== Copyright status ==

== Source ==

[Phillips, 2005] Richard Phillips, Retrieved at October 29, 2005. http://richardphillips.org.uk/maps/symbols.html#ge

File:Vierte1.png

2005-11-03T20:03:35Z

UE-InfoVis0506 0027476: /* Source */

== Summary ==

== Copyright status ==

== Source ==

[Phillips, 2005] Richard Phillips, Retrieved at October 29, 2005. http://richardphillips.org.uk/maps/symbols.html#ge

File:Dritte1.png

2005-11-03T20:03:29Z

UE-InfoVis0506 0027476: /* Source */

== Summary ==

== Copyright status ==

== Source ==

[Phillips, 2005] Richard Phillips, Retrieved at October 29, 2005. http://richardphillips.org.uk/maps/symbols.html#ge

File:Zweite1.png

2005-11-03T20:03:23Z

UE-InfoVis0506 0027476: /* Source */

== Summary ==

== Copyright status ==

== Source ==

[Phillips, 2005] Richard Phillips, Retrieved at October 29, 2005. http://richardphillips.org.uk/maps/symbols.html#ge