InfoVis:Wiki - User contributions [en]

Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 06 - Aufgabe 4

2010-01-27T23:14:10Z

UE-InfoVis0910 0507049:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/infovis_ue_aufgabe4.html Beschreibung der Aufgabe 4]
=== Zu erstellende Visualisierung ===
-------------------------------
* Stammbaum der Nachkommen von Lisa und Bart Simpson*

...Visualisierung der Nachkommen von Lisa Simpson sowie der Nachkommen von Bart Simpson. Dabei sollen zwei Stammbäume entstehen - einer von Bart und einer von Lisa - die dann miteinander verglichen werden können. Zuerst kommen Lisa und Bart, dann deren Kinder, ihre Enkel, etc. (mind 4 Generationen). Da es noch keine Nachkommen gibt, können diese frei erfunden werden.

Die Visualisierung soll folgende Informationen darstellen:

- Verwandtschaftsverhältnisse (zumindest Eltern-Kinder),

- Unterscheidung zwischen Blutsverwandtschaft und angeheirateten Familienmitgliedern,

- Geburts- und Todestag sowie Lebensdauer von allen Familienmitgliedern,

- wichtige Ereignisse im Leben jedes Familienmitglieds (z.B., Anzeigen, Gefängnisaufenthalte, Schulzeit, Studienzeit, Nobelpreise, Arbeitslosigkeit etc.)

- Zufriedenheit jedes Familienmitglieds (Skala: sehr niedrig - niedrig - mittel - hoch - sehr hoch); kann sich im Laufe des Lebens ändern.

Die Visualisierung soll die interaktive Auseinandersetzung mit den Daten ermöglichen.
Verpflichtend:
Möglichkeiten zum besseren Vergleich von einzelnen Abschnitten der Stammbäume bzw. Vergleich von Ausschnitten aus Lisas und Barts Stammbäumen.
+ mind. 2 weitere Interaktionsmöglichkeiten (z.B., Details on Demand, Filteroptionen)

Allgemein:

- Die Daten sollen zur Analyse von Zusammenhängen zwischen Familienverhältnissen, wichtigen Ereignissen und Zufriedenheit visualisiert werden (die Anwendungsgebiets- und Zielgruppenanalyse kann kurz gehalten werden).

- Die bisher erlernten Design-Prinzipien sollen umgesetzt werden z.B.: Optimierung der Data-ink ratio (keine Comics!), visuelle Attribute (Größe, Farbe, Position, etc.) sollen sinnvoll eingesetzt werden (Information darstellen).

- Die Mockups sollten zumindest 1) die beiden Stammbäume im Überblick und 2) eine detaillierte Vergleichsansicht von 2 Teil-Stammbäumen wiedergeben.

- Alle nicht angeführten Daten können frei erfunden werden.

------------------------------

== analysis ==

=== application area ===
This graph is about family-tree visualization, where parents-children connections should be shown. It should not just be about family relations, but also be about individual happenings and feelings. The family tree should visualize hierarchical structures.
As already mentioned the tree should not only contain family relations, but also individual content and most important is, that the tree should be interactive:
* show detail information of a person, if demanded
* enable detailed comparisons of a section

=== dataset ===

* Sex is a nominal data because it cannot be ordered in a meaningful way. Both genders are equivalent. Additionally, the gender is a binary value (being male or female).
* The date of birth and death are ordinal values, because of the chronological order. In reality continual, we simplified the modelling by leaving out the time of birth. So are only discrete values are possible.
* The contentedness of a person is a discrete value, there are three different values possible (good, neutral, bad). It is 2-dimensional, because the contentedness is dependent on the time (what makes it temporal too) and of the value (good, bad, neutral).
* Important happenings are temporal, because they change by time.
* Text data like first and last name is a nominal value.
* The family tree itself has a hierarchical data, the ancestors are on top and are followed by their children, grand children etc. Relations of the same generation (partners, siblings) are shown on the same level. The hierarchy is shown implicitly, no extra hint is made.

=== target group ===
In general, the main target group are descendants, who want to know more about their ancestors and not just who they are / were, but it could be also interesting for everyone, who wants to know more about the specified family. (In this case it would be interesting for all serious Simpsons fans, who want to know everything about their favorite characters).
But in general this type of family tree contains some very sensitive data (like criminal records) and shouldn't be viewed by everyone due to privacy reasons.

=== use of visualization ===
To show relations a graph is much better than a table. So the primary aim of the visualization is to show relations between the family trees. An interesting aspect in this visualization could be, that there could be some time shift between different generations. For Example: 4.generation child from one parent could be as old as 3.generation from another parent.

==== questions getting answered by visualization ====
* Who were my ancestors?
* Who is related with me?
* Were my ancestors lucky with their lives?
* Did some happenings change their contentedness?
* How long did they live or are they still alive?
* What special happenings did they have in their lives?

== concept ==

=== techniques used ===
We like to see our family-tree as computer application (maybe just a internet page), because it's very easy to create and very easy to use interactive applications on computer-systems and almost everyone should be familiar with it.

==== family tree ====
The family relationships are shown in a classical tree view. Generations are shown in one line. To show relationships a conduit is used, for example: Between two persons, who get children a conduit is used, a conduit is also used between those parents and their children and so on.

The family-tree overview contains following data:
* Name of the person
* Conduit and position are showing relations
* Conduit also shows if person is related by marriage
* Sex is shown by color background

==== timeline ====

To bring a time dimension into our application, we included the so called "timeline mode". This is a special compare view, to show time differences between different persons. In the timeline mode you can see, when a person, was born, died, which mood he/she had, when he/she was alive, and also relations between married and blood relatet persons are visible.

==== mouse over effect ====
By sliding with the mouse cursor over a member of the family tree a pop up window appears with short informations about the specified family-member. If more information is needed, one can click on the window, to show more detailed information about the person. An advantage of this method (nesting) is, that sensitive data can be preserved with a password. A Disadvantage is, that it could be more inconvenient to use the application. Therefore a login-system would be very helpful.

The hover field contains following data:
* Picture, if available
* Name
* Sex
* Date of birth
* Date of death

==== detail information ====
By clicking on the popup-window button in the hover menu an extra pop-up window appears, in which all the registered data of the person shows up. The Contentedness-scale also has a mouse over effect: When sliding with the mouse over a specific time (from left to right) it shows the nearest happening from the happening list.

The detail information contains following data:
* All the data shown in the popup window
* Contentedness-scale
* Important happenings

==== additional interactivity ====

To increase the number of possibilities for user interaction a filtering and sorting mode was added to the Mock-Up's. The user can sort and filter name, date, etc.

==== comparison view ====
To compare specified family tree details a member of the tree has to be selected at first. This happens by double clicking a specified member. To compare with another family tree just double click a member of the other family tree to get into the comparison view.
There the two specified family tree's are going to be compared. Also different generations can be compared.

===explanation===

We used hierarchical trees to visualize the realtions between the persons, because it is the easiest and most common way to do it. Everybody can relate to it. To visualize gender and marriage/divorce we used symbols. As an additional mode we used the timeline mode to ease the comparisons. For the Contentedness-scale we used the colors green to red, because green is naturally related to good and red to bad/angry. We used the mouse-over effect to show the events so that the user has the feelings and the related event combined and also the time aspect.

=== mockups ===

==== family tree ====
[[Image:06-stammbaum.jpg|900px]]

==== mouse over effect ====
[[Image:06-Stammbaum1.jpg|900px]]
==== detail information ====
[[Image:06-Stammbaum2.jpg|900px]]
==== selection of specified tree ====
[[Image:06-Stammbaum-selected.jpg|900px]]
==== selection of blood tree ====
[[Image:06-Stammbaum-blood.jpg|900px]]
==== comparison view ====
[[Image:06-Stammbaum-comparison.jpg|900px]]
==== timeline ====
[[Image:06-Stammbaum-timeline.jpg|900px]]
== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2009/10|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/ UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 06|Gruppe 06]]

Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 06 - Aufgabe 4

2010-01-27T23:11:27Z

UE-InfoVis0910 0507049:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/infovis_ue_aufgabe4.html Beschreibung der Aufgabe 4]
=== Zu erstellende Visualisierung ===
-------------------------------
* Stammbaum der Nachkommen von Lisa und Bart Simpson*

...Visualisierung der Nachkommen von Lisa Simpson sowie der Nachkommen von Bart Simpson. Dabei sollen zwei Stammbäume entstehen - einer von Bart und einer von Lisa - die dann miteinander verglichen werden können. Zuerst kommen Lisa und Bart, dann deren Kinder, ihre Enkel, etc. (mind 4 Generationen). Da es noch keine Nachkommen gibt, können diese frei erfunden werden.

Die Visualisierung soll folgende Informationen darstellen:

- Verwandtschaftsverhältnisse (zumindest Eltern-Kinder),

- Unterscheidung zwischen Blutsverwandtschaft und angeheirateten Familienmitgliedern,

- Geburts- und Todestag sowie Lebensdauer von allen Familienmitgliedern,

- wichtige Ereignisse im Leben jedes Familienmitglieds (z.B., Anzeigen, Gefängnisaufenthalte, Schulzeit, Studienzeit, Nobelpreise, Arbeitslosigkeit etc.)

- Zufriedenheit jedes Familienmitglieds (Skala: sehr niedrig - niedrig - mittel - hoch - sehr hoch); kann sich im Laufe des Lebens ändern.

Die Visualisierung soll die interaktive Auseinandersetzung mit den Daten ermöglichen.
Verpflichtend:
Möglichkeiten zum besseren Vergleich von einzelnen Abschnitten der Stammbäume bzw. Vergleich von Ausschnitten aus Lisas und Barts Stammbäumen.
+ mind. 2 weitere Interaktionsmöglichkeiten (z.B., Details on Demand, Filteroptionen)

Allgemein:

- Die Daten sollen zur Analyse von Zusammenhängen zwischen Familienverhältnissen, wichtigen Ereignissen und Zufriedenheit visualisiert werden (die Anwendungsgebiets- und Zielgruppenanalyse kann kurz gehalten werden).

- Die bisher erlernten Design-Prinzipien sollen umgesetzt werden z.B.: Optimierung der Data-ink ratio (keine Comics!), visuelle Attribute (Größe, Farbe, Position, etc.) sollen sinnvoll eingesetzt werden (Information darstellen).

- Die Mockups sollten zumindest 1) die beiden Stammbäume im Überblick und 2) eine detaillierte Vergleichsansicht von 2 Teil-Stammbäumen wiedergeben.

- Alle nicht angeführten Daten können frei erfunden werden.

------------------------------

== analysis ==

=== application area ===
This graph is about family-tree visualization, where parents-children connections should be shown. It should not just be about family relations, but also be about individual happenings and feelings. The family tree should visualize hierarchical structures.
As already mentioned the tree should not only contain family relations, but also individual content and most important is, that the tree should be interactive:
* show detail information of a person, if demanded
* enable detailed comparisons of a section

=== dataset ===

* Sex is a nominal data because it cannot be ordered in a meaningful way. Both genders are equivalent. Additionally, the gender is a binary value (being male or female).
* The date of birth and death are ordinal values, because of the chronological order. In reality continual, we simplified the modelling by leaving out the time of birth. So are only discrete values are possible.
* The contentedness of a person is a discrete value, there are three different values possible (good, neutral, bad). It is 2-dimensional, because the contentedness is dependent on the time (what makes it temporal too) and of the value (good, bad, neutral).
* Important happenings are temporal, because they change by time.
* Text data like first and last name is a nominal value.
* The family tree itself has a hierarchical data, the ancestors are on top and are followed by their children, grand children etc. Relations of the same generation (partners, siblings) are shown on the same level. The hierarchy is shown implicitly, no extra hint is made.

=== target group ===
In general, the main target group are descendants, who want to know more about their ancestors and not just who they are / were, but it could be also interesting for everyone, who wants to know more about the specified family. (In this case it would be interesting for all serious Simpsons fans, who want to know everything about their favorite characters).
But in general this type of family tree contains some very sensitive data (like criminal records) and shouldn't be viewed by everyone due to privacy reasons.

=== use of visualization ===
To show relations a graph is much better than a table. So the primary aim of the visualization is to show relations between the family trees. An interesting aspect in this visualization could be, that there could be some time shift between different generations. For Example: 4.generation child from one parent could be as old as 3.generation from another parent.

==== questions getting answered by visualization ====
* Who were my ancestors?
* Who is related with me?
* Were my ancestors lucky with their lives?
* Did some happenings change their contentedness?
* How long did they live or are they still alive?
* What special happenings did they have in their lives?

== concept ==

=== Techniques used ===
We like to see our family-tree as computer application (maybe just a internet page), because it's very easy to create and very easy to use interactive applications on computer-systems and almost everyone should be familiar with it.

==== family tree ====
The family relationships are shown in a classical tree view. Generations are shown in one line. To show relationships a conduit is used, for example: Between two persons, who get children a conduit is used, a conduit is also used between those parents and their children and so on.

The family-tree overview contains following data:
* Name of the person
* Conduit and position are showing relations
* Conduit also shows if person is related by marriage
* Sex is shown by color background

=== Timeline ===

To bring a time dimension into our application, we included the so called "timeline mode". This is a special compare view, to show time differences between different persons. In the timeline mode you can see, when a person, was born, died, which mood he/she had, when he/she was alive, and also relations between married and blood relatet persons are visible.

==== mouse over effect ====
By sliding with the mouse cursor over a member of the family tree a pop up window appears with short informations about the specified family-member. If more information is needed, one can click on the window, to show more detailed information about the person. An advantage of this method (nesting) is, that sensitive data can be preserved with a password. A Disadvantage is, that it could be more inconvenient to use the application. Therefore a login-system would be very helpful.

The hover field contains following data:
* Picture, if available
* Name
* Sex
* Date of birth
* Date of death

==== detail information ====
By clicking on the popup-window button in the hover menu an extra pop-up window appears, in which all the registered data of the person shows up. The Contentedness-scale also has a mouse over effect: When sliding with the mouse over a specific time (from left to right) it shows the nearest happening from the happening list.

The detail information contains following data:
* All the data shown in the popup window
* Contentedness-scale
* Important happenings

==== Additional interactivity ====

To increase the number of possibilities for user interaction a filtering and sorting mode was added to the Mock-Up's. The user can sort and filter name, date, etc.

==== comparison view ====
To compare specified family tree details a member of the tree has to be selected at first. This happens by double clicking a specified member. To compare with another family tree just double click a member of the other family tree to get into the comparison view.
There the two specified family tree's are going to be compared. Also different generations can be compared.

===Explanation===

We used hierarchical trees to visualize the realtions between the persons, because it is the easiest and most common way to do it. Everybody can relate to it. To visualize gender and marriage/divorce we used symbols. As an additional mode we used the timeline mode to ease the comparisons. For the Contentedness-scale we used the colors green to red, because green is naturally related to good and red to bad/angry. We used the mouse-over effect to show the events so that the user has the feelings and the related event combined and also the time aspect.

=== mockups ===

==== family tree ====
[[Image:06-stammbaum.jpg|900px]]

==== mouse over effect ====
[[Image:06-Stammbaum1.jpg|900px]]
==== detail information ====
[[Image:06-Stammbaum2.jpg|900px]]
==== selection of specified tree ====
[[Image:06-Stammbaum-selected.jpg|900px]]
==== selection of blood tree ====
[[Image:06-Stammbaum-blood.jpg|900px]]
==== comparison view ====
[[Image:06-Stammbaum-comparison.jpg|900px]]
==== timeline ====
[[Image:06-Stammbaum-timeline.jpg|900px]]
== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2009/10|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/ UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 06|Gruppe 06]]

Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 06 - Aufgabe 4

2010-01-27T23:02:28Z

UE-InfoVis0910 0507049:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/infovis_ue_aufgabe4.html Beschreibung der Aufgabe 4]
=== Zu erstellende Visualisierung ===
-------------------------------
* Stammbaum der Nachkommen von Lisa und Bart Simpson*

...Visualisierung der Nachkommen von Lisa Simpson sowie der Nachkommen von Bart Simpson. Dabei sollen zwei Stammbäume entstehen - einer von Bart und einer von Lisa - die dann miteinander verglichen werden können. Zuerst kommen Lisa und Bart, dann deren Kinder, ihre Enkel, etc. (mind 4 Generationen). Da es noch keine Nachkommen gibt, können diese frei erfunden werden.

Die Visualisierung soll folgende Informationen darstellen:

- Verwandtschaftsverhältnisse (zumindest Eltern-Kinder),

- Unterscheidung zwischen Blutsverwandtschaft und angeheirateten Familienmitgliedern,

- Geburts- und Todestag sowie Lebensdauer von allen Familienmitgliedern,

- wichtige Ereignisse im Leben jedes Familienmitglieds (z.B., Anzeigen, Gefängnisaufenthalte, Schulzeit, Studienzeit, Nobelpreise, Arbeitslosigkeit etc.)

- Zufriedenheit jedes Familienmitglieds (Skala: sehr niedrig - niedrig - mittel - hoch - sehr hoch); kann sich im Laufe des Lebens ändern.

Die Visualisierung soll die interaktive Auseinandersetzung mit den Daten ermöglichen.
Verpflichtend:
Möglichkeiten zum besseren Vergleich von einzelnen Abschnitten der Stammbäume bzw. Vergleich von Ausschnitten aus Lisas und Barts Stammbäumen.
+ mind. 2 weitere Interaktionsmöglichkeiten (z.B., Details on Demand, Filteroptionen)

Allgemein:

- Die Daten sollen zur Analyse von Zusammenhängen zwischen Familienverhältnissen, wichtigen Ereignissen und Zufriedenheit visualisiert werden (die Anwendungsgebiets- und Zielgruppenanalyse kann kurz gehalten werden).

- Die bisher erlernten Design-Prinzipien sollen umgesetzt werden z.B.: Optimierung der Data-ink ratio (keine Comics!), visuelle Attribute (Größe, Farbe, Position, etc.) sollen sinnvoll eingesetzt werden (Information darstellen).

- Die Mockups sollten zumindest 1) die beiden Stammbäume im Überblick und 2) eine detaillierte Vergleichsansicht von 2 Teil-Stammbäumen wiedergeben.

- Alle nicht angeführten Daten können frei erfunden werden.

------------------------------

== analysis ==

=== application area ===
This graph is about family-tree visualization, where parents-children connections should be shown. It should not just be about family relations, but also be about individual happenings and feelings. The family tree should visualize hierarchical structures.
As already mentioned the tree should not only contain family relations, but also individual content and most important is, that the tree should be interactive:
* show detail information of a person, if demanded
* enable detailed comparisons of a section

=== dataset ===

* Sex is a nominal data because it cannot be ordered in a meaningful way. Both genders are equivalent. Additionally, the gender is a binary value (being male or female).
* The date of birth and death are ordinal values, because of the chronological order. In reality continual, we simplified the modelling by leaving out the time of birth. So are only discrete values are possible.
* The contentedness of a person is a discrete value, there are three different values possible (good, neutral, bad). It is 2-dimensional, because the contentedness is dependent on the time (what makes it temporal too) and of the value (good, bad, neutral).
* Important happenings are temporal, because they change by time.
* Text data like first and last name is a nominal value.
* The family tree itself has a hierarchical data, the ancestors are on top and are followed by their children, grand children etc. Relations of the same generation (partners, siblings) are shown on the same level. The hierarchy is shown implicitly, no extra hint is made.

=== target group ===
In general, the main target group are descendants, who want to know more about their ancestors and not just who they are / were, but it could be also interesting for everyone, who wants to know more about the specified family. (In this case it would be interesting for all serious Simpsons fans, who want to know everything about their favorite characters).
But in general this type of family tree contains some very sensitive data (like criminal records) and shouldn't be viewed by everyone due to privacy reasons.

=== use of visualization ===
To show relations a graph is much better than a table. So the primary aim of the visualization is to show relations between the family trees. An interesting aspect in this visualization could be, that there could be some time shift between different generations. For Example: 4.generation child from one parent could be as old as 3.generation from another parent.

==== questions getting answered by visualization ====
* Who were my ancestors?
* Who is related with me?
* Were my ancestors lucky with their lives?
* Did some happenings change their contentedness?
* How long did they live or are they still alive?
* What special happenings did they have in their lives?

== concept ==

=== Techniques used ===
We like to see our family-tree as computer application (maybe just a internet page), because it's very easy to create and very easy to use interactive applications on computer-systems and almost everyone should be familiar with it.

==== family tree ====
The family relationships are shown in a classical tree view. Generations are shown in one line. To show relationships a conduit is used, for example: Between two persons, who get children a conduit is used, a conduit is also used between those parents and their children and so on.

The family-tree overview contains following data:
* Name of the person
* Conduit and position are showing relations
* Conduit also shows if person is related by marriage
* Sex is shown by color background

=== Timeline ===

To bring a time dimension into our application, we included the so called "timeline mode". This is a special compare view, to show time differences between different persons. In the timeline mode you can see, when a person, was born, died, which mood he/she had, when he/she was alive, and also relations between married and blood relatet persons are visible.

==== mouse over effect ====
By sliding with the mouse cursor over a member of the family tree a pop up window appears with short informations about the specified family-member. If more information is needed, one can click on the window, to show more detailed information about the person. An advantage of this method (nesting) is, that sensitive data can be preserved with a password. A Disadvantage is, that it could be more inconvenient to use the application. Therefore a login-system would be very helpful.

The hover field contains following data:
* Picture, if available
* Name
* Sex
* Date of birth
* Date of death

==== detail information ====
By clicking on the popup-window button in the hover menu an extra pop-up window appears, in which all the registered data of the person shows up. The Contentedness-scale also has a mouse over effect: When sliding with the mouse over a specific time (from left to right) it shows the nearest happening from the happening list.

The detail information contains following data:
* All the data shown in the popup window
* Contentedness-scale
* Important happenings

==== Additional interactivity ====

To increase the number of possibilities for user interaction a filtering and sorting mode was added to the Mock-Up's. The user can sort and filter name, date, etc.

==== comparison view ====
To compare specified family tree details a member of the tree has to be selected at first. This happens by double clicking a specified member. To compare with another family tree just double click a member of the other family tree to get into the comparison view.
There the two specified family tree's are going to be compared. Also different generations can be compared.

===Explanation===

We used hierarchical trees to visualize the realtions between the persons, because it is the easiest and most common way to do it. Everybody can relate to it. To visualize gender and marriage/divorce we used symbols. As an additional mode we used the timeline mode to ease the comparisons.

=== mockups ===

==== family tree ====
[[Image:06-stammbaum.jpg|900px]]

==== mouse over effect ====
[[Image:06-Stammbaum1.jpg|900px]]
==== detail information ====
[[Image:06-Stammbaum2.jpg|900px]]
==== selection of specified tree ====
[[Image:06-Stammbaum-selected.jpg|900px]]
==== selection of blood tree ====
[[Image:06-Stammbaum-blood.jpg|900px]]
==== comparison view ====
[[Image:06-Stammbaum-comparison.jpg|900px]]
==== timeline ====
[[Image:06-Stammbaum-timeline.jpg|900px]]
== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2009/10|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/ UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 06|Gruppe 06]]

Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 06 - Aufgabe 4

2010-01-27T22:55:31Z

UE-InfoVis0910 0507049:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/infovis_ue_aufgabe4.html Beschreibung der Aufgabe 4]
=== Zu erstellende Visualisierung ===
-------------------------------
* Stammbaum der Nachkommen von Lisa und Bart Simpson*

...Visualisierung der Nachkommen von Lisa Simpson sowie der Nachkommen von Bart Simpson. Dabei sollen zwei Stammbäume entstehen - einer von Bart und einer von Lisa - die dann miteinander verglichen werden können. Zuerst kommen Lisa und Bart, dann deren Kinder, ihre Enkel, etc. (mind 4 Generationen). Da es noch keine Nachkommen gibt, können diese frei erfunden werden.

Die Visualisierung soll folgende Informationen darstellen:

- Verwandtschaftsverhältnisse (zumindest Eltern-Kinder),

- Unterscheidung zwischen Blutsverwandtschaft und angeheirateten Familienmitgliedern,

- Geburts- und Todestag sowie Lebensdauer von allen Familienmitgliedern,

- wichtige Ereignisse im Leben jedes Familienmitglieds (z.B., Anzeigen, Gefängnisaufenthalte, Schulzeit, Studienzeit, Nobelpreise, Arbeitslosigkeit etc.)

- Zufriedenheit jedes Familienmitglieds (Skala: sehr niedrig - niedrig - mittel - hoch - sehr hoch); kann sich im Laufe des Lebens ändern.

Die Visualisierung soll die interaktive Auseinandersetzung mit den Daten ermöglichen.
Verpflichtend:
Möglichkeiten zum besseren Vergleich von einzelnen Abschnitten der Stammbäume bzw. Vergleich von Ausschnitten aus Lisas und Barts Stammbäumen.
+ mind. 2 weitere Interaktionsmöglichkeiten (z.B., Details on Demand, Filteroptionen)

Allgemein:

- Die Daten sollen zur Analyse von Zusammenhängen zwischen Familienverhältnissen, wichtigen Ereignissen und Zufriedenheit visualisiert werden (die Anwendungsgebiets- und Zielgruppenanalyse kann kurz gehalten werden).

- Die bisher erlernten Design-Prinzipien sollen umgesetzt werden z.B.: Optimierung der Data-ink ratio (keine Comics!), visuelle Attribute (Größe, Farbe, Position, etc.) sollen sinnvoll eingesetzt werden (Information darstellen).

- Die Mockups sollten zumindest 1) die beiden Stammbäume im Überblick und 2) eine detaillierte Vergleichsansicht von 2 Teil-Stammbäumen wiedergeben.

- Alle nicht angeführten Daten können frei erfunden werden.

------------------------------

== analysis ==

=== application area ===
This graph is about family-tree visualization, where parents-children connections should be shown. It should not just be about family relations, but also be about individual happenings and feelings. The family tree should visualize hierarchical structures.
As already mentioned the tree should not only contain family relations, but also individual content and most important is, that the tree should be interactive:
* show detail information of a person, if demanded
* enable detailed comparisons of a section

=== dataset ===

* Sex is a nominal data because it cannot be ordered in a meaningful way. Both genders are equivalent. Additionally, the gender is a binary value (being male or female).
* The date of birth and death are ordinal values, because of the chronological order. In reality continual, we simplified the modelling by leaving out the time of birth. So are only discrete values are possible.
* The contentedness of a person is a discrete value, there are three different values possible (good, neutral, bad). It is 2-dimensional, because the contentedness is dependent on the time (what makes it temporal too) and of the value (good, bad, neutral).
* Important happenings are temporal, because they change by time.
* Text data like first and last name is a nominal value.
* The family tree itself has a hierarchical data, the ancestors are on top and are followed by their children, grand children etc. Relations of the same generation (partners, siblings) are shown on the same level. The hierarchy is shown implicitly, no extra hint is made.

=== target group ===
In general, the main target group are descendants, who want to know more about their ancestors and not just who they are / were, but it could be also interesting for everyone, who wants to know more about the specified family. (In this case it would be interesting for all serious Simpsons fans, who want to know everything about their favorite characters).
But in general this type of family tree contains some very sensitive data (like criminal records) and shouldn't be viewed by everyone due to privacy reasons.

=== use of visualization ===
To show relations a graph is much better than a table. So the primary aim of the visualization is to show relations between the family trees. An interesting aspect in this visualization could be, that there could be some time shift between different generations. For Example: 4.generation child from one parent could be as old as 3.generation from another parent.

==== questions getting answered by visualization ====
* Who were my ancestors?
* Who is related with me?
* Were my ancestors lucky with their lives?
* Did some happenings change their contentedness?
* How long did they live or are they still alive?
* What special happenings did they have in their lives?

== concept ==

=== Techniques used ===
We like to see our family-tree as computer application (maybe just a internet page), because it's very easy to create and very easy to use interactive applications on computer-systems and almost everyone should be familiar with it.

==== family tree ====
The family relationships are shown in a classical tree view. Generations are shown in one line. To show relationships a conduit is used, for example: Between two persons, who get children a conduit is used, a conduit is also used between those parents and their children and so on.

The family-tree overview contains following data:
* Name of the person
* Conduit and position are showing relations
* Conduit also shows if person is related by marriage
* Sex is shown by color background

=== Timeline ===

To bring a time dimension into our application, we included the so called "timeline mode". This is a special compare view, to show time differences between different persons. In the timeline mode you can see, when a person, was born, died, which mood he/she had, when he/she was alive, and also relations between married and blood relatet persons are visible.

==== mouse over effect ====
By sliding with the mouse cursor over a member of the family tree a pop up window appears with short informations about the specified family-member. If more information is needed, one can click on the window, to show more detailed information about the person. An advantage of this method (nesting) is, that sensitive data can be preserved with a password. A Disadvantage is, that it could be more inconvenient to use the application. Therefore a login-system would be very helpful.

The hover field contains following data:
* Picture, if available
* Name
* Sex
* Date of birth
* Date of death

==== detail information ====
By clicking on the popup-window button in the hover menu an extra pop-up window appears, in which all the registered data of the person shows up. The Contentedness-scale also has a mouse over effect: When sliding with the mouse over a specific time (from left to right) it shows the nearest happening from the happening list.

The detail information contains following data:
* All the data shown in the popup window
* Contentedness-scale
* Important happenings

=== Additional interactivity ===

To increase the number of possibilities for user interaction a filtering and sorting mode was added to the Mock-Up's. The user can sort and filter name, date, etc.

==== comparison view ====
To compare specified family tree details a member of the tree has to be selected at first. This happens by double clicking a specified member. To compare with another family tree just double click a member of the other family tree to get into the comparison view.
There the two specified family tree's are going to be compared. Also different generations can be compared.

=== mockups ===

==== family tree ====
[[Image:06-stammbaum.jpg|900px]]

==== mouse over effect ====
[[Image:06-Stammbaum1.jpg|900px]]
==== detail information ====
[[Image:06-Stammbaum2.jpg|900px]]
==== selection of specified tree ====
[[Image:06-Stammbaum-selected.jpg|900px]]
==== selection of blood tree ====
[[Image:06-Stammbaum-blood.jpg|900px]]
==== comparison view ====
[[Image:06-Stammbaum-comparison.jpg|900px]]
==== timeline ====
[[Image:06-Stammbaum-timeline.jpg|900px]]
== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2009/10|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/ UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 06|Gruppe 06]]

Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 06 - Aufgabe 4

2010-01-27T22:48:09Z

UE-InfoVis0910 0507049:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/infovis_ue_aufgabe4.html Beschreibung der Aufgabe 4]
=== Zu erstellende Visualisierung ===
-------------------------------
* Stammbaum der Nachkommen von Lisa und Bart Simpson*

...Visualisierung der Nachkommen von Lisa Simpson sowie der Nachkommen von Bart Simpson. Dabei sollen zwei Stammbäume entstehen - einer von Bart und einer von Lisa - die dann miteinander verglichen werden können. Zuerst kommen Lisa und Bart, dann deren Kinder, ihre Enkel, etc. (mind 4 Generationen). Da es noch keine Nachkommen gibt, können diese frei erfunden werden.

Die Visualisierung soll folgende Informationen darstellen:

- Verwandtschaftsverhältnisse (zumindest Eltern-Kinder),

- Unterscheidung zwischen Blutsverwandtschaft und angeheirateten Familienmitgliedern,

- Geburts- und Todestag sowie Lebensdauer von allen Familienmitgliedern,

- wichtige Ereignisse im Leben jedes Familienmitglieds (z.B., Anzeigen, Gefängnisaufenthalte, Schulzeit, Studienzeit, Nobelpreise, Arbeitslosigkeit etc.)

- Zufriedenheit jedes Familienmitglieds (Skala: sehr niedrig - niedrig - mittel - hoch - sehr hoch); kann sich im Laufe des Lebens ändern.

Die Visualisierung soll die interaktive Auseinandersetzung mit den Daten ermöglichen.
Verpflichtend:
Möglichkeiten zum besseren Vergleich von einzelnen Abschnitten der Stammbäume bzw. Vergleich von Ausschnitten aus Lisas und Barts Stammbäumen.
+ mind. 2 weitere Interaktionsmöglichkeiten (z.B., Details on Demand, Filteroptionen)

Allgemein:

- Die Daten sollen zur Analyse von Zusammenhängen zwischen Familienverhältnissen, wichtigen Ereignissen und Zufriedenheit visualisiert werden (die Anwendungsgebiets- und Zielgruppenanalyse kann kurz gehalten werden).

- Die bisher erlernten Design-Prinzipien sollen umgesetzt werden z.B.: Optimierung der Data-ink ratio (keine Comics!), visuelle Attribute (Größe, Farbe, Position, etc.) sollen sinnvoll eingesetzt werden (Information darstellen).

- Die Mockups sollten zumindest 1) die beiden Stammbäume im Überblick und 2) eine detaillierte Vergleichsansicht von 2 Teil-Stammbäumen wiedergeben.

- Alle nicht angeführten Daten können frei erfunden werden.

------------------------------

== analysis ==

=== application area ===
This graph is about family-tree visualization, where parents-children connections should be shown. It should not just be about family relations, but also be about individual happenings and feelings. The family tree should visualize hierarchical structures.
As already mentioned the tree should not only contain family relations, but also individual content and most important is, that the tree should be interactive:
* show detail information of a person, if demanded
* enable detailed comparisons of a section

=== dataset ===

* Sex is a nominal data because it cannot be ordered in a meaningful way. Both genders are equivalent. Additionally, the gender is a binary value (being male or female).
* The date of birth and death are ordinal values, because of the chronological order. In reality continual, we simplified the modelling by leaving out the time of birth. So are only discrete values are possible.
* The contentedness of a person is a discrete value, there are three different values possible (good, neutral, bad). It is 2-dimensional, because the contentedness is dependent on the time (what makes it temporal too) and of the value (good, bad, neutral).
* Important happenings are temporal, because they change by time.
* Text data like first and last name is a nominal value.
* The family tree itself has a hierarchical data, the ancestors are on top and are followed by their children, grand children etc. Relations of the same generation (partners, siblings) are shown on the same level. The hierarchy is shown implicitly, no extra hint is made.

=== target group ===
In general, the main target group are descendants, who want to know more about their ancestors and not just who they are / were, but it could be also interesting for everyone, who wants to know more about the specified family. (In this case it would be interesting for all serious Simpsons fans, who want to know everything about their favorite characters).
But in general this type of family tree contains some very sensitive data (like criminal records) and shouldn't be viewed by everyone due to privacy reasons.

=== use of visualization ===
To show relations a graph is much better than a table. So the primary aim of the visualization is to show relations between the family trees. An interesting aspect in this visualization could be, that there could be some time shift between different generations. For Example: 4.generation child from one parent could be as old as 3.generation from another parent.

==== questions getting answered by visualization ====
* Who were my ancestors?
* Who is related with me?
* Were my ancestors lucky with their lives?
* Did some happenings change their contentedness?
* How long did they live or are they still alive?
* What special happenings did they have in their lives?

== concept ==

=== Techniques used ===
We like to see our family-tree as computer application (maybe just a internet page), because it's very easy to create and very easy to use interactive applications on computer-systems and almost everyone should be familiar with it.

==== family tree ====
The family relationships are shown in a classical tree view. Generations are shown in one line. To show relationships a conduit is used, for example: Between two persons, who get children a conduit is used, a conduit is also used between those parents and their children and so on.

The family-tree overview contains following data:
* Name of the person
* Conduit and position are showing relations
* Conduit also shows if person is related by marriage
* Sex is shown by color background

==== mouse over effect ====
By sliding with the mouse cursor over a member of the family tree a pop up window appears with short informations about the specified family-member. If more information is needed, one can click on the window, to show more detailed information about the person. An advantage of this method (nesting) is, that sensitive data can be preserved with a password. A Disadvantage is, that it could be more inconvenient to use the application. Therefore a login-system would be very helpful.

The hover field contains following data:
* Picture, if available
* Name
* Sex
* Date of birth
* Date of death

==== detail information ====
By clicking on the popup-window button in the hover menu an extra pop-up window appears, in which all the registered data of the person shows up. The Contentedness-scale also has a mouse over effect: When sliding with the mouse over a specific time (from left to right) it shows the nearest happening from the happening list.

The detail information contains following data:
* All the data shown in the popup window
* Contentedness-scale
* Important happenings

=== Additional interactivity ===

To increase the number of possibilities for user interaction a filtering and sorting mode was added to the Mock-Up's. The user can sort and filter name, date, etc.

==== comparison view ====
To compare specified family tree details a member of the tree has to be selected at first. This happens by double clicking a specified member. To compare with another family tree just double click a member of the other family tree to get into the comparison view.
There the two specified family tree's are going to be compared. Also different generations can be compared.

=== mockups ===

==== family tree ====
[[Image:06-stammbaum.jpg|900px]]

==== mouse over effect ====
[[Image:06-Stammbaum1.jpg|900px]]
==== detail information ====
[[Image:06-Stammbaum2.jpg|900px]]
==== selection of specified tree ====
[[Image:06-Stammbaum-selected.jpg|900px]]
==== selection of blood tree ====
[[Image:06-Stammbaum-blood.jpg|900px]]
==== comparison view ====
[[Image:06-Stammbaum-comparison.jpg|900px]]
==== timeline ====
[[Image:06-Stammbaum-timeline.jpg|900px]]
== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2009/10|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/ UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 06|Gruppe 06]]

Teaching talk:TUW - UE InfoVis WS 2009/10 - Gruppe 06 - Aufgabe 4

2010-01-27T22:40:01Z

UE-InfoVis0910 0507049:

==Bewertung==

'''vorläufige Bewertung: 24 Punkte''' 

Begründung:

* zeitliche Aspekte (Geburt, Tod, Lebensdauer) nicht visuell dargestellt
* wichtige Ereignisse nicht visuell dargestellt
* Erkennbarkeit von Blutsverwandtschaft nicht visuell unterstützt
* zu wenig Interaktionsmöglichkeiten (z.B. Filtern)
* Legende (Farbcodierung Zufriedenheit) fehlt
* Es ist nicht notwendig, die Kästchen entweder rosa oder blau zu füllen. Das Geschlecht kann auch anders dargestellt werden. Die Farbe lenkt nur ab.
* Begründung, warum ihr welche visuellen Attribute gewählt habt, fehlt.

[[User:Katharina-Anna Wendelin|Katharina-Anna Wendelin]] 11:02, 20 January 2010 
----

'''TO-DO:'''

'''* zeitliche Aspekte (Geburt, Tod, Lebensdauer) nicht visuell dargestellt'''
'''* wichtige Ereignisse nicht visuell dargestellt'''

Dies war zuerst in der Detailansicht an den Mouseovereffekt geknüpft.
Dort wurden die div. Informationen eingeblendet.
Jetzt wurde diese Verknüpfung noch stärker visuell mit einem Pfeil dargestellt bzw. verbunden
damit der Zusammenhang leicht ersichtlich ist. Die Befindlichkeitsskala ist gleichzeitig auch Timeline, da oft die Befindlichkeit mit wichtigen Ereignissen zusammenhängt (z.B. Tod).

Zusätzlich wurde noch ein Mock-Up hinzugefügt, dass das ganze auf der Zeitachse zeigt.
Hier sind vor Allem gut die Kinder zu erkennen und wiederum der Mouse-Over Effekt eingebaut.
Sobald der Mauszeiger über der Befindlichkeitsskala ist wird das entsprechende Ereignis angezeigt bzw. ist es möglich die genau Zeit abzulesen.

'''* Erkennbarkeit von Blutsverwandtschaft nicht visuell unterstützt'''

Bei der Auswahl eines speziellen Pfades wurde zusätzlich ein Filter hinzugefügt um nur den Blutpfad anzuzeigen. Die Angeheirateten Personen werden in den Hintergrund gerückt/überblendet.

'''* zu wenig Interaktionsmöglichkeiten (z.B. Filtern)'''

Zusätzlich zum Mouse Over und dem Vergleich von Stammbäumen, wurde als Interaktivität noch Sortieren (nach Name, Datum, etc.) und Filtern eingebaut (von Namen, Datum, etc.).

'''* Legende (Farbcodierung Zufriedenheit) fehlt'''

die Legende wurde ergänzt

'''* Es ist nicht notwendig, die Kästchen entweder rosa oder blau zu füllen. Das Geschlecht kann auch anders dargestellt werden. Die Farbe lenkt nur ab.'''

Alle Farben wurden auf dieses Feedback hin entfernt und das Geschlecht durch die üblichen Symbole dargestellt.

'''* Begründung, warum ihr welche visuellen Attribute gewählt habt, fehlt.'''

wurde ergänzt

File:06-Stammbaum-timeline.jpg

2010-01-27T22:19:04Z

UE-InfoVis0910 0507049: New page: == Summary == == Copyright status == == Source ==

== Summary ==

== Copyright status ==

== Source ==

File:06-Stammbaum-blood.jpg

2010-01-27T22:18:45Z

UE-InfoVis0910 0507049: New page: == Summary == == Copyright status == == Source ==

== Summary ==

== Copyright status ==

== Source ==

Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 06 - Aufgabe 4

2010-01-27T22:18:21Z

UE-InfoVis0910 0507049:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/infovis_ue_aufgabe4.html Beschreibung der Aufgabe 4]
=== Zu erstellende Visualisierung ===
-------------------------------
* Stammbaum der Nachkommen von Lisa und Bart Simpson*

...Visualisierung der Nachkommen von Lisa Simpson sowie der Nachkommen von Bart Simpson. Dabei sollen zwei Stammbäume entstehen - einer von Bart und einer von Lisa - die dann miteinander verglichen werden können. Zuerst kommen Lisa und Bart, dann deren Kinder, ihre Enkel, etc. (mind 4 Generationen). Da es noch keine Nachkommen gibt, können diese frei erfunden werden.

Die Visualisierung soll folgende Informationen darstellen:

- Verwandtschaftsverhältnisse (zumindest Eltern-Kinder),

- Unterscheidung zwischen Blutsverwandtschaft und angeheirateten Familienmitgliedern,

- Geburts- und Todestag sowie Lebensdauer von allen Familienmitgliedern,

- wichtige Ereignisse im Leben jedes Familienmitglieds (z.B., Anzeigen, Gefängnisaufenthalte, Schulzeit, Studienzeit, Nobelpreise, Arbeitslosigkeit etc.)

- Zufriedenheit jedes Familienmitglieds (Skala: sehr niedrig - niedrig - mittel - hoch - sehr hoch); kann sich im Laufe des Lebens ändern.

Die Visualisierung soll die interaktive Auseinandersetzung mit den Daten ermöglichen.
Verpflichtend:
Möglichkeiten zum besseren Vergleich von einzelnen Abschnitten der Stammbäume bzw. Vergleich von Ausschnitten aus Lisas und Barts Stammbäumen.
+ mind. 2 weitere Interaktionsmöglichkeiten (z.B., Details on Demand, Filteroptionen)

Allgemein:

- Die Daten sollen zur Analyse von Zusammenhängen zwischen Familienverhältnissen, wichtigen Ereignissen und Zufriedenheit visualisiert werden (die Anwendungsgebiets- und Zielgruppenanalyse kann kurz gehalten werden).

- Die bisher erlernten Design-Prinzipien sollen umgesetzt werden z.B.: Optimierung der Data-ink ratio (keine Comics!), visuelle Attribute (Größe, Farbe, Position, etc.) sollen sinnvoll eingesetzt werden (Information darstellen).

- Die Mockups sollten zumindest 1) die beiden Stammbäume im Überblick und 2) eine detaillierte Vergleichsansicht von 2 Teil-Stammbäumen wiedergeben.

- Alle nicht angeführten Daten können frei erfunden werden.

------------------------------

== analysis ==

=== application area ===
This graph is about family-tree visualization, where parents-children connections should be shown. It should not just be about family relations, but also be about individual happenings and feelings. The family tree should visualize hierarchical structures.
As already mentioned the tree should not only contain family relations, but also individual content and most important is, that the tree should be interactive:
* show detail information of a person, if demanded
* enable detailed comparisons of a section

=== dataset ===

* Sex is a nominal data because it cannot be ordered in a meaningful way. Both genders are equivalent. Additionally, the gender is a binary value (being male or female).
* The date of birth and death are ordinal values, because of the chronological order. In reality continual, we simplified the modelling by leaving out the time of birth. So are only discrete values are possible.
* The contentedness of a person is a discrete value, there are three different values possible (good, neutral, bad). It is 2-dimensional, because the contentedness is dependent on the time (what makes it temporal too) and of the value (good, bad, neutral).
* Important happenings are temporal, because they change by time.
* Text data like first and last name is a nominal value.
* The family tree itself has a hierarchical data, the ancestors are on top and are followed by their children, grand children etc. Relations of the same generation (partners, siblings) are shown on the same level. The hierarchy is shown implicitly, no extra hint is made.

=== target group ===
In general, the main target group are descendants, who want to know more about their ancestors and not just who they are / were, but it could be also interesting for everyone, who wants to know more about the specified family. (In this case it would be interesting for all serious Simpsons fans, who want to know everything about their favorite characters).
But in general this type of family tree contains some very sensitive data (like criminal records) and shouldn't be viewed by everyone due to privacy reasons.

=== use of visualization ===
To show relations a graph is much better than a table. So the primary aim of the visualization is to show relations between the family trees. An interesting aspect in this visualization could be, that there could be some time shift between different generations. For Example: 4.generation child from one parent could be as old as 3.generation from another parent.

==== questions getting answered by visualization ====
* Who were my ancestors?
* Who is related with me?
* Were my ancestors lucky with their lives?
* Did some happenings change their contentedness?
* How long did they live or are they still alive?
* What special happenings did they have in their lives?

== concept ==

=== Techniques used ===
We like to see our family-tree as computer application (maybe just a internet page), because it's very easy to create and very easy to use interactive applications on computer-systems and almost everyone should be familiar with it.

==== family tree ====
The family relationships are shown in a classical tree view. Generations are shown in one line. To show relationships a conduit is used, for example: Between two persons, who get children a conduit is used, a conduit is also used between those parents and their children and so on.

The family-tree overview contains following data:
* Name of the person
* Conduit and position are showing relations
* Conduit also shows if person is related by marriage
* Sex is shown by color background

==== mouse over effect ====
By sliding with the mouse cursor over a member of the family tree a pop up window appears with short informations about the specified family-member. If more information is needed, one can click on the window, to show more detailed information about the person. An advantage of this method (nesting) is, that sensitive data can be preserved with a password. A Disadvantage is, that it could be more inconvenient to use the application. Therefore a login-system would be very helpful.

The hover field contains following data:
* Picture, if available
* Name
* Sex
* Date of birth
* Date of death

==== detail information ====
By clicking on the popup-window button in the hover menu an extra pop-up window appears, in which all the registered data of the person shows up. The Contentedness-scale also has a mouse over effect: When sliding with the mouse over a specific time (from left to right) it shows the nearest happening from the happening list.

The detail information contains following data:
* All the data shown in the popup window
* Contentedness-scale
* Important happenings

==== comparison view ====
To compare specified family tree details a member of the tree has to be selected at first. This happens by double clicking a specified member. To compare with another family tree just double click a member of the other family tree to get into the comparison view.
There the two specified family tree's are going to be compared. Also different generations can be compared.

=== mockups ===

==== family tree ====
[[Image:06-stammbaum.jpg|900px]]

==== mouse over effect ====
[[Image:06-Stammbaum1.jpg|900px]]
==== detail information ====
[[Image:06-Stammbaum2.jpg|900px]]
==== selection of specified tree ====
[[Image:06-Stammbaum-selected.jpg|900px]]
==== selection of blood tree ====
[[Image:06-Stammbaum-blood.jpg|900px]]
==== comparison view ====
[[Image:06-Stammbaum-comparison.jpg|900px]]
==== timeline ====
[[Image:06-Stammbaum-timeline.jpg|900px]]
== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2009/10|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/ UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 06|Gruppe 06]]

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

2009-12-06T20:25:39Z

UE-InfoVis0910 0507049:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/infovis_ue_aufgabe3.html Beschreibung der Aufgabe 3]
=== Zu verbessernde Grafik ===
------------------------------- 
[[Image:geo3.jpg]]

=== Critique about the Graph ===
* data ink ratio is very high
* The world map is not really necessary (except for showing the shipment routes)
* The circles are overlapping
* The values are not ordered (because they are shown on the map)
* Much unimportant information, only the necessary info should be on the graph

===Redesign===

[[Image:Diagramm2.jpg|1322px]]

* We made two graphs that separate the information. The second one shows the values of the hazardous waste production. That is acutally the key information in the graph.
* The values are ordered in a bar chart.
* The ship routes are only labelled by the continents, the additional information (goods etc) is removed, because that information is not as important.

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

2009-12-06T16:11:58Z

UE-InfoVis0910 0507049:

== Aufgabenstellung ==
[http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/infovis_ue_aufgabe2.html Beschreibung der Aufgabe 2]
=== Zu beurteilende Tabelle ===
[[Image:statistics308.jpg]]

===Critique about the table ===
* The grid encloses the entire table. This should be avoided, because it breaks up the data. (Use white spaces or rules under the header and over the footer instead) (Page 136).
* Time based data should be arranged in columns from left to right rather than in rows from top to bottom (Page 142).
* Groups and Breaks: All the content is put in one table. Split the table instead in all the data groups that belong together (Page 143).
* No whitespacing between different groups of the table (Page 144).
* Headers are not repeated over the different group sections (Page 144).
* Text align of numbers should not be aligned to the left side (Page 147).
*Number format is not consistent: Column "Median Price" uses two different formats (Sold in March 2007 vs. Sold in March 2008: Thousand sepatator is once a point and once a comma). Column 1 ("Units") doesn't use any separators at all (Page 149).
* $ sign is not necessary in every cell.
* Columns are to small, so the data is split in two rows.
* difficult formulations: 1/1/08 - 3/31/08 instead of 1st Quartal 2008
* Text align is left and makes it difficult to compare the numbers.
* % values don't have the same number of positions after decimal point.
* The change rows shouldn't be in the same columns because they do not even have the same measurement than the other columns.
* Different meanings in the same column. For example 4 different Meanings of 'Units':
**Units on the market
**Units sold in one period
**Change of Units on the market between to periods
**Change of Units sold between two periods
*'Average Day on the market' is illogical in context of a defined period
* The order of the values that are compared (2007 and 2008) is confusing because the summary (change) is the wrong way around (6725 compared to 5993 is not an increase of 12%).

===New Table ===
[[Image:Table_2_group_6.png|950px]]

===Explanation of the changes===
* Table is split into two different tables because the data doesn't really belong together.
* The grid is removed, just a ruler under the header is kept to make a difference between the data and the header.
* The ruler is in a very light grey (black bold rulers seperates them)
* Simpler formulation (Quartal instead of 1/1 - 3/31), so that the meaning of the column is seen at first sight.
* Columns and Rows are switched because time based data should be put in columns.
* Consistent form of percentage values (1 digit after the comma).
* $ sign is removed and put in the header.
* Text align is right, so numbers can be compared easliy.
* Consistent use of thousands separators (comma).
* Whitespaces are added, so the data is optically split into groups that belong together

===Explanation of the changes===
* Compared to the first table, the rows and columns are in the same way as in the original table.
* Data is split in two groups because it does not really belong together.
* Whitespaces seperate the summary rows from data rows.
* Whitespaces are used to separate the different tables too.

=== Improvement ===
[[Image:Table_group_6_verbesserung.png|526px]]

We made the changes according to the discussion page, except putting 0.0% in empty cells, because we thought it is irritating to write that there is a change of 0% although the values have changed. So we calculated the appropriate value and put it in there.

== References ==
[Few, 2004] Stephen Few. Show Me the Numbers: Designing Tables and Graphs to Enlighten. Analytics Press, 2004, Chapter 8 – Table Design

[Wallace, 2004] Rosa Wallace, NC State University. Designing Tables. http://www.ncsu.edu/labwrite/res/gh/gh-tables.html

== Links ==

* [[Teaching:TUW_-_UE_InfoVis_WS_2009/10|InfoVis:Wiki UE Homepage]]

* [http://ieg.ifs.tuwien.ac.at/~gschwand/teaching/infovis_ue_ws09/ UE InfoVis]

*[[Teaching:TUW - UE InfoVis WS 2009/10 - Gruppe 06|Gruppe 06]]

Teaching talk:TUW - UE InfoVis WS 2009/10 - Gruppe 06 - Aufgabe 1

2009-11-17T00:52:26Z

UE-InfoVis0910 0507049:

'''vorläufige Bewertung: 5 Punkte'''

Begründung:

'''Drag and Drop'''

* Definition als solche Kennzeichnen
* Artikel CPOF ist 1:1 aus wikipedia rauskopiert ohne Zitat.
* Auch die Passage über lookmark ist 1:1 aus dem Paper kopiert.

'''InfoZoom'''

* Fehlende Kennzeichnung der Textstellen als Zitate.
* Der Part, der als Definition gekennzeichnet ist, ist keine Definition.

[[User:Katharina-Anna Wendelin|Katharina-Anna Wendelin]] 00:12, 17 November 2009 

'''''TODO:'''''

'''Drag and Drop'''

* Definition als solche Kennzeichnen
::'''DONE'''
* Artikel CPOF ist 1:1 aus wikipedia rauskopiert ohne Zitat.
::'''DONE'''
* Auch die Passage über lookmark ist 1:1 aus dem Paper kopiert.
::'''ist eig als zitat gekennzeichnet. muss da sonst noch was gemacht werden?'''

'''InfoZoom'''

* Fehlende Kennzeichnung der Textstellen als Zitate.
::'''soweit ich das sehe sind nur die "View Modes" nicht gekennzeichnet und das mMn deswegen weil sie nicht zitiert sondern selber formuliert wurden, oder? Sonst würd ich hier überall noch "Spenke" als Quelle angeben.
* Der Part, der als Definition gekennzeichnet ist, ist keine Definition.
::'''Wurde geändert. Definition muss kein Zitat sein, oder?

Teaching:TUW - UE InfoVis WS 2006/07 - Gruppe 03 - Aufgabe 1 - InfoZoom

2009-11-17T00:43:05Z

UE-InfoVis0910 0507049:

==Definition==
{{definition|InfoZoom is a computer application, developed by the company humanIT, a spin-off of Fraunhofer Society and subsidiary company of proALPHA Software AG, for analyzing and displaying large amounts of data in an easy-to-understand format.}}

== History ==

InfoZoom evolved from another system called FOCUS, a focus+context table layout [Kort, 2004]. 
The current and newest version is InfoZoom V6.0.

== Description ==

=== Overview ===

Primarily, InfoZoom was developed for manipulating tables. By default it uses parallel bargrams for larger sizes of data sets and special focus+context tables for smaller ones [Wittenburg et al, 2001]. So it is possible to present information in table or distribution oriented formats.

When displaying relational data tables, InfoZoom uses one row for each record. This data can be sorted sequential, hierarchical or in any other way the user wants it to be sorted. If necessary, the user can "zoom" into the information. This happens for example by doubleclicking on attribute values or sets/ranges of values [Mark et al, 2003]. This "zooming" can also be done by selecting columns of a row interactively and then promoting them into qualified records. All other records except those marked as qualified records are hidden instantly, enabling a "zoomed" view on the information.

The primary interactions supported in InfoZoom are simple selection and filtering, accomplished with a single mouse click on a value bin. Interesting graphical renderings of values are included. Animation is used to transition between set sizes. [Wittenburg et al, 2001]
[[Image:Software_architecture.gif|200px|thumb|software architecture of InfoZoom V6.0]]
=== Data Source & Compatibility ===

With its versatility and open architecture for quick and easy OEM installation based on commonly used industry standards (ODBC, OLE DB, OLE DB for OLAP, COM, ActiveX) and native interfaces (proALPHA, SAP, Lotus Notes, etc.), InfoZoom offers a major advantage for integration partners. It can also be used as a stand-alone application under Windows. [humanIT, 2009]

=== View Modes ===

InfoZoom offers three modes for data analysis: wide table, compressed table and overview.

==== Wide Table ====

The wide table looks like a table we know from spreadsheets or database tables. Every attribute is shown as a row and the objects as columns. If the windows is not big enough to show all records or attributes, it's possible to scroll vertically or horizontally.

[[Image:Wide_table.gif|200px]]

==== Compressed Table ====

The compressed table shows all objects pushed together to fit on the screen. Numerical values are represented by the vertical position of dots. The data can be sorted by individual attributes in ascending or descendig order.

[[Image:Compressed_table.gif|200px]]

==== Overview Mode ====

The overview mode allows that the content of each attributes row are sorted independently. The identical values are placed together in a cell. The width of the cell represents the frequency of this value.

[[Image:Overview_mode.gif|200px]]

=== Filter ===

The user can search for data or find patterns in a dataset by using filters. It is possible to look for a specific value or value range on an attribute.

=== Derived Attribute ===

Attributes and derived atrributes can be combined by the user. The new value is calculated from the values of one or two already existing attributes.

=== Graphics Report ===

Graphic Reports can be created with different styles, e.g. Pie, Donut, Bar, Horiz Bar, Line, Area, Point, Bubble, Volume, ...

[[Image:Chart.png|200px]]

== Use ==

InfoZoom is often used for Visual Data Mining (VDM), a process which aims at the recognition of patterns in data by an human expert. VDM makes use of an technique called focus+context. Here, it's possible for the expert to show focused and contextual information at the same time. [Kort, 2004]

Infozoom can be used for a wide range of areas, such as:
* Ad hoc evaluation
* Data cleansing
* Data selection
* Data management
* Data format verification
* Data migration
* Data plausibility
* Data quality
* Data checking
* Gap analysis

== Example ==
An example of a special Version of InfoZoom called 'InfoZoom JApp', which is used to present data on the internet or intranet, can be viewed at the InfoZoome homepage: http://www.infozoom.com/files/japp/bank/enu/index.html

== References ==

[humanIT, 2009] Author unknown, InfoZoom. humanIT Software GmbH. Created at: 2009. Retrieved at: November 4, 2009. http://infozoom.com/244/-/product.html

[humanIT, 2006] Author unknown, InfoZoom. humanIT Software GmbH. Retrieved at: October 30, 2006.

[Kort, 2004] Alexander Kort. Visual Data Mining and Zoomable Interfaces. In ''Proceedings of the 9th international conference on Intelligent user interface''. pages 274-276, New York, NY, 2004. ACM Press

[Mark et al, 2003] Gloria Mark, Keri Carpenter, Alfred Kobsa. Are There Benefits in Seeing Double? A Study of Collaborative Information Visualization. In ''CHI '03 extended abstracts on Human factors in computing systems'', pages 840-841, Irvine, CA, April 2003. ACM Press

[Spenke, 2000] Michael Spenke and Christian Beilken. InfoZoom - Analysing Formula One Racing Results With an Interactive Data Mining and Visualisation Tool. In ''Second Conference on Data Mining 2000'', pages 1-11, Cambridge, UK. Created at: July 2000, Retrieved at: November 6, 2009. http://www.ifs.tuwien.ac.at/~silvia/wien/vu-infovis/articles/spenke00infozoom.pdf

[Wittenburg et al, 2001] Kent Wittenburg, Tom Lanning, Michael Heinrichs, Michael Stanton. Parallel bargrams for consumer-based information exploration and choice. In ''Proceedings of the 14th annual ACM symposium on User interface software and technology'', pages 51-60, Waltham, MA, November 2001. ACM Press

[Xie, 2006] Zaixian Xie, Review on InfoZoom. Worcester Polytechnic Insitute: Course Data Visualization. Created at: February 1, 2006. Retrieved at: November 6, 2009. http://users.wpi.edu/~xiezx/courses/cs525d/infozoom/infozoom.htm

Teaching talk:TUW - UE InfoVis WS 2009/10 - Gruppe 06 - Aufgabe 1

2009-11-17T00:29:15Z

UE-InfoVis0910 0507049:

'''vorläufige Bewertung: 5 Punkte'''

Begründung:

'''Drag and Drop'''

* Definition als solche Kennzeichnen
* Artikel CPOF ist 1:1 aus wikipedia rauskopiert ohne Zitat.
* Auch die Passage über lookmark ist 1:1 aus dem Paper kopiert.

'''InfoZoom'''

* Fehlende Kennzeichnung der Textstellen als Zitate.
* Der Part, der als Definition gekennzeichnet ist, ist keine Definition.

[[User:Katharina-Anna Wendelin|Katharina-Anna Wendelin]] 00:12, 17 November 2009 

'''''TODO:'''''

'''Drag and Drop'''

* Definition als solche Kennzeichnen
::'''DONE'''
* Artikel CPOF ist 1:1 aus wikipedia rauskopiert ohne Zitat.
::'''DONE'''
* Auch die Passage über lookmark ist 1:1 aus dem Paper kopiert.
::'''ist eig als zitat gekennzeichnet. muss da sonst noch was gemacht werden?'''

'''InfoZoom'''

* Fehlende Kennzeichnung der Textstellen als Zitate.
* Der Part, der als Definition gekennzeichnet ist, ist keine Definition.

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 01 - Aufgabe 1 - Drag and Drop

2009-11-17T00:16:00Z

UE-InfoVis0910 0507049:

==Definition==
[[Image:800px-Drag-and-drop-en.svg.png|200px|thumb|Dragging files to a folder]]
{{Quotation|In computer graphical user interfaces, drag-and-drop is the action of (or support for the action of) clicking on a virtual object and dragging it to a different location or onto another virtual object. In general, it can be used to invoke many kinds of actions, or create various types of associations between two abstract objects |[Wikipedia, 2009].
}}

==History==
The first drag & drop implementation for Windows was a shareware program called Aporia by Jeffrey Greenberg in 1988 under Windows 2.0, and later commercialized as WinTools. This program elaborated the single icon on the Macintosh that supported drag & drop, the trash icon. In Aporia/WinTools all icons had functions that could be obtained by double clicking the left mouse button, by clicking on the right mouse button, or by dragging onto one of several functional icons, such as printing, copying, viewing, and other actions. If an icon was double-clicked on and ran a program, the icon changed to indicate that a program was running, and if it was then dragged to the trash, the program was exited.

Subsequently numerous other competitors provided drag & drop desktop replacements to the standard Windows interface including the Norton Desktop, Xerox, NewWave, and Central Point. In Windows 95, Microsoft prevented developers from taking over the desktop and released a drag & drop model of their own.

==Technical Overview==

A drag and drop transaction consists of the following actions:

*A user presses and holds BTransfer, usually mouse button 2, over a source object starting a drag transaction. The application owning that object is the initiator of the drag. The current pointer is replaced by a drag icon-a picture representing the item being dragged.
*The user moves the pointer. From now until a drop occurs, the drag icon replaces the mouse pointer.
*The user drops the object, usually by releasing the mouse button.

Locations on the screen that can accept drops are drop sites, and the application owning that drop site is the destination or receiver.

The drag icon can be dropped anywhere on the screen. However, only certain widgets have registered themselves as drop sites and are able to process the drop.

The receiver application usually performs some action on the information represented by the dragged icon. The initiator application may also perform some action based on the results of a drag transaction.

A drop can be between applications or within the same application. An application can be both source and destination of a drop, source only, destination only, or not participate in drag and drop at all.

The user can request help about a drop site, if available, by dragging to the drop site, and pressing KHelp (usually F1).

The user can cancel the drag at any time by pressing KCancel, usually Escape. [The Santa Cruz Operation, 1996]

==Drag & Drop in Information Visualization==
=== Use in Common Applications ===
The most common uses of Drag and Drop are
*changing the point of view in visualisation data For example:
** An application where you can see an overview of a map: by draging on the map and moving around you change the view position. By releasing the button the new view on the data and in most cases completely different to the output before.
* order visualisation data For Example:
** Picture Application where you order the sequenz of a slide show
** When you are cleaning up your Desktop by draging folders around

===Command Post of the Future (CPOF)===

[[Image:Cpof_rev2.jpg|150px|thumb|CPOF]]

The United States Army's Command Post of the Future (CPOF) is a C2 software system that allows commanders to maintain topsight over the battlefield; collaborate with superiors, peers and subordinates over live data; and communicate their intent.

All visual elements in CPOF are interactive via drag-and-drop gestures. Users can drag data-elements and annotation from any visualization framework into any other (i.e., from a chart to a table), which reveal different data-attributes in context depending on the visualization used. Most data-elements can be grouped and nested via drag-and-drop to form associations that remain with the data in all of its views.Drag-and-drop composition on live visualizations is CPOF's primary mechanism for editing data values, such as locations on a map or tasks on a schedule (for example, moving an event-icon on a map changes the lat/lon values of that event in the shared repository; moving a task icon on a schedule changes its time-based values in the shared repository).
The results of editing gestures are conveyed in real-time to all observers and users of a visualization; when one user moves an event on a map, for example, that event-icon moves on all maps and shared views, such that all users see its new location immediately. Data inputs from warfighters are conveyed to all collaborators as the "natural" result of a drop-gesture in-situ, requiring no explicit publishing mechanism. [Wikipedia: Command Post of the Future, 2009]

===A Drag-and-Drop Strategy for Labeling Photos===

[[Image:Clipboard01.jpg|150px|thumb|Figure 1. US Map with City Names]]

[[Image:Clipboard03.jpg|150px|thumb|Figure 2. Hyperbolic Tree]]

[[Image:Clipboard02.jpg|150px|thumb|Figure 3. LifeLines Medical Patient History]]

Annotation of photos is a variation on previously explored problems such as annotation on maps in which the challenge is to place city, state, river, or lake labels close to the features. There is a long history of work on this problem, but new possibilities emerge because of the dynamics of the computer screen (Figure 1).
However, annotation is usually seen as an authoring process conducted by specialists and users only chose whether to show or hide annotations. Variations on annotation also come from the placement of labels on markers in information visualization tasks such as in tree structures, such in the hyperbolic tree (Figure 2) or in medical histories, such as LifeLines (Figure 3).

Previous work on annotation focused on writing programs to make label placements that reduced overlaps, but there are many situations in which it is helpful for users to place labels manually, much like post-it notes, on documents, photos, maps, diagrams, webpages, etc. Annotation of paper and electronic documents by hand is also a much-studied topic with continuing innovations.
While many systems allow notes to be placed on a document or object, the demands of annotating personal photo libraries are worthy of special study. We believe that personal photo libraries are a special case because users are concentrating on the photos (and may have a low interested in the underlying technology), are concerned about the social aspects of sharing photos, and are intermittent users. They seek enjoyment and have little patience for form filling or data entry. [Shneiderman and Kang, 2000]

===Lookmark: A 2.5D Web Information Visualization System===
[[Image:Clipboard04.jpg|150px|thumb|Lookmark user interface screenshot]]

Lookmarks are thumbnails of existing web pages that can be arranged within a 2.5-dimensional space, just like documents can be arranged on a normal desk. The Lookmark system offers the user the opportunity of taking individual web pages and structuring and managing them within a 2.5-dimensional space. In Lookmark both standard devices, mouse and keyboard, can be used. Mouse handling is limited to single click, double click and drag-and-drop. The meaning of mouse events depends on the context of the object that receives the event:
* Thumbnails. With a single mouse click one can add resp. delete the clicked thumbnail to resp. from the current selection. At the same time the name of the corresponding web page is displayed in the status bar of the user interface. By double clicking on a specific thumbnail, one can open the corresponding web page in the associated Web-browser. By using drag-and-drop one can move a thumbnail along the horizontal and depth dimension (X- and Z-axis).
* Groups of thumbnails. Thumbnails in a group are handled like single thumbnails. Groups of thumbnails can be moved simultaneously by dragging the group label.
* Selections. Dragging a thumbnail of a selection moves all selected thumbnails. A selection can be dissolved by clicking somewhere in the manipulation panel. [Breiteneder et al., 2002]

==References==
[Wikipedia: Drag-and-drop, 2009] Drag-and-drop, Wikipedia, Created at: November 5, 2009 (last change), Retrieved at: November 6, 2009, http://en.wikipedia.org/wiki/Drag_and_drop

[The Santa Cruz Operation, 1994-1996] The Santa Cruz Operation, 1994-1996. Motif Programmer's Guide. http://www.s-and-b.ru/syshlp/motif_guide/MotifProgGuide/TOC.html

[Wikipedia: Command Post of the Future, 2009] The United States Army's Command Post of the Future (CPOF), Wikipedia, Created at: July 6, 2009, Retrieved at: November 6, 2009, http://en.wikipedia.org/wiki/Command_Post_of_the_Future

[General Dynamics C4 System, 2007] General Dynamics C4 Systems, 2007, http://www.gdc4s.com/content/detail.cfm?item=2a58f8e2-ef2b-4bb1-9251-42ee4961dd7f

[Shneiderman and Kang, 2000] Ben Shneiderman and Hyunmo Kang, Dept. of Computer Science, Human-Computer Interaction Laboratory, Institute for Advanced Computer Studies & Institute for Systems Research University of Maryland. A Drag-and-Drop Strategy for Labeling Photos, Created at: April 29, 2000. Retrieved at: November 3, 2009. http://hdl.handle.net/1903/1068

[Breiteneder et al., 2002] Christian Breiteneder, Horst Eidenberger, Geert Fiedler and Markus Raab. Vienna University of Technology, Institute of Software Technology and Interactive Systems. A 2.5D Web Information Visualization System. Created at: July 24, 2002. Retrieved at: November 3, 2009. http://www.ims.tuwien.ac.at/media/documents/publications/eurasia2002.pdf

Teaching talk:TUW - UE InfoVis WS 2007/08 - Gruppe 01 - Aufgabe 1 - Drag and Drop

2009-11-17T00:14:01Z

UE-InfoVis0910 0507049:

Ich denke hier sollte Drag and Drop auch im Kontext der Informationsvisualisierung beschrieben werden.

Zum Beispiel:
*Panning mittels DnD wie zB in Google Maps
*Direct Manipulation: Ändern der Visualisierung zugrundeliegenden Daten mittels DnD, zB: verschieben von Aktivitäten in einem Projektplanungstool
*Position eines visuellen Elements ändern (ohne die Daten selbst zu ändern) um die Visualisierung zu manuell zu verändern...hier fällt mir im Moment leider kein konkretes Beispiel ein.

Was meint ihr?

ja sicher, nur was hat Drag & Drop schon viel mit Visualisierung zu tun? Maximal dann wenn ich Informationen interaktiv einblenden/ausblenden/ändern will. Der Ansatz den ich hier gefunden habe ist aber "nur" technischer Natur und sollte auf das Wesentliche gekürzt werden falls wir brauchbare Informationen in die andere Richtung haben.

== ok ==

ja, du hast recht.

für die paar punkte muss man sich wohl nicht zuviel arbeit antun.

== Begründungen der Änderungen der Gruppe 6, 2009/10 ==
* Einleitungssatz hat gefehlt
* Referenzen waren nicht korrekt formatiert.
* Referenzenlink aktualisiert.
* Referenzen ans Artikelende verschoben.
* Use in Common Applications hinzugefügt, um auch auf den alltäglichen Gebrauch von Drag and Dop einzugehen.
* Bild bei der Einleitung hinzugefügt (mit Quellenangabe).

* Definition als solche gekennzeichnet, CPOF Absatz Zitatkennzeichnung hinzugefügt

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 01 - Aufgabe 1 - Drag and Drop

2009-11-17T00:12:20Z

UE-InfoVis0910 0507049:

[[Image:800px-Drag-and-drop-en.svg.png|200px|thumb|Dragging files to a folder]]
==Definition==
{{Quotation|In computer graphical user interfaces, drag-and-drop is the action of (or support for the action of) clicking on a virtual object and dragging it to a different location or onto another virtual object. In general, it can be used to invoke many kinds of actions, or create various types of associations between two abstract objects |[Wikipedia, 2009].
}}

==History==
The first drag & drop implementation for Windows was a shareware program called Aporia by Jeffrey Greenberg in 1988 under Windows 2.0, and later commercialized as WinTools. This program elaborated the single icon on the Macintosh that supported drag & drop, the trash icon. In Aporia/WinTools all icons had functions that could be obtained by double clicking the left mouse button, by clicking on the right mouse button, or by dragging onto one of several functional icons, such as printing, copying, viewing, and other actions. If an icon was double-clicked on and ran a program, the icon changed to indicate that a program was running, and if it was then dragged to the trash, the program was exited.

Subsequently numerous other competitors provided drag & drop desktop replacements to the standard Windows interface including the Norton Desktop, Xerox, NewWave, and Central Point. In Windows 95, Microsoft prevented developers from taking over the desktop and released a drag & drop model of their own.

==Technical Overview==

A drag and drop transaction consists of the following actions:

*A user presses and holds BTransfer, usually mouse button 2, over a source object starting a drag transaction. The application owning that object is the initiator of the drag. The current pointer is replaced by a drag icon-a picture representing the item being dragged.
*The user moves the pointer. From now until a drop occurs, the drag icon replaces the mouse pointer.
*The user drops the object, usually by releasing the mouse button.

Locations on the screen that can accept drops are drop sites, and the application owning that drop site is the destination or receiver.

The drag icon can be dropped anywhere on the screen. However, only certain widgets have registered themselves as drop sites and are able to process the drop.

The receiver application usually performs some action on the information represented by the dragged icon. The initiator application may also perform some action based on the results of a drag transaction.

A drop can be between applications or within the same application. An application can be both source and destination of a drop, source only, destination only, or not participate in drag and drop at all.

The user can request help about a drop site, if available, by dragging to the drop site, and pressing KHelp (usually F1).

The user can cancel the drag at any time by pressing KCancel, usually Escape. [The Santa Cruz Operation, 1996]

==Drag & Drop in Information Visualization==
=== Use in Common Applications ===
The most common uses of Drag and Drop are
*changing the point of view in visualisation data For example:
** An application where you can see an overview of a map: by draging on the map and moving around you change the view position. By releasing the button the new view on the data and in most cases completely different to the output before.
* order visualisation data For Example:
** Picture Application where you order the sequenz of a slide show
** When you are cleaning up your Desktop by draging folders around

===Command Post of the Future (CPOF)===

[[Image:Cpof_rev2.jpg|150px|thumb|CPOF]]

The United States Army's Command Post of the Future (CPOF) is a C2 software system that allows commanders to maintain topsight over the battlefield; collaborate with superiors, peers and subordinates over live data; and communicate their intent.

All visual elements in CPOF are interactive via drag-and-drop gestures. Users can drag data-elements and annotation from any visualization framework into any other (i.e., from a chart to a table), which reveal different data-attributes in context depending on the visualization used. Most data-elements can be grouped and nested via drag-and-drop to form associations that remain with the data in all of its views.Drag-and-drop composition on live visualizations is CPOF's primary mechanism for editing data values, such as locations on a map or tasks on a schedule (for example, moving an event-icon on a map changes the lat/lon values of that event in the shared repository; moving a task icon on a schedule changes its time-based values in the shared repository).
The results of editing gestures are conveyed in real-time to all observers and users of a visualization; when one user moves an event on a map, for example, that event-icon moves on all maps and shared views, such that all users see its new location immediately. Data inputs from warfighters are conveyed to all collaborators as the "natural" result of a drop-gesture in-situ, requiring no explicit publishing mechanism. [Wikipedia: Command Post of the Future, 2009]

===A Drag-and-Drop Strategy for Labeling Photos===

[[Image:Clipboard01.jpg|150px|thumb|Figure 1. US Map with City Names]]

[[Image:Clipboard03.jpg|150px|thumb|Figure 2. Hyperbolic Tree]]

[[Image:Clipboard02.jpg|150px|thumb|Figure 3. LifeLines Medical Patient History]]

Annotation of photos is a variation on previously explored problems such as annotation on maps in which the challenge is to place city, state, river, or lake labels close to the features. There is a long history of work on this problem, but new possibilities emerge because of the dynamics of the computer screen (Figure 1).
However, annotation is usually seen as an authoring process conducted by specialists and users only chose whether to show or hide annotations. Variations on annotation also come from the placement of labels on markers in information visualization tasks such as in tree structures, such in the hyperbolic tree (Figure 2) or in medical histories, such as LifeLines (Figure 3).

Previous work on annotation focused on writing programs to make label placements that reduced overlaps, but there are many situations in which it is helpful for users to place labels manually, much like post-it notes, on documents, photos, maps, diagrams, webpages, etc. Annotation of paper and electronic documents by hand is also a much-studied topic with continuing innovations.
While many systems allow notes to be placed on a document or object, the demands of annotating personal photo libraries are worthy of special study. We believe that personal photo libraries are a special case because users are concentrating on the photos (and may have a low interested in the underlying technology), are concerned about the social aspects of sharing photos, and are intermittent users. They seek enjoyment and have little patience for form filling or data entry. [Shneiderman and Kang, 2000]

===Lookmark: A 2.5D Web Information Visualization System===
[[Image:Clipboard04.jpg|150px|thumb|Lookmark user interface screenshot]]

Lookmarks are thumbnails of existing web pages that can be arranged within a 2.5-dimensional space, just like documents can be arranged on a normal desk. The Lookmark system offers the user the opportunity of taking individual web pages and structuring and managing them within a 2.5-dimensional space. In Lookmark both standard devices, mouse and keyboard, can be used. Mouse handling is limited to single click, double click and drag-and-drop. The meaning of mouse events depends on the context of the object that receives the event:
* Thumbnails. With a single mouse click one can add resp. delete the clicked thumbnail to resp. from the current selection. At the same time the name of the corresponding web page is displayed in the status bar of the user interface. By double clicking on a specific thumbnail, one can open the corresponding web page in the associated Web-browser. By using drag-and-drop one can move a thumbnail along the horizontal and depth dimension (X- and Z-axis).
* Groups of thumbnails. Thumbnails in a group are handled like single thumbnails. Groups of thumbnails can be moved simultaneously by dragging the group label.
* Selections. Dragging a thumbnail of a selection moves all selected thumbnails. A selection can be dissolved by clicking somewhere in the manipulation panel. [Breiteneder et al., 2002]

==References==
[Wikipedia: Drag-and-drop, 2009] Drag-and-drop, Wikipedia, Created at: November 5, 2009 (last change), Retrieved at: November 6, 2009, http://en.wikipedia.org/wiki/Drag_and_drop

[The Santa Cruz Operation, 1994-1996] The Santa Cruz Operation, 1994-1996. Motif Programmer's Guide. http://www.s-and-b.ru/syshlp/motif_guide/MotifProgGuide/TOC.html

[Wikipedia: Command Post of the Future, 2009] The United States Army's Command Post of the Future (CPOF), Wikipedia, Created at: July 6, 2009, Retrieved at: November 6, 2009, http://en.wikipedia.org/wiki/Command_Post_of_the_Future

[General Dynamics C4 System, 2007] General Dynamics C4 Systems, 2007, http://www.gdc4s.com/content/detail.cfm?item=2a58f8e2-ef2b-4bb1-9251-42ee4961dd7f

[Shneiderman and Kang, 2000] Ben Shneiderman and Hyunmo Kang, Dept. of Computer Science, Human-Computer Interaction Laboratory, Institute for Advanced Computer Studies & Institute for Systems Research University of Maryland. A Drag-and-Drop Strategy for Labeling Photos, Created at: April 29, 2000. Retrieved at: November 3, 2009. http://hdl.handle.net/1903/1068

[Breiteneder et al., 2002] Christian Breiteneder, Horst Eidenberger, Geert Fiedler and Markus Raab. Vienna University of Technology, Institute of Software Technology and Interactive Systems. A 2.5D Web Information Visualization System. Created at: July 24, 2002. Retrieved at: November 3, 2009. http://www.ims.tuwien.ac.at/media/documents/publications/eurasia2002.pdf

Teaching:TUW - UE InfoVis WS 2007/08 - Gruppe 01 - Aufgabe 1 - Drag and Drop

2009-11-17T00:04:19Z

UE-InfoVis0910 0507049:

[[Image:800px-Drag-and-drop-en.svg.png|200px|thumb|Dragging files to a folder]]
{{Quotation|In computer graphical user interfaces, drag-and-drop is the action of (or support for the action of) clicking on a virtual object and dragging it to a different location or onto another virtual object. In general, it can be used to invoke many kinds of actions, or create various types of associations between two abstract objects |[Wikipedia, 2009].
}}

==History==
The first drag & drop implementation for Windows was a shareware program called Aporia by Jeffrey Greenberg in 1988 under Windows 2.0, and later commercialized as WinTools. This program elaborated the single icon on the Macintosh that supported drag & drop, the trash icon. In Aporia/WinTools all icons had functions that could be obtained by double clicking the left mouse button, by clicking on the right mouse button, or by dragging onto one of several functional icons, such as printing, copying, viewing, and other actions. If an icon was double-clicked on and ran a program, the icon changed to indicate that a program was running, and if it was then dragged to the trash, the program was exited.

Subsequently numerous other competitors provided drag & drop desktop replacements to the standard Windows interface including the Norton Desktop, Xerox, NewWave, and Central Point. In Windows 95, Microsoft prevented developers from taking over the desktop and released a drag & drop model of their own.

==Technical Overview==

A drag and drop transaction consists of the following actions:

*A user presses and holds BTransfer, usually mouse button 2, over a source object starting a drag transaction. The application owning that object is the initiator of the drag. The current pointer is replaced by a drag icon-a picture representing the item being dragged.
*The user moves the pointer. From now until a drop occurs, the drag icon replaces the mouse pointer.
*The user drops the object, usually by releasing the mouse button.

Locations on the screen that can accept drops are drop sites, and the application owning that drop site is the destination or receiver.

The drag icon can be dropped anywhere on the screen. However, only certain widgets have registered themselves as drop sites and are able to process the drop.

The receiver application usually performs some action on the information represented by the dragged icon. The initiator application may also perform some action based on the results of a drag transaction.

A drop can be between applications or within the same application. An application can be both source and destination of a drop, source only, destination only, or not participate in drag and drop at all.

The user can request help about a drop site, if available, by dragging to the drop site, and pressing KHelp (usually F1).

The user can cancel the drag at any time by pressing KCancel, usually Escape. [The Santa Cruz Operation, 1996]

==Drag & Drop in Information Visualization==
=== Use in Common Applications ===
The most common uses of Drag and Drop are
*changing the point of view in visualisation data For example:
** An application where you can see an overview of a map: by draging on the map and moving around you change the view position. By releasing the button the new view on the data and in most cases completely different to the output before.
* order visualisation data For Example:
** Picture Application where you order the sequenz of a slide show
** When you are cleaning up your Desktop by draging folders around

===Command Post of the Future (CPOF)===

[[Image:Cpof_rev2.jpg|150px|thumb|CPOF]]

The United States Army's Command Post of the Future (CPOF) is a C2 software system that allows commanders to maintain topsight over the battlefield; collaborate with superiors, peers and subordinates over live data; and communicate their intent.

All visual elements in CPOF are interactive via drag-and-drop gestures. Users can drag data-elements and annotation from any visualization framework into any other (i.e., from a chart to a table), which reveal different data-attributes in context depending on the visualization used. Most data-elements can be grouped and nested via drag-and-drop to form associations that remain with the data in all of its views.Drag-and-drop composition on live visualizations is CPOF's primary mechanism for editing data values, such as locations on a map or tasks on a schedule (for example, moving an event-icon on a map changes the lat/lon values of that event in the shared repository; moving a task icon on a schedule changes its time-based values in the shared repository).
The results of editing gestures are conveyed in real-time to all observers and users of a visualization; when one user moves an event on a map, for example, that event-icon moves on all maps and shared views, such that all users see its new location immediately. Data inputs from warfighters are conveyed to all collaborators as the "natural" result of a drop-gesture in-situ, requiring no explicit publishing mechanism.

===A Drag-and-Drop Strategy for Labeling Photos===

[[Image:Clipboard01.jpg|150px|thumb|Figure 1. US Map with City Names]]

[[Image:Clipboard03.jpg|150px|thumb|Figure 2. Hyperbolic Tree]]

[[Image:Clipboard02.jpg|150px|thumb|Figure 3. LifeLines Medical Patient History]]

Annotation of photos is a variation on previously explored problems such as annotation on maps in which the challenge is to place city, state, river, or lake labels close to the features. There is a long history of work on this problem, but new possibilities emerge because of the dynamics of the computer screen (Figure 1).
However, annotation is usually seen as an authoring process conducted by specialists and users only chose whether to show or hide annotations. Variations on annotation also come from the placement of labels on markers in information visualization tasks such as in tree structures, such in the hyperbolic tree (Figure 2) or in medical histories, such as LifeLines (Figure 3).

Previous work on annotation focused on writing programs to make label placements that reduced overlaps, but there are many situations in which it is helpful for users to place labels manually, much like post-it notes, on documents, photos, maps, diagrams, webpages, etc. Annotation of paper and electronic documents by hand is also a much-studied topic with continuing innovations.
While many systems allow notes to be placed on a document or object, the demands of annotating personal photo libraries are worthy of special study. We believe that personal photo libraries are a special case because users are concentrating on the photos (and may have a low interested in the underlying technology), are concerned about the social aspects of sharing photos, and are intermittent users. They seek enjoyment and have little patience for form filling or data entry. [Shneiderman and Kang, 2000]

===Lookmark: A 2.5D Web Information Visualization System===
[[Image:Clipboard04.jpg|150px|thumb|Lookmark user interface screenshot]]

Lookmarks are thumbnails of existing web pages that can be arranged within a 2.5-dimensional space, just like documents can be arranged on a normal desk. The Lookmark system offers the user the opportunity of taking individual web pages and structuring and managing them within a 2.5-dimensional space. In Lookmark both standard devices, mouse and keyboard, can be used. Mouse handling is limited to single click, double click and drag-and-drop. The meaning of mouse events depends on the context of the object that receives the event:
* Thumbnails. With a single mouse click one can add resp. delete the clicked thumbnail to resp. from the current selection. At the same time the name of the corresponding web page is displayed in the status bar of the user interface. By double clicking on a specific thumbnail, one can open the corresponding web page in the associated Web-browser. By using drag-and-drop one can move a thumbnail along the horizontal and depth dimension (X- and Z-axis).
* Groups of thumbnails. Thumbnails in a group are handled like single thumbnails. Groups of thumbnails can be moved simultaneously by dragging the group label.
* Selections. Dragging a thumbnail of a selection moves all selected thumbnails. A selection can be dissolved by clicking somewhere in the manipulation panel. [Breiteneder et al., 2002]

==References==
[Wikipedia: Drag-and-drop, 2009] Drag-and-drop, Wikipedia, Created at: November 5, 2009 (last change), Retrieved at: November 6, 2009, http://en.wikipedia.org/wiki/Drag_and_drop

[The Santa Cruz Operation, 1994-1996] The Santa Cruz Operation, 1994-1996. Motif Programmer's Guide. http://www.s-and-b.ru/syshlp/motif_guide/MotifProgGuide/TOC.html

[Wikipedia: Command Post of the Future, 2009] The United States Army's Command Post of the Future (CPOF), Wikipedia, Created at: July 6, 2009, Retrieved at: November 6, 2009, http://en.wikipedia.org/wiki/Command_Post_of_the_Future

[General Dynamics C4 System, 2007] General Dynamics C4 Systems, 2007, http://www.gdc4s.com/content/detail.cfm?item=2a58f8e2-ef2b-4bb1-9251-42ee4961dd7f

[Shneiderman and Kang, 2000] Ben Shneiderman and Hyunmo Kang, Dept. of Computer Science, Human-Computer Interaction Laboratory, Institute for Advanced Computer Studies & Institute for Systems Research University of Maryland. A Drag-and-Drop Strategy for Labeling Photos, Created at: April 29, 2000. Retrieved at: November 3, 2009. http://hdl.handle.net/1903/1068

[Breiteneder et al., 2002] Christian Breiteneder, Horst Eidenberger, Geert Fiedler and Markus Raab. Vienna University of Technology, Institute of Software Technology and Interactive Systems. A 2.5D Web Information Visualization System. Created at: July 24, 2002. Retrieved at: November 3, 2009. http://www.ims.tuwien.ac.at/media/documents/publications/eurasia2002.pdf

File talk:Clipboard04.jpg

2009-11-06T22:53:43Z

UE-InfoVis0910 0507049: New page: == Begründungen der Änderungen der Gruppe 6, 2009/10 == * Copyrightstatus überarbeitet * Quelle formatiert, erweitert, überprüft

== Begründungen der Änderungen der Gruppe 6, 2009/10 ==
* Copyrightstatus überarbeitet
* Quelle formatiert, erweitert, überprüft

File talk:Clipboard02.jpg

2009-11-06T22:52:32Z

UE-InfoVis0910 0507049: New page: == Begründungen der Änderungen der Gruppe 6, 2009/10 == * Copyrightstatus und Zusammenfassung überarbeitet * Quelle formatiert, erweitert, überprüft * aktueller funktionierender Link ...

== Begründungen der Änderungen der Gruppe 6, 2009/10 ==
* Copyrightstatus und Zusammenfassung überarbeitet
* Quelle formatiert, erweitert, überprüft
* aktueller funktionierender Link der Quelle hinzugefügt (auf die Seite die von DRUM erwünscht wird)

File:Clipboard02.jpg

2009-11-06T22:51:54Z

UE-InfoVis0910 0507049:

== Summary ==
LifeLines Medical Patient History
== Copyright status ==
Protected by copyright, with all rights reserved by DRUM and the creator.
== Source ==
:[Shneiderman and Kang, 2000] Ben Shneiderman and Hyunmo Kang, Dept. of Computer Science, Human-Computer Interaction Laboratory, Institute for Advanced Computer Studies & Institute for Systems Research University of Maryland. A Drag-and-Drop Strategy for Labeling Photos, Created at: April 29, 2000. Retrieved at: November 3, 2009. http://hdl.handle.net/1903/1068

File talk:Clipboard01.jpg

2009-11-06T22:51:34Z

UE-InfoVis0910 0507049:

File talk:Clipboard03.jpg

2009-11-06T22:51:17Z

File:Clipboard03.jpg

2009-11-06T22:50:48Z

UE-InfoVis0910 0507049:

== Summary ==
Hyperbolic Tree
== Copyright status ==
Protected by copyright, with all rights reserved by DRUM and the creator.
== Source ==

:[Shneiderman and Kang, 2000] Ben Shneiderman and Hyunmo Kang, Dept. of Computer Science, Human-Computer Interaction Laboratory, Institute for Advanced Computer Studies & Institute for Systems Research University of Maryland. A Drag-and-Drop Strategy for Labeling Photos, Created at: April 29, 2000. Retrieved at: November 3, 2009. http://hdl.handle.net/1903/1068

File:Clipboard01.jpg

2009-11-06T22:50:11Z

UE-InfoVis0910 0507049:

== Summary ==
US Map with City Names
== Copyright status ==
Protected by copyright, with all rights reserved by DRUM and the creator.
== Source ==
:[Shneiderman and Kang, 2000] Ben Shneiderman and Hyunmo Kang, Dept. of Computer Science, Human-Computer Interaction Laboratory, Institute for Advanced Computer Studies & Institute for Systems Research University of Maryland. A Drag-and-Drop Strategy for Labeling Photos, Created at: April 29, 2000. Retrieved at: November 3, 2009. http://hdl.handle.net/1903/1068

File talk:Clipboard01.jpg

2009-11-06T22:49:54Z

File talk:Cpof rev2.jpg

2009-11-06T22:46:52Z

UE-InfoVis0910 0507049: New page: == Begründungen der Änderungen der Gruppe 6, 2009/10 == * Copyrightstatus und Zusammenfassung überarbeitet * Quelle formatiert, erweitert, überprüft

== Begründungen der Änderungen der Gruppe 6, 2009/10 ==
* Copyrightstatus und Zusammenfassung überarbeitet
* Quelle formatiert, erweitert, überprüft

File talk:800px-Drag-and-drop-en.svg.png

2009-11-06T22:46:02Z

UE-InfoVis0910 0507049: New page: == Begründungen der Änderungen der Gruppe 6, 2009/10 == * Copyrightstatus und Zusammenfassung überarbeitet * Quelle formatiert, erweitert, überprüft

== Begründungen der Änderungen der Gruppe 6, 2009/10 ==
* Copyrightstatus und Zusammenfassung überarbeitet
* Quelle formatiert, erweitert, überprüft

File talk:Chart.png

2009-11-06T22:43:26Z

UE-InfoVis0910 0507049: New page: == Begründungen der Änderungen der Gruppe 6, 2009/10 == * Copyrightstatus überarbeitet * Quelle formatiert, erweitert, überprüft * Deutsche Überschriften entfernt und durch englische...

== Begründungen der Änderungen der Gruppe 6, 2009/10 ==
* Copyrightstatus überarbeitet
* Quelle formatiert, erweitert, überprüft
* Deutsche Überschriften entfernt und durch englische ersetzt

File talk:Overview mode.gif

2009-11-06T22:41:19Z

== Begründungen der Änderungen der Gruppe 6, 2009/10 ==
* Copyrightstatus überarbeitet
* Quelle formatiert, erweitert, überprüft
* Deutsche Überschriften entfernt und durch englische ersetzt

File talk:Compressed table.gif

2009-11-06T22:40:48Z

== Begründungen der Änderungen der Gruppe 6, 2009/10 ==
* Copyrightstatus überarbeitet
* Quelle formatiert, erweitert, überprüft
* Deutsche Überschriften entfernt und durch englische ersetzt

File talk:Wide table.gif

2009-11-06T22:40:04Z

== Begründungen der Änderungen der Gruppe 6, 2009/10 ==
* Copyrightstatus überarbeitet
* Quelle formatiert, erweitert, überprüft
* Deutsche Überschriften entfernt und durch englische ersetzt

File talk:Software architecture.gif

2009-11-06T22:38:54Z

UE-InfoVis0910 0507049: New page: == Begründungen der Änderungen der Gruppe 6, 2009/10 == * Copyrightstatus überarbeitet * Quelle formatiert, erweitert, überprüft

== Begründungen der Änderungen der Gruppe 6, 2009/10 ==
* Copyrightstatus überarbeitet
* Quelle formatiert, erweitert, überprüft

Teaching talk:TUW - UE InfoVis WS 2006/07 - Gruppe 03 - Aufgabe 1 - InfoZoom

2009-11-06T22:36:53Z

UE-InfoVis0910 0507049:

==Begründungen der Änderungen der Gruppe 6, 2009/10==
* Einheitliche Formatierung (Überschriften, etc.)
* Genauere Beschreibung
* Angabe der derzeitigen aktuellen Programmversion
* Software Architektur genauer beschrieben und Grafik zur Übersicht hinzugefügt
* Beschreibung für welchen Gebrauch InfoZoom geegnet ist (Aufzählung)
* Beispiel hinzugefügt, bei der die Webapplication von InfoZoom betrachtet werden kann
* Bessere englische Formulierung: Verwendung der Passiv-Formulierung und korrekte Präposition (search for statt search after)

* Referenzen: Verweis auf neue Homepage, Verweise auf alte gelöscht (da nicht mehr vorhanden), Formatierung

Teaching:TUW - UE InfoVis WS 2006/07 - Gruppe 03 - Aufgabe 1 - InfoZoom

2009-11-06T22:35:09Z

UE-InfoVis0910 0507049:

InfoZoom is a computer application, developed by the company humanIT, a spin-off of Fraunhofer Society and subsidiary company of proALPHA Software AG, for analyzing and displaying large amounts of data in an easy-to-understand format.

== History ==

InfoZoom evolved from another system called FOCUS, a focus+context table layout [Kort, 2004]. 
The current and newest version is InfoZoom V6.0.

== Description ==

=== Overview ===

Primarily, InfoZoom was developed for manipulating tables. By default it uses parallel bargrams for larger sizes of data sets and special focus+context tables for smaller ones [Wittenburg et al, 2001]. So it is possible to present information in table or distribution oriented formats.

When displaying relational data tables, InfoZoom uses one row for each record. This data can be sorted sequential, hierarchical or in any other way the user wants it to be sorted. If necessary, the user can "zoom" into the information. This happens for example by doubleclicking on attribute values or sets/ranges of values [Mark et al, 2003]. This "zooming" can also be done by selecting columns of a row interactively and then promoting them into qualified records. All other records except those marked as qualified records are hidden instantly, enabling a "zoomed" view on the information.

{{Quotation|The primary interactions supported in InfoZoom are simple selection and filtering, accomplished with a single mouse click on a value bin. Interesting graphical renderings of values are included. Animation is used to transition between set sizes.| [Wittenburg et al, 2001]}}
[[Image:Software_architecture.gif|200px|thumb|software architecture of InfoZoom V6.0]]
=== Data Source & Compatibility ===

With its versatility and open architecture for quick and easy OEM installation based on commonly used industry standards (ODBC, OLE DB, OLE DB for OLAP, COM, ActiveX) and native interfaces (proALPHA, SAP, Lotus Notes, etc.), InfoZoom offers a major advantage for integration partners. It can also be used as a stand-alone application under Windows. [humanIT, 2009]

=== View Modes ===

InfoZoom offers three modes for data analysis: wide table, compressed table and overview.

==== Wide Table ====

The wide table looks like a table we know from spreadsheets or database tables. Every attribute is shown as a row and the objects as columns. If the windows is not big enough to show all records or attributes, it's possible to scroll vertically or horizontally.

[[Image:Wide_table.gif|200px]]

==== Compressed Table ====

The compressed table shows all objects pushed together to fit on the screen. Numerical values are represented by the vertical position of dots. The data can be sorted by individual attributes in ascending or descendig order.

[[Image:Compressed_table.gif|200px]]

==== Overview Mode ====

The overview mode allows that the content of each attributes row are sorted independently. The identical values are placed together in a cell. The width of the cell represents the frequency of this value.

[[Image:Overview_mode.gif|200px]]

=== Filter ===

The user can search for data or find patterns in a dataset by using filters. It is possible to look for a specific value or value range on an attribute.

=== Derived Attribute ===

Attributes and derived atrributes can be combined by the user. The new value is calculated from the values of one or two already existing attributes.

=== Graphics Report ===

Graphic Reports can be created with different styles, e.g. Pie, Donut, Bar, Horiz Bar, Line, Area, Point, Bubble, Volume, ...

[[Image:Chart.png|200px]]

== Use ==

InfoZoom is often used for Visual Data Mining (VDM), a process which aims at the recognition of patterns in data by an human expert. VDM makes use of an technique called focus+context. Here, it's possible for the expert to show focused and contextual information at the same time. [Kort, 2004]

Infozoom can be used for a wide range of areas, such as:
* Ad hoc evaluation
* Data cleansing
* Data selection
* Data management
* Data format verification
* Data migration
* Data plausibility
* Data quality
* Data checking
* Gap analysis

== Example ==
An example of a special Version of InfoZoom called 'InfoZoom JApp', which is used to present data on the internet or intranet, can be viewed at the InfoZoome homepage: http://www.infozoom.com/files/japp/bank/enu/index.html

== References ==

[humanIT, 2009] Author unknown, InfoZoom. humanIT Software GmbH. Created at: 2009. Retrieved at: November 4, 2009. http://infozoom.com/244/-/product.html

[humanIT, 2006] Author unknown, InfoZoom. humanIT Software GmbH. Retrieved at: October 30, 2006.

[Kort, 2004] Alexander Kort. Visual Data Mining and Zoomable Interfaces. In ''Proceedings of the 9th international conference on Intelligent user interface''. pages 274-276, New York, NY, 2004. ACM Press

[Mark et al, 2003] Gloria Mark, Keri Carpenter, Alfred Kobsa. Are There Benefits in Seeing Double? A Study of Collaborative Information Visualization. In ''CHI '03 extended abstracts on Human factors in computing systems'', pages 840-841, Irvine, CA, April 2003. ACM Press

[Spenke, 2000] Michael Spenke and Christian Beilken. InfoZoom - Analysing Formula One Racing Results With an Interactive Data Mining and Visualisation Tool. In ''Second Conference on Data Mining 2000'', pages 1-11, Cambridge, UK. Created at: July 2000, Retrieved at: November 6, 2009. http://www.ifs.tuwien.ac.at/~silvia/wien/vu-infovis/articles/spenke00infozoom.pdf

[Wittenburg et al, 2001] Kent Wittenburg, Tom Lanning, Michael Heinrichs, Michael Stanton. Parallel bargrams for consumer-based information exploration and choice. In ''Proceedings of the 14th annual ACM symposium on User interface software and technology'', pages 51-60, Waltham, MA, November 2001. ACM Press

[Xie, 2006] Zaixian Xie, Review on InfoZoom. Worcester Polytechnic Insitute: Course Data Visualization. Created at: February 1, 2006. Retrieved at: November 6, 2009. http://users.wpi.edu/~xiezx/courses/cs525d/infozoom/infozoom.htm

File:Software architecture.gif

2009-11-06T22:30:58Z

UE-InfoVis0910 0507049:

== Summary ==
Software architecture of InfoZoom V6.0
== Copyright status ==
Protected by copyright, with all rights reserved by humanIT Software GmbH
== Source ==
[humanIT,2009]humanIT, Created at: 2009. Retrieved at: November 4, 2009, http://infozoom.com/253/-/files/PDF/EN/IZ_Technichal_Datasheet_E_screen_02032009.pdf

File:Overview mode.gif

2009-11-06T22:30:12Z

UE-InfoVis0910 0507049:

== Summary ==
InfoZoom Overview mode
== Copyright status ==
Protected by copyright, with all rights reserved by the creator.
== Source ==
[Spenke, 2000] Michael Spenke and Christian Beilken. InfoZoom - Analysing Formula One Racing Results With an Interactive Data Mining and Visualisation Tool. In ''Second Conference on Data Mining 2000'', pages 1-11, Cambridge, UK. Created at: July 5, 2000. Retrieved at: November 6, 2009. http://www.ifs.tuwien.ac.at/~silvia/wien/vu-infovis/articles/spenke00infozoom.pdf

File:Compressed table.gif

2009-11-06T22:29:18Z

UE-InfoVis0910 0507049:

== Summary ==
InfoZoom Compressed Table mode
== Copyright status ==
Protected by copyright, with all rights reserved by the creator.
== Source ==
[Spenke, 2000] Michael Spenke and Christian Beilken. InfoZoom - Analysing Formula One Racing Results With an Interactive Data Mining and Visualisation Tool. In ''Second Conference on Data Mining 2000'', pages 1-11, Cambridge, UK. Created at: July 5, 2000. Retrieved at: November 6, 2009. http://www.ifs.tuwien.ac.at/~silvia/wien/vu-infovis/articles/spenke00infozoom.pdf

File:Compressed table.gif

2009-11-06T22:25:46Z

UE-InfoVis0910 0507049:

== Summary ==
InfoZoom Compressed Table mode
== Copyright status ==
Protected by copyright, with all rights reserved by the creator.
== Source ==
[Spenke, 2000] Michael Spenke and Christian Beilken. InfoZoom - Analysing Formula One Racing Results With an Interactive Data Mining and Visualisation Tool. In ''Second Conference on Data Mining 2000'', pages 1-11, Cambridge, UK. Created at: July 5, 2000, Retrieved at: November 6, 2009. http://www.ifs.tuwien.ac.at/~silvia/wien/vu-infovis/articles/spenke00infozoom.pdf

File:Wide table.gif

2009-11-06T22:22:55Z

UE-InfoVis0910 0507049:

== Summary ==
InfoZoom Wide Table mode
== Copyright status ==
Protected by copyright, with all rights reserved by the creator.
== Source ==
[Spenke, 2000] Michael Spenke and Christian Beilken. InfoZoom - Analysing Formula One Racing Results With an Interactive Data Mining and Visualisation Tool. In ''Second Conference on Data Mining 2000'', pages 1-11, Cambridge, UK. Created at: July 2000, Retrieved at: November 6, 2009. http://www.ifs.tuwien.ac.at/~silvia/wien/vu-infovis/articles/spenke00infozoom.pdf

Teaching:TUW - UE InfoVis WS 2006/07 - Gruppe 03 - Aufgabe 1 - InfoZoom

2009-11-06T22:21:12Z

UE-InfoVis0910 0507049:

InfoZoom is a computer application, developed by the company humanIT, a spin-off of Fraunhofer Society and subsidiary company of proALPHA Software AG, for analyzing and displaying large amounts of data in an easy-to-understand format.

== History ==

InfoZoom evolved from another system called FOCUS, a focus+context table layout [Kort, 2004]. 
The current and newest version is InfoZoom V6.0.

== Description ==

=== Overview ===

Primarily, InfoZoom was developed for manipulating tables. By default it uses parallel bargrams for larger sizes of data sets and special focus+context tables for smaller ones [Wittenburg et al, 2001]. So it is possible to present information in table or distribution oriented formats.

When displaying relational data tables, InfoZoom uses one row for each record. This data can be sorted sequential, hierarchical or in any other way the user wants it to be sorted. If necessary, the user can "zoom" into the information. This happens for example by doubleclicking on attribute values or sets/ranges of values [Mark et al, 2003]. This "zooming" can also be done by selecting columns of a row interactively and then promoting them into qualified records. All other records except those marked as qualified records are hidden instantly, enabling a "zoomed" view on the information.

{{Quotation|The primary interactions supported in InfoZoom are simple selection and filtering, accomplished with a single mouse click on a value bin. Interesting graphical renderings of values are included. Animation is used to transition between set sizes.| [Wittenburg et al, 2001]}}
[[Image:Software_architecture.gif|200px|thumb|software architecture of InfoZoom V6.0]]
=== Data Source & Compatibility ===

With its versatility and open architecture for quick and easy OEM installation based on commonly used industry standards (ODBC, OLE DB, OLE DB for OLAP, COM, ActiveX) and native interfaces (proALPHA, SAP, Lotus Notes, etc.), InfoZoom offers a major advantage for integration partners. It can also be used as a stand-alone application under Windows. [humanIT, 2009]

=== View Modes ===

InfoZoom offers three modes for data analysis: wide table, compressed table and overview.

==== Wide Table ====

The wide table looks like a table we know from spreadsheets or database tables. Every attribute is shown as a row and the objects as columns. If the windows is not big enough to show all records or attributes, it's possible to scroll vertically or horizontally.

[[Image:Wide_table.gif|200px]]

==== Compressed Table ====

The compressed table shows all objects pushed together to fit on the screen. Numerical values are represented by the vertical position of dots. The data can be sorted by individual attributes in ascending or descendig order.

[[Image:Compressed_table.gif|200px]]

==== Overview Mode ====

The overview mode allows that the content of each attributes row are sorted independently. The identical values are placed together in a cell. The width of the cell represents the frequency of this value.

[[Image:Overview_mode.gif|200px]]

=== Filter ===

The user can search for data or find patterns in a dataset by using filters. It is possible to look for a specific value or value range on an attribute.

=== Derived Attribute ===

Attributes and derived atrributes can be combined by the user. The new value is calculated from the values of one or two already existing attributes.

=== Graphics Report ===

Graphic Reports can be created with different styles, e.g. Pie, Donut, Bar, Horiz Bar, Line, Area, Point, Bubble, Volume, ...

[[Image:Chart.png|200px]]

== Use ==

InfoZoom is often used for Visual Data Mining (VDM), a process which aims at the recognition of patterns in data by an human expert. VDM makes use of an technique called focus+context. Here, it's possible for the expert to show focused and contextual information at the same time. [Kort, 2004]

Infozoom can be used for a wide range of areas, such as:
* Ad hoc evaluation
* Data cleansing
* Data selection
* Data management
* Data format verification
* Data migration
* Data plausibility
* Data quality
* Data checking
* Gap analysis

== Example ==
An example of a special Version of InfoZoom called 'InfoZoom JApp', which is used to present data on the internet or intranet, can be viewed at the InfoZoome homepage: http://www.infozoom.com/files/japp/bank/enu/index.html

== References ==

[humanIT, 2009] Author unknown, InfoZoom. humanIT Software GmbH. Created at: 2009, Retrieved at: November 4 2009. http://infozoom.com/244/-/product.html

[humanIT, 2006] Author unknown, InfoZoom. humanIT Software GmbH. Retrieved at: October 30, 2006.

[Kort, 2004] Alexander Kort. Visual Data Mining and Zoomable Interfaces. In ''Proceedings of the 9th international conference on Intelligent user interface''. pages 274-276, New York, NY, 2004. ACM Press

[Mark et al, 2003] Gloria Mark, Keri Carpenter, Alfred Kobsa. Are There Benefits in Seeing Double? A Study of Collaborative Information Visualization. In ''CHI '03 extended abstracts on Human factors in computing systems'', pages 840-841, Irvine, CA, April 2003. ACM Press

[Spenke, 2000] Michael Spenke and Christian Beilken. InfoZoom - Analysing Formula One Racing Results With an Interactive Data Mining and Visualisation Tool. In ''Second Conference on Data Mining 2000'', pages 1-11, Cambridge, UK, July 2000. http://www.ifs.tuwien.ac.at/~silvia/wien/vu-infovis/articles/spenke00infozoom.pdf

[Wittenburg et al, 2001] Kent Wittenburg, Tom Lanning, Michael Heinrichs, Michael Stanton. Parallel bargrams for consumer-based information exploration and choice. In ''Proceedings of the 14th annual ACM symposium on User interface software and technology'', pages 51-60, Waltham, MA, November 2001. ACM Press

[Xie, 2006] Zaixian Xie, Review on InfoZoom. Worcester Polytechnic Insitute: Course Data Visualization. Created at: February 1, 2006. Retrieved at: October 30, 2006. http://users.wpi.edu/~xiezx/courses/cs525d/infozoom/infozoom.htm

File:Chart.png

2009-11-06T22:20:25Z

UE-InfoVis0910 0507049:

== Summary ==
InfoZoom Graphics Report
== Copyright status ==
Protected by copyright, with all rights reserved by the creator.
== Source ==
[Xie, 2006] Zaixian Xie, Review on InfoZoom. Worcester Polytechnic Insitute: Course Data Visualization. Created at: February 1, 2006. Retrieved at: November 6, 2009. http://users.wpi.edu/~xiezx/courses/cs525d/infozoom/infozoom.htm

File:Software architecture.gif

2009-11-06T22:19:20Z

UE-InfoVis0910 0507049:

== Summary ==
Software architecture of InfoZoom V6.0
== Copyright status ==
Protected by copyright, with all rights reserved by humanIT Software GmbH
== Source ==
[humanIT,2009]humanIT, Created at: 2009, Retrieved at: November 4, 2009, http://infozoom.com/253/-/files/PDF/EN/IZ_Technichal_Datasheet_E_screen_02032009.pdf

File:Chart.png

2009-11-06T22:18:34Z

UE-InfoVis0910 0507049:

== Summary ==
InfoZoom Graphics Report
== Copyright status ==
Protected by copyright, with all rights reserved by the creator.
== Source ==
[Xie, 2006] Zaixian Xie, Review on InfoZoom. Worcester Polytechnic Insitute: Course Data Visualization. Created at: February 1, 2006. Retrieved at: October 30, 2006. http://users.wpi.edu/~xiezx/courses/cs525d/infozoom/infozoom.htm

File:Overview mode.gif

2009-11-06T22:14:31Z

UE-InfoVis0910 0507049:

== Summary ==
InfoZoom Overview mode
== Copyright status ==
Protected by copyright, with all rights reserved by the creator.
== Source ==
[Spenke, 2000] Michael Spenke and Christian Beilken. InfoZoom - Analysing Formula One Racing Results With an Interactive Data Mining and Visualisation Tool. In ''Second Conference on Data Mining 2000'', pages 1-11, Cambridge, UK, July 2000. http://www.ifs.tuwien.ac.at/~silvia/wien/vu-infovis/articles/spenke00infozoom.pdf

File:Compressed table.gif

2009-11-06T22:13:49Z

UE-InfoVis0910 0507049:

== Summary ==
InfoZoom Compressed Table mode
== Copyright status ==
Protected by copyright, with all rights reserved by the creator.
== Source ==
[Spenke, 2000] Michael Spenke and Christian Beilken. InfoZoom - Analysing Formula One Racing Results With an Interactive Data Mining and Visualisation Tool. In ''Second Conference on Data Mining 2000'', pages 1-11, Cambridge, UK, July 2000. http://www.ifs.tuwien.ac.at/~silvia/wien/vu-infovis/articles/spenke00infozoom.pdf

File:Wide table.gif

2009-11-06T22:11:24Z

UE-InfoVis0910 0507049:

== Summary ==
InfoZoom Wide Table mode
== Copyright status ==
Protected by copyright, with all rights reserved by the creator.
== Source ==
[Spenke, 2000] Michael Spenke and Christian Beilken. InfoZoom - Analysing Formula One Racing Results With an Interactive Data Mining and Visualisation Tool. In ''Second Conference on Data Mining 2000'', pages 1-11, Cambridge, UK, July 2000. http://www.ifs.tuwien.ac.at/~silvia/wien/vu-infovis/articles/spenke00infozoom.pdf

File:Wide table.gif

2009-11-06T22:10:37Z

UE-InfoVis0910 0507049:

== Summary ==
InfoZoom Wide Table mode
== Copyright-Status ==
Protected by copyright, with all rights reserved by the creator.
== Source ==
[Spenke, 2000] Michael Spenke and Christian Beilken. InfoZoom - Analysing Formula One Racing Results With an Interactive Data Mining and Visualisation Tool. In ''Second Conference on Data Mining 2000'', pages 1-11, Cambridge, UK, July 2000. http://www.ifs.tuwien.ac.at/~silvia/wien/vu-infovis/articles/spenke00infozoom.pdf

File:Software architecture.gif

2009-11-06T22:05:12Z

UE-InfoVis0910 0507049:

== Summary ==
Software architecture of InfoZoom V6.0
== Copyright status ==
Protected by copyright, with all rights reserved by humanIT Software GmbH
== Source ==
[humanIT,2009]humanIT, Created at: 2009, Retrieved at: November 04, 2009, http://infozoom.com/253/-/files/PDF/EN/IZ_Technichal_Datasheet_E_screen_02032009.pdf

Teaching talk:TUW - UE InfoVis WS 2007/08 - Gruppe 01 - Aufgabe 1 - Drag and Drop

2009-11-06T21:55:28Z

UE-InfoVis0910 0507049: