InfoVis:Wiki - User contributions [en]

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

2005-12-21T09:51:01Z

UE-InfoVis0506 0057001:

== Group 7 ==

Josef Froschauer 
Thomas Lehrer 
Erwin Starl 
Seung-bin Yim 

== Task ==

Create a tool to analyze a web server log file on user behaviour.

== Implementation ==

The current version uses a randomized data creation routine to populate the web log.
Every web page has a list of "LineObjects", i.e. lines of the log file, which belong to this particular resource. This line contains the following information: Browser, operating system, date, weekday, country of origin and, if available, referer.

Often used outside referers (pages from other sites) are displayed on the left pane, all other pages on the right side. Each page is represented by a dot with relative size and each connection (referer) is shown by a triangle, pointing to the target page. Within each dot an arc displays the time this page has been looked at (if available), of course also only a relative value.

== Things to try ==

* Clicking on a browser, operating system or weekday check box reduces or increases the displayed data set. Numbers next to the settings change accordingly. 
* Clicking on a web page in net view also updates these numbers: The time lens and filters show the number of accesses to this resource. Releasing the mouse button resets that view. 
* Clicking on the Time Lense currently only zooms in on that year.

== Things to wait for ==

* Advanced Time Lense with Range Slider
* Filtering by world map
* Import
* Placing algorithm

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

2005-12-21T09:45:33Z

UE-InfoVis0506 0057001:

==Topic==
Webserver Logfile Visualization

==Area of Application==

===Analysis of Application Area===

====General Description====
Webservers typically generate logfiles containing huge amounts of information on page accesses, used client software, type of access, and many more. Analysis tools like for example AWStats try to make use of this information and present simple statistics mostly in form of tables or simple bar graphs. Unfortunately, they are mostly very limited and "low-level" regarding their information representation. More interesting questions like user behavior in combination with site structure, dead ends, changes in behavior regarding to time (evolution), typical behavioral patterns, finding groups of users that share similar behavioral patterns, site entry points, or intrusion detection cannot be answered by using similar tools. For being able to deal with this kind of topics, more advanced visual tools are needed that unveil this information. [Behlendorf et al., 2005]

====Special Issues====

There are many different known solutions/methods to visualize Webeserver Logfiles. Most of them make use of simple chart or bar diagrams. The question is, if it is possible to present this huge set of informations in just one diagram, that illustrates all the data in a simple and undastandable way.

===Analysis of the Dataset===

Here is an example of such a logfile entry: [Cooper,2004]

205.218.110.166 - - [08/Dec/1996:15:02:10 -0800] "GET /info/index.html HTTP/1.0" 200 14912 "http://www.yourcompany.com/index.html " "Mozilla/3.0Gold (Win95; I)" "35bebd61b31211cfbdcd00c04fd611cf"

The content of this entry explained, from left to right:

'''"205.218.110.166"''' - - This is the IP address of the machine making a request of your web server - its domain name can be determined in HitList by enabling Reverse DNS lookups, assuming your server hasn't put this information in already - many so, some don't. (if the domain name was in there, you'd see its URL instead of the raw IP). 
This is the Remote hostname or IP number if DNS hostname is not available, or if DNSLookup is Off. 
remotehost is a one-dimensional discreet datatype.[6]

'''"-"''' - this first dash is typically the server's IP address, which most NCSA format servers don't insert by default.

'''"-"''' - this second dash is typically authenticated usernames, which again many NCSA format servers don't insert by default.

'''"[08/Dec/1996:15:02:10 -0800]"''' - This is the date and time of the access, including the offset from Greenwich Mean Time - the latter is the "-800", meaning the web server being accessed is 8 hours ahead of GMT. 
date has seven dimensions in the following format: [day/month/year:hour:minute:second zone]
 
Day: ordinal, 2 digits 
Month: nominal, 3 letters 
year = ordinal, 4 digits 
hour = ordinal, 2 digits 
minute = ordinal, 2 digits 
second = ordinal, 2 digits 
zone = nominal, + or - and 4 digits[6]

'''"GET /info/index.html HTTP/1.0"''' - This is the actual request the visitor's browser made when at your page or server. 
request has three dimensions in the following format: "request method /filename HTTP/version]" 
The request method is nominal. 
The filename is discrete.[6]

'''"HTTP/1.0"''' refers to the protocol and its version, here being version 1.0 of the http protocol. 
The HTTP version is theoretically ordinal. However, so far there exists only version 0.9, 1.0 and the current version 1.0[6]

'''"200"''' - this is the server response code - a "successful" request (meaning the visitor's browser loaded the entire HTML/GIF/JPEG, etc.) generates a response code of 200. Others include:

206 - Partial request successful (not complete)
302 - URL has been redirected to another document
400 - Bad request was made by the client
401 - Authorization is required for this document
403 - Access to this document is forbidden
404 - Document not found
500 - Server internal error
501 - Application method (either GET or POST) is not implemented
503 - Server is out of resources 
status is a one-dimensional nominal datatype.[6]

'''"14912"''' - This is the number of bytes transferred to the client during the visit. Since every request has some response, even erroneous requests will have a non-zero value for this field.
"http://www.yourcompany.com/index.html" - This is the referrer field, or the site the visitor was on immediately prior to making this entry's request - in this case, the person was looking at the index.html (probably the home page) page before going to the /info/index.html page in this entry.
"Mozilla/3.0Gold (Win95; I)" - this is the user-agent field, meaning the actual browser and OS used by the visitor - in this case, Mozilla is Netscape, the next value is the version (here, 3.0Gold), and the final value is the OS it was using (Windows 95). 
Bytes are a one-dimensional ordinal datatype.[6]

Finally, the '''"35bebd61b31211cfbdcd00c04fd611cf"''' is the cookie information, which may or may not be there, depending on whether the webserver used has cookies enabled and whether one was passed from webserver to the visitor's computer.

There are several different specific Logfile Formats, for example: Microsoft IIS 3.0 and 2.0, Microsoft IIS4.0 (W3SVC format), Netscape (NCSA format with/without unique format header), Lotus Domino format, O'Reilly WebSite format...

==Target Group==

===Identifying the Target===
We identified the following Target groups:
#Software Companies: especially those who develop browsers and web based applications
#Web Dsigners
#Administrators
#Advertising Companys
#Web Users

===Special Issues of the Target Group===

Software Companies: In order to optimize their software, they have to explore the user's needs. Logfiles can offer them some useful informations.

For Web Designers it can be helpful to know some facts about their visitors. Logfiles tell them, which browsers they use, when they access the site, traffic, and so on. This Informations allow them to organize the webpage in a convenient and reliable way. It's the same with Web Administrators.

Advertising Companies strive to study user behaviour in order to orientate their adds more effectively.

===Known Solutions / Methods (related to the target group)===
#Radial Tree Viewer
#Anemone
#Internet Cartographer
#WebTracer
#WebHopper
#WebPath
#The Chicago Tribune Website
#Visualizing the online debate on the European Constitution
#Mercator 
...[5]

==Intended Purpose==

===Goals and Objectives===
#Which client software is used, which browsers
#How users behave, in combination with site structure, dead ends, changes in behavior regarding to time.
#Identify groups of users who act in a similar way.
#Identify "hot" topics

===Problems and Tasks to Solve===
- '''Improve the Servers''': Administrators, Web Designers and Software Companies need this information, to improve the Servers. They need to know what people are interested in, if there are special groups, which have similar behavior, navigate to the same themes and in a similar way. What kind of themes are often searched for, and how. With this information, they can help Users to get the things they want faster and easier. They can adapt the Server to the needs of the Users. 
In order to effectively manage a web server, it is necessary to get feedback about the activity and performance of the server as well as any problems that may be occuring 
- '''Adapt Advertising to Users interests''':Advertising Companys can use the information to identify themes and products of interest to a group of users. You get an overview of groups of things people are interessted in. So they can adapt the topics of their advertisement to this information.

==Proposed Design==

===Types of Visualization Applied===

The following techniques will be used:

* Filtering
* Linking
* Detail on Demand
* Range Slider [Ahlberg and Shneiderman, 1994] with Time Lense.

{{quotation |"Overview first, zoom and filter, then details on demand. View relationships and history..." | Visual Information-Seeking Mantra [Shneiderman, 1996] }}

First, the user is presented with a net of accessed web pages and resources. She is able to filter the information using the checkboxes of OS, browser,.. and the Time Lens Range Slider.
When clicking on a resource, the view zooms if necessary and marks all nodes linking to and from this page, image,...

===Visual Mapping===

(Datadimension => Attribute)

The log contains the following information:

IP, date, request, protocol, response code, bytes, referer, user agent, cookie

From a given IP it is possible to determin the country of origin, so IPs are mapped to the world map. <Unknown> will also be listed.

The date is listed on the date lens slider. After choosing a date range the corresponding numbers and entries will change.
Above this date slider the user will find bars of transferred bytes in this date region.

The request is mapped onto the "web site" net in the middle. Further calculation is necessary to match /file/ to /file/index.php and /file/index.php?somesessionid=2139123123.
Only successful requests are listed here (eg response code 200).

If referer is an URL from within the server, the "web site" net draws a connection between the two pages. This connection width is determined by access count and direction (ie more wide at the referer than the target page). If the page is referred from the outside, the referring page is listed on the left hand side panel "external referers"

The user agent is parsed for operating system and browser information. Each is listed on the right with checkboxes, so the user can remove or include certain browsers or OS to the data set.

The number of hits is mapped to the size of the dots in the net view and external referer list.

When following the interaction of users it is possible to estimate a page reading time. This is displayed as arc in each page dot.

===Description of Used Techniques===

===Possibilities of Interaction===

Klicking on a browser, operating system or weekday check box reduces or increases the displayed data set. Numbers next to the settings change accordingly.

Klicking on a web page in net view also updates these numbers: The time lens and filters show the number of accesses to this resource. Marked are other pages which have been visited by users, who have been watching this page. Klicking on a blank spot resets that view.

If the button "filtered list" is pressed, the program produces a list of the webserver log file according to the settings (browser, page, time, os,...)

The "hide media" check box removes, if checked, all images, css and media files from the list, keeping only html, php, ...

===Mockups / Fake Screenshots===

[[Image:Infovis_weblog_fake.png|Screenshot|800px]]

== Resources ==

:[1] [Behlendorf et al., 2005] Brian Behlendorf, Apache HTTP Server Logfiles, Apache HTTP Server Project, Access Date: 17 October 2005, http://httpd.apache.org/docs/1.3/logs.html

:[2] [Cooper, 2004] Colin Cooper, Logfile Definitions and Examples, Intranet Software Solutions (Europe) Limited [ISSEL], Access Date: 17 October 2005, http://www.issel.co.uk/FAQ/logfile_definitions_examples.htm

:[3] [Shneiderman, 1996] Ben Shneiderman (1996), The Eyes Have It: A Task by Data Type Taxonomy for Information Visualizations, In Proceedings of the IEEE Symposium on Visual Languages, pages 336-343, Washington. IEEE Computer Society Press.

:[4] [Ahlberg and Shneiderman, 1994] Christopher Ahlberg and Ben Shneiderman (1994), Visual Information Seeking: Tight Coupling of Dynamic Query Filters with Starfield Displays, In Proceedings of the Conference on Human Factors in Computing Systems (CHI'94), pages 313-317. ACM Press.

:[5] [Visual Complexity] World Wide Web, Access Date: 15 November 2005, http://www.visualcomplexity.com/vc/index.cfm?domain=World%20Wide%20Web

:[6] [2] [Rainer, Karim, Kargl, Akcaglayan, 2005] Rainer Andreas, Karim Muhammad Shuaib, Kargl Horst, Akcaglayan Ali, TUW - UE InfoVis WS 2005/06 - Gruppe G3 - Aufgabe 3, Access Date: 22 November 2005, http://www.infovis-wiki.net/index.php/Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G3_-_Aufgabe_3

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

2005-12-21T09:45:16Z

UE-InfoVis0506 0057001:

== Webserver Logfile Visualization ==

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

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

2005-11-22T11:29:32Z

UE-InfoVis0506 0057001:

==Topic==
Webserver Logfile Visualization

==Area of Application==

===Analysis of Application Area===

====General Description====
Webservers typically generate logfiles containing huge amounts of information on page accesses, used client software, type of access, and many more. Analysis tools like for example AWStats try to make use of this information and present simple statistics mostly in form of tables or simple bar graphs. Unfortunately, they are mostly very limited and "low-level" regarding their information representation. More interesting questions like user behavior in combination with site structure, dead ends, changes in behavior regarding to time (evolution), typical behavioral patterns, finding groups of users that share similar behavioral patterns, site entry points, or intrusion detection cannot be answered by using similar tools. For being able to deal with this kind of topics, more advanced visual tools are needed that unveil this information. [Behlendorf et al., 2005]

====Special Issues====

There are many different known solutions/methods to visualize Webeserver Logfiles. Most of them make use of simple chart or bar diagrams. The question is, if it is possible to present this huge set of informations in just one diagram, that illustrates all the data in a simple and undastandable way.

===Analysis of the Dataset===

Here is an example of such a logfile entry: [Cooper,2004]

205.218.110.166 - - [08/Dec/1996:15:02:10 -0800] "GET /info/index.html HTTP/1.0" 200 14912 "http://www.yourcompany.com/index.html " "Mozilla/3.0Gold (Win95; I)" "35bebd61b31211cfbdcd00c04fd611cf"

The content of this entry explained, from left to right:

'''"205.218.110.166"''' - - This is the IP address of the machine making a request of your web server - its domain name can be determined in HitList by enabling Reverse DNS lookups, assuming your server hasn't put this information in already - many so, some don't. (if the domain name was in there, you'd see its URL instead of the raw IP). 
This is the Remote hostname or IP number if DNS hostname is not available, or if DNSLookup is Off. 
remotehost is a one-dimensional discreet datatype.[6]

'''"-"''' - this first dash is typically the server's IP address, which most NCSA format servers don't insert by default.

'''"-"''' - this second dash is typically authenticated usernames, which again many NCSA format servers don't insert by default.

'''"[08/Dec/1996:15:02:10 -0800]"''' - This is the date and time of the access, including the offset from Greenwich Mean Time - the latter is the "-800", meaning the web server being accessed is 8 hours ahead of GMT. 
date has seven dimensions in the following format: [day/month/year:hour:minute:second zone]
 
Day: ordinal, 2 digits 
Month: nominal, 3 letters 
year = ordinal, 4 digits 
hour = ordinal, 2 digits 
minute = ordinal, 2 digits 
second = ordinal, 2 digits 
zone = nominal, + or - and 4 digits[6]

'''"GET /info/index.html HTTP/1.0"''' - This is the actual request the visitor's browser made when at your page or server. 
request has three dimensions in the following format: "request method /filename HTTP/version]" 
The request method is nominal. 
The filename is discrete.[6]

'''"HTTP/1.0"''' refers to the protocol and its version, here being version 1.0 of the http protocol. 
The HTTP version is theoretically ordinal. However, so far there exists only version 0.9, 1.0 and the current version 1.0[6]

'''"200"''' - this is the server response code - a "successful" request (meaning the visitor's browser loaded the entire HTML/GIF/JPEG, etc.) generates a response code of 200. Others include:

206 - Partial request successful (not complete)
302 - URL has been redirected to another document
400 - Bad request was made by the client
401 - Authorization is required for this document
403 - Access to this document is forbidden
404 - Document not found
500 - Server internal error
501 - Application method (either GET or POST) is not implemented
503 - Server is out of resources 
status is a one-dimensional nominal datatype.[6]

'''"14912"''' - This is the number of bytes transferred to the client during the visit. Since every request has some response, even erroneous requests will have a non-zero value for this field.
"http://www.yourcompany.com/index.html" - This is the referrer field, or the site the visitor was on immediately prior to making this entry's request - in this case, the person was looking at the index.html (probably the home page) page before going to the /info/index.html page in this entry.
"Mozilla/3.0Gold (Win95; I)" - this is the user-agent field, meaning the actual browser and OS used by the visitor - in this case, Mozilla is Netscape, the next value is the version (here, 3.0Gold), and the final value is the OS it was using (Windows 95). 
Bytes are a one-dimensional ordinal datatype.[6]

Finally, the '''"35bebd61b31211cfbdcd00c04fd611cf"''' is the cookie information, which may or may not be there, depending on whether the webserver used has cookies enabled and whether one was passed from webserver to the visitor's computer.

There are several different specific Logfile Formats, for example: Microsoft IIS 3.0 and 2.0, Microsoft IIS4.0 (W3SVC format), Netscape (NCSA format with/without unique format header), Lotus Domino format, O'Reilly WebSite format...

==Target Group==

===Identifying the Target===
We identified the following Target groups:
#Software Companies: especially those who develop browsers and web based applications
#Web Dsigners
#Administrators
#Advertising Companys
#Web Users

===Special Issues of the Target Group===

Software Companies: In order to optimize their software, they have to explore the user's needs. Logfiles can offer them some useful informations.

For Web Designers it can be helpful to know some facts about their visitors. Logfiles tell them, which browsers they use, when they access the site, traffic, and so on. This Informations allow them to organize the webpage in a convenient and reliable way. It's the same with Web Administrators.

Advertising Companies strive to study user behaviour in order to orientate their adds more effectively.

===Known Solutions / Methods (related to the target group)===
#Radial Tree Viewer
#Anemone
#Internet Cartographer
#WebTracer
#WebHopper
#WebPath
#The Chicago Tribune Website
#Visualizing the online debate on the European Constitution
#Mercator 
...[5]

==Intended Purpose==

===Goals and Objectives===
#Which client software is used, which browsers
#How users behave, in combination with site structure, dead ends, changes in behavior regarding to time.
#Identify groups of users who act in a similar way.
#Identify "hot" topics

===Problems and Tasks to Solve===
- '''Improve the Servers''': Administrators, Web Designers and Software Companies need this information, to improve the Servers. They need to know what people are interested in, if there are special groups, which have similar behavior, navigate to the same themes and in a similar way. What kind of themes are often searched for, and how. With this information, they can help Users to get the things they want faster and easier. They can adapt the Server to the needs of the Users. 
In order to effectively manage a web server, it is necessary to get feedback about the activity and performance of the server as well as any problems that may be occuring 
- '''Adapt Advertising to Users interests''':Advertising Companys can use the information to identify themes and products of interest to a group of users. You get an overview of groups of things people are interessted in. So they can adapt the topics of their advertisement to this information.

==Proposed Design==

===Types of Visualization Applied===

The following techniques will be used:

* Filtering
* Linking
* Detail on Demand
* Range Slider [Ahlberg and Shneiderman, 1994] with Time Lense.

{{quotation |"Overview first, zoom and filter, then details on demand. View relationships and history..." | Visual Information-Seeking Mantra [Shneiderman, 1996] }}

First, the user is presented with a net of accessed web pages and resources. She is able to filter the information using the checkboxes of OS, browser,.. and the Time Lens Range Slider.
When clicking on a resource, the view zooms if necessary and marks all nodes linking to and from this page, image,...

===Visual Mapping===

(Datadimension => Attribute)

The log contains the following information:

IP, date, request, protocol, response code, bytes, referer, user agent, cookie

From a given IP it is possible to determin the country of origin, so IPs are mapped to the world map. <Unknown> will also be listed.

The date is listed on the date lens slider. After choosing a date range the corresponding numbers and entries will change.
Above this date slider the user will find bars of transferred bytes in this date region.

The request is mapped onto the "web site" net in the middle. Further calculation is necessary to match /file/ to /file/index.php and /file/index.php?somesessionid=2139123123.
Only successful requests are listed here (eg response code 200).

If referer is an URL from within the server, the "web site" net draws a connection between the two pages. If the page is referred from the outside, the referring page is listed on the left hand side panel "external referers"

The user agent is parsed for operating system and browser information. Each is listed on the right with checkboxes, so the user can remove or include certain browsers or OS to the data set.

The number of hits is mapped to the size of the dots in the net view and external referer list.

When following the interaction of users it is possible to estimate a page reading time. This is displayed as arc in each page dot.

===Description of Used Techniques===

===Possibilities of Interaction===

Klicking on a browser, operating system or weekday check box reduces or increases the displayed data set. Numbers next to the settings change accordingly.

Klicking on a web page in net view also updates these numbers: The time lens and filters show the number of accesses to this resource. Marked are other pages which have been visited by users, who have been watching this page. Klicking on a blank spot resets that view.

If the button "filtered list" is pressed, the program produces a list of the webserver log file according to the settings (browser, page, time, os,...)

The "hide media" check box removes, if checked, all images, css and media files from the list, keeping only html, php, ...

===Mockups / Fake Screenshots===

[[Image:Infovis_weblog_fake.png|Screenshot|800px]]

== Resources ==

:[1] [Behlendorf et al., 2005] Brian Behlendorf, Apache HTTP Server Logfiles, Apache HTTP Server Project, Access Date: 17 October 2005, http://httpd.apache.org/docs/1.3/logs.html

:[2] [Cooper, 2004] Colin Cooper, Logfile Definitions and Examples, Intranet Software Solutions (Europe) Limited [ISSEL], Access Date: 17 October 2005, http://www.issel.co.uk/FAQ/logfile_definitions_examples.htm

:[3] [Shneiderman, 1996] Ben Shneiderman (1996), The Eyes Have It: A Task by Data Type Taxonomy for Information Visualizations, In Proceedings of the IEEE Symposium on Visual Languages, pages 336-343, Washington. IEEE Computer Society Press.

:[4] [Ahlberg and Shneiderman, 1994] Christopher Ahlberg and Ben Shneiderman (1994), Visual Information Seeking: Tight Coupling of Dynamic Query Filters with Starfield Displays, In Proceedings of the Conference on Human Factors in Computing Systems (CHI'94), pages 313-317. ACM Press.

:[5] [Visual Complexity] World Wide Web, Access Date: 15 November 2005, http://www.visualcomplexity.com/vc/index.cfm?domain=World%20Wide%20Web

:[6] [2] [Rainer, Karim, Kargl, Akcaglayan, 2005] Rainer Andreas, Karim Muhammad Shuaib, Kargl Horst, Akcaglayan Ali, TUW - UE InfoVis WS 2005/06 - Gruppe G3 - Aufgabe 3, Access Date: 22 November 2005, http://www.infovis-wiki.net/index.php/Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G3_-_Aufgabe_3

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

2005-11-22T11:05:49Z

UE-InfoVis0506 0057001:

==Topic==
Webserver Logfile Visualization

==Area of Application==

===Analysis of Application Area===

====General Description====
Webservers typically generate logfiles containing huge amounts of information on page accesses, used client software, type of access, and many more. Analysis tools like for example AWStats try to make use of this information and present simple statistics mostly in form of tables or simple bar graphs. Unfortunately, they are mostly very limited and "low-level" regarding their information representation. More interesting questions like user behavior in combination with site structure, dead ends, changes in behavior regarding to time (evolution), typical behavioral patterns, finding groups of users that share similar behavioral patterns, site entry points, or intrusion detection cannot be answered by using similar tools. For being able to deal with this kind of topics, more advanced visual tools are needed that unveil this information. [Behlendorf et al., 2005]

====Special Issues====

There are many different known solutions/methods to visualize Webeserver Logfiles. Most of them make use of simple chart or bar diagrams. The question is, if it is possible to present this huge set of informations in just one diagram, that illustrates all the data in a simple and undastandable way.

===Analysis of the Dataset===

Here is an example of such a logfile entry: [Cooper,2004]

205.218.110.166 - - [08/Dec/1996:15:02:10 -0800] "GET /info/index.html HTTP/1.0" 200 14912 "http://www.yourcompany.com/index.html " "Mozilla/3.0Gold (Win95; I)" "35bebd61b31211cfbdcd00c04fd611cf"

The content of this entry explained, from left to right:

'''"205.218.110.166"''' - - This is the IP address of the machine making a request of your web server - its domain name can be determined in HitList by enabling Reverse DNS lookups, assuming your server hasn't put this information in already - many so, some don't. (if the domain name was in there, you'd see its URL instead of the raw IP). 
This is the Remote hostname or IP number if DNS hostname is not available, or if DNSLookup is Off. 
remotehost is a one-dimensional discreet datatype.[6]

'''"-"''' - this first dash is typically the server's IP address, which most NCSA format servers don't insert by default.

'''"-"''' - this second dash is typically authenticated usernames, which again many NCSA format servers don't insert by default.

'''"[08/Dec/1996:15:02:10 -0800]"''' - This is the date and time of the access, including the offset from Greenwich Mean Time - the latter is the "-800", meaning the web server being accessed is 8 hours ahead of GMT. 
date has seven dimensions in the following format: [day/month/year:hour:minute:second zone]
 
Day: ordinal, 2 digits 
Month: nominal, 3 letters 
year = ordinal, 4 digits 
hour = ordinal, 2 digits 
minute = ordinal, 2 digits 
second = ordinal, 2 digits 
zone = nominal, + or - and 4 digits[6]

'''"GET /info/index.html HTTP/1.0"''' - This is the actual request the visitor's browser made when at your page or server. 
request has three dimensions in the following format: "request method /filename HTTP/version]" 
The request method is nominal. 
The filename is discrete.[6]

'''"HTTP/1.0"''' refers to the protocol and its version, here being version 1.0 of the http protocol. 
The HTTP version is theoretically ordinal. However, so far there exists only version 0.9, 1.0 and the current version 1.0[6]

'''"200"''' - this is the server response code - a "successful" request (meaning the visitor's browser loaded the entire HTML/GIF/JPEG, etc.) generates a response code of 200. Others include:

206 - Partial request successful (not complete)
302 - URL has been redirected to another document
400 - Bad request was made by the client
401 - Authorization is required for this document
403 - Access to this document is forbidden
404 - Document not found
500 - Server internal error
501 - Application method (either GET or POST) is not implemented
503 - Server is out of resources 
status is a one-dimensional nominal datatype.

'''"14912"''' - This is the number of bytes transferred to the client during the visit. Since every request has some response, even erroneous requests will have a non-zero value for this field.
"http://www.yourcompany.com/index.html" - This is the referrer field, or the site the visitor was on immediately prior to making this entry's request - in this case, the person was looking at the index.html (probably the home page) page before going to the /info/index.html page in this entry.
"Mozilla/3.0Gold (Win95; I)" - this is the user-agent field, meaning the actual browser and OS used by the visitor - in this case, Mozilla is Netscape, the next value is the version (here, 3.0Gold), and the final value is the OS it was using (Windows 95). 
bytes is a one-dimensional ordinal datatype.

Finally, the '''"35bebd61b31211cfbdcd00c04fd611cf"''' is the cookie information, which may or may not be there, depending on whether the webserver used has cookies enabled and whether one was passed from webserver to the visitor's computer.

There are several different specific Logfile Formats, for example: Microsoft IIS 3.0 and 2.0, Microsoft IIS4.0 (W3SVC format), Netscape (NCSA format with/without unique format header), Lotus Domino format, O'Reilly WebSite format...

==Target Group==

===Identifying the Target===
We identified the following Target groups:
#Software Companies: especially those who develop browsers and web based applications
#Web Dsigners
#Administrators
#Advertising Companys
#Web Users

===Special Issues of the Target Group===

Software Companies: In order to optimize their software, they have to explore the user's needs. Logfiles can offer them some useful informations.

For Web Designers it can be helpful to know some facts about their visitors. Logfiles tell them, which browsers they use, when they access the site, traffic, and so on. This Informations allow them to organize the webpage in a convenient and reliable way. It's the same with Web Administrators.

Advertising Companies strive to study user behaviour in order to orientate their adds more effectively.

===Known Solutions / Methods (related to the target group)===
#Radial Tree Viewer
#Anemone
#Internet Cartographer
#WebTracer
#WebHopper
#WebPath
#The Chicago Tribune Website
#Visualizing the online debate on the European Constitution
#Mercator 
...[5]

==Intended Purpose==

===Goals and Objectives===
#Which client software is used, which browsers
#How users behave, in combination with site structure, dead ends, changes in behavior regarding to time.
#Identify groups of users who act in a similar way.
#Identify "hot" topics

===Problems and Tasks to Solve===
- '''Improve the Servers''': Administrators, Web Designers and Software Companies need this information, to improve the Servers. They need to know what people are interested in, if there are special groups, which have similar behavior, navigate to the same themes and in a similar way. What kind of themes are often searched for, and how. With this information, they can help Users to get the things they want faster and easier. They can adapt the Server to the needs of the Users. 
In order to effectively manage a web server, it is necessary to get feedback about the activity and performance of the server as well as any problems that may be occuring 
- '''Adapt Advertising to Users interests''':Advertising Companys can use the information to identify themes and products of interest to a group of users. You get an overview of groups of things people are interessted in. So they can adapt the topics of their advertisement to this information.

==Proposed Design==

===Types of Visualization Applied===

The following techniques will be used:

* Filtering
* Linking
* Detail on Demand
* Range Slider [Ahlberg and Shneiderman, 1994] with Time Lense.

{{quotation |"Overview first, zoom and filter, then details on demand. View relationships and history..." | Visual Information-Seeking Mantra [Shneiderman, 1996] }}

First, the user is presented with a net of accessed web pages and resources. She is able to filter the information using the checkboxes of OS, browser,.. and the Time Lens Range Slider.
When clicking on a resource, the view zooms if necessary and marks all nodes linking to and from this page, image,...

===Visual Mapping===

(Datadimension => Attribute)

The log contains the following information:

IP, date, request, protocol, response code, bytes, referer, user agent, cookie

From a given IP it is possible to determin the country of origin, so IPs are mapped to the world map. <Unknown> will also be listed.

The date is listed on the date lens slider. After choosing a date range the corresponding numbers and entries will change.
Above this date slider the user will find bars of transferred bytes in this date region.

The request is mapped onto the "web site" net in the middle. Further calculation is necessary to match /file/ to /file/index.php and /file/index.php?somesessionid=2139123123.
Only successful requests are listed here (eg response code 200).

If referer is an URL from within the server, the "web site" net draws a connection between the two pages. If the page is referred from the outside, the referring page is listed on the left hand side panel "external referers"

The user agent is parsed for operating system and browser information. Each is listed on the right with checkboxes, so the user can remove or include certain browsers or OS to the data set.

The number of hits is mapped to the size of the dots in the net view and external referer list.

When following the interaction of users it is possible to estimate a page reading time. This is displayed as arc in each page dot.

===Description of Used Techniques===

===Possibilities of Interaction===

Klicking on a browser, operating system or weekday check box reduces or increases the displayed data set. Numbers next to the settings change accordingly.

Klicking on a web page in net view also updates these numbers: The time lens and filters show the number of accesses to this resource. Marked are other pages which have been visited by users, who have been watching this page. Klicking on a blank spot resets that view.

If the button "filtered list" is pressed, the program produces a list of the webserver log file according to the settings (browser, page, time, os,...)

The "hide media" check box removes, if checked, all images, css and media files from the list, keeping only html, php, ...

===Mockups / Fake Screenshots===

[[Image:Infovis_weblog_fake.png|Screenshot|800px]]

== Resources ==

:[1] [Behlendorf et al., 2005] Brian Behlendorf, Apache HTTP Server Logfiles, Apache HTTP Server Project, Access Date: 17 October 2005, http://httpd.apache.org/docs/1.3/logs.html

:[2] [Cooper, 2004] Colin Cooper, Logfile Definitions and Examples, Intranet Software Solutions (Europe) Limited [ISSEL], Access Date: 17 October 2005, http://www.issel.co.uk/FAQ/logfile_definitions_examples.htm

:[3] [Shneiderman, 1996] Ben Shneiderman (1996), The Eyes Have It: A Task by Data Type Taxonomy for Information Visualizations, In Proceedings of the IEEE Symposium on Visual Languages, pages 336-343, Washington. IEEE Computer Society Press.

:[4] [Ahlberg and Shneiderman, 1994] Christopher Ahlberg and Ben Shneiderman (1994), Visual Information Seeking: Tight Coupling of Dynamic Query Filters with Starfield Displays, In Proceedings of the Conference on Human Factors in Computing Systems (CHI'94), pages 313-317. ACM Press.

:[5] [Visual Complexity] World Wide Web, Access Date: 15 November 2005, http://www.visualcomplexity.com/vc/index.cfm?domain=World%20Wide%20Web

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

2005-11-22T11:04:14Z

UE-InfoVis0506 0057001:

==Topic==
Webserver Logfile Visualization

==Area of Application==

===Analysis of Application Area===

====General Description====
Webservers typically generate logfiles containing huge amounts of information on page accesses, used client software, type of access, and many more. Analysis tools like for example AWStats try to make use of this information and present simple statistics mostly in form of tables or simple bar graphs. Unfortunately, they are mostly very limited and "low-level" regarding their information representation. More interesting questions like user behavior in combination with site structure, dead ends, changes in behavior regarding to time (evolution), typical behavioral patterns, finding groups of users that share similar behavioral patterns, site entry points, or intrusion detection cannot be answered by using similar tools. For being able to deal with this kind of topics, more advanced visual tools are needed that unveil this information. [Behlendorf et al., 2005]

====Special Issues====

There are many different known solutions/methods to visualize Webeserver Logfiles. Most of them make use of simple chart or bar diagrams. The question is, if it is possible to present this huge set of informations in just one diagram, that illustrates all the data in a simple and undastandable way.

===Analysis of the Dataset===

Here is an example of such a logfile entry: [Cooper,2004]

205.218.110.166 - - [08/Dec/1996:15:02:10 -0800] "GET /info/index.html HTTP/1.0" 200 14912 "http://www.yourcompany.com/index.html " "Mozilla/3.0Gold (Win95; I)" "35bebd61b31211cfbdcd00c04fd611cf"

The content of this entry explained, from left to right:

'''"205.218.110.166"''' - - This is the IP address of the machine making a request of your web server - its domain name can be determined in HitList by enabling Reverse DNS lookups, assuming your server hasn't put this information in already - many so, some don't. (if the domain name was in there, you'd see its URL instead of the raw IP). 
This is the Remote hostname or IP number if DNS hostname is not available, or if DNSLookup is Off. 
remotehost is a one-dimensional discreet datatype.[6]

'''"-"''' - this first dash is typically the server's IP address, which most NCSA format servers don't insert by default.

'''"-"''' - this second dash is typically authenticated usernames, which again many NCSA format servers don't insert by default.

'''"[08/Dec/1996:15:02:10 -0800]"''' - This is the date and time of the access, including the offset from Greenwich Mean Time - the latter is the "-800", meaning the web server being accessed is 8 hours ahead of GMT. 
date has seven dimensions in the following format: [day/month/year:hour:minute:second zone]
 
Day: ordinal, 2 digits 
Month: nominal, 3 letters 
year = ordinal, 4 digits 
hour = ordinal, 2 digits 
minute = ordinal, 2 digits 
second = ordinal, 2 digits 
zone = nominal, + or - and 4 digits[6]

'''"GET /info/index.html HTTP/1.0"''' - This is the actual request the visitor's browser made when at your page or server. 
request has three dimensions in the following format: "request method /filename HTTP/version] 
The request method is nominal. 
The filename is discrete.[6]

'''"HTTP/1.0"''' refers to the protocol and its version, here being version 1.0 of the http protocol. 
The HTTP version is theoretically ordinal. However, so far there exists only version 0.9, 1.0 and the current version 1.0[6]

'''"200"''' - this is the server response code - a "successful" request (meaning the visitor's browser loaded the entire HTML/GIF/JPEG, etc.) generates a response code of 200. Others include:

206 - Partial request successful (not complete)
302 - URL has been redirected to another document
400 - Bad request was made by the client
401 - Authorization is required for this document
403 - Access to this document is forbidden
404 - Document not found
500 - Server internal error
501 - Application method (either GET or POST) is not implemented
503 - Server is out of resources 
status is a one-dimensional nominal datatype.

'''"14912"''' - This is the number of bytes transferred to the client during the visit. Since every request has some response, even erroneous requests will have a non-zero value for this field.
"http://www.yourcompany.com/index.html" - This is the referrer field, or the site the visitor was on immediately prior to making this entry's request - in this case, the person was looking at the index.html (probably the home page) page before going to the /info/index.html page in this entry.
"Mozilla/3.0Gold (Win95; I)" - this is the user-agent field, meaning the actual browser and OS used by the visitor - in this case, Mozilla is Netscape, the next value is the version (here, 3.0Gold), and the final value is the OS it was using (Windows 95).

Finally, the '''"35bebd61b31211cfbdcd00c04fd611cf"''' is the cookie information, which may or may not be there, depending on whether the webserver used has cookies enabled and whether one was passed from webserver to the visitor's computer.

There are several different specific Logfile Formats, for example: Microsoft IIS 3.0 and 2.0, Microsoft IIS4.0 (W3SVC format), Netscape (NCSA format with/without unique format header), Lotus Domino format, O'Reilly WebSite format...

==Target Group==

===Identifying the Target===
We identified the following Target groups:
#Software Companies: especially those who develop browsers and web based applications
#Web Dsigners
#Administrators
#Advertising Companys
#Web Users

===Special Issues of the Target Group===

Software Companies: In order to optimize their software, they have to explore the user's needs. Logfiles can offer them some useful informations.

For Web Designers it can be helpful to know some facts about their visitors. Logfiles tell them, which browsers they use, when they access the site, traffic, and so on. This Informations allow them to organize the webpage in a convenient and reliable way. It's the same with Web Administrators.

Advertising Companies strive to study user behaviour in order to orientate their adds more effectively.

===Known Solutions / Methods (related to the target group)===
#Radial Tree Viewer
#Anemone
#Internet Cartographer
#WebTracer
#WebHopper
#WebPath
#The Chicago Tribune Website
#Visualizing the online debate on the European Constitution
#Mercator 
...[5]

==Intended Purpose==

===Goals and Objectives===
#Which client software is used, which browsers
#How users behave, in combination with site structure, dead ends, changes in behavior regarding to time.
#Identify groups of users who act in a similar way.
#Identify "hot" topics

===Problems and Tasks to Solve===
- '''Improve the Servers''': Administrators, Web Designers and Software Companies need this information, to improve the Servers. They need to know what people are interested in, if there are special groups, which have similar behavior, navigate to the same themes and in a similar way. What kind of themes are often searched for, and how. With this information, they can help Users to get the things they want faster and easier. They can adapt the Server to the needs of the Users. 
In order to effectively manage a web server, it is necessary to get feedback about the activity and performance of the server as well as any problems that may be occuring 
- '''Adapt Advertising to Users interests''':Advertising Companys can use the information to identify themes and products of interest to a group of users. You get an overview of groups of things people are interessted in. So they can adapt the topics of their advertisement to this information.

==Proposed Design==

===Types of Visualization Applied===

The following techniques will be used:

* Filtering
* Linking
* Detail on Demand
* Range Slider [Ahlberg and Shneiderman, 1994] with Time Lense.

{{quotation |"Overview first, zoom and filter, then details on demand. View relationships and history..." | Visual Information-Seeking Mantra [Shneiderman, 1996] }}

First, the user is presented with a net of accessed web pages and resources. She is able to filter the information using the checkboxes of OS, browser,.. and the Time Lens Range Slider.
When clicking on a resource, the view zooms if necessary and marks all nodes linking to and from this page, image,...

===Visual Mapping===

(Datadimension => Attribute)

The log contains the following information:

IP, date, request, protocol, response code, bytes, referer, user agent, cookie

From a given IP it is possible to determin the country of origin, so IPs are mapped to the world map. <Unknown> will also be listed.

The date is listed on the date lens slider. After choosing a date range the corresponding numbers and entries will change.
Above this date slider the user will find bars of transferred bytes in this date region.

The request is mapped onto the "web site" net in the middle. Further calculation is necessary to match /file/ to /file/index.php and /file/index.php?somesessionid=2139123123.
Only successful requests are listed here (eg response code 200).

If referer is an URL from within the server, the "web site" net draws a connection between the two pages. If the page is referred from the outside, the referring page is listed on the left hand side panel "external referers"

The user agent is parsed for operating system and browser information. Each is listed on the right with checkboxes, so the user can remove or include certain browsers or OS to the data set.

The number of hits is mapped to the size of the dots in the net view and external referer list.

When following the interaction of users it is possible to estimate a page reading time. This is displayed as arc in each page dot.

===Description of Used Techniques===

===Possibilities of Interaction===

Klicking on a browser, operating system or weekday check box reduces or increases the displayed data set. Numbers next to the settings change accordingly.

Klicking on a web page in net view also updates these numbers: The time lens and filters show the number of accesses to this resource. Marked are other pages which have been visited by users, who have been watching this page. Klicking on a blank spot resets that view.

If the button "filtered list" is pressed, the program produces a list of the webserver log file according to the settings (browser, page, time, os,...)

The "hide media" check box removes, if checked, all images, css and media files from the list, keeping only html, php, ...

===Mockups / Fake Screenshots===

[[Image:Infovis_weblog_fake.png|Screenshot|800px]]

== Resources ==

:[1] [Behlendorf et al., 2005] Brian Behlendorf, Apache HTTP Server Logfiles, Apache HTTP Server Project, Access Date: 17 October 2005, http://httpd.apache.org/docs/1.3/logs.html

:[2] [Cooper, 2004] Colin Cooper, Logfile Definitions and Examples, Intranet Software Solutions (Europe) Limited [ISSEL], Access Date: 17 October 2005, http://www.issel.co.uk/FAQ/logfile_definitions_examples.htm

:[3] [Shneiderman, 1996] Ben Shneiderman (1996), The Eyes Have It: A Task by Data Type Taxonomy for Information Visualizations, In Proceedings of the IEEE Symposium on Visual Languages, pages 336-343, Washington. IEEE Computer Society Press.

:[4] [Ahlberg and Shneiderman, 1994] Christopher Ahlberg and Ben Shneiderman (1994), Visual Information Seeking: Tight Coupling of Dynamic Query Filters with Starfield Displays, In Proceedings of the Conference on Human Factors in Computing Systems (CHI'94), pages 313-317. ACM Press.

:[5] [Visual Complexity] World Wide Web, Access Date: 15 November 2005, http://www.visualcomplexity.com/vc/index.cfm?domain=World%20Wide%20Web

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

2005-11-22T11:01:24Z

UE-InfoVis0506 0057001:

==Topic==
Webserver Logfile Visualization

==Area of Application==

===Analysis of Application Area===

====General Description====
Webservers typically generate logfiles containing huge amounts of information on page accesses, used client software, type of access, and many more. Analysis tools like for example AWStats try to make use of this information and present simple statistics mostly in form of tables or simple bar graphs. Unfortunately, they are mostly very limited and "low-level" regarding their information representation. More interesting questions like user behavior in combination with site structure, dead ends, changes in behavior regarding to time (evolution), typical behavioral patterns, finding groups of users that share similar behavioral patterns, site entry points, or intrusion detection cannot be answered by using similar tools. For being able to deal with this kind of topics, more advanced visual tools are needed that unveil this information. [Behlendorf et al., 2005]

====Special Issues====

There are many different known solutions/methods to visualize Webeserver Logfiles. Most of them make use of simple chart or bar diagrams. The question is, if it is possible to present this huge set of informations in just one diagram, that illustrates all the data in a simple and undastandable way.

===Analysis of the Dataset===

Here is an example of such a logfile entry: [Cooper,2004]

205.218.110.166 - - [08/Dec/1996:15:02:10 -0800] "GET /info/index.html HTTP/1.0" 200 14912 "http://www.yourcompany.com/index.html " "Mozilla/3.0Gold (Win95; I)" "35bebd61b31211cfbdcd00c04fd611cf"

The content of this entry explained, from left to right:

'''"205.218.110.166"''' - - This is the IP address of the machine making a request of your web server - its domain name can be determined in HitList by enabling Reverse DNS lookups, assuming your server hasn't put this information in already - many so, some don't. (if the domain name was in there, you'd see its URL instead of the raw IP). 
This is the Remote hostname or IP number if DNS hostname is not available, or if DNSLookup is Off. 
remotehost is a one-dimensional discreet datatype.

'''"-"''' - this first dash is typically the server's IP address, which most NCSA format servers don't insert by default.

'''"-"''' - this second dash is typically authenticated usernames, which again many NCSA format servers don't insert by default.

'''"[08/Dec/1996:15:02:10 -0800]"''' - This is the date and time of the access, including the offset from Greenwich Mean Time - the latter is the "-800", meaning the web server being accessed is 8 hours ahead of GMT. 
date has seven dimensions in the following format: [day/month/year:hour:minute:second zone]
 
Day: ordinal, 2 digits 
Month: nominal, 3 letters 
year = ordinal, 4 digits 
hour = ordinal, 2 digits 
minute = ordinal, 2 digits 
second = ordinal, 2 digits 
zone = nominal, + or - and 4 digits

'''"GET /info/index.html HTTP/1.0"''' - This is the actual request the visitor's browser made when at your page or server. 
request has three dimensions in the following format: "request method /filename HTTP/version] 

The request method is nominal.
The filename is discrete.
The HTTP version is theoretically ordinal. However, so far there exists only version 0.9, 1.0 and the current version 1.0

'''"HTTP/1.0"''' refers to the protocol and its version, here being version 1.0 of the http protocol.

'''"200"''' - this is the server response code - a "successful" request (meaning the visitor's browser loaded the entire HTML/GIF/JPEG, etc.) generates a response code of 200. Others include:

206 - Partial request successful (not complete)
302 - URL has been redirected to another document
400 - Bad request was made by the client
401 - Authorization is required for this document
403 - Access to this document is forbidden
404 - Document not found
500 - Server internal error
501 - Application method (either GET or POST) is not implemented
503 - Server is out of resources

'''"14912"''' - This is the number of bytes transferred to the client during the visit. Since every request has some response, even erroneous requests will have a non-zero value for this field.
"http://www.yourcompany.com/index.html" - This is the referrer field, or the site the visitor was on immediately prior to making this entry's request - in this case, the person was looking at the index.html (probably the home page) page before going to the /info/index.html page in this entry.
"Mozilla/3.0Gold (Win95; I)" - this is the user-agent field, meaning the actual browser and OS used by the visitor - in this case, Mozilla is Netscape, the next value is the version (here, 3.0Gold), and the final value is the OS it was using (Windows 95).

Finally, the '''"35bebd61b31211cfbdcd00c04fd611cf"''' is the cookie information, which may or may not be there, depending on whether the webserver used has cookies enabled and whether one was passed from webserver to the visitor's computer.

There are several different specific Logfile Formats, for example: Microsoft IIS 3.0 and 2.0, Microsoft IIS4.0 (W3SVC format), Netscape (NCSA format with/without unique format header), Lotus Domino format, O'Reilly WebSite format...

==Target Group==

===Identifying the Target===
We identified the following Target groups:
#Software Companies: especially those who develop browsers and web based applications
#Web Dsigners
#Administrators
#Advertising Companys
#Web Users

===Special Issues of the Target Group===

Software Companies: In order to optimize their software, they have to explore the user's needs. Logfiles can offer them some useful informations.

For Web Designers it can be helpful to know some facts about their visitors. Logfiles tell them, which browsers they use, when they access the site, traffic, and so on. This Informations allow them to organize the webpage in a convenient and reliable way. It's the same with Web Administrators.

Advertising Companies strive to study user behaviour in order to orientate their adds more effectively.

===Known Solutions / Methods (related to the target group)===
#Radial Tree Viewer
#Anemone
#Internet Cartographer
#WebTracer
#WebHopper
#WebPath
#The Chicago Tribune Website
#Visualizing the online debate on the European Constitution
#Mercator 
...[5]

==Intended Purpose==

===Goals and Objectives===
#Which client software is used, which browsers
#How users behave, in combination with site structure, dead ends, changes in behavior regarding to time.
#Identify groups of users who act in a similar way.
#Identify "hot" topics

===Problems and Tasks to Solve===
- '''Improve the Servers''': Administrators, Web Designers and Software Companies need this information, to improve the Servers. They need to know what people are interested in, if there are special groups, which have similar behavior, navigate to the same themes and in a similar way. What kind of themes are often searched for, and how. With this information, they can help Users to get the things they want faster and easier. They can adapt the Server to the needs of the Users. 
In order to effectively manage a web server, it is necessary to get feedback about the activity and performance of the server as well as any problems that may be occuring 
- '''Adapt Advertising to Users interests''':Advertising Companys can use the information to identify themes and products of interest to a group of users. You get an overview of groups of things people are interessted in. So they can adapt the topics of their advertisement to this information.

==Proposed Design==

===Types of Visualization Applied===

The following techniques will be used:

* Filtering
* Linking
* Detail on Demand
* Range Slider [Ahlberg and Shneiderman, 1994] with Time Lense.

{{quotation |"Overview first, zoom and filter, then details on demand. View relationships and history..." | Visual Information-Seeking Mantra [Shneiderman, 1996] }}

First, the user is presented with a net of accessed web pages and resources. She is able to filter the information using the checkboxes of OS, browser,.. and the Time Lens Range Slider.
When clicking on a resource, the view zooms if necessary and marks all nodes linking to and from this page, image,...

===Visual Mapping===

(Datadimension => Attribute)

The log contains the following information:

IP, date, request, protocol, response code, bytes, referer, user agent, cookie

From a given IP it is possible to determin the country of origin, so IPs are mapped to the world map. <Unknown> will also be listed.

The date is listed on the date lens slider. After choosing a date range the corresponding numbers and entries will change.
Above this date slider the user will find bars of transferred bytes in this date region.

The request is mapped onto the "web site" net in the middle. Further calculation is necessary to match /file/ to /file/index.php and /file/index.php?somesessionid=2139123123.
Only successful requests are listed here (eg response code 200).

If referer is an URL from within the server, the "web site" net draws a connection between the two pages. If the page is referred from the outside, the referring page is listed on the left hand side panel "external referers"

The user agent is parsed for operating system and browser information. Each is listed on the right with checkboxes, so the user can remove or include certain browsers or OS to the data set.

The number of hits is mapped to the size of the dots in the net view and external referer list.

When following the interaction of users it is possible to estimate a page reading time. This is displayed as arc in each page dot.

===Description of Used Techniques===

===Possibilities of Interaction===

Klicking on a browser, operating system or weekday check box reduces or increases the displayed data set. Numbers next to the settings change accordingly.

Klicking on a web page in net view also updates these numbers: The time lens and filters show the number of accesses to this resource. Marked are other pages which have been visited by users, who have been watching this page. Klicking on a blank spot resets that view.

If the button "filtered list" is pressed, the program produces a list of the webserver log file according to the settings (browser, page, time, os,...)

The "hide media" check box removes, if checked, all images, css and media files from the list, keeping only html, php, ...

===Mockups / Fake Screenshots===

[[Image:Infovis_weblog_fake.png|Screenshot|800px]]

== Resources ==

:[1] [Behlendorf et al., 2005] Brian Behlendorf, Apache HTTP Server Logfiles, Apache HTTP Server Project, Access Date: 17 October 2005, http://httpd.apache.org/docs/1.3/logs.html

:[2] [Cooper, 2004] Colin Cooper, Logfile Definitions and Examples, Intranet Software Solutions (Europe) Limited [ISSEL], Access Date: 17 October 2005, http://www.issel.co.uk/FAQ/logfile_definitions_examples.htm

:[3] [Shneiderman, 1996] Ben Shneiderman (1996), The Eyes Have It: A Task by Data Type Taxonomy for Information Visualizations, In Proceedings of the IEEE Symposium on Visual Languages, pages 336-343, Washington. IEEE Computer Society Press.

:[4] [Ahlberg and Shneiderman, 1994] Christopher Ahlberg and Ben Shneiderman (1994), Visual Information Seeking: Tight Coupling of Dynamic Query Filters with Starfield Displays, In Proceedings of the Conference on Human Factors in Computing Systems (CHI'94), pages 313-317. ACM Press.

:[5] [Visual Complexity] World Wide Web, Access Date: 15 November 2005, http://www.visualcomplexity.com/vc/index.cfm?domain=World%20Wide%20Web

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

2005-11-22T10:59:31Z

UE-InfoVis0506 0057001:

==Topic==
Webserver Logfile Visualization

==Area of Application==

===Analysis of Application Area===

====General Description====
Webservers typically generate logfiles containing huge amounts of information on page accesses, used client software, type of access, and many more. Analysis tools like for example AWStats try to make use of this information and present simple statistics mostly in form of tables or simple bar graphs. Unfortunately, they are mostly very limited and "low-level" regarding their information representation. More interesting questions like user behavior in combination with site structure, dead ends, changes in behavior regarding to time (evolution), typical behavioral patterns, finding groups of users that share similar behavioral patterns, site entry points, or intrusion detection cannot be answered by using similar tools. For being able to deal with this kind of topics, more advanced visual tools are needed that unveil this information. [Behlendorf et al., 2005]

====Special Issues====

There are many different known solutions/methods to visualize Webeserver Logfiles. Most of them make use of simple chart or bar diagrams. The question is, if it is possible to present this huge set of informations in just one diagram, that illustrates all the data in a simple and undastandable way.

===Analysis of the Dataset===

Here is an example of such a logfile entry: [Cooper,2004]

205.218.110.166 - - [08/Dec/1996:15:02:10 -0800] "GET /info/index.html HTTP/1.0" 200 14912 "http://www.yourcompany.com/index.html " "Mozilla/3.0Gold (Win95; I)" "35bebd61b31211cfbdcd00c04fd611cf"

The content of this entry explained, from left to right:

'''"205.218.110.166"''' - - This is the IP address of the machine making a request of your web server - its domain name can be determined in HitList by enabling Reverse DNS lookups, assuming your server hasn't put this information in already - many so, some don't. (if the domain name was in there, you'd see its URL instead of the raw IP). 
This is the Remote hostname or IP number if DNS hostname is not available, or if DNSLookup is Off. 
remotehost is a one-dimensional discreet datatype.

'''"-"''' - this first dash is typically the server's IP address, which most NCSA format servers don't insert by default.

'''"-"''' - this second dash is typically authenticated usernames, which again many NCSA format servers don't insert by default.

'''"[08/Dec/1996:15:02:10 -0800]"''' - This is the date and time of the access, including the offset from Greenwich Mean Time - the latter is the "-800", meaning the web server being accessed is 8 hours ahead of GMT. 
date has seven dimensions in the following format: [day/month/year:hour:minute:second zone]
 
Day: ordinal, 2 digits 
Month: nominal, 3 letters 
year = ordinal, 4 digits 
hour = ordinal, 2 digits 
minute = ordinal, 2 digits 
second = ordinal, 2 digits 
zone = nominal, + or - and 4 digits

'''"GET /info/index.html HTTP/1.0"''' - This is the actual request the visitor's browser made when at your page or server.

'''"HTTP/1.0"''' refers to the protocol and its version, here being version 1.0 of the http protocol.

'''"200"''' - this is the server response code - a "successful" request (meaning the visitor's browser loaded the entire HTML/GIF/JPEG, etc.) generates a response code of 200. Others include:

206 - Partial request successful (not complete)
302 - URL has been redirected to another document
400 - Bad request was made by the client
401 - Authorization is required for this document
403 - Access to this document is forbidden
404 - Document not found
500 - Server internal error
501 - Application method (either GET or POST) is not implemented
503 - Server is out of resources

'''"14912"''' - This is the number of bytes transferred to the client during the visit. Since every request has some response, even erroneous requests will have a non-zero value for this field.
"http://www.yourcompany.com/index.html" - This is the referrer field, or the site the visitor was on immediately prior to making this entry's request - in this case, the person was looking at the index.html (probably the home page) page before going to the /info/index.html page in this entry.
"Mozilla/3.0Gold (Win95; I)" - this is the user-agent field, meaning the actual browser and OS used by the visitor - in this case, Mozilla is Netscape, the next value is the version (here, 3.0Gold), and the final value is the OS it was using (Windows 95).

Finally, the '''"35bebd61b31211cfbdcd00c04fd611cf"''' is the cookie information, which may or may not be there, depending on whether the webserver used has cookies enabled and whether one was passed from webserver to the visitor's computer.

There are several different specific Logfile Formats, for example: Microsoft IIS 3.0 and 2.0, Microsoft IIS4.0 (W3SVC format), Netscape (NCSA format with/without unique format header), Lotus Domino format, O'Reilly WebSite format...

==Target Group==

===Identifying the Target===
We identified the following Target groups:
#Software Companies: especially those who develop browsers and web based applications
#Web Dsigners
#Administrators
#Advertising Companys
#Web Users

===Special Issues of the Target Group===

Software Companies: In order to optimize their software, they have to explore the user's needs. Logfiles can offer them some useful informations.

For Web Designers it can be helpful to know some facts about their visitors. Logfiles tell them, which browsers they use, when they access the site, traffic, and so on. This Informations allow them to organize the webpage in a convenient and reliable way. It's the same with Web Administrators.

Advertising Companies strive to study user behaviour in order to orientate their adds more effectively.

===Known Solutions / Methods (related to the target group)===
#Radial Tree Viewer
#Anemone
#Internet Cartographer
#WebTracer
#WebHopper
#WebPath
#The Chicago Tribune Website
#Visualizing the online debate on the European Constitution
#Mercator 
...[5]

==Intended Purpose==

===Goals and Objectives===
#Which client software is used, which browsers
#How users behave, in combination with site structure, dead ends, changes in behavior regarding to time.
#Identify groups of users who act in a similar way.
#Identify "hot" topics

===Problems and Tasks to Solve===
- '''Improve the Servers''': Administrators, Web Designers and Software Companies need this information, to improve the Servers. They need to know what people are interested in, if there are special groups, which have similar behavior, navigate to the same themes and in a similar way. What kind of themes are often searched for, and how. With this information, they can help Users to get the things they want faster and easier. They can adapt the Server to the needs of the Users. 
In order to effectively manage a web server, it is necessary to get feedback about the activity and performance of the server as well as any problems that may be occuring 
- '''Adapt Advertising to Users interests''':Advertising Companys can use the information to identify themes and products of interest to a group of users. You get an overview of groups of things people are interessted in. So they can adapt the topics of their advertisement to this information.

==Proposed Design==

===Types of Visualization Applied===

The following techniques will be used:

* Filtering
* Linking
* Detail on Demand
* Range Slider [Ahlberg and Shneiderman, 1994] with Time Lense.

{{quotation |"Overview first, zoom and filter, then details on demand. View relationships and history..." | Visual Information-Seeking Mantra [Shneiderman, 1996] }}

First, the user is presented with a net of accessed web pages and resources. She is able to filter the information using the checkboxes of OS, browser,.. and the Time Lens Range Slider.
When clicking on a resource, the view zooms if necessary and marks all nodes linking to and from this page, image,...

===Visual Mapping===

(Datadimension => Attribute)

The log contains the following information:

IP, date, request, protocol, response code, bytes, referer, user agent, cookie

From a given IP it is possible to determin the country of origin, so IPs are mapped to the world map. <Unknown> will also be listed.

The date is listed on the date lens slider. After choosing a date range the corresponding numbers and entries will change.
Above this date slider the user will find bars of transferred bytes in this date region.

The request is mapped onto the "web site" net in the middle. Further calculation is necessary to match /file/ to /file/index.php and /file/index.php?somesessionid=2139123123.
Only successful requests are listed here (eg response code 200).

If referer is an URL from within the server, the "web site" net draws a connection between the two pages. If the page is referred from the outside, the referring page is listed on the left hand side panel "external referers"

The user agent is parsed for operating system and browser information. Each is listed on the right with checkboxes, so the user can remove or include certain browsers or OS to the data set.

The number of hits is mapped to the size of the dots in the net view and external referer list.

When following the interaction of users it is possible to estimate a page reading time. This is displayed as arc in each page dot.

===Description of Used Techniques===

===Possibilities of Interaction===

Klicking on a browser, operating system or weekday check box reduces or increases the displayed data set. Numbers next to the settings change accordingly.

Klicking on a web page in net view also updates these numbers: The time lens and filters show the number of accesses to this resource. Marked are other pages which have been visited by users, who have been watching this page. Klicking on a blank spot resets that view.

If the button "filtered list" is pressed, the program produces a list of the webserver log file according to the settings (browser, page, time, os,...)

The "hide media" check box removes, if checked, all images, css and media files from the list, keeping only html, php, ...

===Mockups / Fake Screenshots===

[[Image:Infovis_weblog_fake.png|Screenshot|800px]]

== Resources ==

:[1] [Behlendorf et al., 2005] Brian Behlendorf, Apache HTTP Server Logfiles, Apache HTTP Server Project, Access Date: 17 October 2005, http://httpd.apache.org/docs/1.3/logs.html

:[2] [Cooper, 2004] Colin Cooper, Logfile Definitions and Examples, Intranet Software Solutions (Europe) Limited [ISSEL], Access Date: 17 October 2005, http://www.issel.co.uk/FAQ/logfile_definitions_examples.htm

:[3] [Shneiderman, 1996] Ben Shneiderman (1996), The Eyes Have It: A Task by Data Type Taxonomy for Information Visualizations, In Proceedings of the IEEE Symposium on Visual Languages, pages 336-343, Washington. IEEE Computer Society Press.

:[4] [Ahlberg and Shneiderman, 1994] Christopher Ahlberg and Ben Shneiderman (1994), Visual Information Seeking: Tight Coupling of Dynamic Query Filters with Starfield Displays, In Proceedings of the Conference on Human Factors in Computing Systems (CHI'94), pages 313-317. ACM Press.

:[5] [Visual Complexity] World Wide Web, Access Date: 15 November 2005, http://www.visualcomplexity.com/vc/index.cfm?domain=World%20Wide%20Web

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

2005-11-22T10:57:02Z

UE-InfoVis0506 0057001:

==Topic==
Webserver Logfile Visualization

==Area of Application==

===Analysis of Application Area===

====General Description====
Webservers typically generate logfiles containing huge amounts of information on page accesses, used client software, type of access, and many more. Analysis tools like for example AWStats try to make use of this information and present simple statistics mostly in form of tables or simple bar graphs. Unfortunately, they are mostly very limited and "low-level" regarding their information representation. More interesting questions like user behavior in combination with site structure, dead ends, changes in behavior regarding to time (evolution), typical behavioral patterns, finding groups of users that share similar behavioral patterns, site entry points, or intrusion detection cannot be answered by using similar tools. For being able to deal with this kind of topics, more advanced visual tools are needed that unveil this information. [Behlendorf et al., 2005]

====Special Issues====

There are many different known solutions/methods to visualize Webeserver Logfiles. Most of them make use of simple chart or bar diagrams. The question is, if it is possible to present this huge set of informations in just one diagram, that illustrates all the data in a simple and undastandable way.

===Analysis of the Dataset===

Here is an example of such a logfile entry: [Cooper,2004]

205.218.110.166 - - [08/Dec/1996:15:02:10 -0800] "GET /info/index.html HTTP/1.0" 200 14912 "http://www.yourcompany.com/index.html " "Mozilla/3.0Gold (Win95; I)" "35bebd61b31211cfbdcd00c04fd611cf"

The content of this entry explained, from left to right:

'''"205.218.110.166"''' - - This is the IP address of the machine making a request of your web server - its domain name can be determined in HitList by enabling Reverse DNS lookups, assuming your server hasn't put this information in already - many so, some don't. (if the domain name was in there, you'd see its URL instead of the raw IP).
Remote hostname or IP number if DNS hostname is not available, or if DNSLookup is Off.
remotehost is a one-dimensional discreet datatype.

'''"-"''' - this first dash is typically the server's IP address, which most NCSA format servers don't insert by default.

'''"-"''' - this second dash is typically authenticated usernames, which again many NCSA format servers don't insert by default.

'''"[08/Dec/1996:15:02:10 -0800]"''' - This is the date and time of the access, including the offset from Greenwich Mean Time - the latter is the "-800", meaning the web server being accessed is 8 hours ahead of GMT.

'''"GET /info/index.html HTTP/1.0"''' - This is the actual request the visitor's browser made when at your page or server.

'''"HTTP/1.0"''' refers to the protocol and its version, here being version 1.0 of the http protocol.

'''"200"''' - this is the server response code - a "successful" request (meaning the visitor's browser loaded the entire HTML/GIF/JPEG, etc.) generates a response code of 200. Others include:

206 - Partial request successful (not complete)
302 - URL has been redirected to another document
400 - Bad request was made by the client
401 - Authorization is required for this document
403 - Access to this document is forbidden
404 - Document not found
500 - Server internal error
501 - Application method (either GET or POST) is not implemented
503 - Server is out of resources

'''"14912"''' - This is the number of bytes transferred to the client during the visit. Since every request has some response, even erroneous requests will have a non-zero value for this field.
"http://www.yourcompany.com/index.html" - This is the referrer field, or the site the visitor was on immediately prior to making this entry's request - in this case, the person was looking at the index.html (probably the home page) page before going to the /info/index.html page in this entry.
"Mozilla/3.0Gold (Win95; I)" - this is the user-agent field, meaning the actual browser and OS used by the visitor - in this case, Mozilla is Netscape, the next value is the version (here, 3.0Gold), and the final value is the OS it was using (Windows 95).

Finally, the '''"35bebd61b31211cfbdcd00c04fd611cf"''' is the cookie information, which may or may not be there, depending on whether the webserver used has cookies enabled and whether one was passed from webserver to the visitor's computer.

There are several different specific Logfile Formats, for example: Microsoft IIS 3.0 and 2.0, Microsoft IIS4.0 (W3SVC format), Netscape (NCSA format with/without unique format header), Lotus Domino format, O'Reilly WebSite format...

==Target Group==

===Identifying the Target===
We identified the following Target groups:
#Software Companies: especially those who develop browsers and web based applications
#Web Dsigners
#Administrators
#Advertising Companys
#Web Users

===Special Issues of the Target Group===

Software Companies: In order to optimize their software, they have to explore the user's needs. Logfiles can offer them some useful informations.

For Web Designers it can be helpful to know some facts about their visitors. Logfiles tell them, which browsers they use, when they access the site, traffic, and so on. This Informations allow them to organize the webpage in a convenient and reliable way. It's the same with Web Administrators.

Advertising Companies strive to study user behaviour in order to orientate their adds more effectively.

===Known Solutions / Methods (related to the target group)===
#Radial Tree Viewer
#Anemone
#Internet Cartographer
#WebTracer
#WebHopper
#WebPath
#The Chicago Tribune Website
#Visualizing the online debate on the European Constitution
#Mercator 
...[5]

==Intended Purpose==

===Goals and Objectives===
#Which client software is used, which browsers
#How users behave, in combination with site structure, dead ends, changes in behavior regarding to time.
#Identify groups of users who act in a similar way.
#Identify "hot" topics

===Problems and Tasks to Solve===
- '''Improve the Servers''': Administrators, Web Designers and Software Companies need this information, to improve the Servers. They need to know what people are interested in, if there are special groups, which have similar behavior, navigate to the same themes and in a similar way. What kind of themes are often searched for, and how. With this information, they can help Users to get the things they want faster and easier. They can adapt the Server to the needs of the Users. 
In order to effectively manage a web server, it is necessary to get feedback about the activity and performance of the server as well as any problems that may be occuring 
- '''Adapt Advertising to Users interests''':Advertising Companys can use the information to identify themes and products of interest to a group of users. You get an overview of groups of things people are interessted in. So they can adapt the topics of their advertisement to this information.

==Proposed Design==

===Types of Visualization Applied===

The following techniques will be used:

* Filtering
* Linking
* Detail on Demand
* Range Slider [Ahlberg and Shneiderman, 1994] with Time Lense.

{{quotation |"Overview first, zoom and filter, then details on demand. View relationships and history..." | Visual Information-Seeking Mantra [Shneiderman, 1996] }}

First, the user is presented with a net of accessed web pages and resources. She is able to filter the information using the checkboxes of OS, browser,.. and the Time Lens Range Slider.
When clicking on a resource, the view zooms if necessary and marks all nodes linking to and from this page, image,...

===Visual Mapping===

(Datadimension => Attribute)

The log contains the following information:

IP, date, request, protocol, response code, bytes, referer, user agent, cookie

From a given IP it is possible to determin the country of origin, so IPs are mapped to the world map. <Unknown> will also be listed.

The date is listed on the date lens slider. After choosing a date range the corresponding numbers and entries will change.
Above this date slider the user will find bars of transferred bytes in this date region.

The request is mapped onto the "web site" net in the middle. Further calculation is necessary to match /file/ to /file/index.php and /file/index.php?somesessionid=2139123123.
Only successful requests are listed here (eg response code 200).

If referer is an URL from within the server, the "web site" net draws a connection between the two pages. If the page is referred from the outside, the referring page is listed on the left hand side panel "external referers"

The user agent is parsed for operating system and browser information. Each is listed on the right with checkboxes, so the user can remove or include certain browsers or OS to the data set.

The number of hits is mapped to the size of the dots in the net view and external referer list.

When following the interaction of users it is possible to estimate a page reading time. This is displayed as arc in each page dot.

===Description of Used Techniques===

===Possibilities of Interaction===

Klicking on a browser, operating system or weekday check box reduces or increases the displayed data set. Numbers next to the settings change accordingly.

Klicking on a web page in net view also updates these numbers: The time lens and filters show the number of accesses to this resource. Marked are other pages which have been visited by users, who have been watching this page. Klicking on a blank spot resets that view.

If the button "filtered list" is pressed, the program produces a list of the webserver log file according to the settings (browser, page, time, os,...)

The "hide media" check box removes, if checked, all images, css and media files from the list, keeping only html, php, ...

===Mockups / Fake Screenshots===

[[Image:Infovis_weblog_fake.png|Screenshot|800px]]

== Resources ==

:[1] [Behlendorf et al., 2005] Brian Behlendorf, Apache HTTP Server Logfiles, Apache HTTP Server Project, Access Date: 17 October 2005, http://httpd.apache.org/docs/1.3/logs.html

:[2] [Cooper, 2004] Colin Cooper, Logfile Definitions and Examples, Intranet Software Solutions (Europe) Limited [ISSEL], Access Date: 17 October 2005, http://www.issel.co.uk/FAQ/logfile_definitions_examples.htm

:[3] [Shneiderman, 1996] Ben Shneiderman (1996), The Eyes Have It: A Task by Data Type Taxonomy for Information Visualizations, In Proceedings of the IEEE Symposium on Visual Languages, pages 336-343, Washington. IEEE Computer Society Press.

:[4] [Ahlberg and Shneiderman, 1994] Christopher Ahlberg and Ben Shneiderman (1994), Visual Information Seeking: Tight Coupling of Dynamic Query Filters with Starfield Displays, In Proceedings of the Conference on Human Factors in Computing Systems (CHI'94), pages 313-317. ACM Press.

:[5] [Visual Complexity] World Wide Web, Access Date: 15 November 2005, http://www.visualcomplexity.com/vc/index.cfm?domain=World%20Wide%20Web

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

2005-11-22T10:56:30Z

UE-InfoVis0506 0057001:

==Topic==
Webserver Logfile Visualization

==Area of Application==

===Analysis of Application Area===

====General Description====
Webservers typically generate logfiles containing huge amounts of information on page accesses, used client software, type of access, and many more. Analysis tools like for example AWStats try to make use of this information and present simple statistics mostly in form of tables or simple bar graphs. Unfortunately, they are mostly very limited and "low-level" regarding their information representation. More interesting questions like user behavior in combination with site structure, dead ends, changes in behavior regarding to time (evolution), typical behavioral patterns, finding groups of users that share similar behavioral patterns, site entry points, or intrusion detection cannot be answered by using similar tools. For being able to deal with this kind of topics, more advanced visual tools are needed that unveil this information. [Behlendorf et al., 2005]

====Special Issues====

There are many different known solutions/methods to visualize Webeserver Logfiles. Most of them make use of simple chart or bar diagrams. The question is, if it is possible to present this huge set of informations in just one diagram, that illustrates all the data in a simple and undastandable way.

===Analysis of the Dataset===

Here is an example of such a logfile entry: [Cooper,2004]

205.218.110.166 - - [08/Dec/1996:15:02:10 -0800] "GET /info/index.html HTTP/1.0" 200 14912 "http://www.yourcompany.com/index.html " "Mozilla/3.0Gold (Win95; I)" "35bebd61b31211cfbdcd00c04fd611cf"

The content of this entry explained, from left to right:

'''"205.218.110.166"''' - - This is the IP address of the machine making a request of your web server - its domain name can be determined in HitList by enabling Reverse DNS lookups, assuming your server hasn't put this information in already - many so, some don't. (if the domain name was in there, you'd see its URL instead of the raw IP).
|Remote hostname (or IP number if DNS hostname is not available, or if DNSLookup is Off.)
remotehost is a one-dimensional discreet datatype.

'''"-"''' - this first dash is typically the server's IP address, which most NCSA format servers don't insert by default.

'''"-"''' - this second dash is typically authenticated usernames, which again many NCSA format servers don't insert by default.

'''"[08/Dec/1996:15:02:10 -0800]"''' - This is the date and time of the access, including the offset from Greenwich Mean Time - the latter is the "-800", meaning the web server being accessed is 8 hours ahead of GMT.

'''"GET /info/index.html HTTP/1.0"''' - This is the actual request the visitor's browser made when at your page or server.

'''"HTTP/1.0"''' refers to the protocol and its version, here being version 1.0 of the http protocol.

'''"200"''' - this is the server response code - a "successful" request (meaning the visitor's browser loaded the entire HTML/GIF/JPEG, etc.) generates a response code of 200. Others include:

206 - Partial request successful (not complete)
302 - URL has been redirected to another document
400 - Bad request was made by the client
401 - Authorization is required for this document
403 - Access to this document is forbidden
404 - Document not found
500 - Server internal error
501 - Application method (either GET or POST) is not implemented
503 - Server is out of resources

'''"14912"''' - This is the number of bytes transferred to the client during the visit. Since every request has some response, even erroneous requests will have a non-zero value for this field.
"http://www.yourcompany.com/index.html" - This is the referrer field, or the site the visitor was on immediately prior to making this entry's request - in this case, the person was looking at the index.html (probably the home page) page before going to the /info/index.html page in this entry.
"Mozilla/3.0Gold (Win95; I)" - this is the user-agent field, meaning the actual browser and OS used by the visitor - in this case, Mozilla is Netscape, the next value is the version (here, 3.0Gold), and the final value is the OS it was using (Windows 95).

Finally, the '''"35bebd61b31211cfbdcd00c04fd611cf"''' is the cookie information, which may or may not be there, depending on whether the webserver used has cookies enabled and whether one was passed from webserver to the visitor's computer.

There are several different specific Logfile Formats, for example: Microsoft IIS 3.0 and 2.0, Microsoft IIS4.0 (W3SVC format), Netscape (NCSA format with/without unique format header), Lotus Domino format, O'Reilly WebSite format...

==Target Group==

===Identifying the Target===
We identified the following Target groups:
#Software Companies: especially those who develop browsers and web based applications
#Web Dsigners
#Administrators
#Advertising Companys
#Web Users

===Special Issues of the Target Group===

Software Companies: In order to optimize their software, they have to explore the user's needs. Logfiles can offer them some useful informations.

For Web Designers it can be helpful to know some facts about their visitors. Logfiles tell them, which browsers they use, when they access the site, traffic, and so on. This Informations allow them to organize the webpage in a convenient and reliable way. It's the same with Web Administrators.

Advertising Companies strive to study user behaviour in order to orientate their adds more effectively.

===Known Solutions / Methods (related to the target group)===
#Radial Tree Viewer
#Anemone
#Internet Cartographer
#WebTracer
#WebHopper
#WebPath
#The Chicago Tribune Website
#Visualizing the online debate on the European Constitution
#Mercator 
...[5]

==Intended Purpose==

===Goals and Objectives===
#Which client software is used, which browsers
#How users behave, in combination with site structure, dead ends, changes in behavior regarding to time.
#Identify groups of users who act in a similar way.
#Identify "hot" topics

===Problems and Tasks to Solve===
- '''Improve the Servers''': Administrators, Web Designers and Software Companies need this information, to improve the Servers. They need to know what people are interested in, if there are special groups, which have similar behavior, navigate to the same themes and in a similar way. What kind of themes are often searched for, and how. With this information, they can help Users to get the things they want faster and easier. They can adapt the Server to the needs of the Users. 
In order to effectively manage a web server, it is necessary to get feedback about the activity and performance of the server as well as any problems that may be occuring 
- '''Adapt Advertising to Users interests''':Advertising Companys can use the information to identify themes and products of interest to a group of users. You get an overview of groups of things people are interessted in. So they can adapt the topics of their advertisement to this information.

==Proposed Design==

===Types of Visualization Applied===

The following techniques will be used:

* Filtering
* Linking
* Detail on Demand
* Range Slider [Ahlberg and Shneiderman, 1994] with Time Lense.

{{quotation |"Overview first, zoom and filter, then details on demand. View relationships and history..." | Visual Information-Seeking Mantra [Shneiderman, 1996] }}

First, the user is presented with a net of accessed web pages and resources. She is able to filter the information using the checkboxes of OS, browser,.. and the Time Lens Range Slider.
When clicking on a resource, the view zooms if necessary and marks all nodes linking to and from this page, image,...

===Visual Mapping===

(Datadimension => Attribute)

The log contains the following information:

IP, date, request, protocol, response code, bytes, referer, user agent, cookie

From a given IP it is possible to determin the country of origin, so IPs are mapped to the world map. <Unknown> will also be listed.

The date is listed on the date lens slider. After choosing a date range the corresponding numbers and entries will change.
Above this date slider the user will find bars of transferred bytes in this date region.

The request is mapped onto the "web site" net in the middle. Further calculation is necessary to match /file/ to /file/index.php and /file/index.php?somesessionid=2139123123.
Only successful requests are listed here (eg response code 200).

If referer is an URL from within the server, the "web site" net draws a connection between the two pages. If the page is referred from the outside, the referring page is listed on the left hand side panel "external referers"

The user agent is parsed for operating system and browser information. Each is listed on the right with checkboxes, so the user can remove or include certain browsers or OS to the data set.

The number of hits is mapped to the size of the dots in the net view and external referer list.

When following the interaction of users it is possible to estimate a page reading time. This is displayed as arc in each page dot.

===Description of Used Techniques===

===Possibilities of Interaction===

Klicking on a browser, operating system or weekday check box reduces or increases the displayed data set. Numbers next to the settings change accordingly.

Klicking on a web page in net view also updates these numbers: The time lens and filters show the number of accesses to this resource. Marked are other pages which have been visited by users, who have been watching this page. Klicking on a blank spot resets that view.

If the button "filtered list" is pressed, the program produces a list of the webserver log file according to the settings (browser, page, time, os,...)

The "hide media" check box removes, if checked, all images, css and media files from the list, keeping only html, php, ...

===Mockups / Fake Screenshots===

[[Image:Infovis_weblog_fake.png|Screenshot|800px]]

== Resources ==

:[1] [Behlendorf et al., 2005] Brian Behlendorf, Apache HTTP Server Logfiles, Apache HTTP Server Project, Access Date: 17 October 2005, http://httpd.apache.org/docs/1.3/logs.html

:[2] [Cooper, 2004] Colin Cooper, Logfile Definitions and Examples, Intranet Software Solutions (Europe) Limited [ISSEL], Access Date: 17 October 2005, http://www.issel.co.uk/FAQ/logfile_definitions_examples.htm

:[3] [Shneiderman, 1996] Ben Shneiderman (1996), The Eyes Have It: A Task by Data Type Taxonomy for Information Visualizations, In Proceedings of the IEEE Symposium on Visual Languages, pages 336-343, Washington. IEEE Computer Society Press.

:[4] [Ahlberg and Shneiderman, 1994] Christopher Ahlberg and Ben Shneiderman (1994), Visual Information Seeking: Tight Coupling of Dynamic Query Filters with Starfield Displays, In Proceedings of the Conference on Human Factors in Computing Systems (CHI'94), pages 313-317. ACM Press.

:[5] [Visual Complexity] World Wide Web, Access Date: 15 November 2005, http://www.visualcomplexity.com/vc/index.cfm?domain=World%20Wide%20Web

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

2005-11-22T10:49:32Z

UE-InfoVis0506 0057001:

==Topic==
Webserver Logfile Visualization

==Area of Application==

===Analysis of Application Area===

====General Description====
Webservers typically generate logfiles containing huge amounts of information on page accesses, used client software, type of access, and many more. Analysis tools like for example AWStats try to make use of this information and present simple statistics mostly in form of tables or simple bar graphs. Unfortunately, they are mostly very limited and "low-level" regarding their information representation. More interesting questions like user behavior in combination with site structure, dead ends, changes in behavior regarding to time (evolution), typical behavioral patterns, finding groups of users that share similar behavioral patterns, site entry points, or intrusion detection cannot be answered by using similar tools. For being able to deal with this kind of topics, more advanced visual tools are needed that unveil this information. [Behlendorf et al., 2005]

====Special Issues====

There are many different known solutions/methods to visualize Webeserver Logfiles. Most of them make use of simple chart or bar diagrams. The question is, if it is possible to present this huge set of informations in just one diagram, that illustrates all the data in a simple and undastandable way.

===Analysis of the Dataset===

Here is an example of such a logfile entry: [Cooper,2004]

205.218.110.166 - - [08/Dec/1996:15:02:10 -0800] "GET /info/index.html HTTP/1.0" 200 14912 "http://www.yourcompany.com/index.html " "Mozilla/3.0Gold (Win95; I)" "35bebd61b31211cfbdcd00c04fd611cf"

The content of this entry explained, from left to right:

'''"205.218.110.166"''' - - This is the IP address of the machine making a request of your web server - its domain name can be determined in HitList by enabling Reverse DNS lookups, assuming your server hasn't put this information in already - many so, some don't. (if the domain name was in there, you'd see its URL instead of the raw IP).

'''"-"''' - this first dash is typically the server's IP address, which most NCSA format servers don't insert by default.

'''"-"''' - this second dash is typically authenticated usernames, which again many NCSA format servers don't insert by default.

'''"[08/Dec/1996:15:02:10 -0800]"''' - This is the date and time of the access, including the offset from Greenwich Mean Time - the latter is the "-800", meaning the web server being accessed is 8 hours ahead of GMT.

'''"GET /info/index.html HTTP/1.0"''' - This is the actual request the visitor's browser made when at your page or server.

'''"HTTP/1.0"''' refers to the protocol and its version, here being version 1.0 of the http protocol.

'''"200"''' - this is the server response code - a "successful" request (meaning the visitor's browser loaded the entire HTML/GIF/JPEG, etc.) generates a response code of 200. Others include:

206 - Partial request successful (not complete)
302 - URL has been redirected to another document
400 - Bad request was made by the client
401 - Authorization is required for this document
403 - Access to this document is forbidden
404 - Document not found
500 - Server internal error
501 - Application method (either GET or POST) is not implemented
503 - Server is out of resources

'''"14912"''' - This is the number of bytes transferred to the client during the visit. Since every request has some response, even erroneous requests will have a non-zero value for this field.
"http://www.yourcompany.com/index.html" - This is the referrer field, or the site the visitor was on immediately prior to making this entry's request - in this case, the person was looking at the index.html (probably the home page) page before going to the /info/index.html page in this entry.
"Mozilla/3.0Gold (Win95; I)" - this is the user-agent field, meaning the actual browser and OS used by the visitor - in this case, Mozilla is Netscape, the next value is the version (here, 3.0Gold), and the final value is the OS it was using (Windows 95).

Finally, the '''"35bebd61b31211cfbdcd00c04fd611cf"''' is the cookie information, which may or may not be there, depending on whether the webserver used has cookies enabled and whether one was passed from webserver to the visitor's computer.

There are several different specific Logfile Formats, for example: Microsoft IIS 3.0 and 2.0, Microsoft IIS4.0 (W3SVC format), Netscape (NCSA format with/without unique format header), Lotus Domino format, O'Reilly WebSite format...

==Target Group==

===Identifying the Target===
We identified the following Target groups:
#Software Companies: especially those who develop browsers and web based applications
#Web Dsigners
#Administrators
#Advertising Companys
#Web Users

===Special Issues of the Target Group===

Software Companies: In order to optimize their software, they have to explore the user's needs. Logfiles can offer them some useful informations.

For Web Designers it can be helpful to know some facts about their visitors. Logfiles tell them, which browsers they use, when they access the site, traffic, and so on. This Informations allow them to organize the webpage in a convenient and reliable way. It's the same with Web Administrators.

Advertising Companies strive to study user behaviour in order to orientate their adds more effectively.

===Known Solutions / Methods (related to the target group)===
#Radial Tree Viewer
#Anemone
#Internet Cartographer
#WebTracer
#WebHopper
#WebPath
#The Chicago Tribune Website
#Visualizing the online debate on the European Constitution
#Mercator 
...[5]

==Intended Purpose==

===Goals and Objectives===
#Which client software is used, which browsers
#How users behave, in combination with site structure, dead ends, changes in behavior regarding to time.
#Identify groups of users who act in a similar way.
#Identify "hot" topics

===Problems and Tasks to Solve===
- '''Improve the Servers''': Administrators, Web Designers and Software Companies need this information, to improve the Servers. They need to know what people are interested in, if there are special groups, which have similar behavior, navigate to the same themes and in a similar way. What kind of themes are often searched for, and how. With this information, they can help Users to get the things they want faster and easier. They can adapt the Server to the needs of the Users. 
In order to effectively manage a web server, it is necessary to get feedback about the activity and performance of the server as well as any problems that may be occuring 
- '''Adapt Advertising to Users interests''':Advertising Companys can use the information to identify themes and products of interest to a group of users. You get an overview of groups of things people are interessted in. So they can adapt the topics of their advertisement to this information.

==Proposed Design==

===Types of Visualization Applied===

The following techniques will be used:

* Filtering
* Linking
* Detail on Demand
* Range Slider [Ahlberg and Shneiderman, 1994] with Time Lense.

{{quotation |"Overview first, zoom and filter, then details on demand. View relationships and history..." | Visual Information-Seeking Mantra [Shneiderman, 1996] }}

First, the user is presented with a net of accessed web pages and resources. She is able to filter the information using the checkboxes of OS, browser,.. and the Time Lens Range Slider.
When clicking on a resource, the view zooms if necessary and marks all nodes linking to and from this page, image,...

===Visual Mapping===

(Datadimension => Attribute)

The log contains the following information:

IP, date, request, protocol, response code, bytes, referer, user agent, cookie

From a given IP it is possible to determin the country of origin, so IPs are mapped to the world map. <Unknown> will also be listed.

The date is listed on the date lens slider. After choosing a date range the corresponding numbers and entries will change.
Above this date slider the user will find bars of transferred bytes in this date region.

The request is mapped onto the "web site" net in the middle. Further calculation is necessary to match /file/ to /file/index.php and /file/index.php?somesessionid=2139123123.
Only successful requests are listed here (eg response code 200).

If referer is an URL from within the server, the "web site" net draws a connection between the two pages. If the page is referred from the outside, the referring page is listed on the left hand side panel "external referers"

The user agent is parsed for operating system and browser information. Each is listed on the right with checkboxes, so the user can remove or include certain browsers or OS to the data set.

The number of hits is mapped to the size of the dots in the net view and external referer list.

When following the interaction of users it is possible to estimate a page reading time. This is displayed as arc in each page dot.

===Description of Used Techniques===

===Possibilities of Interaction===

Klicking on a browser, operating system or weekday check box reduces or increases the displayed data set. Numbers next to the settings change accordingly.

Klicking on a web page in net view also updates these numbers: The time lens and filters show the number of accesses to this resource. Marked are other pages which have been visited by users, who have been watching this page. Klicking on a blank spot resets that view.

If the button "filtered list" is pressed, the program produces a list of the webserver log file according to the settings (browser, page, time, os,...)

The "hide media" check box removes, if checked, all images, css and media files from the list, keeping only html, php, ...

===Mockups / Fake Screenshots===

[[Image:Infovis_weblog_fake.png|Screenshot|800px]]

== Resources ==

:[1] [Behlendorf et al., 2005] Brian Behlendorf, Apache HTTP Server Logfiles, Apache HTTP Server Project, Access Date: 17 October 2005, http://httpd.apache.org/docs/1.3/logs.html

:[2] [Cooper, 2004] Colin Cooper, Logfile Definitions and Examples, Intranet Software Solutions (Europe) Limited [ISSEL], Access Date: 17 October 2005, http://www.issel.co.uk/FAQ/logfile_definitions_examples.htm

:[3] [Shneiderman, 1996] Ben Shneiderman (1996), The Eyes Have It: A Task by Data Type Taxonomy for Information Visualizations, In Proceedings of the IEEE Symposium on Visual Languages, pages 336-343, Washington. IEEE Computer Society Press.

:[4] [Ahlberg and Shneiderman, 1994] Christopher Ahlberg and Ben Shneiderman (1994), Visual Information Seeking: Tight Coupling of Dynamic Query Filters with Starfield Displays, In Proceedings of the Conference on Human Factors in Computing Systems (CHI'94), pages 313-317. ACM Press.

:[5] [Visual Complexity] World Wide Web, Access Date: 15 November 2005, http://www.visualcomplexity.com/vc/index.cfm?domain=World%20Wide%20Web

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

2005-11-22T10:47:57Z

UE-InfoVis0506 0057001:

==Topic==
Webserver Logfile Visualization

==Area of Application==

===Analysis of Application Area===

====General Description====
Webservers typically generate logfiles containing huge amounts of information on page accesses, used client software, type of access, and many more. Analysis tools like for example AWStats try to make use of this information and present simple statistics mostly in form of tables or simple bar graphs. Unfortunately, they are mostly very limited and "low-level" regarding their information representation. More interesting questions like user behavior in combination with site structure, dead ends, changes in behavior regarding to time (evolution), typical behavioral patterns, finding groups of users that share similar behavioral patterns, site entry points, or intrusion detection cannot be answered by using similar tools. For being able to deal with this kind of topics, more advanced visual tools are needed that unveil this information. [Behlendorf et al., 2005]

====Special Issues====

There are many different known solutions/methods to visualize Webeserver Logfiles. Most of them make use of simple chart or bar diagrams. The question is, if it is possible to present this huge set of informations in just one diagram, that illustrates all the data in a simple and undastandable way.

===Analysis of the Dataset===

Here is an example of such a logfile entry: [Cooper,2004]

205.218.110.166 - - [08/Dec/1996:15:02:10 -0800] "GET /info/index.html HTTP/1.0" 200 14912 "http://www.yourcompany.com/index.html " "Mozilla/3.0Gold (Win95; I)" "35bebd61b31211cfbdcd00c04fd611cf"

The content of this entry explained, from left to right:

'''"205.218.110.166"''' - - This is the IP address of the machine making a request of your web server - its domain name can be determined in HitList by enabling Reverse DNS lookups, assuming your server hasn't put this information in already - many so, some don't. (if the domain name was in there, you'd see its URL instead of the raw IP).

'''"-"''' - this first dash is typically the server's IP address, which most NCSA format servers don't insert by default.

'''"-"''' - this second dash is typically authenticated usernames, which again many NCSA format servers don't insert by default.

'''"[08/Dec/1996:15:02:10 -0800]"''' - This is the date and time of the access, including the offset from Greenwich Mean Time - the latter is the "-800", meaning the web server being accessed is 8 hours ahead of GMT.

'''"GET /info/index.html HTTP/1.0"''' - This is the actual request the visitor's browser made when at your page or server.

'''"HTTP/1.0"''' refers to the protocol and its version, here being version 1.0 of the http protocol.

'''"200"''' - this is the server response code - a "successful" request (meaning the visitor's browser loaded the entire HTML/GIF/JPEG, etc.) generates a response code of 200. Others include:

206 - Partial request successful (not complete)
302 - URL has been redirected to another document
400 - Bad request was made by the client
401 - Authorization is required for this document
403 - Access to this document is forbidden
404 - Document not found
500 - Server internal error
501 - Application method (either GET or POST) is not implemented
503 - Server is out of resources

'''"14912"''' - This is the number of bytes transferred to the client during the visit. Since every request has some response, even erroneous requests will have a non-zero value for this field.
"http://www.yourcompany.com/index.html" - This is the referrer field, or the site the visitor was on immediately prior to making this entry's request - in this case, the person was looking at the index.html (probably the home page) page before going to the /info/index.html page in this entry.
"Mozilla/3.0Gold (Win95; I)" - this is the user-agent field, meaning the actual browser and OS used by the visitor - in this case, Mozilla is Netscape, the next value is the version (here, 3.0Gold), and the final value is the OS it was using (Windows 95).

Finally, the '''"35bebd61b31211cfbdcd00c04fd611cf"''' is the cookie information, which may or may not be there, depending on whether the webserver used has cookies enabled and whether one was passed from webserver to the visitor's computer.

There are several different specific Logfile Formats, for example: Microsoft IIS 3.0 and 2.0, Microsoft IIS4.0 (W3SVC format), Netscape (NCSA format with/without unique format header), Lotus Domino format, O'Reilly WebSite format...

==Target Group==

===Identifying the Target===
We identified the following Target groups:
#Software Companies: especially those who develop browsers and web based applications
#Web Dsigners
#Administrators
#Advertising Companys
#Web Users

===Special Issues of the Target Group===

Software Companies: In order to optimize their software, they have to explore the user's needs. Logfiles can offer them some useful informations.

For Web Designers it can be helpful to know some facts about their visitors. Logfiles tell them, which browsers they use, when they access the site, traffic, and so on. This Informations allow them to organize the webpage in a convenient and reliable way. It's the same with Web Administrators.

Advertising Companies strive to study user behaviour in order to orientate their adds more effectively.

===Known Solutions / Methods (related to the target group)===
#Radial Tree Viewer
#Anemone
#Internet Cartographer
#WebTracer
#WebHopper
#WebPath
#The Chicago Tribune Website
#Visualizing the online debate on the European Constitution
#Mercator 
...[5]

==Intended Purpose==

===Goals and Objectives===
#Which client software is used, which browsers
#How users behave, in combination with site structure, dead ends, changes in behavior regarding to time.
#Identify groups of users who act in a similar way.
#Identify "hot" topics

===Problems and Tasks to Solve===
- '''Improve the Servers''': Administrators, Web Designers and Software Companies need this information, to improve the Servers. They need to know what people are interested in, if there are special groups, which have similar behavior, navigate to the same themes and in a similar way. What kind of themes are often searched for, and how. With this information, they can help Users to get the things they want faster and easier. They can adapt the Server to the needs of the Users. 
In order to effectively manage a web server, it is necessary to get feedback about the activity and performance of the server as well as any problems that may be occuring 
- '''Adapt Advertising to Users interests''':Advertising Companys can use the information to identify themes and products of interest to a group of users. You get an overview of groups of things people are interessted in. So they can adapt the topics of their advertisement to this information.

==Proposed Design==

===Types of Visualization Applied===

The following techniques will be used:

* Filtering
* Linking
* Detail on Demand
* Range Slider [Ahlberg and Shneiderman, 1994] with Time Lense.

{{quotation |"Overview first, zoom and filter, then details on demand. View relationships and history..." | Visual Information-Seeking Mantra [Shneiderman, 1996] }}

First, the user is presented with a net of accessed web pages and resources. She is able to filter the information using the checkboxes of OS, browser,.. and the Time Lens Range Slider.
When clicking on a resource, the view zooms if necessary and marks all nodes linking to and from this page, image,...

===Visual Mapping===

(Datadimension => Attribute)

The log contains the following information:

IP, date, request, protocol, response code, bytes, referer, user agent, cookie

From a given IP it is possible to determin the country of origin, so IPs are mapped to the world map. <Unknown> will also be listed.

The date is listed on the date lens slider. After choosing a date range the corresponding numbers and entries will change.
Above this date slider the user will find bars of transferred bytes in this date region.

The request is mapped onto the "web site" net in the middle. Further calculation is necessary to match /file/ to /file/index.php and /file/index.php?somesessionid=2139123123.
Only successful requests are listed here (eg response code 200).

If referer is an URL from within the server, the "web site" net draws a connection between the two pages. If the page is referred from the outside, the referring page is listed on the left hand side panel "external referers"

The user agent is parsed for operating system and browser information. Each is listed on the right with checkboxes, so the user can remove or include certain browsers or OS to the data set.

The number of hits is mapped to the size of the dots in the net view and external referer list.

When following the interaction of users it is possible to estimate a page reading time. This is displayed as arc in each page dot.

===Description of Used Techniques===

===Possibilities of Interaction===

Klicking on a browser, operating system or weekday check box reduces or increases the displayed data set. Numbers next to the settings change accordingly.

Klicking on a web page in net view also updates these numbers: The time lens and filters show the number of accesses to this resource. Marked are other pages which have been visited by users, who have been watching this page. Klicking on a blank spot resets that view.

If the button "filtered list" is pressed, the program produces a list of the webserver log file according to the settings (browser, page, time, os,...)

The "hide media" check box removes, if checked, all images, css and media files from the list, keeping only html, php, ...

===Mockups / Fake Screenshots===

[[Image:Infovis_weblog_fake.png|Screenshot|800px]]

== Resources ==

:[1] [Behlendorf et al., 2005] Brian Behlendorf, Apache HTTP Server Logfiles, Apache HTTP Server Project, Access Date: 17 October 2005, http://httpd.apache.org/docs/1.3/logs.html

:[2] [Cooper, 2004] Colin Cooper, Logfile Definitions and Examples, Intranet Software Solutions (Europe) Limited [ISSEL], Access Date: 17 October 2005, http://www.issel.co.uk/FAQ/logfile_definitions_examples.htm

:[3] [Shneiderman, 1996] Ben Shneiderman (1996), The Eyes Have It: A Task by Data Type Taxonomy for Information Visualizations, In Proceedings of the IEEE Symposium on Visual Languages, pages 336-343, Washington. IEEE Computer Society Press.

:[4] [Ahlberg and Shneiderman, 1994] Christopher Ahlberg and Ben Shneiderman (1994), Visual Information Seeking: Tight Coupling of Dynamic Query Filters with Starfield Displays, In Proceedings of the Conference on Human Factors in Computing Systems (CHI'94), pages 313-317. ACM Press.

:[5] World Wide Web, Visual Complexity,
http://www.visualcomplexity.com/vc/index.cfm?domain=World%20Wide%20Web

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

2005-11-15T11:58:11Z

UE-InfoVis0506 0057001: /* Goals and Objectives */

==Topic==
Webserver Logfile Visualization

==Area of Application==

===Analysis of Application Area===

====General Description====

====Special Issues====

===Analysis of the Dataset===

====Description of the Datatypes====

====Description of the Datastructures====

==Target Group==

===Identifying the Target===
We identified the following Target groups:
#Software Companies: especially those who develop browsers and web based applications
#Web Dsigners
#Administrators
#Advertising Companys
#Web Users

===Special Issues of the Target Group===
- '''Improve the Servers''': Administrators, Web Designers and Software Companies need this information, to improve the Servers. They need to know what people are interested in, if there are special groups, which have similar behavior, navigate to the same themes and in a similar way. What kind of themes are often searched for, and how. With this information, they can help Users to get the things they want faster and easier. They can adapt the Server to the needs of the Users. 
- '''Adapt Advertising to Users interests''':Advertising Companys can use the information to identify themes and products of interest to a group of users. You get an overview of groups of things people are interessted in. So they can adapt the topics of their advertisement to this information.

===Known Solutions / Methods (related to the target group)===
#Apache Log File Description
#AWStats

==Intended Purpose==

===Goals and Objectives===
#Which client software is used, which browsers
#How users behave, in combination with site structure, dead ends, changes in behavior regarding to time.
#Identify groups of users who act in a similar way.
#Identify "hot" topics

===Problems and Tasks to Solve===

===Example Questions===

==Proposed Design==

===Types of Visualization Applied===

===Visual Mapping===

(Datadimension => Attribute)

===Description of Used Techniques===

===Possibilities of Interaction===

===Mockups / Fake Screenshots===

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

2005-11-15T11:55:14Z

UE-InfoVis0506 0057001: /* Special Issues of the Target Group */

==Topic==
Webserver Logfile Visualization

==Area of Application==

===Analysis of Application Area===

====General Description====

====Special Issues====

===Analysis of the Dataset===

====Description of the Datatypes====

====Description of the Datastructures====

==Target Group==

===Identifying the Target===
We identified the following Target groups:
#Software Companies: especially those who develop browsers and web based applications
#Web Dsigners
#Administrators
#Advertising Companys
#Web Users

===Special Issues of the Target Group===
- '''Improve the Servers''': Administrators, Web Designers and Software Companies need this information, to improve the Servers. They need to know what people are interested in, if there are special groups, which have similar behavior, navigate to the same themes and in a similar way. What kind of themes are often searched for, and how. With this information, they can help Users to get the things they want faster and easier. They can adapt the Server to the needs of the Users. 
- '''Adapt Advertising to Users interests''':Advertising Companys can use the information to identify themes and products of interest to a group of users. You get an overview of groups of things people are interessted in. So they can adapt the topics of their advertisement to this information.

===Known Solutions / Methods (related to the target group)===
#Apache Log File Description
#AWStats

==Intended Purpose==

===Goals and Objectives===

===Problems and Tasks to Solve===

===Example Questions===

==Proposed Design==

===Types of Visualization Applied===

===Visual Mapping===

(Datadimension => Attribute)

===Description of Used Techniques===

===Possibilities of Interaction===

===Mockups / Fake Screenshots===

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

2005-11-15T11:53:47Z

UE-InfoVis0506 0057001: /* Known Solutions / Methods (related to the target group) */

==Topic==
Webserver Logfile Visualization

==Area of Application==

===Analysis of Application Area===

====General Description====

====Special Issues====

===Analysis of the Dataset===

====Description of the Datatypes====

====Description of the Datastructures====

==Target Group==

===Identifying the Target===
We identified the following Target groups:
#Software Companies: especially those who develop browsers and web based applications
#Web Dsigners
#Administrators
#Advertising Companys
#Web Users

===Special Issues of the Target Group===
Administrators, Web Designers and Software Companies need this information, to improve the Servers. They need to know what people are interested in, if there are special groups, which have similar behavior, navigate to the same themes and in a similar way. What kind of themes are often searched for, and how. With this information, they can help Users to get the things they want faster and easier. They can adapt the Server to the needs of the Users. 
Advertising Companys can use the information to identify themes and products of interest to a group of users. You get an overview of groups of things people are interessted in. So they can adapt the topics of their advertisement to this information.

===Known Solutions / Methods (related to the target group)===
#Apache Log File Description
#AWStats

==Intended Purpose==

===Goals and Objectives===

===Problems and Tasks to Solve===

===Example Questions===

==Proposed Design==

===Types of Visualization Applied===

===Visual Mapping===

(Datadimension => Attribute)

===Description of Used Techniques===

===Possibilities of Interaction===

===Mockups / Fake Screenshots===

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

2005-11-15T11:52:58Z

UE-InfoVis0506 0057001: /* Special Issues of the Target Group */

==Topic==
Webserver Logfile Visualization

==Area of Application==

===Analysis of Application Area===

====General Description====

====Special Issues====

===Analysis of the Dataset===

====Description of the Datatypes====

====Description of the Datastructures====

==Target Group==

===Identifying the Target===
We identified the following Target groups:
#Software Companies: especially those who develop browsers and web based applications
#Web Dsigners
#Administrators
#Advertising Companys
#Web Users

===Special Issues of the Target Group===
Administrators, Web Designers and Software Companies need this information, to improve the Servers. They need to know what people are interested in, if there are special groups, which have similar behavior, navigate to the same themes and in a similar way. What kind of themes are often searched for, and how. With this information, they can help Users to get the things they want faster and easier. They can adapt the Server to the needs of the Users. 
Advertising Companys can use the information to identify themes and products of interest to a group of users. You get an overview of groups of things people are interessted in. So they can adapt the topics of their advertisement to this information.

===Known Solutions / Methods (related to the target group)===

==Intended Purpose==

===Goals and Objectives===

===Problems and Tasks to Solve===

===Example Questions===

==Proposed Design==

===Types of Visualization Applied===

===Visual Mapping===

(Datadimension => Attribute)

===Description of Used Techniques===

===Possibilities of Interaction===

===Mockups / Fake Screenshots===

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

2005-11-15T11:51:07Z

UE-InfoVis0506 0057001: /* Special Issues of the Target Group */

==Topic==
Webserver Logfile Visualization

==Area of Application==

===Analysis of Application Area===

====General Description====

====Special Issues====

===Analysis of the Dataset===

====Description of the Datatypes====

====Description of the Datastructures====

==Target Group==

===Identifying the Target===
We identified the following Target groups:
#Software Companies: especially those who develop browsers and web based applications
#Web Dsigners
#Administrators
#Advertising Companys
#Web Users

===Special Issues of the Target Group===
Administrators, Web Designers and Software Companies need this information, to improve the Servers. They need to know what people are interested in, if there are special groups, which have similar behavior, navigate to the same themes and in a similar way. What kind of themes are often searched for, and how. With this information, they can help Users to get the things they want faster and easier. They can adapt the Server to the needs of the Users.

===Known Solutions / Methods (related to the target group)===

==Intended Purpose==

===Goals and Objectives===

===Problems and Tasks to Solve===

===Example Questions===

==Proposed Design==

===Types of Visualization Applied===

===Visual Mapping===

(Datadimension => Attribute)

===Description of Used Techniques===

===Possibilities of Interaction===

===Mockups / Fake Screenshots===

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

2005-11-15T11:45:29Z

UE-InfoVis0506 0057001: /* Identifying the Target */

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

2005-11-15T11:44:23Z

UE-InfoVis0506 0057001: /* Special Issues of the Target Group */

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

2005-11-15T11:43:59Z

UE-InfoVis0506 0057001: /* Special Issues of the Target Group */

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

2005-11-15T11:32:36Z

UE-InfoVis0506 0057001:

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

2005-10-26T17:57:55Z

UE-InfoVis0506 0057001:

== Poor Graphic ==
[[Image:Perceptualedge03world-car-production.gif|none|thumb|600px|World Car Production 1977-80 (click on image for larger version)]]

== Drawbacks ==

This image is far away from a good Visualization of the underlying Data. It has drawbacks according to some well known Design Principles, which we will explain in the following:

- '''data ink''':

Everything that communicates actual data is data ink and is needed.[1] But our image contains some unnecessary data ink. The white Border around all the charts and the white lines around each single chart and between the pies of the charts are unnecessary data ink.

- '''color''':

Lines, bars and charts should be colored in a way, that that no one color stands out more prominently than the others, thus supporting the equal importance of the three data sets.[1] In our image the red and blue pies of the charts violate this principle because they stand out more promonently than the others.

- '''lie factor''':

The lie lactor is a value to describe the relation between the size of effect shown in a graphic and the size of effect shown in the data.[3] The first problem is, it seems that we look at the image not from the front but a little from the side. That distorts the message since neither the angles nor the areas are in proportion to the data.[2] The second one is that the charts have different distances to each other. The distance of the chart 1977 to the chart 1978 is shorter than that from 1979 to 1980. It schould be the same.

- '''past experience''':

That means that past experience have an effect of how we see and interpret things.[4] You can say that our image somehow violates this principle. We are used to read from left to right, but the charts on the image are organized from right to left. This can be confusing.

- '''simplicity''':

You should keep your image as simple as possible, which also means that you have to reduce redundant information.[1] Our image violates this principle. The percentage of a lands contribution to the world production is shown on one hand via the angle and size of the pies and on the other hand it is written numerical above the pies.

== verbessertes Bild ==

== was wurde verbessert ==

== Resources ==

:[1] [Few, 2004] Stephen Few, Elegance Through Simplicity, Intelligent Enterprise, Access Date: 26 October 2005, http://www.intelligententerprise.com/showArticle.jhtml;jsessionid=N2ATDQWY5VYKSQSNDBGCKHSCJUMEKJVN?articleID=49400920

:[2] [Seyfang, Fritz, Schnabl, Baldass, 2005] Leonhard Seyfang, Heinrich Fritz, Stefan Schnabl, Gioia Baldass , Gruppe G8 - Aufgabe 1 - Chart Junk, InfoVis Wiki, Access Date: 26 October 2005, http://www.infovis-wiki.net/index.php/Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G8_-_Aufgabe_1_-_Chart_Junk

:[3] [Muster, Puchta, Rainer, Sölder, 2005] Anna Muster, Jürgen Puchta, Christian Rainer, Christoph Sölder, Gruppe G4 - Aufgabe 1 - Lie Factor, InfoVis Wiki, Access Date: 26 October 2005, http://www.infovis-wiki.net/index.php/Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G4_-_Aufgabe_1_-_Lie_Factor

:[4] [Starl, Froschauer, 205] Erwin Starl, Joseph Froschauer, Gruppe G7 - Aufgabe 1, InfoVis Wiki, Access Date: 26 October 2005, http://www.infovis-wiki.net/index.php/Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G7_-_Aufgabe_1_-_Gestalt_Laws

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

2005-10-26T16:30:25Z

UE-InfoVis0506 0057001:

== Poor Graphic ==
[[Image:Perceptualedge03world-car-production.gif|none|thumb|600px|World Car Production 1977-80 (click on image for larger version)]]

== Drawbacks ==

This image is far away from a good Visualization of the underlying Data. It has drawbacks according to some well known Design Principles, which we will explain in the following:

- '''data ink''':

Everything that communicates actual data is data ink and is needed.[1] But our image contains some unnecessary data ink. The white Border around all the charts and the white lines around each single chart and between the pies of the charts are unnecessary data ink.

- '''chart chunk''':

Chartjunk is a term for unnecessary or confusing visual elements in charts and graphs.[2] Our image uses 2D Pie charts. The problem is it seems that we look at the image not from the front but a little from the side. That distorts the message since neither the angles nor the areas are in proportion to the data.

- '''color''':

Lines, bars and charts should be colored in a way, that that no one color stands out more prominently than the others, thus supporting the equal importance of the three data sets.[1] In our image the red and blue pies of the charts violate this principle because they stand out more promonently than the others.

- '''lie factor''':

The lie lactor is a value to describe the relation between the size of effect shown in a graphic and the size of effect shown in the data.[3] You can consider the above mentioned chart chunk as a lie factor. The second one is that the charts have different distances to each other. The distance of the chart 1977 to the chart 1978 is shorter than that from 1979 to 1980. It schould be the same.

- '''past experience''':

That means that past experience have an effect of how we see and interpret things.[4] You can say that our image somehow violates this principle. We are used to read from left to right, but the charts on the image are organized from right to left. This can be confusing.

- '''simplicity''':

You should keep your image as simple as possible, which also means that you have to reduce redundant information.[1] Our image violates this principle. The percentage of a lands contribution to the world production is shown on one hand via the angle and size of the pies and on the other hand it is written numerical above the pies.

== verbessertes Bild ==

== was wurde verbessert ==

== Resources ==

:[1] [Few, 2004] Stephen Few, Elegance Through Simplicity, Intelligent Enterprise, Access Date: 26 October 2005, http://www.intelligententerprise.com/showArticle.jhtml;jsessionid=N2ATDQWY5VYKSQSNDBGCKHSCJUMEKJVN?articleID=49400920

:[2] [Seyfang, Fritz, Schnabl, Baldass, 2005] Leonhard Seyfang, Heinrich Fritz, Stefan Schnabl, Gioia Baldass , Gruppe G8 - Aufgabe 1 - Chart Junk, InfoVis Wiki, Access Date: 26 October 2005, http://www.infovis-wiki.net/index.php/Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G8_-_Aufgabe_1_-_Chart_Junk

:[3] [Muster, Puchta, Rainer, Sölder, 2005] Anna Muster, Jürgen Puchta, Christian Rainer, Christoph Sölder, Gruppe G4 - Aufgabe 1 - Lie Factor, InfoVis Wiki, Access Date: 26 October 2005, http://www.infovis-wiki.net/index.php/Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G4_-_Aufgabe_1_-_Lie_Factor

:[4] [Starl, Froschauer, 205] Erwin Starl, Joseph Froschauer, Gruppe G7 - Aufgabe 1, InfoVis Wiki, Access Date: 26 October 2005, http://www.infovis-wiki.net/index.php/Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G7_-_Aufgabe_1_-_Gestalt_Laws

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

2005-10-26T16:29:51Z

UE-InfoVis0506 0057001:

== Poor Graphic ==
[[Image:Perceptualedge03world-car-production.gif|none|thumb|600px|World Car Production 1977-80 (click on image for larger version)]]

== Drawbacks ==

This image is far away from a good Visualization of the underlying Data. It has drawbacks according to some well known Design Principles, which we will explain in the following:

- '''data ink''':

Everything that communicates actual data is data ink and is needed.[1] But our image contains some unnecessary data ink. The white Border around all the charts and the white lines around each single chart and between the pies of the charts are unnecessary data ink.

- '''chart chunk''':

Chartjunk is a term for unnecessary or confusing visual elements in charts and graphs.[2] Our image uses 2D Pie charts. The problem is it seems that we look at the image not from the front but a little from the side. That distorts the message since neither the angles nor the areas are in proportion to the data.

- '''color''':

Lines, bars and charts should be colored in a way, that that no one color stands out more prominently than the others, thus supporting the equal importance of the three data sets.[1] In our image the red and blue pies of the charts violate this principle because they stand out more promonently than the others.

- '''lie factor''':

The lie lactor is a value to describe the relation between the size of effect shown in a graphic and the size of effect shown in the data.[3] You can consider the above mentioned chart chunk as a lie factor. The second one is that the charts have different distances to each other. The distance of the chart 1977 to the chart 1978 is shorter than that from 1979 to 1980. It schould be the same.

- '''past experience''':

That means that past experience have an effect of how we see and interpret things.[4] You can say that our image somehow violates this principle. We are used to read from left to right, but the charts on the image are organized from right to left. This can be confusing.

- '''simplicity''':

You should keep your image as simple as possible, which also means that you have to reduce redundant information. Our image violates this principle. The percentage of a lands contribution to the world production is shown on one hand via the angle and size of the pies and on the other hand it is written numerical above the pies.

== verbessertes Bild ==

== was wurde verbessert ==

== Resources ==

:[1] [Few, 2004] Stephen Few, Elegance Through Simplicity, Intelligent Enterprise, Access Date: 26 October 2005, http://www.intelligententerprise.com/showArticle.jhtml;jsessionid=N2ATDQWY5VYKSQSNDBGCKHSCJUMEKJVN?articleID=49400920

:[2] [Seyfang, Fritz, Schnabl, Baldass, 2005] Leonhard Seyfang, Heinrich Fritz, Stefan Schnabl, Gioia Baldass , Gruppe G8 - Aufgabe 1 - Chart Junk, InfoVis Wiki, Access Date: 26 October 2005, http://www.infovis-wiki.net/index.php/Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G8_-_Aufgabe_1_-_Chart_Junk

:[3] [Muster, Puchta, Rainer, Sölder, 2005] Anna Muster, Jürgen Puchta, Christian Rainer, Christoph Sölder, Gruppe G4 - Aufgabe 1 - Lie Factor, InfoVis Wiki, Access Date: 26 October 2005, http://www.infovis-wiki.net/index.php/Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G4_-_Aufgabe_1_-_Lie_Factor

:[4] [Starl, Froschauer, 205] Erwin Starl, Joseph Froschauer, Gruppe G7 - Aufgabe 1, InfoVis Wiki, Access Date: 26 October 2005, http://www.infovis-wiki.net/index.php/Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G7_-_Aufgabe_1_-_Gestalt_Laws

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

2005-10-26T16:27:23Z

UE-InfoVis0506 0057001:

== Poor Graphic ==
[[Image:Perceptualedge03world-car-production.gif|none|thumb|600px|World Car Production 1977-80 (click on image for larger version)]]

== Drawbacks ==

This image is far away from a good Visualization of the underlying Data. It has drawbacks according to some well known Design Principles, which we will explain in the following:

- '''data ink''':

Everything that communicates actual data is data ink and is needed.[1] But our image contains some unnecessary data ink. The white Border around all the charts and the white lines around each single chart and between the pies of the charts are unnecessary data ink.

- '''chart chunk''':

Chartjunk is a term for unnecessary or confusing visual elements in charts and graphs.[2] Our image uses 2D Pie charts. The problem is it seems that we look at the image not from the front but a little from the side. That distorts the message since neither the angles nor the areas are in proportion to the data.

- '''color''':

Lines, bars and charts should be colored in a way, that that no one color stands out more prominently than the others, thus supporting the equal importance of the three data sets.[1] In our image the red and blue pies of the charts violate this principle because they stand out more promonently than the others.

- '''lie factor''':

The lie lactor is a value to describe the relation between the size of effect shown in a graphic and the size of effect shown in the data.[3] You can consider the above mentioned chart chunk as a lie factor. The second one is that the charts have different distances to each other. The distance of the chart 1977 to the chart 1978 is shorter than that from 1979 to 1980. It schould be the same.

- '''past experience''':

That means that past experience have an effect of how we see and interpret things. You can say that our image somehow violates this principle. We are used to read from left to right, but the charts on the image are organized from right to left. This can be confusing.

- '''simplicity''':

You should keep your image as simple as possible, which also means that you have to reduce redundant information. Our image violates this principle. The percentage of a lands contribution to the world production is shown on one hand via the angle and size of the pies and on the other hand it is written numerical above the pies.

== verbessertes Bild ==

== was wurde verbessert ==

== Resources ==

:[1] [Few, 2004] Stephen Few, Elegance Through Simplicity, Intelligent Enterprise, Access Date: 26 October 2005, http://www.intelligententerprise.com/showArticle.jhtml;jsessionid=N2ATDQWY5VYKSQSNDBGCKHSCJUMEKJVN?articleID=49400920

:[2] [Seyfang, Fritz, Schnabl, Baldass, 2005] Leonhard Seyfang, Heinrich Fritz, Stefan Schnabl, Gioia Baldass , Gruppe G8 - Aufgabe 1 - Chart Junk, InfoVis Wiki, Access Date: 26 October 2005,
http://www.infovis-wiki.net/index.php/Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G8_-_Aufgabe_1_-_Chart_Junk

:[3] [Muster, Puchta, Rainer, Sölder, 2005] Anna Muster, Jürgen Puchta, Christian Rainer, Christoph Sölder, Gruppe G4 - Aufgabe 1 - Lie Factor, InfoVis Wiki, Access Date: 26 October 2005,
http://www.infovis-wiki.net/index.php/Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G4_-_Aufgabe_1_-_Lie_Factor

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

2005-10-26T15:55:11Z

UE-InfoVis0506 0057001:

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

2005-10-26T15:54:44Z

UE-InfoVis0506 0057001:

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

2005-10-26T15:54:33Z

UE-InfoVis0506 0057001:

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

2005-10-26T15:51:44Z

UE-InfoVis0506 0057001:

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

2005-10-26T15:47:07Z

UE-InfoVis0506 0057001:

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

2005-10-26T15:42:08Z

UE-InfoVis0506 0057001:

Teaching:TUW - UE InfoVis WS 2005/06

2005-10-17T20:44:32Z

UE-InfoVis0506 0057001:

[[Image:Aigner03infovis ue.gif]] <big>WS 2005/06</big>

'''LVA Nr:''' 188.308 ([http://tuwis.tuwien.ac.at/zope/_ZopeId/61534949A2B1pKks5u4/tpp/lv/lva_html?num=188308&sem=2005W TUWIS++ Seite])

'''LVA Homepage:''' http://www.asgaard.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html

'''Leitung:''' [[Aigner, Wolfgang|Wolfgang Aigner]] [aigner (at) ifs.tuwien.ac.at]

'''ACHTUNG:''' Namenskonventionen für Usernamen und Seiten einhalten! (siehe [http://www.asgaard.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe0.html Aufgabenstellung])

'''Bemerkung:''' Ein '''Stub''' ist ein Link bei dem das Ziel noch '''''nicht''''' existiert. (Die Links zu den Aufgabenseiten von den Gruppenseiten aus sollen Stubs sein.) 
*[[Das ist ein Stub]]
*[[Main Page|Das ist ein Link auf eine Seite innerhalb des Wikis]] (kein Stub)
*[http://www.asgaard.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html Das ist ein Link auf eine Seite ausserhalb des Wikis] (kein Stub)

'''FYI:''' Die E-mail Benachrichtigung funktioniert jetzt wieder. 
-- [[User:Iwolf|Wolfgang Aigner]] 09:48, 14 October 2005 (CEST)

Sollte jemand seine GruppenkollegInnen noch nicht kennen,
entweder über das TUWIS Forum der LVA posten oder
mich unter ''aigner (at) ifs.tuwien.ac.at'' kontaktieren. 
-- [[User:Iwolf|Wolfgang Aigner]] 11:45, 17 October 2005 (CEST)

== Gruppen ==
*[[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G1|Gruppe G1 (Schwarz, Ledinek)]]
*
*[[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G3|Gruppe G3 (Kargl, Karim, Rainer, ???)]]
*[[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G4|Gruppe G4 (Muster, Puchta, Rainer, Sölder)]]
*
*
*[[Teaching:TUW - UE InfoVis WS 2005/06 -Gruppe G7|Gruppe G7 (Yim, Froschauer, Lehrer, Starl)]]
*[[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G8|Gruppe G8 (Seyfang, Fritz, Schnabl, Winkelhofer)]]
*[[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 09|Gruppe 09 (Glashütter, Tonkovic, Obermair)]]
*[[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 10|Gruppe 10 (Minarik, Kals, Sahin, Slabschi)]]

Teaching:TUW - UE InfoVis WS 2005/06 -Gruppe G7

2005-10-17T20:37:56Z

UE-InfoVis0506 0057001:

== '''Gruppe G7''' ==

Die Gruppe G7 besteht bis jetzt aus den folgenden Mitgliedern: 
The following people are part of the G7 group by now:

* [[User:UE-InfoVis0506_0204041|Yim Seung-bin]]
* [[User:UE-InfoVis0506_0125718|Froschauer Josef]]
* [[User:UE-InfoVis0506_9426777|Lehrer Thomas]]
* [[User:UE-InfoVis0506_0057001|Starl Erwin]]

---- 
[[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 0|Aufgabe 0]] 
[[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 1|Aufgabe 1]] 
[[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 2|Aufgabe 2]] 
[[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G7 - Aufgabe 3|Aufgabe 3]]

User:UE-InfoVis0506 0057001

2005-10-17T20:35:47Z

UE-InfoVis0506 0057001:

'''Name:''' Starl Erwin 
'''MatNr:''' 0057001 
'''Kennzahl:''' 033 532 
'''e-mail:''' erwin_starl(at)gmx.at

User:UE-InfoVis0506 0057001

2005-10-17T20:35:40Z

UE-InfoVis0506 0057001:

'''Name:''' Starl Erwin 
'''MatNr:''' 0057001 
'''kennzahl:''' 033 532 
'''e-mail:''' erwin_starl(at)gmx.at

Teaching:TUW - UE InfoVis WS 2005/06 -Gruppe G7

2005-10-17T20:34:44Z

UE-InfoVis0506 0057001:

== '''Gruppe G7''' ==

Die Gruppe G7 besteht bis jetzt aus den folgenden Mitgliedern: 
The following people are part of the G7 group by now:

* [[User:UE-InfoVis0506_0204041|Yim Seung-bin]]
* [[User:UE-InfoVis0506_0125718|Froschauer Josef]]
* [[User:UE-InfoVis0506_9426777|Lehrer Thomas]]
* [[User:UE-InfoVis0506_0057001|Starl Erwin]]

---- 
[[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G4 - Aufgabe 0|Aufgabe 0]] 
[[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G4 - Aufgabe 1|Aufgabe 1]] 
[[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G4 - Aufgabe 2|Aufgabe 2]] 
[[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G4 - Aufgabe 3|Aufgabe 3]]

User:UE-InfoVis0506 0057001

2005-10-17T20:32:34Z

UE-InfoVis0506 0057001:

Starl Erwin
0057001
532
erwin_starl(at)gmx.at

User:UE-InfoVis0506 0057001

2005-10-17T20:32:19Z

UE-InfoVis0506 0057001:

Erwin Starl
0057001
532
erwin_starl(at)gmx.at