https://infovis-wiki.net/w/api.php?action=feedcontributions&feedformat=atom&user=UE-InfoVis0506+0025081 2026-04-20T16:50:29Z User contributions MediaWiki 1.45.3 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G3_-_Aufgabe_3_-_HTTP_Status_Code&diff=7976 2005-11-20T17:54:50Z

<p>UE-InfoVis0506 0025081: /* HTTP Status Codes */</p> <hr /> <div>===HTTP Status Codes===<br /> <br /> 100 Continue &lt;br&gt;<br /> 101 Switching Protocols &lt;br&gt;<br /> 200 OK &lt;br&gt;<br /> 201 Created &lt;br&gt;<br /> 202 Accepted &lt;br&gt;<br /> 203 Non-Authoritative Information &lt;br&gt;<br /> 204 No Content &lt;br&gt;<br /> 205 Reset Content &lt;br&gt;<br /> 206 Partial Content &lt;br&gt;<br /> 300 Multiple Choices &lt;br&gt;<br /> 301 Moved Permanently &lt;br&gt;<br /> 302 Moved Temporarily &lt;br&gt;<br /> 303 See Other &lt;br&gt;<br /> 304 Not Modified &lt;br&gt;<br /> 305 Use Proxy &lt;br&gt;<br /> 306 [Unused] &lt;br&gt;<br /> 307 Temporary Redirect &lt;br&gt;<br /> 400 Bad Request &lt;br&gt;<br /> 401 Unauthorized &lt;br&gt;<br /> 402 Payment Required &lt;br&gt;<br /> 403 Forbidden &lt;br&gt;<br /> 404 Not Found &lt;br&gt;<br /> 405 Method Not Allowed &lt;br&gt;<br /> 406 Not Acceptable &lt;br&gt;<br /> 407 Proxy Authentication Required &lt;br&gt;<br /> 408 Request Timeout &lt;br&gt;<br /> 409 Conflict &lt;br&gt;<br /> 410 Gone &lt;br&gt;<br /> 411 Length Required &lt;br&gt;<br /> 412 Precondition Failed &lt;br&gt;<br /> 413 Request Entity Too Large &lt;br&gt;<br /> 414 Request-URL Too Long &lt;br&gt;<br /> 415 Unsupported Media Type &lt;br&gt;<br /> 416 Requested Range Not Satisfiable &lt;br&gt;<br /> 417 Expectation Failed &lt;br&gt;<br /> 500 Internal Server Error &lt;br&gt;<br /> 501 Not Implemented &lt;br&gt;<br /> 502 Bad Gateway &lt;br&gt;<br /> 503 Service Unavailable &lt;br&gt;<br /> 504 Gateway Timeout &lt;br&gt;<br /> 505 HTTP Version Not Supported &lt;br&gt;<br /> <br /> Taken from Muenz [1][Mue]<br /> <br /> ===Reference===<br /> [1][Mue] Stefan Muenz, ''HTTP-Status-Codes''. Created at: March 21, 2005. Retrieved at: November 16, 2005. http://de.selfhtml.org/servercgi/server/httpstatuscodes.htm.</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G3_-_Aufgabe_3_-_HTTP_Status_Code&diff=7975 2005-11-20T17:54:26Z

<p>UE-InfoVis0506 0025081: /* HTTP Status Codes */</p> <hr /> <div>===HTTP Status Codes===<br /> <br /> 100 Continue &lt;br&gt;<br /> 101 Switching Protocols &lt;br&gt;<br /> 200 OK &lt;br&gt;<br /> 201 Created &lt;br&gt;<br /> 202 Accepted &lt;br&gt;<br /> 203 Non-Authoritative Information &lt;br&gt;<br /> 204 No Content &lt;br&gt;<br /> 205 Reset Content &lt;br&gt;<br /> 206 Partial Content &lt;br&gt;<br /> 300 Multiple Choices &lt;br&gt;<br /> 301 Moved Permanently &lt;br&gt;<br /> 302 Moved Temporarily &lt;br&gt;<br /> 303 See Other &lt;br&gt;<br /> 304 Not Modified &lt;br&gt;<br /> 305 Use Proxy &lt;br&gt;<br /> 306 [Unused] &lt;br&gt;<br /> 307 Temporary Redirect &lt;br&gt;<br /> 400 Bad Request &lt;br&gt;<br /> 401 Unauthorized &lt;br&gt;<br /> 402 Payment Required &lt;br&gt;<br /> 403 Forbidden &lt;br&gt;<br /> 404 Not Found &lt;br&gt;<br /> 405 Method Not Allowed &lt;br&gt;<br /> 406 Not Acceptable &lt;br&gt;<br /> 407 Proxy Authentication Required &lt;br&gt;<br /> 408 Request Timeout &lt;br&gt;<br /> 409 Conflict &lt;br&gt;<br /> 410 Gone &lt;br&gt;<br /> 411 Length Required &lt;br&gt;<br /> 412 Precondition Failed &lt;br&gt;<br /> 413 Request Entity Too Large &lt;br&gt;<br /> 414 Request-URL Too Long &lt;br&gt;<br /> 415 Unsupported Media Type &lt;br&gt;<br /> 416 Requested Range Not Satisfiable &lt;br&gt;<br /> 417 Expectation Failed &lt;br&gt;<br /> 500 Internal Server Error &lt;br&gt;<br /> 501 Not Implemented &lt;br&gt;<br /> 502 Bad Gateway &lt;br&gt;<br /> 503 Service Unavailable &lt;br&gt;<br /> 504 Gateway Timeout &lt;br&gt;<br /> 505 HTTP Version Not Supported &lt;br&gt;<br /> Taken from Muenz [1][Mue]<br /> <br /> ===Reference===<br /> [1][Mue] Stefan Muenz, ''HTTP-Status-Codes''. Created at: March 21, 2005. Retrieved at: November 16, 2005. http://de.selfhtml.org/servercgi/server/httpstatuscodes.htm.</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G3_-_Aufgabe_3&diff=7974 2005-11-20T17:53:46Z

<p>UE-InfoVis0506 0025081: /* References */</p> <hr /> <div>==Topic: Webserver Logfile Visualization==<br /> ==Application Area Analysis==<br /> ==Dataset Analysis==<br /> ===The Common Logfile Format===<br /> According to the World Wide Web Consortium the Common Logfile Format is as follows:<br /> ''remotehost rfc931 authuser [date] &quot;request&quot; status bytes''<br /> ''remotehost'': Remote hostname (or IP number if DNS hostname is not available, or if DNSLookup is Off.<br /> <br /> ''rfc931'': The remote logname of the user. <br /> <br /> ''authuser'': The username as which the user has authenticated himself. <br /> <br /> ''[date]'': Date and time of the request. <br /> <br /> ''&quot;request&quot;'': The request line exactly as it came from the client. <br /> <br /> ''status'': The [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G3 - Aufgabe 3 - HTTP Status Code| HTTP Status Code]] returned to the client. <br /> <br /> ''bytes'': The content-length of the document transferred. [1][W3C]<br /> ====Example====<br /> 66.249.71.39 - - [16/Oct/2005:05:57:17 +0200] &quot;GET /robots.txt HTTP/1.0&quot; 404 290 &quot;-&quot;&lt;br&gt; &quot;Googlebot/2.1 (+http://www.google.com/bot.html)&quot;<br /> <br /> ''remotehost'': 66.249.71.39<br /> <br /> ''rfc931'': -<br /> <br /> ''authuser'': -<br /> <br /> ''[date]'': [16/Oct/2005:05:57:17 +0200]<br /> <br /> ''&quot;request&quot;'': &quot;GET /robots.txt HTTP/1.0&quot;<br /> <br /> ''status'': 404<br /> <br /> ''bytes'': 290<br /> <br /> ===Datatypes===<br /> <br /> ==Target Group Analysis==<br /> <br /> <br /> ==Aim of the Visualization==<br /> ==Designproposal==<br /> ==References==<br /> [1][W3C] World Wide Web Consortium, &lt;i&gt;Logging Control In W3C httpd&lt;/i&gt;. Created at: July, 1995. Retrieved at: November 16, 2005. http://www.w3.org/Daemon/User/Config/Logging.html#common-logfile-format.</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G3_-_Aufgabe_3_-_HTTP_Status_Code&diff=7973 2005-11-20T17:53:23Z

<p>UE-InfoVis0506 0025081: </p> <hr /> <div>===HTTP Status Codes===<br /> <br /> 100 Continue &lt;br&gt;<br /> 101 Switching Protocols &lt;br&gt;<br /> 200 OK &lt;br&gt;<br /> 201 Created &lt;br&gt;<br /> 202 Accepted &lt;br&gt;<br /> 203 Non-Authoritative Information &lt;br&gt;<br /> 204 No Content &lt;br&gt;<br /> 205 Reset Content &lt;br&gt;<br /> 206 Partial Content &lt;br&gt;<br /> 300 Multiple Choices &lt;br&gt;<br /> 301 Moved Permanently &lt;br&gt;<br /> 302 Moved Temporarily &lt;br&gt;<br /> 303 See Other &lt;br&gt;<br /> 304 Not Modified &lt;br&gt;<br /> 305 Use Proxy &lt;br&gt;<br /> 306 [Unused] &lt;br&gt;<br /> 307 Temporary Redirect &lt;br&gt;<br /> 400 Bad Request &lt;br&gt;<br /> 401 Unauthorized &lt;br&gt;<br /> 402 Payment Required &lt;br&gt;<br /> 403 Forbidden &lt;br&gt;<br /> 404 Not Found &lt;br&gt;<br /> 405 Method Not Allowed &lt;br&gt;<br /> 406 Not Acceptable &lt;br&gt;<br /> 407 Proxy Authentication Required &lt;br&gt;<br /> 408 Request Timeout &lt;br&gt;<br /> 409 Conflict &lt;br&gt;<br /> 410 Gone &lt;br&gt;<br /> 411 Length Required &lt;br&gt;<br /> 412 Precondition Failed &lt;br&gt;<br /> 413 Request Entity Too Large &lt;br&gt;<br /> 414 Request-URL Too Long &lt;br&gt;<br /> 415 Unsupported Media Type &lt;br&gt;<br /> 416 Requested Range Not Satisfiable &lt;br&gt;<br /> 417 Expectation Failed &lt;br&gt;<br /> 500 Internal Server Error &lt;br&gt;<br /> 501 Not Implemented &lt;br&gt;<br /> 502 Bad Gateway &lt;br&gt;<br /> 503 Service Unavailable &lt;br&gt;<br /> 504 Gateway Timeout &lt;br&gt;<br /> 505 HTTP Version Not Supported &lt;br&gt;<br /> [2][Mue]</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G3_-_Aufgabe_3&diff=7972 2005-11-20T17:52:55Z

<p>UE-InfoVis0506 0025081: /* The Common Logfile Format */</p> <hr /> <div>==Topic: Webserver Logfile Visualization==<br /> ==Application Area Analysis==<br /> ==Dataset Analysis==<br /> ===The Common Logfile Format===<br /> According to the World Wide Web Consortium the Common Logfile Format is as follows:<br /> ''remotehost rfc931 authuser [date] &quot;request&quot; status bytes''<br /> ''remotehost'': Remote hostname (or IP number if DNS hostname is not available, or if DNSLookup is Off.<br /> <br /> ''rfc931'': The remote logname of the user. <br /> <br /> ''authuser'': The username as which the user has authenticated himself. <br /> <br /> ''[date]'': Date and time of the request. <br /> <br /> ''&quot;request&quot;'': The request line exactly as it came from the client. <br /> <br /> ''status'': The [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G3 - Aufgabe 3 - HTTP Status Code| HTTP Status Code]] returned to the client. <br /> <br /> ''bytes'': The content-length of the document transferred. [1][W3C]<br /> ====Example====<br /> 66.249.71.39 - - [16/Oct/2005:05:57:17 +0200] &quot;GET /robots.txt HTTP/1.0&quot; 404 290 &quot;-&quot;&lt;br&gt; &quot;Googlebot/2.1 (+http://www.google.com/bot.html)&quot;<br /> <br /> ''remotehost'': 66.249.71.39<br /> <br /> ''rfc931'': -<br /> <br /> ''authuser'': -<br /> <br /> ''[date]'': [16/Oct/2005:05:57:17 +0200]<br /> <br /> ''&quot;request&quot;'': &quot;GET /robots.txt HTTP/1.0&quot;<br /> <br /> ''status'': 404<br /> <br /> ''bytes'': 290<br /> <br /> ===Datatypes===<br /> <br /> ==Target Group Analysis==<br /> <br /> <br /> ==Aim of the Visualization==<br /> ==Designproposal==<br /> ==References==<br /> [1][W3C] World Wide Web Consortium, &lt;i&gt;Logging Control In W3C httpd&lt;/i&gt;. Created at: July, 1995. Retrieved at: November 16, 2005. http://www.w3.org/Daemon/User/Config/Logging.html#common-logfile-format.<br /> <br /> [2][Mue] Stefan Muenz, ''HTTP-Status-Codes''. Created at: March 21, 2005. Retrieved at: November 16, 2005. http://de.selfhtml.org/servercgi/server/httpstatuscodes.htm.</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G3_-_Aufgabe_3&diff=7971 2005-11-20T17:50:17Z

<p>UE-InfoVis0506 0025081: /* The Common Logfile Format */</p> <hr /> <div>==Topic: Webserver Logfile Visualization==<br /> ==Application Area Analysis==<br /> ==Dataset Analysis==<br /> ===The Common Logfile Format===<br /> According to the World Wide Web Consortium the Common Logfile Format is as follows:<br /> ''remotehost rfc931 authuser [date] &quot;request&quot; status bytes''<br /> ''remotehost'': Remote hostname (or IP number if DNS hostname is not available, or if DNSLookup is Off.<br /> <br /> ''rfc931'': The remote logname of the user. <br /> <br /> ''authuser'': The username as which the user has authenticated himself. <br /> <br /> ''[date]'': Date and time of the request. <br /> <br /> ''&quot;request&quot;'': The request line exactly as it came from the client. <br /> <br /> ''status'': The [[HTTP status code]] returned to the client. <br /> <br /> ''bytes'': The content-length of the document transferred. [1][W3C]<br /> ====Example====<br /> 66.249.71.39 - - [16/Oct/2005:05:57:17 +0200] &quot;GET /robots.txt HTTP/1.0&quot; 404 290 &quot;-&quot;&lt;br&gt; &quot;Googlebot/2.1 (+http://www.google.com/bot.html)&quot;<br /> <br /> ''remotehost'': 66.249.71.39<br /> <br /> ''rfc931'': -<br /> <br /> ''authuser'': -<br /> <br /> ''[date]'': [16/Oct/2005:05:57:17 +0200]<br /> <br /> ''&quot;request&quot;'': &quot;GET /robots.txt HTTP/1.0&quot;<br /> <br /> ''status'': 404<br /> <br /> ''bytes'': 290<br /> <br /> ====HTTP Status Codes====<br /> <br /> 100 Continue &lt;br&gt;<br /> 101 Switching Protocols &lt;br&gt;<br /> 200 OK &lt;br&gt;<br /> 201 Created &lt;br&gt;<br /> 202 Accepted &lt;br&gt;<br /> 203 Non-Authoritative Information &lt;br&gt;<br /> 204 No Content &lt;br&gt;<br /> 205 Reset Content &lt;br&gt;<br /> 206 Partial Content &lt;br&gt;<br /> 300 Multiple Choices &lt;br&gt;<br /> 301 Moved Permanently &lt;br&gt;<br /> 302 Moved Temporarily &lt;br&gt;<br /> 303 See Other &lt;br&gt;<br /> 304 Not Modified &lt;br&gt;<br /> 305 Use Proxy &lt;br&gt;<br /> 306 [Unused] &lt;br&gt;<br /> 307 Temporary Redirect &lt;br&gt;<br /> 400 Bad Request &lt;br&gt;<br /> 401 Unauthorized &lt;br&gt;<br /> 402 Payment Required &lt;br&gt;<br /> 403 Forbidden &lt;br&gt;<br /> 404 Not Found &lt;br&gt;<br /> 405 Method Not Allowed &lt;br&gt;<br /> 406 Not Acceptable &lt;br&gt;<br /> 407 Proxy Authentication Required &lt;br&gt;<br /> 408 Request Timeout &lt;br&gt;<br /> 409 Conflict &lt;br&gt;<br /> 410 Gone &lt;br&gt;<br /> 411 Length Required &lt;br&gt;<br /> 412 Precondition Failed &lt;br&gt;<br /> 413 Request Entity Too Large &lt;br&gt;<br /> 414 Request-URL Too Long &lt;br&gt;<br /> 415 Unsupported Media Type &lt;br&gt;<br /> 416 Requested Range Not Satisfiable &lt;br&gt;<br /> 417 Expectation Failed &lt;br&gt;<br /> 500 Internal Server Error &lt;br&gt;<br /> 501 Not Implemented &lt;br&gt;<br /> 502 Bad Gateway &lt;br&gt;<br /> 503 Service Unavailable &lt;br&gt;<br /> 504 Gateway Timeout &lt;br&gt;<br /> 505 HTTP Version Not Supported &lt;br&gt;<br /> [2][Mue]<br /> <br /> ===Datatypes===<br /> <br /> ==Target Group Analysis==<br /> <br /> <br /> ==Aim of the Visualization==<br /> ==Designproposal==<br /> ==References==<br /> [1][W3C] World Wide Web Consortium, &lt;i&gt;Logging Control In W3C httpd&lt;/i&gt;. Created at: July, 1995. Retrieved at: November 16, 2005. http://www.w3.org/Daemon/User/Config/Logging.html#common-logfile-format.<br /> <br /> [2][Mue] Stefan Muenz, ''HTTP-Status-Codes''. Created at: March 21, 2005. Retrieved at: November 16, 2005. http://de.selfhtml.org/servercgi/server/httpstatuscodes.htm.</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G3_-_Aufgabe_3&diff=7969 2005-11-20T17:48:37Z

<p>UE-InfoVis0506 0025081: /* HTTP Status Codes */</p> <hr /> <div>==Topic: Webserver Logfile Visualization==<br /> ==Application Area Analysis==<br /> ==Dataset Analysis==<br /> ===The Common Logfile Format===<br /> According to the World Wide Web Consortium the Common Logfile Format is as follows:<br /> ''remotehost rfc931 authuser [date] &quot;request&quot; status bytes''<br /> ''remotehost'': Remote hostname (or IP number if DNS hostname is not available, or if DNSLookup is Off.<br /> <br /> ''rfc931'': The remote logname of the user. <br /> <br /> ''authuser'': The username as which the user has authenticated himself. <br /> <br /> ''[date]'': Date and time of the request. <br /> <br /> ''&quot;request&quot;'': The request line exactly as it came from the client. <br /> <br /> ''status'': The HTTP status code returned to the client. <br /> <br /> ''bytes'': The content-length of the document transferred. [1][W3C]<br /> ====Example====<br /> 66.249.71.39 - - [16/Oct/2005:05:57:17 +0200] &quot;GET /robots.txt HTTP/1.0&quot; 404 290 &quot;-&quot;&lt;br&gt; &quot;Googlebot/2.1 (+http://www.google.com/bot.html)&quot;<br /> <br /> ''remotehost'': 66.249.71.39<br /> <br /> ''rfc931'': -<br /> <br /> ''authuser'': -<br /> <br /> ''[date]'': [16/Oct/2005:05:57:17 +0200]<br /> <br /> ''&quot;request&quot;'': &quot;GET /robots.txt HTTP/1.0&quot;<br /> <br /> ''status'': 404<br /> <br /> ''bytes'': 290<br /> <br /> ====HTTP Status Codes====<br /> <br /> 100 Continue &lt;br&gt;<br /> 101 Switching Protocols &lt;br&gt;<br /> 200 OK &lt;br&gt;<br /> 201 Created &lt;br&gt;<br /> 202 Accepted &lt;br&gt;<br /> 203 Non-Authoritative Information &lt;br&gt;<br /> 204 No Content &lt;br&gt;<br /> 205 Reset Content &lt;br&gt;<br /> 206 Partial Content &lt;br&gt;<br /> 300 Multiple Choices &lt;br&gt;<br /> 301 Moved Permanently &lt;br&gt;<br /> 302 Moved Temporarily &lt;br&gt;<br /> 303 See Other &lt;br&gt;<br /> 304 Not Modified &lt;br&gt;<br /> 305 Use Proxy &lt;br&gt;<br /> 306 [Unused] &lt;br&gt;<br /> 307 Temporary Redirect &lt;br&gt;<br /> 400 Bad Request &lt;br&gt;<br /> 401 Unauthorized &lt;br&gt;<br /> 402 Payment Required &lt;br&gt;<br /> 403 Forbidden &lt;br&gt;<br /> 404 Not Found &lt;br&gt;<br /> 405 Method Not Allowed &lt;br&gt;<br /> 406 Not Acceptable &lt;br&gt;<br /> 407 Proxy Authentication Required &lt;br&gt;<br /> 408 Request Timeout &lt;br&gt;<br /> 409 Conflict &lt;br&gt;<br /> 410 Gone &lt;br&gt;<br /> 411 Length Required &lt;br&gt;<br /> 412 Precondition Failed &lt;br&gt;<br /> 413 Request Entity Too Large &lt;br&gt;<br /> 414 Request-URL Too Long &lt;br&gt;<br /> 415 Unsupported Media Type &lt;br&gt;<br /> 416 Requested Range Not Satisfiable &lt;br&gt;<br /> 417 Expectation Failed &lt;br&gt;<br /> 500 Internal Server Error &lt;br&gt;<br /> 501 Not Implemented &lt;br&gt;<br /> 502 Bad Gateway &lt;br&gt;<br /> 503 Service Unavailable &lt;br&gt;<br /> 504 Gateway Timeout &lt;br&gt;<br /> 505 HTTP Version Not Supported &lt;br&gt;<br /> [2][Mue]<br /> <br /> ===Datatypes===<br /> <br /> ==Target Group Analysis==<br /> <br /> <br /> ==Aim of the Visualization==<br /> ==Designproposal==<br /> ==References==<br /> [1][W3C] World Wide Web Consortium, &lt;i&gt;Logging Control In W3C httpd&lt;/i&gt;. Created at: July, 1995. Retrieved at: November 16, 2005. http://www.w3.org/Daemon/User/Config/Logging.html#common-logfile-format.<br /> <br /> [2][Mue] Stefan Muenz, ''HTTP-Status-Codes''. Created at: March 21, 2005. Retrieved at: November 16, 2005. http://de.selfhtml.org/servercgi/server/httpstatuscodes.htm.</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G3_-_Aufgabe_3&diff=7968 2005-11-20T17:48:23Z

<p>UE-InfoVis0506 0025081: /* References */</p> <hr /> <div>==Topic: Webserver Logfile Visualization==<br /> ==Application Area Analysis==<br /> ==Dataset Analysis==<br /> ===The Common Logfile Format===<br /> According to the World Wide Web Consortium the Common Logfile Format is as follows:<br /> ''remotehost rfc931 authuser [date] &quot;request&quot; status bytes''<br /> ''remotehost'': Remote hostname (or IP number if DNS hostname is not available, or if DNSLookup is Off.<br /> <br /> ''rfc931'': The remote logname of the user. <br /> <br /> ''authuser'': The username as which the user has authenticated himself. <br /> <br /> ''[date]'': Date and time of the request. <br /> <br /> ''&quot;request&quot;'': The request line exactly as it came from the client. <br /> <br /> ''status'': The HTTP status code returned to the client. <br /> <br /> ''bytes'': The content-length of the document transferred. [1][W3C]<br /> ====Example====<br /> 66.249.71.39 - - [16/Oct/2005:05:57:17 +0200] &quot;GET /robots.txt HTTP/1.0&quot; 404 290 &quot;-&quot;&lt;br&gt; &quot;Googlebot/2.1 (+http://www.google.com/bot.html)&quot;<br /> <br /> ''remotehost'': 66.249.71.39<br /> <br /> ''rfc931'': -<br /> <br /> ''authuser'': -<br /> <br /> ''[date]'': [16/Oct/2005:05:57:17 +0200]<br /> <br /> ''&quot;request&quot;'': &quot;GET /robots.txt HTTP/1.0&quot;<br /> <br /> ''status'': 404<br /> <br /> ''bytes'': 290<br /> <br /> ====HTTP Status Codes====<br /> <br /> 100 Continue &lt;br&gt;<br /> 101 Switching Protocols &lt;br&gt;<br /> 200 OK &lt;br&gt;<br /> 201 Created &lt;br&gt;<br /> 202 Accepted &lt;br&gt;<br /> 203 Non-Authoritative Information &lt;br&gt;<br /> 204 No Content &lt;br&gt;<br /> 205 Reset Content &lt;br&gt;<br /> 206 Partial Content &lt;br&gt;<br /> 300 Multiple Choices &lt;br&gt;<br /> 301 Moved Permanently &lt;br&gt;<br /> 302 Moved Temporarily &lt;br&gt;<br /> 303 See Other &lt;br&gt;<br /> 304 Not Modified &lt;br&gt;<br /> 305 Use Proxy &lt;br&gt;<br /> 306 [Unused] &lt;br&gt;<br /> 307 Temporary Redirect &lt;br&gt;<br /> 400 Bad Request &lt;br&gt;<br /> 401 Unauthorized &lt;br&gt;<br /> 402 Payment Required &lt;br&gt;<br /> 403 Forbidden &lt;br&gt;<br /> 404 Not Found &lt;br&gt;<br /> 405 Method Not Allowed &lt;br&gt;<br /> 406 Not Acceptable &lt;br&gt;<br /> 407 Proxy Authentication Required &lt;br&gt;<br /> 408 Request Timeout &lt;br&gt;<br /> 409 Conflict &lt;br&gt;<br /> 410 Gone &lt;br&gt;<br /> 411 Length Required &lt;br&gt;<br /> 412 Precondition Failed &lt;br&gt;<br /> 413 Request Entity Too Large &lt;br&gt;<br /> 414 Request-URL Too Long &lt;br&gt;<br /> 415 Unsupported Media Type &lt;br&gt;<br /> 416 Requested Range Not Satisfiable &lt;br&gt;<br /> 417 Expectation Failed &lt;br&gt;<br /> 500 Internal Server Error &lt;br&gt;<br /> 501 Not Implemented &lt;br&gt;<br /> 502 Bad Gateway &lt;br&gt;<br /> 503 Service Unavailable &lt;br&gt;<br /> 504 Gateway Timeout &lt;br&gt;<br /> 505 HTTP Version Not Supported &lt;br&gt;<br /> [2][Sel]<br /> <br /> ===Datatypes===<br /> <br /> ==Target Group Analysis==<br /> <br /> <br /> ==Aim of the Visualization==<br /> ==Designproposal==<br /> ==References==<br /> [1][W3C] World Wide Web Consortium, &lt;i&gt;Logging Control In W3C httpd&lt;/i&gt;. Created at: July, 1995. Retrieved at: November 16, 2005. http://www.w3.org/Daemon/User/Config/Logging.html#common-logfile-format.<br /> <br /> [2][Mue] Stefan Muenz, ''HTTP-Status-Codes''. Created at: March 21, 2005. Retrieved at: November 16, 2005. http://de.selfhtml.org/servercgi/server/httpstatuscodes.htm.</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G3_-_Aufgabe_3&diff=7967 2005-11-20T17:48:11Z

<p>UE-InfoVis0506 0025081: /* References */</p> <hr /> <div>==Topic: Webserver Logfile Visualization==<br /> ==Application Area Analysis==<br /> ==Dataset Analysis==<br /> ===The Common Logfile Format===<br /> According to the World Wide Web Consortium the Common Logfile Format is as follows:<br /> ''remotehost rfc931 authuser [date] &quot;request&quot; status bytes''<br /> ''remotehost'': Remote hostname (or IP number if DNS hostname is not available, or if DNSLookup is Off.<br /> <br /> ''rfc931'': The remote logname of the user. <br /> <br /> ''authuser'': The username as which the user has authenticated himself. <br /> <br /> ''[date]'': Date and time of the request. <br /> <br /> ''&quot;request&quot;'': The request line exactly as it came from the client. <br /> <br /> ''status'': The HTTP status code returned to the client. <br /> <br /> ''bytes'': The content-length of the document transferred. [1][W3C]<br /> ====Example====<br /> 66.249.71.39 - - [16/Oct/2005:05:57:17 +0200] &quot;GET /robots.txt HTTP/1.0&quot; 404 290 &quot;-&quot;&lt;br&gt; &quot;Googlebot/2.1 (+http://www.google.com/bot.html)&quot;<br /> <br /> ''remotehost'': 66.249.71.39<br /> <br /> ''rfc931'': -<br /> <br /> ''authuser'': -<br /> <br /> ''[date]'': [16/Oct/2005:05:57:17 +0200]<br /> <br /> ''&quot;request&quot;'': &quot;GET /robots.txt HTTP/1.0&quot;<br /> <br /> ''status'': 404<br /> <br /> ''bytes'': 290<br /> <br /> ====HTTP Status Codes====<br /> <br /> 100 Continue &lt;br&gt;<br /> 101 Switching Protocols &lt;br&gt;<br /> 200 OK &lt;br&gt;<br /> 201 Created &lt;br&gt;<br /> 202 Accepted &lt;br&gt;<br /> 203 Non-Authoritative Information &lt;br&gt;<br /> 204 No Content &lt;br&gt;<br /> 205 Reset Content &lt;br&gt;<br /> 206 Partial Content &lt;br&gt;<br /> 300 Multiple Choices &lt;br&gt;<br /> 301 Moved Permanently &lt;br&gt;<br /> 302 Moved Temporarily &lt;br&gt;<br /> 303 See Other &lt;br&gt;<br /> 304 Not Modified &lt;br&gt;<br /> 305 Use Proxy &lt;br&gt;<br /> 306 [Unused] &lt;br&gt;<br /> 307 Temporary Redirect &lt;br&gt;<br /> 400 Bad Request &lt;br&gt;<br /> 401 Unauthorized &lt;br&gt;<br /> 402 Payment Required &lt;br&gt;<br /> 403 Forbidden &lt;br&gt;<br /> 404 Not Found &lt;br&gt;<br /> 405 Method Not Allowed &lt;br&gt;<br /> 406 Not Acceptable &lt;br&gt;<br /> 407 Proxy Authentication Required &lt;br&gt;<br /> 408 Request Timeout &lt;br&gt;<br /> 409 Conflict &lt;br&gt;<br /> 410 Gone &lt;br&gt;<br /> 411 Length Required &lt;br&gt;<br /> 412 Precondition Failed &lt;br&gt;<br /> 413 Request Entity Too Large &lt;br&gt;<br /> 414 Request-URL Too Long &lt;br&gt;<br /> 415 Unsupported Media Type &lt;br&gt;<br /> 416 Requested Range Not Satisfiable &lt;br&gt;<br /> 417 Expectation Failed &lt;br&gt;<br /> 500 Internal Server Error &lt;br&gt;<br /> 501 Not Implemented &lt;br&gt;<br /> 502 Bad Gateway &lt;br&gt;<br /> 503 Service Unavailable &lt;br&gt;<br /> 504 Gateway Timeout &lt;br&gt;<br /> 505 HTTP Version Not Supported &lt;br&gt;<br /> [2][Sel]<br /> <br /> ===Datatypes===<br /> <br /> ==Target Group Analysis==<br /> <br /> <br /> ==Aim of the Visualization==<br /> ==Designproposal==<br /> ==References==<br /> [1][W3C] World Wide Web Consortium, &lt;i&gt;Logging Control In W3C httpd&lt;/i&gt;. Created at: July, 1995. Retrieved at: November 16, 2005. http://www.w3.org/Daemon/User/Config/Logging.html#common-logfile-format.<br /> [2][Mue] Stefan Muenz, ''HTTP-Status-Codes''. Created at: March 21, 2005. Retrieved at: November 16, 2005. http://de.selfhtml.org/servercgi/server/httpstatuscodes.htm.</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G3_-_Aufgabe_3&diff=7966 2005-11-20T17:45:06Z

<p>UE-InfoVis0506 0025081: /* The Common Logfile Format */</p> <hr /> <div>==Topic: Webserver Logfile Visualization==<br /> ==Application Area Analysis==<br /> ==Dataset Analysis==<br /> ===The Common Logfile Format===<br /> According to the World Wide Web Consortium the Common Logfile Format is as follows:<br /> ''remotehost rfc931 authuser [date] &quot;request&quot; status bytes''<br /> ''remotehost'': Remote hostname (or IP number if DNS hostname is not available, or if DNSLookup is Off.<br /> <br /> ''rfc931'': The remote logname of the user. <br /> <br /> ''authuser'': The username as which the user has authenticated himself. <br /> <br /> ''[date]'': Date and time of the request. <br /> <br /> ''&quot;request&quot;'': The request line exactly as it came from the client. <br /> <br /> ''status'': The HTTP status code returned to the client. <br /> <br /> ''bytes'': The content-length of the document transferred. [1][W3C]<br /> ====Example====<br /> 66.249.71.39 - - [16/Oct/2005:05:57:17 +0200] &quot;GET /robots.txt HTTP/1.0&quot; 404 290 &quot;-&quot;&lt;br&gt; &quot;Googlebot/2.1 (+http://www.google.com/bot.html)&quot;<br /> <br /> ''remotehost'': 66.249.71.39<br /> <br /> ''rfc931'': -<br /> <br /> ''authuser'': -<br /> <br /> ''[date]'': [16/Oct/2005:05:57:17 +0200]<br /> <br /> ''&quot;request&quot;'': &quot;GET /robots.txt HTTP/1.0&quot;<br /> <br /> ''status'': 404<br /> <br /> ''bytes'': 290<br /> <br /> ====HTTP Status Codes====<br /> <br /> 100 Continue &lt;br&gt;<br /> 101 Switching Protocols &lt;br&gt;<br /> 200 OK &lt;br&gt;<br /> 201 Created &lt;br&gt;<br /> 202 Accepted &lt;br&gt;<br /> 203 Non-Authoritative Information &lt;br&gt;<br /> 204 No Content &lt;br&gt;<br /> 205 Reset Content &lt;br&gt;<br /> 206 Partial Content &lt;br&gt;<br /> 300 Multiple Choices &lt;br&gt;<br /> 301 Moved Permanently &lt;br&gt;<br /> 302 Moved Temporarily &lt;br&gt;<br /> 303 See Other &lt;br&gt;<br /> 304 Not Modified &lt;br&gt;<br /> 305 Use Proxy &lt;br&gt;<br /> 306 [Unused] &lt;br&gt;<br /> 307 Temporary Redirect &lt;br&gt;<br /> 400 Bad Request &lt;br&gt;<br /> 401 Unauthorized &lt;br&gt;<br /> 402 Payment Required &lt;br&gt;<br /> 403 Forbidden &lt;br&gt;<br /> 404 Not Found &lt;br&gt;<br /> 405 Method Not Allowed &lt;br&gt;<br /> 406 Not Acceptable &lt;br&gt;<br /> 407 Proxy Authentication Required &lt;br&gt;<br /> 408 Request Timeout &lt;br&gt;<br /> 409 Conflict &lt;br&gt;<br /> 410 Gone &lt;br&gt;<br /> 411 Length Required &lt;br&gt;<br /> 412 Precondition Failed &lt;br&gt;<br /> 413 Request Entity Too Large &lt;br&gt;<br /> 414 Request-URL Too Long &lt;br&gt;<br /> 415 Unsupported Media Type &lt;br&gt;<br /> 416 Requested Range Not Satisfiable &lt;br&gt;<br /> 417 Expectation Failed &lt;br&gt;<br /> 500 Internal Server Error &lt;br&gt;<br /> 501 Not Implemented &lt;br&gt;<br /> 502 Bad Gateway &lt;br&gt;<br /> 503 Service Unavailable &lt;br&gt;<br /> 504 Gateway Timeout &lt;br&gt;<br /> 505 HTTP Version Not Supported &lt;br&gt;<br /> [2][Sel]<br /> <br /> ===Datatypes===<br /> <br /> ==Target Group Analysis==<br /> <br /> <br /> ==Aim of the Visualization==<br /> ==Designproposal==<br /> ==References==<br /> [1][W3C]World Wide Web Consortium, &lt;i&gt;Logging Control In W3C httpd&lt;/i&gt;. Created at: July, 1995. Retrieved at: November 16, 2005. http://www.w3.org/Daemon/User/Config/Logging.html#common-logfile-format.</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G3_-_Aufgabe_3&diff=7965 2005-11-20T17:41:15Z

<p>UE-InfoVis0506 0025081: /* The Common Logfile Format */</p> <hr /> <div>==Topic: Webserver Logfile Visualization==<br /> ==Application Area Analysis==<br /> ==Dataset Analysis==<br /> ===The Common Logfile Format===<br /> According to the World Wide Web Consortium the Common Logfile Format is as follows:<br /> ''remotehost rfc931 authuser [date] &quot;request&quot; status bytes''<br /> ''remotehost'': Remote hostname (or IP number if DNS hostname is not available, or if DNSLookup is Off.<br /> <br /> ''rfc931'': The remote logname of the user. <br /> <br /> ''authuser'': The username as which the user has authenticated himself. <br /> <br /> ''[date]'': Date and time of the request. <br /> <br /> ''&quot;request&quot;'': The request line exactly as it came from the client. <br /> <br /> ''status'': The HTTP status code returned to the client. <br /> <br /> ''bytes'': The content-length of the document transferred. [1][W3C]<br /> ====Example====<br /> 66.249.71.39 - - [16/Oct/2005:05:57:17 +0200] &quot;GET /robots.txt HTTP/1.0&quot; 404 290 &quot;-&quot; &quot;Googlebot/2.1 (+http://www.google.com/bot.html)&quot;<br /> <br /> ''remotehost'': 66.249.71.39<br /> <br /> ''rfc931'': -<br /> <br /> ''authuser'': -<br /> <br /> ''[date]'': [16/Oct/2005:05:57:17 +0200]<br /> <br /> ''&quot;request&quot;'': &quot;GET /robots.txt HTTP/1.0&quot;<br /> <br /> ''status'': 404<br /> <br /> ''bytes'': 290<br /> <br /> ====HTTP Status Codes====<br /> <br /> Status-Code zugehörige Meldung<br /> 100 Continue<br /> 101 Switching Protocols<br /> 200 OK<br /> 201 Created<br /> 202 Accepted<br /> 203 Non-Authoritative Information<br /> 204 No Content<br /> 205 Reset Content<br /> 206 Partial Content<br /> 300 Multiple Choices<br /> 301 Moved Permanently<br /> 302 Moved Temporarily<br /> 303 See Other<br /> 304 Not Modified<br /> 305 Use Proxy<br /> 306 [Unused]<br /> 307 Temporary Redirect<br /> 400 Bad Request<br /> 401 Unauthorized<br /> 402 Payment Required<br /> 403 Forbidden<br /> 404 Not Found<br /> 405 Method Not Allowed<br /> 406 Not Acceptable<br /> 407 Proxy Authentication Required<br /> 408 Request Timeout<br /> 409 Conflict<br /> 410 Gone<br /> 411 Length Required<br /> 412 Precondition Failed<br /> 413 Request Entity Too Large<br /> 414 Request-URL Too Long<br /> 415 Unsupported Media Type<br /> 416 Requested Range Not Satisfiable<br /> 417 Expectation Failed<br /> 500 Internal Server Error<br /> 501 Not Implemented<br /> 502 Bad Gateway<br /> 503 Service Unavailable<br /> 504 Gateway Timeout<br /> 505 HTTP Version Not Supported<br /> <br /> ===Datatypes===<br /> <br /> ==Target Group Analysis==<br /> <br /> <br /> ==Aim of the Visualization==<br /> ==Designproposal==<br /> ==References==<br /> [1][W3C]World Wide Web Consortium, &lt;i&gt;Logging Control In W3C httpd&lt;/i&gt;. Created at: July, 1995. Retrieved at: November 16, 2005. http://www.w3.org/Daemon/User/Config/Logging.html#common-logfile-format.</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G3_-_Aufgabe_3&diff=7963 2005-11-20T17:37:33Z

<p>UE-InfoVis0506 0025081: /* The Common Logfile Format */</p> <hr /> <div>==Topic: Webserver Logfile Visualization==<br /> ==Application Area Analysis==<br /> ==Dataset Analysis==<br /> ===The Common Logfile Format===<br /> According to the World Wide Web Consortium the Common Logfile Format is as follows:<br /> ''remotehost rfc931 authuser [date] &quot;request&quot; status bytes''<br /> ''remotehost'': Remote hostname (or IP number if DNS hostname is not available, or if DNSLookup is Off.<br /> <br /> ''rfc931'': The remote logname of the user. <br /> <br /> ''authuser'': The username as which the user has authenticated himself. <br /> <br /> ''[date]'': Date and time of the request. <br /> <br /> ''&quot;request&quot;'': The request line exactly as it came from the client. <br /> <br /> ''status'': The HTTP status code returned to the client. <br /> <br /> ''bytes'': The content-length of the document transferred. [1][W3C]<br /> ====Example====<br /> 66.249.71.39 - - [16/Oct/2005:05:57:17 +0200] &quot;GET /robots.txt HTTP/1.0&quot; 404 290 &quot;-&quot; &quot;Googlebot/2.1 (+http://www.google.com/bot.html)&quot;<br /> <br /> ''remotehost'': 66.249.71.39<br /> <br /> ''rfc931'': -<br /> <br /> ''authuser'': -<br /> <br /> ''[date]'': [16/Oct/2005:05:57:17 +0200]<br /> <br /> ''&quot;request&quot;'': &quot;GET /robots.txt HTTP/1.0&quot;<br /> <br /> ''status'': 404<br /> <br /> ''bytes'': 290<br /> <br /> ===Datatypes===<br /> <br /> ==Target Group Analysis==<br /> <br /> <br /> ==Aim of the Visualization==<br /> ==Designproposal==<br /> ==References==<br /> [1][W3C]World Wide Web Consortium, &lt;i&gt;Logging Control In W3C httpd&lt;/i&gt;. Created at: July, 1995. Retrieved at: November 16, 2005. http://www.w3.org/Daemon/User/Config/Logging.html#common-logfile-format.</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G3_-_Aufgabe_3&diff=7959 2005-11-20T17:26:26Z

<p>UE-InfoVis0506 0025081: /* The Common Logfile Format */</p> <hr /> <div>==Topic: Webserver Logfile Visualization==<br /> ==Application Area Analysis==<br /> ==Dataset Analysis==<br /> ===The Common Logfile Format===<br /> According to the World Wide Web Consortium the Common Logfile Format is as follows:<br /> ''remotehost rfc931 authuser [date] &quot;request&quot; status bytes''<br /> ''remotehost'': Remote hostname (or IP number if DNS hostname is not available, or if DNSLookup is Off.<br /> <br /> ''rfc931'': The remote logname of the user. <br /> <br /> ''authuser'': The username as which the user has authenticated himself. <br /> <br /> ''[date]'': Date and time of the request. <br /> <br /> ''&quot;request&quot;'': The request line exactly as it came from the client. <br /> <br /> ''status'': The HTTP status code returned to the client. <br /> <br /> ''bytes'': The content-length of the document transferred. [1][W3C]<br /> <br /> ===Datatypes===<br /> <br /> ==Target Group Analysis==<br /> <br /> <br /> ==Aim of the Visualization==<br /> ==Designproposal==<br /> ==References==<br /> [1][W3C]World Wide Web Consortium, &lt;i&gt;Logging Control In W3C httpd&lt;/i&gt;. Created at: July, 1995. Retrieved at: November 16, 2005. http://www.w3.org/Daemon/User/Config/Logging.html#common-logfile-format.</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G3_-_Aufgabe_3&diff=7958 2005-11-20T17:05:49Z

<p>UE-InfoVis0506 0025081: /* The Common Logfile Format */</p> <hr /> <div>==Topic: Webserver Logfile Visualization==<br /> ==Application Area Analysis==<br /> ==Dataset Analysis==<br /> ===The Common Logfile Format===<br /> According to the World Wide Web Consortium [1][W3C] the Common Logfile Format is as follows:<br /> ''remotehost rfc931 authuser [date] &quot;request&quot; status bytes''<br /> ''remotehost'': Remote hostname (or IP number if DNS hostname is not available, or if DNSLookup is Off.<br /> <br /> ''rfc931'': The remote logname of the user. <br /> <br /> ''authuser'': The username as which the user has authenticated himself. <br /> <br /> ''[date]'': Date and time of the request. <br /> <br /> ''&quot;request&quot;'': The request line exactly as it came from the client. <br /> <br /> ''status'': The HTTP status code returned to the client. <br /> <br /> ''bytes'': The content-length of the document transferred.<br /> <br /> ===Datatypes===<br /> <br /> ==Target Group Analysis==<br /> <br /> <br /> ==Aim of the Visualization==<br /> ==Designproposal==<br /> ==References==<br /> [1][W3C]World Wide Web Consortium, &lt;i&gt;Logging Control In W3C httpd&lt;/i&gt;. Created at: July, 1995. Retrieved at: November 16, 2005. http://www.w3.org/Daemon/User/Config/Logging.html#common-logfile-format.</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G3_-_Aufgabe_3&diff=7956 2005-11-20T16:58:49Z

<p>UE-InfoVis0506 0025081: /* Dataset Analysis */</p> <hr /> <div>==Topic: Webserver Logfile Visualization==<br /> ==Application Area Analysis==<br /> ==Dataset Analysis==<br /> ===The Common Logfile Format===<br /> The common logfile format is as follows:<br /> ''remotehost rfc931 authuser [date] &quot;request&quot; status bytes''<br /> ''remotehost'': Remote hostname (or IP number if DNS hostname is not available, or if DNSLookup is Off.<br /> <br /> ''rfc931'': The remote logname of the user. <br /> <br /> ''authuser'': The username as which the user has authenticated himself. <br /> <br /> ''[date]'': Date and time of the request. <br /> <br /> ''&quot;request&quot;'': The request line exactly as it came from the client. <br /> <br /> ''status'': The HTTP status code returned to the client. <br /> <br /> ''bytes'': The content-length of the document transferred. [1][W3C]<br /> ===Datatypes===<br /> <br /> ==Target Group Analysis==<br /> <br /> <br /> ==Aim of the Visualization==<br /> ==Designproposal==<br /> ==References==<br /> [1][W3C]World Wide Web Consortium, &lt;i&gt;Logging Control In W3C httpd&lt;/i&gt;. Created at: July, 1995. Retrieved at: November 16, 2005. http://www.w3.org/Daemon/User/Config/Logging.html#common-logfile-format.</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G3_-_Aufgabe_3&diff=7949 2005-11-20T16:34:27Z

<p>UE-InfoVis0506 0025081: /* Dataset Analysis */</p> <hr /> <div>==Topic: Webserver Logfile Visualization==<br /> ==Application Area Analysis==<br /> ==Dataset Analysis==<br /> ===The Common Logfile Format===<br /> The common logfile format is as follows:<br /> ''remotehost rfc931 authuser [date] &quot;request&quot; status bytes''<br /> ''remotehost'': Remote hostname (or IP number if DNS hostname is not available, or if DNSLookup is Off.<br /> <br /> ''rfc931'': The remote logname of the user. <br /> <br /> ''authuser'': The username as which the user has authenticated himself. <br /> <br /> ''[date]'': Date and time of the request. <br /> <br /> ''&quot;request&quot;'': The request line exactly as it came from the client. <br /> <br /> ''status'': The HTTP status code returned to the client. <br /> <br /> ''bytes'': The content-length of the document transferred. [1][W3C]<br /> <br /> ==Target Group Analysis==<br /> <br /> <br /> ==Aim of the Visualization==<br /> ==Designproposal==<br /> ==References==<br /> [1][W3C]World Wide Web Consortium, &lt;i&gt;Logging Control In W3C httpd&lt;/i&gt;. Created at: July, 1995. Retrieved at: November 16, 2005. http://www.w3.org/Daemon/User/Config/Logging.html#common-logfile-format.</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G3_-_Aufgabe_3&diff=7948 2005-11-20T16:34:17Z

<p>UE-InfoVis0506 0025081: /* The Common Logfile Format */</p> <hr /> <div>==Topic: Webserver Logfile Visualization==<br /> ==Application Area Analysis==<br /> ==Dataset Analysis==<br /> ==Target Group Analysis==<br /> <br /> <br /> ==Aim of the Visualization==<br /> ==Designproposal==<br /> ==References==<br /> [1][W3C]World Wide Web Consortium, &lt;i&gt;Logging Control In W3C httpd&lt;/i&gt;. Created at: July, 1995. Retrieved at: November 16, 2005. http://www.w3.org/Daemon/User/Config/Logging.html#common-logfile-format.</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G3_-_Aufgabe_3&diff=7886 2005-11-16T19:46:12Z

<p>UE-InfoVis0506 0025081: /* References */</p> <hr /> <div>==Topic: Webserver Logfile Visualization==<br /> ==Application Area Analysis==<br /> ==Dataset Analysis==<br /> ==Target Group Analysis==<br /> ===The Common Logfile Format===<br /> The common logfile format is as follows:<br /> ''remotehost rfc931 authuser [date] &quot;request&quot; status bytes''<br /> ''remotehost'': Remote hostname (or IP number if DNS hostname is not available, or if DNSLookup is Off.<br /> <br /> ''rfc931'': The remote logname of the user. <br /> <br /> ''authuser'': The username as which the user has authenticated himself. <br /> <br /> ''[date]'': Date and time of the request. <br /> <br /> ''&quot;request&quot;'': The request line exactly as it came from the client. <br /> <br /> ''status'': The HTTP status code returned to the client. <br /> <br /> ''bytes'': The content-length of the document transferred. [1][W3C]<br /> <br /> ==Aim of the Visualization==<br /> ==Designproposal==<br /> ==References==<br /> [1][W3C]World Wide Web Consortium, &lt;i&gt;Logging Control In W3C httpd&lt;/i&gt;. Created at: July, 1995. Retrieved at: November 16, 2005. http://www.w3.org/Daemon/User/Config/Logging.html#common-logfile-format.</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G3_-_Aufgabe_3&diff=7885 2005-11-16T19:40:36Z

<p>UE-InfoVis0506 0025081: </p> <hr /> <div>==Topic: Webserver Logfile Visualization==<br /> ==Application Area Analysis==<br /> ==Dataset Analysis==<br /> ==Target Group Analysis==<br /> ===The Common Logfile Format===<br /> The common logfile format is as follows:<br /> ''remotehost rfc931 authuser [date] &quot;request&quot; status bytes''<br /> ''remotehost'': Remote hostname (or IP number if DNS hostname is not available, or if DNSLookup is Off.<br /> <br /> ''rfc931'': The remote logname of the user. <br /> <br /> ''authuser'': The username as which the user has authenticated himself. <br /> <br /> ''[date]'': Date and time of the request. <br /> <br /> ''&quot;request&quot;'': The request line exactly as it came from the client. <br /> <br /> ''status'': The HTTP status code returned to the client. <br /> <br /> ''bytes'': The content-length of the document transferred. [1][W3C]<br /> <br /> ==Aim of the Visualization==<br /> ==Designproposal==<br /> ==References==</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G3_-_Aufgabe_3&diff=7884 2005-11-16T19:40:20Z

<p>UE-InfoVis0506 0025081: /* The Common Logfile Format */</p> <hr /> <div>==Topic: Webserver Logfile Visualization==<br /> ==Application Area Analysis==<br /> ==Dataset Analysis==<br /> ==Target Group Analysis==<br /> ===The Common Logfile Format===<br /> The common logfile format is as follows:<br /> ''remotehost rfc931 authuser [date] &quot;request&quot; status bytes''<br /> ''remotehost'': Remote hostname (or IP number if DNS hostname is not available, or if DNSLookup is Off.<br /> <br /> ''rfc931'': The remote logname of the user. <br /> <br /> ''authuser'': The username as which the user has authenticated himself. <br /> <br /> ''[date]'': Date and time of the request. <br /> <br /> ''&quot;request&quot;'': The request line exactly as it came from the client. <br /> <br /> ''status'': The HTTP status code returned to the client. <br /> <br /> ''bytes'': The content-length of the document transferred. [1][W3C]<br /> <br /> ==Aim of the Visualization==<br /> ==Designproposal==</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G3_-_Aufgabe_3&diff=7883 2005-11-16T19:39:52Z

<p>UE-InfoVis0506 0025081: /* The Common Logfile Format */</p> <hr /> <div>==Topic: Webserver Logfile Visualization==<br /> ==Application Area Analysis==<br /> ==Dataset Analysis==<br /> ==Target Group Analysis==<br /> ===The Common Logfile Format===<br /> The common logfile format is as follows:<br /> ''remotehost rfc931 authuser [date] &quot;request&quot; status bytes''<br /> ''remotehost'': Remote hostname (or IP number if DNS hostname is not available, or if DNSLookup is Off.<br /> <br /> ''rfc931'': The remote logname of the user. <br /> <br /> ''authuser'': The username as which the user has authenticated himself. <br /> <br /> ''[date]'': Date and time of the request. <br /> <br /> ''&quot;request&quot;'': The request line exactly as it came from the client. <br /> <br /> ''status'': The HTTP status code returned to the client. <br /> <br /> ''bytes'': The content-length of the document transferred.<br /> <br /> ==Aim of the Visualization==<br /> ==Designproposal==</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G3_-_Aufgabe_3&diff=7882 2005-11-16T19:37:14Z

<p>UE-InfoVis0506 0025081: /* Target Group Analysis */</p> <hr /> <div>==Topic: Webserver Logfile Visualization==<br /> ==Application Area Analysis==<br /> ==Dataset Analysis==<br /> ==Target Group Analysis==<br /> ===The Common Logfile Format===<br /> The common logfile format is as follows:<br /> <br /> ''remotehost rfc931 authuser [date] &quot;request&quot; status bytes''<br /> <br /> '''remotehost'''<br /> Remote hostname (or IP number if DNS hostname is not available, or if DNSLookup is Off.<br /> <br /> '''rfc931'''<br /> The remote logname of the user. <br /> <br /> '''authuser'''<br /> The username as which the user has authenticated himself. <br /> <br /> '''[date]'''<br /> Date and time of the request. <br /> <br /> '''&quot;request&quot;'''<br /> The request line exactly as it came from the client. <br /> <br /> '''status'''<br /> The HTTP status code returned to the client. <br /> <br /> '''bytes'''<br /> The content-length of the document transferred.<br /> <br /> ==Aim of the Visualization==<br /> ==Designproposal==</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G3_-_Aufgabe_3&diff=7881 2005-11-16T19:32:06Z

<p>UE-InfoVis0506 0025081: /* Target Group Analysis */</p> <hr /> <div>==Topic: Webserver Logfile Visualization==<br /> ==Application Area Analysis==<br /> ==Dataset Analysis==<br /> ==Target Group Analysis==<br /> <br /> The Common Logfile Format<br /> The common logfile format is as follows:<br /> <br /> remotehost rfc931 authuser [date] &quot;request&quot; status bytes<br /> <br /> remotehost<br /> Remote hostname (or IP number if DNS hostname is not available, or if DNSLookup is Off. <br /> rfc931<br /> The remote logname of the user. <br /> authuser<br /> The username as which the user has authenticated himself. <br /> [date]<br /> Date and time of the request. <br /> &quot;request&quot;<br /> The request line exactly as it came from the client. <br /> status<br /> The HTTP status code returned to the client. <br /> bytes<br /> The content-length of the document transferred.<br /> <br /> ==Aim of the Visualization==<br /> ==Designproposal==</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G3_-_Aufgabe_3&diff=7880 2005-11-16T19:31:34Z

<p>UE-InfoVis0506 0025081: </p> <hr /> <div>==Topic: Webserver Logfile Visualization==<br /> ==Application Area Analysis==<br /> ==Dataset Analysis==<br /> ==Target Group Analysis==<br /> ==Aim of the Visualization==<br /> ==Designproposal==</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G3_-_Aufgabe_3&diff=7879 2005-11-16T19:31:20Z

<p>UE-InfoVis0506 0025081: </p> <hr /> <div>==Topic: Webserver Logfile Visualization==<br /> <br /> <br /> ==Application Area Analysis==<br /> ==Dataset Analysis==<br /> ==Target Group Analysis==<br /> ==Aim of the Visualization==<br /> ==Designproposal==</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G3_-_Aufgabe_3&diff=7878 2005-11-16T19:27:04Z

<p>UE-InfoVis0506 0025081: </p> <hr /> <div>=Webserver Logfile Visualization=<br /> <br /> <br /> ==Area of Application==<br /> ==Target Group Analysis==<br /> ==Aim of the Visualization==<br /> ==Designproposal==</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G3_-_Aufgabe_3&diff=7877 2005-11-16T19:05:44Z

<p>UE-InfoVis0506 0025081: </p> <hr /> <div>==Topic==<br /> Webserver Logfile Visualization<br /> <br /> ==Area of Application==<br /> ==Target Group Analysis==<br /> ==Aim of the Visualization==<br /> ==Designproposal==</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Five_Hat_Racks&diff=7273 2005-10-31T21:34:07Z

<p>UE-InfoVis0506 0025081: /* Bibliography */</p> <hr /> <div>==Definitions==<br /> The concept of the &lt;b&gt;„Five Hat Racks”&lt;/b&gt; was originally developed by Richard Saul Wurman in his book Information Anxiety [Wurman, 1989]. In the words of Truong the concept sounds as follows:<br /> <br /> &lt;i&gt;<br /> There are five ways to organize information: category (similarity relatedness), time (chronological sequence), location (geographical or spatial references), alphabet (alphabetical sequence), and continuum (magnitude; highest to lowest, best to worse). &lt;/i&gt;[Truong, 2004]<br /> <br /> Wurman is chairman and creative director of the TED Conferences who focus on technology, entertainment, and design. In 1976 Wurman defines the term &quot;information architect&quot;. In his book, Information Architects [Wurman, 1996] he presents the creations of 20 colleagues who've mastered the skill of presenting clear information. In this book he redefined his “Five Hat Racks” Concept slightly to form the LATCH Principle:<br /> &lt;i&gt;<br /> <br /> Information may be infinite, however...The organization of information is finite as it can only be organized by LATCH: Location, Alphabet, Time, Category, or Hierarchy. &lt;/i&gt;[Wurman, 1996]<br /> <br /> &quot;I've tried a thousand times to find other ways to organize, but I always end up using one of these five.&quot; [Wurman, 1996]<br /> <br /> ==The LATCH Principle==<br /> <br /> ;Location<br /> Location is chosen when the information who you are comparing comes from several different sources or locales. Doctors use different locations of the body to group and study medicine. Concerning an industry you might want to know where on the world goods are distributed.<br /> <br /> ;Alphabet<br /> Alphabet is best used when you have enormous amount of data. For example words in a dictionary or names in a telephone. As usually everybody is familiar with the Alphabet, categorizing by Alphabet is recommendable when not all the audience is familiar with different kind of groupings or categories you could use instead.<br /> <br /> ;Time<br /> Time is the best form of categorization for events that happen over fixed durations. Meeting schedules or our calendar are examples. The work of important persons might be displayed as timeline as well. Time is an easily framework in which changes can be observed and comparisons made.<br /> <br /> ;Category<br /> Category is an organization type often used for goods and industries. Shops and services in the yellow pages are easy to find by category. Retail stores are divided into e.g. men- and woman-clothing. This mode works well to organizing items of similar importance. <br /> <br /> ;Hierarchy<br /> Hierarchy organizes by magnitude. From small to large, least expensive to most expensive, by order of importance, etc. Hierarchy is to be used if you want to assign weight or value to the ordered information.<br /> <br /> ==Bibliography==<br /> <br /> [Fischetti, 1997] Mark Fischetti, Blueprint for Information Architects. &lt;i&gt;Fastcompany Magazine&lt;/i&gt;, Issue 10, pp.186, August/September 1997.&lt;br&gt;<br /> [Truong, 2004] Donny Truong, &lt;i&gt;Universal Principles of design&lt;/i&gt;. Created at: Jannuary 21, 2004. Retrieved at: October 21, 2005. http://www.visualgui.com/index.php?p=1.&lt;br&gt;<br /> [Wurman, 1989] Richard Saul Wurman, &lt;i&gt;Information Anxiety&lt;/i&gt;. Doubleday Books, New York, 1989.&lt;br&gt;<br /> [Wurman and Bredford, 1996] Richard Saul Wurman, Peter Bradford, &lt;i&gt;Information Architects&lt;/i&gt;. Graphis Press Corp, Zurich, Switzerland, 1996.&lt;br&gt;<br /> [Wurman, 2000] Richard Saul Wurman. &lt;i&gt;Information Anxiety 2&lt;/i&gt;. Que Publishing, Indianapolis, IN, 2000.&lt;br&gt;<br /> [Wurman, 2000] Richard Saul Wurman, &lt;i&gt;The Business of Understanding&lt;/i&gt;.Created at: December 28, 2000. Retrieved at: October 21, 2005. http://www.informit.com/articles/article.asp?p=130881&amp;seqNum=6&amp;rl=1.&lt;br&gt;<br /> <br /> ----<br /> Back to [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G3|G3]]</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Five_Hat_Racks&diff=7272 2005-10-31T21:32:14Z

<p>UE-InfoVis0506 0025081: /* Definitions */</p> <hr /> <div>==Definitions==<br /> The concept of the &lt;b&gt;„Five Hat Racks”&lt;/b&gt; was originally developed by Richard Saul Wurman in his book Information Anxiety [Wurman, 1989]. In the words of Truong the concept sounds as follows:<br /> <br /> &lt;i&gt;<br /> There are five ways to organize information: category (similarity relatedness), time (chronological sequence), location (geographical or spatial references), alphabet (alphabetical sequence), and continuum (magnitude; highest to lowest, best to worse). &lt;/i&gt;[Truong, 2004]<br /> <br /> Wurman is chairman and creative director of the TED Conferences who focus on technology, entertainment, and design. In 1976 Wurman defines the term &quot;information architect&quot;. In his book, Information Architects [Wurman, 1996] he presents the creations of 20 colleagues who've mastered the skill of presenting clear information. In this book he redefined his “Five Hat Racks” Concept slightly to form the LATCH Principle:<br /> &lt;i&gt;<br /> <br /> Information may be infinite, however...The organization of information is finite as it can only be organized by LATCH: Location, Alphabet, Time, Category, or Hierarchy. &lt;/i&gt;[Wurman, 1996]<br /> <br /> &quot;I've tried a thousand times to find other ways to organize, but I always end up using one of these five.&quot; [Wurman, 1996]<br /> <br /> ==The LATCH Principle==<br /> <br /> ;Location<br /> Location is chosen when the information who you are comparing comes from several different sources or locales. Doctors use different locations of the body to group and study medicine. Concerning an industry you might want to know where on the world goods are distributed.<br /> <br /> ;Alphabet<br /> Alphabet is best used when you have enormous amount of data. For example words in a dictionary or names in a telephone. As usually everybody is familiar with the Alphabet, categorizing by Alphabet is recommendable when not all the audience is familiar with different kind of groupings or categories you could use instead.<br /> <br /> ;Time<br /> Time is the best form of categorization for events that happen over fixed durations. Meeting schedules or our calendar are examples. The work of important persons might be displayed as timeline as well. Time is an easily framework in which changes can be observed and comparisons made.<br /> <br /> ;Category<br /> Category is an organization type often used for goods and industries. Shops and services in the yellow pages are easy to find by category. Retail stores are divided into e.g. men- and woman-clothing. This mode works well to organizing items of similar importance. <br /> <br /> ;Hierarchy<br /> Hierarchy organizes by magnitude. From small to large, least expensive to most expensive, by order of importance, etc. Hierarchy is to be used if you want to assign weight or value to the ordered information.<br /> <br /> ==Bibliography==<br /> <br /> [Fischetti, 1997] Mark Fischetti, Blueprint for Information Architects. &lt;i&gt;Fastcompany Magazine&lt;/i&gt;, Issue 10, pp.186, August/September 1997&lt;br&gt;<br /> [Truong, 2004] Donny Truong, &lt;i&gt;Universal Principles of design&lt;/i&gt;. Created at: Jannuary 21, 2004. Retrieved at: October 21, 2005. http://www.visualgui.com/index.php?p=1&lt;br&gt;<br /> [Wurman, 1989] Richard Saul Wurman, &lt;i&gt;Information Anxiety&lt;/i&gt;. Doubleday Books, New York, 1989&lt;br&gt;<br /> [Wurman and Bredford, 1996] Richard Saul Wurman, Peter Bradford, &lt;i&gt;Information Architects&lt;/i&gt;. Graphis Press Corp, Zurich, Switzerland, 1996&lt;br&gt;<br /> [Wurman, 2000] Richard Saul Wurman. &lt;i&gt;Information Anxiety 2&lt;/i&gt;. Que Publishing, Indianapolis, IN, 2000&lt;br&gt;<br /> [Wurman, 2000] Richard Saul Wurman, &lt;i&gt;The Business of Understanding&lt;/i&gt;.Created at: December 28, 2000. Retrieved at: October 21, 2005. http://www.informit.com/articles/article.asp?p=130881&amp;seqNum=6&amp;rl=1&lt;br&gt;<br /> <br /> <br /> <br /> ----<br /> Back to [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G3|G3]]</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Five_Hat_Racks&diff=7271 2005-10-31T21:30:54Z

<p>UE-InfoVis0506 0025081: /* Bibliography */</p> <hr /> <div>==Definitions==<br /> The concept of the &lt;b&gt;„Five Hat Racks”&lt;/b&gt; was originally developed by Richard Saul Wurman in his book Information Anxiety [Wurman, 1989]. In the words of Truong the concept sounds as follows:<br /> <br /> &lt;i&gt;<br /> There are five ways to organize information: category (similarity relatedness), time (chronological sequence), location (geographical or spatial references), alphabet (alphabetical sequence), and continuum (magnitude; highest to lowest, best to worse). &lt;/i&gt;[Truong, 2004]<br /> <br /> Wurman is chairman and creative director of the TED Conferences who focus on technology, entertainment, and design. In 1976 Wurman defines the term &quot;information architect&quot;. In his book, Information Architects [Wurman, 1996] he presents the creations of 20 colleagues who've mastered the skill of presenting clear information. In this book he redefined his “Five Hat Racks” Concept slightly to form the LATCH Principle:<br /> &lt;i&gt;<br /> <br /> Information may be infinite, however...The organization of information is finite as it can only be organized by LATCH: Location, Alphabet, Time, Category, or Hierarchy. &lt;/i&gt;[Wurman, 1996]<br /> <br /> &quot;I've tried a thousand times to find other ways to organize,&quot; Wurman says, &quot;but I always end up using one of these five.&quot; [Wurman, 1996]<br /> <br /> ==The LATCH Principle==<br /> <br /> ;Location<br /> Location is chosen when the information who you are comparing comes from several different sources or locales. Doctors use different locations of the body to group and study medicine. Concerning an industry you might want to know where on the world goods are distributed.<br /> <br /> ;Alphabet<br /> Alphabet is best used when you have enormous amount of data. For example words in a dictionary or names in a telephone. As usually everybody is familiar with the Alphabet, categorizing by Alphabet is recommendable when not all the audience is familiar with different kind of groupings or categories you could use instead.<br /> <br /> ;Time<br /> Time is the best form of categorization for events that happen over fixed durations. Meeting schedules or our calendar are examples. The work of important persons might be displayed as timeline as well. Time is an easily framework in which changes can be observed and comparisons made.<br /> <br /> ;Category<br /> Category is an organization type often used for goods and industries. Shops and services in the yellow pages are easy to find by category. Retail stores are divided into e.g. men- and woman-clothing. This mode works well to organizing items of similar importance. <br /> <br /> ;Hierarchy<br /> Hierarchy organizes by magnitude. From small to large, least expensive to most expensive, by order of importance, etc. Hierarchy is to be used if you want to assign weight or value to the ordered information.<br /> <br /> ==Bibliography==<br /> <br /> [Fischetti, 1997] Mark Fischetti, Blueprint for Information Architects. &lt;i&gt;Fastcompany Magazine&lt;/i&gt;, Issue 10, pp.186, August/September 1997&lt;br&gt;<br /> [Truong, 2004] Donny Truong, &lt;i&gt;Universal Principles of design&lt;/i&gt;. Created at: Jannuary 21, 2004. Retrieved at: October 21, 2005. http://www.visualgui.com/index.php?p=1&lt;br&gt;<br /> [Wurman, 1989] Richard Saul Wurman, &lt;i&gt;Information Anxiety&lt;/i&gt;. Doubleday Books, New York, 1989&lt;br&gt;<br /> [Wurman and Bredford, 1996] Richard Saul Wurman, Peter Bradford, &lt;i&gt;Information Architects&lt;/i&gt;. Graphis Press Corp, Zurich, Switzerland, 1996&lt;br&gt;<br /> [Wurman, 2000] Richard Saul Wurman. &lt;i&gt;Information Anxiety 2&lt;/i&gt;. Que Publishing, Indianapolis, IN, 2000&lt;br&gt;<br /> [Wurman, 2000] Richard Saul Wurman, &lt;i&gt;The Business of Understanding&lt;/i&gt;.Created at: December 28, 2000. Retrieved at: October 21, 2005. http://www.informit.com/articles/article.asp?p=130881&amp;seqNum=6&amp;rl=1&lt;br&gt;<br /> <br /> <br /> <br /> ----<br /> Back to [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G3|G3]]</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Five_Hat_Racks&diff=7270 2005-10-31T21:29:59Z

<p>UE-InfoVis0506 0025081: /* Bibliography */</p> <hr /> <div>==Definitions==<br /> The concept of the &lt;b&gt;„Five Hat Racks”&lt;/b&gt; was originally developed by Richard Saul Wurman in his book Information Anxiety [Wurman, 1989]. In the words of Truong the concept sounds as follows:<br /> <br /> &lt;i&gt;<br /> There are five ways to organize information: category (similarity relatedness), time (chronological sequence), location (geographical or spatial references), alphabet (alphabetical sequence), and continuum (magnitude; highest to lowest, best to worse). &lt;/i&gt;[Truong, 2004]<br /> <br /> Wurman is chairman and creative director of the TED Conferences who focus on technology, entertainment, and design. In 1976 Wurman defines the term &quot;information architect&quot;. In his book, Information Architects [Wurman, 1996] he presents the creations of 20 colleagues who've mastered the skill of presenting clear information. In this book he redefined his “Five Hat Racks” Concept slightly to form the LATCH Principle:<br /> &lt;i&gt;<br /> <br /> Information may be infinite, however...The organization of information is finite as it can only be organized by LATCH: Location, Alphabet, Time, Category, or Hierarchy. &lt;/i&gt;[Wurman, 1996]<br /> <br /> &quot;I've tried a thousand times to find other ways to organize,&quot; Wurman says, &quot;but I always end up using one of these five.&quot; [Wurman, 1996]<br /> <br /> ==The LATCH Principle==<br /> <br /> ;Location<br /> Location is chosen when the information who you are comparing comes from several different sources or locales. Doctors use different locations of the body to group and study medicine. Concerning an industry you might want to know where on the world goods are distributed.<br /> <br /> ;Alphabet<br /> Alphabet is best used when you have enormous amount of data. For example words in a dictionary or names in a telephone. As usually everybody is familiar with the Alphabet, categorizing by Alphabet is recommendable when not all the audience is familiar with different kind of groupings or categories you could use instead.<br /> <br /> ;Time<br /> Time is the best form of categorization for events that happen over fixed durations. Meeting schedules or our calendar are examples. The work of important persons might be displayed as timeline as well. Time is an easily framework in which changes can be observed and comparisons made.<br /> <br /> ;Category<br /> Category is an organization type often used for goods and industries. Shops and services in the yellow pages are easy to find by category. Retail stores are divided into e.g. men- and woman-clothing. This mode works well to organizing items of similar importance. <br /> <br /> ;Hierarchy<br /> Hierarchy organizes by magnitude. From small to large, least expensive to most expensive, by order of importance, etc. Hierarchy is to be used if you want to assign weight or value to the ordered information.<br /> <br /> ==Bibliography==<br /> <br /> [Fischetti, 1997] Mark Fischetti, Blueprint for Information Architects. &lt;i&gt;Fastcompany Magazine&lt;/i&gt;, Issue 10, pp.186, August/September 1997&lt;br&gt;<br /> [Truong, 2004] Donny Truong, &lt;i&gt;Universal Principles of design&lt;/i&gt;. Created at: Jannuary 21, 2004. Retrieved at: October 21, 2005. http://www.visualgui.com/index.php?p=1&lt;br&gt;<br /> [Wurman, 1989] Richard Saul Wurman, &lt;i&gt;Information Anxiety&lt;/i&gt;. Doubleday Books, New York, 1989&lt;br&gt;<br /> [Wurman and Bredford, 1996] Richard Saul Wurman, Peter Bradford, &lt;i&gt;Information Architects&lt;/i&gt;. Graphis Press Corp, Zurich, Switzerland, 1996&lt;br&gt;<br /> [Wurman, 2000] Richard Saul Wurman. &lt;i&gt;Information Anxiety 2&lt;/i&gt;. Que Publishing, Indianapolis, IN, 2000&lt;br&gt;<br /> [Wurman, 2000] Richard Saul Wurman, &lt;i&gt;The Business of Understanding&lt;/i&gt;. Que Publishing, Indianapolis, IN, 2000. Created at: December 28, 2000. Retrieved at: October 21, 2005. http://www.informit.com/articles/article.asp?p=130881&amp;seqNum=6&amp;rl=1&lt;br&gt;<br /> <br /> <br /> <br /> ----<br /> Back to [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G3|G3]]</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Five_Hat_Racks&diff=7269 2005-10-31T20:43:36Z

<p>UE-InfoVis0506 0025081: /* Ressouces */</p> <hr /> <div>==Definitions==<br /> The concept of the &lt;b&gt;„Five Hat Racks”&lt;/b&gt; was originally developed by Richard Saul Wurman in his book Information Anxiety [Wurman, 1989]. In the words of Truong the concept sounds as follows:<br /> <br /> &lt;i&gt;<br /> There are five ways to organize information: category (similarity relatedness), time (chronological sequence), location (geographical or spatial references), alphabet (alphabetical sequence), and continuum (magnitude; highest to lowest, best to worse). &lt;/i&gt;[Truong, 2004]<br /> <br /> Wurman is chairman and creative director of the TED Conferences who focus on technology, entertainment, and design. In 1976 Wurman defines the term &quot;information architect&quot;. In his book, Information Architects [Wurman, 1996] he presents the creations of 20 colleagues who've mastered the skill of presenting clear information. In this book he redefined his “Five Hat Racks” Concept slightly to form the LATCH Principle:<br /> &lt;i&gt;<br /> <br /> Information may be infinite, however...The organization of information is finite as it can only be organized by LATCH: Location, Alphabet, Time, Category, or Hierarchy. &lt;/i&gt;[Wurman, 1996]<br /> <br /> &quot;I've tried a thousand times to find other ways to organize,&quot; Wurman says, &quot;but I always end up using one of these five.&quot; [Wurman, 1996]<br /> <br /> ==The LATCH Principle==<br /> <br /> ;Location<br /> Location is chosen when the information who you are comparing comes from several different sources or locales. Doctors use different locations of the body to group and study medicine. Concerning an industry you might want to know where on the world goods are distributed.<br /> <br /> ;Alphabet<br /> Alphabet is best used when you have enormous amount of data. For example words in a dictionary or names in a telephone. As usually everybody is familiar with the Alphabet, categorizing by Alphabet is recommendable when not all the audience is familiar with different kind of groupings or categories you could use instead.<br /> <br /> ;Time<br /> Time is the best form of categorization for events that happen over fixed durations. Meeting schedules or our calendar are examples. The work of important persons might be displayed as timeline as well. Time is an easily framework in which changes can be observed and comparisons made.<br /> <br /> ;Category<br /> Category is an organization type often used for goods and industries. Shops and services in the yellow pages are easy to find by category. Retail stores are divided into e.g. men- and woman-clothing. This mode works well to organizing items of similar importance. <br /> <br /> ;Hierarchy<br /> Hierarchy organizes by magnitude. From small to large, least expensive to most expensive, by order of importance, etc. Hierarchy is to be used if you want to assign weight or value to the ordered information.<br /> <br /> ==Bibliography==<br /> <br /> [1] Richard Saul Wurman, “Information Anxiety 2“, Que Publishing, Indianapolis 2000<br /> [2] Donny Truong, “Universal Principles of design” Access Date: 21. Oktober 2005 http://www.visualgui.com/index.php?p=1&lt;br&gt;<br /> [3] Richard Soul Wurman, “Information Architects“, Graphis Press Corp. 1996&lt;br&gt;<br /> [4] Mark Fischetti “Blueprint for Information Architects” Fastcompany Magazine, Issue 10 August/September 1997&lt;br&gt;<br /> [5] Richard Soul Wurman, “The Business of Understanding” Que Publishing, 2000. Taken from: http://www.informit.com/articles/article.asp?p=130881&amp;seqNum=6&amp;rl=1 Access Date: 21. Oktober 2005&lt;br&gt;<br /> <br /> <br /> <br /> ----<br /> Back to [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G3|G3]]</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Five_Hat_Racks&diff=7268 2005-10-31T20:40:41Z

<p>UE-InfoVis0506 0025081: /* Definitions */</p> <hr /> <div>==Definitions==<br /> The concept of the &lt;b&gt;„Five Hat Racks”&lt;/b&gt; was originally developed by Richard Saul Wurman in his book Information Anxiety [Wurman, 1989]. In the words of Truong the concept sounds as follows:<br /> <br /> &lt;i&gt;<br /> There are five ways to organize information: category (similarity relatedness), time (chronological sequence), location (geographical or spatial references), alphabet (alphabetical sequence), and continuum (magnitude; highest to lowest, best to worse). &lt;/i&gt;[Truong, 2004]<br /> <br /> Wurman is chairman and creative director of the TED Conferences who focus on technology, entertainment, and design. In 1976 Wurman defines the term &quot;information architect&quot;. In his book, Information Architects [Wurman, 1996] he presents the creations of 20 colleagues who've mastered the skill of presenting clear information. In this book he redefined his “Five Hat Racks” Concept slightly to form the LATCH Principle:<br /> &lt;i&gt;<br /> <br /> Information may be infinite, however...The organization of information is finite as it can only be organized by LATCH: Location, Alphabet, Time, Category, or Hierarchy. &lt;/i&gt;[Wurman, 1996]<br /> <br /> &quot;I've tried a thousand times to find other ways to organize,&quot; Wurman says, &quot;but I always end up using one of these five.&quot; [Wurman, 1996]<br /> <br /> ==The LATCH Principle==<br /> <br /> ;Location<br /> Location is chosen when the information who you are comparing comes from several different sources or locales. Doctors use different locations of the body to group and study medicine. Concerning an industry you might want to know where on the world goods are distributed.<br /> <br /> ;Alphabet<br /> Alphabet is best used when you have enormous amount of data. For example words in a dictionary or names in a telephone. As usually everybody is familiar with the Alphabet, categorizing by Alphabet is recommendable when not all the audience is familiar with different kind of groupings or categories you could use instead.<br /> <br /> ;Time<br /> Time is the best form of categorization for events that happen over fixed durations. Meeting schedules or our calendar are examples. The work of important persons might be displayed as timeline as well. Time is an easily framework in which changes can be observed and comparisons made.<br /> <br /> ;Category<br /> Category is an organization type often used for goods and industries. Shops and services in the yellow pages are easy to find by category. Retail stores are divided into e.g. men- and woman-clothing. This mode works well to organizing items of similar importance. <br /> <br /> ;Hierarchy<br /> Hierarchy organizes by magnitude. From small to large, least expensive to most expensive, by order of importance, etc. Hierarchy is to be used if you want to assign weight or value to the ordered information.<br /> <br /> ==Ressouces==<br /> <br /> [1] Richard Soul Wurman, “Information Anxiety 2“, Que Publishing, Indianapolis 2000&lt;br&gt;<br /> [2] Donny Truong, “Universal Principles of design” Access Date: 21. Oktober 2005 http://www.visualgui.com/index.php?p=1&lt;br&gt;<br /> [3] Richard Soul Wurman, “Information Architects“, Graphis Press Corp. 1996&lt;br&gt;<br /> [4] Mark Fischetti “Blueprint for Information Architects” Fastcompany Magazine, Issue 10 August/September 1997&lt;br&gt;<br /> [5] Richard Soul Wurman, “The Business of Understanding” Que Publishing, 2000. Taken from: http://www.informit.com/articles/article.asp?p=130881&amp;seqNum=6&amp;rl=1 Access Date: 21. Oktober 2005&lt;br&gt;<br /> <br /> <br /> <br /> ----<br /> Back to [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G3|G3]]</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Five_Hat_Racks&diff=7267 2005-10-31T20:40:03Z

<p>UE-InfoVis0506 0025081: /* Definitions */</p> <hr /> <div>==Definitions==<br /> The concept of the &lt;b&gt;„Five Hat Racks”&lt;/b&gt; was originally developed by Richard Saul Wurman in his book Information Anxiety [Wurman, 1989]. In the words of Truong the concept sounds as follows:<br /> <br /> &lt;i&gt;<br /> There are five ways to organize information: category (similarity relatedness), time (chronological sequence), location (geographical or spatial references), alphabet (alphabetical sequence), and continuum (magnitude; highest to lowest, best to worse). [Truong, 2004]<br /> &lt;/i&gt;<br /> <br /> Wurman is chairman and creative director of the TED Conferences who focus on technology, entertainment, and design. In 1976 Wurman defines the term &quot;information architect&quot;. In his book, Information Architects [Wurman, 1996] he presents the creations of 20 colleagues who've mastered the skill of presenting clear information. In this book he redefined his “Five Hat Racks” Concept slightly to form the LATCH Principle:<br /> &lt;i&gt;<br /> <br /> Information may be infinite, however...The organization of information is finite as it can only be organized by LATCH: Location, Alphabet, Time, Category, or Hierarchy. [Wurman, 1996]<br /> &lt;/i&gt;<br /> <br /> &quot;I've tried a thousand times to find other ways to organize,&quot; Wurman says, &quot;but I always end up using one of these five.&quot; [Wurman, 1996]<br /> <br /> ==The LATCH Principle==<br /> <br /> ;Location<br /> Location is chosen when the information who you are comparing comes from several different sources or locales. Doctors use different locations of the body to group and study medicine. Concerning an industry you might want to know where on the world goods are distributed.<br /> <br /> ;Alphabet<br /> Alphabet is best used when you have enormous amount of data. For example words in a dictionary or names in a telephone. As usually everybody is familiar with the Alphabet, categorizing by Alphabet is recommendable when not all the audience is familiar with different kind of groupings or categories you could use instead.<br /> <br /> ;Time<br /> Time is the best form of categorization for events that happen over fixed durations. Meeting schedules or our calendar are examples. The work of important persons might be displayed as timeline as well. Time is an easily framework in which changes can be observed and comparisons made.<br /> <br /> ;Category<br /> Category is an organization type often used for goods and industries. Shops and services in the yellow pages are easy to find by category. Retail stores are divided into e.g. men- and woman-clothing. This mode works well to organizing items of similar importance. <br /> <br /> ;Hierarchy<br /> Hierarchy organizes by magnitude. From small to large, least expensive to most expensive, by order of importance, etc. Hierarchy is to be used if you want to assign weight or value to the ordered information.<br /> <br /> ==Ressouces==<br /> <br /> [1] Richard Soul Wurman, “Information Anxiety 2“, Que Publishing, Indianapolis 2000&lt;br&gt;<br /> [2] Donny Truong, “Universal Principles of design” Access Date: 21. Oktober 2005 http://www.visualgui.com/index.php?p=1&lt;br&gt;<br /> [3] Richard Soul Wurman, “Information Architects“, Graphis Press Corp. 1996&lt;br&gt;<br /> [4] Mark Fischetti “Blueprint for Information Architects” Fastcompany Magazine, Issue 10 August/September 1997&lt;br&gt;<br /> [5] Richard Soul Wurman, “The Business of Understanding” Que Publishing, 2000. Taken from: http://www.informit.com/articles/article.asp?p=130881&amp;seqNum=6&amp;rl=1 Access Date: 21. Oktober 2005&lt;br&gt;<br /> <br /> <br /> <br /> ----<br /> Back to [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G3|G3]]</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Five_Hat_Racks&diff=6871 2005-10-25T19:00:15Z

<p>UE-InfoVis0506 0025081: /* The LATCH Principle */</p> <hr /> <div>==Definitions==<br /> The concept of the &lt;b&gt;„Five Hat Racks”&lt;/b&gt; was originally developed by Richard Soul Wurman in his book Information Anxiety [1]. In the definition of visualgui (http://www.visualgui.com) the concept sounds as follows:<br /> <br /> &lt;i&gt;<br /> There are five ways to organize information: category (similarity relatedness), time (chronological sequence), location (geographical or spatial references), alphabet (alphabetical sequence), and continuum (magnitude; highest to lowest, best to worse). [2]<br /> &lt;/i&gt;<br /> <br /> Wurman is chairman and creative director of the TED Conferences who focus on technology, entertainment, and design. In 1976 Wurman defines the term &quot;information architect&quot;. In his book, Information Architects he presents the creations of 20 colleagues who've mastered the skill of presenting clear information. In this book he redefined his “Five Hat Racks” Concept slightly to form the LATCH Principle:<br /> &lt;i&gt;<br /> <br /> Information may be infinite, however...The organization of information is finite as it can only be organized by LATCH: Location, Alphabet, Time, Category, or Hierarchy. [3]<br /> &lt;/i&gt;<br /> <br /> &quot;I've tried a thousand times to find other ways to organize,&quot; Wurman says, &quot;but I always end up using one of these five.&quot;<br /> <br /> ==The LATCH Principle==<br /> <br /> ;Location<br /> Location is chosen when the information who you are comparing comes from several different sources or locales. Doctors use different locations of the body to group and study medicine. Concerning an industry you might want to know where on the world goods are distributed.<br /> <br /> ;Alphabet<br /> Alphabet is best used when you have enormous amount of data. For example words in a dictionary or names in a telephone. As usually everybody is familiar with the Alphabet, categorizing by Alphabet is recommendable when not all the audience is familiar with different kind of groupings or categories you could use instead.<br /> <br /> ;Time<br /> Time is the best form of categorization for events that happen over fixed durations. Meeting schedules or our calendar are examples. The work of important persons might be displayed as timeline as well. Time is an easily framework in which changes can be observed and comparisons made.<br /> <br /> ;Category<br /> Category is an organization type often used for goods and industries. Shops and services in the yellow pages are easy to find by category. Retail stores are divided into e.g. men- and woman-clothing. This mode works well to organizing items of similar importance. <br /> <br /> ;Hierarchy<br /> Hierarchy organizes by magnitude. From small to large, least expensive to most expensive, by order of importance, etc. Hierarchy is to be used if you want to assign weight or value to the ordered information.<br /> <br /> ==Ressouces==<br /> <br /> [1] Richard Soul Wurman, “Information Anxiety 2“, Que Publishing, Indianapolis 2000&lt;br&gt;<br /> [2] Donny Truong, “Universal Principles of design” Access Date: 21. Oktober 2005 http://www.visualgui.com/index.php?p=1&lt;br&gt;<br /> [3] Richard Soul Wurman, “Information Architects“, Graphis Press Corp. 1996&lt;br&gt;<br /> [4] Mark Fischetti “Blueprint for Information Architects” Fastcompany Magazine, Issue 10 August/September 1997&lt;br&gt;<br /> [5] Richard Soul Wurman, “The Business of Understanding” Que Publishing, 2000. Taken from: http://www.informit.com/articles/article.asp?p=130881&amp;seqNum=6&amp;rl=1 Access Date: 21. Oktober 2005&lt;br&gt;<br /> <br /> <br /> <br /> ----<br /> Back to [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G3|G3]]</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Five_Hat_Racks&diff=6870 2005-10-25T18:59:59Z

<p>UE-InfoVis0506 0025081: /* The LATCH Principle */</p> <hr /> <div>==Definitions==<br /> The concept of the &lt;b&gt;„Five Hat Racks”&lt;/b&gt; was originally developed by Richard Soul Wurman in his book Information Anxiety [1]. In the definition of visualgui (http://www.visualgui.com) the concept sounds as follows:<br /> <br /> &lt;i&gt;<br /> There are five ways to organize information: category (similarity relatedness), time (chronological sequence), location (geographical or spatial references), alphabet (alphabetical sequence), and continuum (magnitude; highest to lowest, best to worse). [2]<br /> &lt;/i&gt;<br /> <br /> Wurman is chairman and creative director of the TED Conferences who focus on technology, entertainment, and design. In 1976 Wurman defines the term &quot;information architect&quot;. In his book, Information Architects he presents the creations of 20 colleagues who've mastered the skill of presenting clear information. In this book he redefined his “Five Hat Racks” Concept slightly to form the LATCH Principle:<br /> &lt;i&gt;<br /> <br /> Information may be infinite, however...The organization of information is finite as it can only be organized by LATCH: Location, Alphabet, Time, Category, or Hierarchy. [3]<br /> &lt;/i&gt;<br /> <br /> &quot;I've tried a thousand times to find other ways to organize,&quot; Wurman says, &quot;but I always end up using one of these five.&quot;<br /> <br /> ==The LATCH Principle==<br /> <br /> *Location<br /> Location is chosen when the information who you are comparing comes from several different sources or locales. Doctors use different locations of the body to group and study medicine. Concerning an industry you might want to know where on the world goods are distributed.<br /> <br /> ;Alphabet<br /> Alphabet is best used when you have enormous amount of data. For example words in a dictionary or names in a telephone. As usually everybody is familiar with the Alphabet, categorizing by Alphabet is recommendable when not all the audience is familiar with different kind of groupings or categories you could use instead.<br /> <br /> *Time<br /> Time is the best form of categorization for events that happen over fixed durations. Meeting schedules or our calendar are examples. The work of important persons might be displayed as timeline as well. Time is an easily framework in which changes can be observed and comparisons made.<br /> <br /> *Category<br /> Category is an organization type often used for goods and industries. Shops and services in the yellow pages are easy to find by category. Retail stores are divided into e.g. men- and woman-clothing. This mode works well to organizing items of similar importance. <br /> <br /> *Hierarchy<br /> Hierarchy organizes by magnitude. From small to large, least expensive to most expensive, by order of importance, etc. Hierarchy is to be used if you want to assign weight or value to the ordered information.<br /> <br /> ==Ressouces==<br /> <br /> [1] Richard Soul Wurman, “Information Anxiety 2“, Que Publishing, Indianapolis 2000&lt;br&gt;<br /> [2] Donny Truong, “Universal Principles of design” Access Date: 21. Oktober 2005 http://www.visualgui.com/index.php?p=1&lt;br&gt;<br /> [3] Richard Soul Wurman, “Information Architects“, Graphis Press Corp. 1996&lt;br&gt;<br /> [4] Mark Fischetti “Blueprint for Information Architects” Fastcompany Magazine, Issue 10 August/September 1997&lt;br&gt;<br /> [5] Richard Soul Wurman, “The Business of Understanding” Que Publishing, 2000. Taken from: http://www.informit.com/articles/article.asp?p=130881&amp;seqNum=6&amp;rl=1 Access Date: 21. Oktober 2005&lt;br&gt;<br /> <br /> <br /> <br /> ----<br /> Back to [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G3|G3]]</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Five_Hat_Racks&diff=6867 2005-10-25T18:59:42Z

<p>UE-InfoVis0506 0025081: /* Definitions */</p> <hr /> <div>==Definitions==<br /> The concept of the &lt;b&gt;„Five Hat Racks”&lt;/b&gt; was originally developed by Richard Soul Wurman in his book Information Anxiety [1]. In the definition of visualgui (http://www.visualgui.com) the concept sounds as follows:<br /> <br /> &lt;i&gt;<br /> There are five ways to organize information: category (similarity relatedness), time (chronological sequence), location (geographical or spatial references), alphabet (alphabetical sequence), and continuum (magnitude; highest to lowest, best to worse). [2]<br /> &lt;/i&gt;<br /> <br /> Wurman is chairman and creative director of the TED Conferences who focus on technology, entertainment, and design. In 1976 Wurman defines the term &quot;information architect&quot;. In his book, Information Architects he presents the creations of 20 colleagues who've mastered the skill of presenting clear information. In this book he redefined his “Five Hat Racks” Concept slightly to form the LATCH Principle:<br /> &lt;i&gt;<br /> <br /> Information may be infinite, however...The organization of information is finite as it can only be organized by LATCH: Location, Alphabet, Time, Category, or Hierarchy. [3]<br /> &lt;/i&gt;<br /> <br /> &quot;I've tried a thousand times to find other ways to organize,&quot; Wurman says, &quot;but I always end up using one of these five.&quot;<br /> <br /> ==The LATCH Principle==<br /> <br /> *Location<br /> Location is chosen when the information who you are comparing comes from several different sources or locales. Doctors use different locations of the body to group and study medicine. Concerning an industry you might want to know where on the world goods are distributed.<br /> <br /> *Alphabet<br /> Alphabet is best used when you have enormous amount of data. For example words in a dictionary or names in a telephone. As usually everybody is familiar with the Alphabet, categorizing by Alphabet is recommendable when not all the audience is familiar with different kind of groupings or categories you could use instead.<br /> <br /> *Time<br /> Time is the best form of categorization for events that happen over fixed durations. Meeting schedules or our calendar are examples. The work of important persons might be displayed as timeline as well. Time is an easily framework in which changes can be observed and comparisons made.<br /> <br /> *Category<br /> Category is an organization type often used for goods and industries. Shops and services in the yellow pages are easy to find by category. Retail stores are divided into e.g. men- and woman-clothing. This mode works well to organizing items of similar importance. <br /> <br /> *Hierarchy<br /> Hierarchy organizes by magnitude. From small to large, least expensive to most expensive, by order of importance, etc. Hierarchy is to be used if you want to assign weight or value to the ordered information.<br /> <br /> ==Ressouces==<br /> <br /> [1] Richard Soul Wurman, “Information Anxiety 2“, Que Publishing, Indianapolis 2000&lt;br&gt;<br /> [2] Donny Truong, “Universal Principles of design” Access Date: 21. Oktober 2005 http://www.visualgui.com/index.php?p=1&lt;br&gt;<br /> [3] Richard Soul Wurman, “Information Architects“, Graphis Press Corp. 1996&lt;br&gt;<br /> [4] Mark Fischetti “Blueprint for Information Architects” Fastcompany Magazine, Issue 10 August/September 1997&lt;br&gt;<br /> [5] Richard Soul Wurman, “The Business of Understanding” Que Publishing, 2000. Taken from: http://www.informit.com/articles/article.asp?p=130881&amp;seqNum=6&amp;rl=1 Access Date: 21. Oktober 2005&lt;br&gt;<br /> <br /> <br /> <br /> ----<br /> Back to [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G3|G3]]</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Five_Hat_Racks&diff=6865 2005-10-25T18:59:22Z

<p>UE-InfoVis0506 0025081: /* Definitions */</p> <hr /> <div>==Definitions==<br /> The concept of the &lt;b&gt;„Five Hat Racks”&lt;/b&gt; was originally developed by Richard Soul Wurman in his book Information Anxiety [1]. In the definition of visualgui (www.visualgui.com) the concept sounds as follows:<br /> <br /> &lt;i&gt;<br /> There are five ways to organize information: category (similarity relatedness), time (chronological sequence), location (geographical or spatial references), alphabet (alphabetical sequence), and continuum (magnitude; highest to lowest, best to worse). [2]<br /> &lt;/i&gt;<br /> <br /> Wurman is chairman and creative director of the TED Conferences who focus on technology, entertainment, and design. In 1976 Wurman defines the term &quot;information architect&quot;. In his book, Information Architects he presents the creations of 20 colleagues who've mastered the skill of presenting clear information. In this book he redefined his “Five Hat Racks” Concept slightly to form the LATCH Principle:<br /> &lt;i&gt;<br /> <br /> Information may be infinite, however...The organization of information is finite as it can only be organized by LATCH: Location, Alphabet, Time, Category, or Hierarchy. [3]<br /> &lt;/i&gt;<br /> <br /> &quot;I've tried a thousand times to find other ways to organize,&quot; Wurman says, &quot;but I always end up using one of these five.&quot;<br /> <br /> ==The LATCH Principle==<br /> <br /> *Location<br /> Location is chosen when the information who you are comparing comes from several different sources or locales. Doctors use different locations of the body to group and study medicine. Concerning an industry you might want to know where on the world goods are distributed.<br /> <br /> *Alphabet<br /> Alphabet is best used when you have enormous amount of data. For example words in a dictionary or names in a telephone. As usually everybody is familiar with the Alphabet, categorizing by Alphabet is recommendable when not all the audience is familiar with different kind of groupings or categories you could use instead.<br /> <br /> *Time<br /> Time is the best form of categorization for events that happen over fixed durations. Meeting schedules or our calendar are examples. The work of important persons might be displayed as timeline as well. Time is an easily framework in which changes can be observed and comparisons made.<br /> <br /> *Category<br /> Category is an organization type often used for goods and industries. Shops and services in the yellow pages are easy to find by category. Retail stores are divided into e.g. men- and woman-clothing. This mode works well to organizing items of similar importance. <br /> <br /> *Hierarchy<br /> Hierarchy organizes by magnitude. From small to large, least expensive to most expensive, by order of importance, etc. Hierarchy is to be used if you want to assign weight or value to the ordered information.<br /> <br /> ==Ressouces==<br /> <br /> [1] Richard Soul Wurman, “Information Anxiety 2“, Que Publishing, Indianapolis 2000&lt;br&gt;<br /> [2] Donny Truong, “Universal Principles of design” Access Date: 21. Oktober 2005 http://www.visualgui.com/index.php?p=1&lt;br&gt;<br /> [3] Richard Soul Wurman, “Information Architects“, Graphis Press Corp. 1996&lt;br&gt;<br /> [4] Mark Fischetti “Blueprint for Information Architects” Fastcompany Magazine, Issue 10 August/September 1997&lt;br&gt;<br /> [5] Richard Soul Wurman, “The Business of Understanding” Que Publishing, 2000. Taken from: http://www.informit.com/articles/article.asp?p=130881&amp;seqNum=6&amp;rl=1 Access Date: 21. Oktober 2005&lt;br&gt;<br /> <br /> <br /> <br /> ----<br /> Back to [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G3|G3]]</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Five_Hat_Racks&diff=6864 2005-10-25T18:59:03Z

<p>UE-InfoVis0506 0025081: /* Definitions */</p> <hr /> <div>==Definitions==<br /> The concept of the &lt;b&gt;„Five Hat Racks”&lt;/b&gt; was originally developed by Richard Soul Wurman in his book Information Anxiety [1]. In the definition of visualgui (www.visualgui.com) the concept sounds as follows:<br /> <br /> &lt;i&gt;&lt;br&gt;<br /> There are five ways to organize information: category (similarity relatedness), time (chronological sequence), location (geographical or spatial references), alphabet (alphabetical sequence), and continuum (magnitude; highest to lowest, best to worse). [2]<br /> &lt;/i&gt;&lt;br&gt;<br /> <br /> Wurman is chairman and creative director of the TED Conferences who focus on technology, entertainment, and design. In 1976 Wurman defines the term &quot;information architect&quot;. In his book, Information Architects he presents the creations of 20 colleagues who've mastered the skill of presenting clear information. In this book he redefined his “Five Hat Racks” Concept slightly to form the LATCH Principle:<br /> &lt;i&gt;&lt;br&gt;<br /> <br /> Information may be infinite, however...The organization of information is finite as it can only be organized by LATCH: Location, Alphabet, Time, Category, or Hierarchy. [3]<br /> &lt;/i&gt;&lt;br&gt;<br /> <br /> &quot;I've tried a thousand times to find other ways to organize,&quot; Wurman says, &quot;but I always end up using one of these five.&quot;&lt;br&gt;<br /> <br /> ==The LATCH Principle==<br /> <br /> *Location<br /> Location is chosen when the information who you are comparing comes from several different sources or locales. Doctors use different locations of the body to group and study medicine. Concerning an industry you might want to know where on the world goods are distributed.<br /> <br /> *Alphabet<br /> Alphabet is best used when you have enormous amount of data. For example words in a dictionary or names in a telephone. As usually everybody is familiar with the Alphabet, categorizing by Alphabet is recommendable when not all the audience is familiar with different kind of groupings or categories you could use instead.<br /> <br /> *Time<br /> Time is the best form of categorization for events that happen over fixed durations. Meeting schedules or our calendar are examples. The work of important persons might be displayed as timeline as well. Time is an easily framework in which changes can be observed and comparisons made.<br /> <br /> *Category<br /> Category is an organization type often used for goods and industries. Shops and services in the yellow pages are easy to find by category. Retail stores are divided into e.g. men- and woman-clothing. This mode works well to organizing items of similar importance. <br /> <br /> *Hierarchy<br /> Hierarchy organizes by magnitude. From small to large, least expensive to most expensive, by order of importance, etc. Hierarchy is to be used if you want to assign weight or value to the ordered information.<br /> <br /> ==Ressouces==<br /> <br /> [1] Richard Soul Wurman, “Information Anxiety 2“, Que Publishing, Indianapolis 2000&lt;br&gt;<br /> [2] Donny Truong, “Universal Principles of design” Access Date: 21. Oktober 2005 http://www.visualgui.com/index.php?p=1&lt;br&gt;<br /> [3] Richard Soul Wurman, “Information Architects“, Graphis Press Corp. 1996&lt;br&gt;<br /> [4] Mark Fischetti “Blueprint for Information Architects” Fastcompany Magazine, Issue 10 August/September 1997&lt;br&gt;<br /> [5] Richard Soul Wurman, “The Business of Understanding” Que Publishing, 2000. Taken from: http://www.informit.com/articles/article.asp?p=130881&amp;seqNum=6&amp;rl=1 Access Date: 21. Oktober 2005&lt;br&gt;<br /> <br /> <br /> <br /> ----<br /> Back to [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G3|G3]]</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Five_Hat_Racks&diff=6861 2005-10-25T18:57:17Z

<p>UE-InfoVis0506 0025081: /* Definitions */</p> <hr /> <div>==Definitions==<br /> The concept of the &lt;b&gt;„Five Hat Racks”&lt;/b&gt; was originally developed by Richard Soul Wurman in his book Information Anxiety [1]. In the definition of visualgui (www.visualgui.com) the concept sounds as follows:<br /> &lt;i&gt;&lt;br&gt;<br /> There are five ways to organize information: category (similarity relatedness), time (chronological sequence), location (geographical or spatial references), alphabet (alphabetical sequence), and continuum (magnitude; highest to lowest, best to worse). [2]<br /> &lt;/i&gt;&lt;br&gt;<br /> Wurman is chairman and creative director of the TED Conferences who focus on technology, entertainment, and design. In 1976 Wurman defines the term &quot;information architect&quot;. In his book, Information Architects he presents the creations of 20 colleagues who've mastered the skill of presenting clear information. In this book he redefined his “Five Hat Racks” Concept slightly to form the LATCH Principle:<br /> &lt;i&gt;&lt;br&gt;<br /> Information may be infinite, however...The organization of information is finite as it can only be organized by LATCH: Location, Alphabet, Time, Category, or Hierarchy. [3]<br /> &lt;/i&gt;&lt;br&gt;<br /> &quot;I've tried a thousand times to find other ways to organize,&quot; Wurman says, &quot;but I always end up using one of these five.&quot;&lt;br&gt;<br /> <br /> ==The LATCH Principle==<br /> <br /> *Location<br /> Location is chosen when the information who you are comparing comes from several different sources or locales. Doctors use different locations of the body to group and study medicine. Concerning an industry you might want to know where on the world goods are distributed.<br /> <br /> *Alphabet<br /> Alphabet is best used when you have enormous amount of data. For example words in a dictionary or names in a telephone. As usually everybody is familiar with the Alphabet, categorizing by Alphabet is recommendable when not all the audience is familiar with different kind of groupings or categories you could use instead.<br /> <br /> *Time<br /> Time is the best form of categorization for events that happen over fixed durations. Meeting schedules or our calendar are examples. The work of important persons might be displayed as timeline as well. Time is an easily framework in which changes can be observed and comparisons made.<br /> <br /> *Category<br /> Category is an organization type often used for goods and industries. Shops and services in the yellow pages are easy to find by category. Retail stores are divided into e.g. men- and woman-clothing. This mode works well to organizing items of similar importance. <br /> <br /> *Hierarchy<br /> Hierarchy organizes by magnitude. From small to large, least expensive to most expensive, by order of importance, etc. Hierarchy is to be used if you want to assign weight or value to the ordered information.<br /> <br /> ==Ressouces==<br /> <br /> [1] Richard Soul Wurman, “Information Anxiety 2“, Que Publishing, Indianapolis 2000&lt;br&gt;<br /> [2] Donny Truong, “Universal Principles of design” Access Date: 21. Oktober 2005 http://www.visualgui.com/index.php?p=1&lt;br&gt;<br /> [3] Richard Soul Wurman, “Information Architects“, Graphis Press Corp. 1996&lt;br&gt;<br /> [4] Mark Fischetti “Blueprint for Information Architects” Fastcompany Magazine, Issue 10 August/September 1997&lt;br&gt;<br /> [5] Richard Soul Wurman, “The Business of Understanding” Que Publishing, 2000. Taken from: http://www.informit.com/articles/article.asp?p=130881&amp;seqNum=6&amp;rl=1 Access Date: 21. Oktober 2005&lt;br&gt;<br /> <br /> <br /> <br /> ----<br /> Back to [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G3|G3]]</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Five_Hat_Racks&diff=6860 2005-10-25T18:56:44Z

<p>UE-InfoVis0506 0025081: /* Definitions */</p> <hr /> <div>==Definitions==<br /> The concept of the &lt;b&gt;„Five Hat Racks”&lt;/b&gt; was originally developed by Richard Soul Wurman in his book Information Anxiety [1]. In the definition of visualgui (www.visualgui.com) the concept sounds as follows:&lt;br&gt;<br /> &lt;i&gt;<br /> There are five ways to organize information: category (similarity relatedness), time (chronological sequence), location (geographical or spatial references), alphabet (alphabetical sequence), and continuum (magnitude; highest to lowest, best to worse). [2]&lt;br&gt;<br /> &lt;/i&gt;<br /> Wurman is chairman and creative director of the TED Conferences who focus on technology, entertainment, and design. In 1976 Wurman defines the term &quot;information architect&quot;. In his book, Information Architects he presents the creations of 20 colleagues who've mastered the skill of presenting clear information. In this book he redefined his “Five Hat Racks” Concept slightly to form the LATCH Principle:&lt;br&gt;<br /> &lt;i&gt;<br /> Information may be infinite, however...The organization of information is finite as it can only be organized by LATCH: Location, Alphabet, Time, Category, or Hierarchy. [3]&lt;br&gt;<br /> &lt;/i&gt;<br /> &quot;I've tried a thousand times to find other ways to organize,&quot; Wurman says, &quot;but I always end up using one of these five.&quot;&lt;br&gt;<br /> <br /> ==The LATCH Principle==<br /> <br /> *Location<br /> Location is chosen when the information who you are comparing comes from several different sources or locales. Doctors use different locations of the body to group and study medicine. Concerning an industry you might want to know where on the world goods are distributed.<br /> <br /> *Alphabet<br /> Alphabet is best used when you have enormous amount of data. For example words in a dictionary or names in a telephone. As usually everybody is familiar with the Alphabet, categorizing by Alphabet is recommendable when not all the audience is familiar with different kind of groupings or categories you could use instead.<br /> <br /> *Time<br /> Time is the best form of categorization for events that happen over fixed durations. Meeting schedules or our calendar are examples. The work of important persons might be displayed as timeline as well. Time is an easily framework in which changes can be observed and comparisons made.<br /> <br /> *Category<br /> Category is an organization type often used for goods and industries. Shops and services in the yellow pages are easy to find by category. Retail stores are divided into e.g. men- and woman-clothing. This mode works well to organizing items of similar importance. <br /> <br /> *Hierarchy<br /> Hierarchy organizes by magnitude. From small to large, least expensive to most expensive, by order of importance, etc. Hierarchy is to be used if you want to assign weight or value to the ordered information.<br /> <br /> ==Ressouces==<br /> <br /> [1] Richard Soul Wurman, “Information Anxiety 2“, Que Publishing, Indianapolis 2000&lt;br&gt;<br /> [2] Donny Truong, “Universal Principles of design” Access Date: 21. Oktober 2005 http://www.visualgui.com/index.php?p=1&lt;br&gt;<br /> [3] Richard Soul Wurman, “Information Architects“, Graphis Press Corp. 1996&lt;br&gt;<br /> [4] Mark Fischetti “Blueprint for Information Architects” Fastcompany Magazine, Issue 10 August/September 1997&lt;br&gt;<br /> [5] Richard Soul Wurman, “The Business of Understanding” Que Publishing, 2000. Taken from: http://www.informit.com/articles/article.asp?p=130881&amp;seqNum=6&amp;rl=1 Access Date: 21. Oktober 2005&lt;br&gt;<br /> <br /> <br /> <br /> ----<br /> Back to [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G3|G3]]</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Five_Hat_Racks&diff=6859 2005-10-25T18:56:19Z

<p>UE-InfoVis0506 0025081: /* Definitions */</p> <hr /> <div>==Definitions==<br /> The concept of the &lt;b&gt;„Five Hat Racks”&lt;/b&gt; was originally developed by Richard Soul Wurman in his book Information Anxiety [1]. In the definition of visualgui (www.visualgui.com) the concept sounds as follows:&lt;br&gt;<br /> <br /> There are five ways to organize information: category (similarity relatedness), time (chronological sequence), location (geographical or spatial references), alphabet (alphabetical sequence), and continuum (magnitude; highest to lowest, best to worse). [2]&lt;br&gt;<br /> <br /> Wurman is chairman and creative director of the TED Conferences who focus on technology, entertainment, and design. In 1976 Wurman defines the term &quot;information architect&quot;. In his book, Information Architects he presents the creations of 20 colleagues who've mastered the skill of presenting clear information. In this book he redefined his “Five Hat Racks” Concept slightly to form the LATCH Principle:&lt;br&gt;<br /> <br /> Information may be infinite, however...The organization of information is finite as it can only be organized by LATCH: Location, Alphabet, Time, Category, or Hierarchy. [3]&lt;br&gt;<br /> <br /> &quot;I've tried a thousand times to find other ways to organize,&quot; Wurman says, &quot;but I always end up using one of these five.&quot;&lt;br&gt;<br /> <br /> ==The LATCH Principle==<br /> <br /> *Location<br /> Location is chosen when the information who you are comparing comes from several different sources or locales. Doctors use different locations of the body to group and study medicine. Concerning an industry you might want to know where on the world goods are distributed.<br /> <br /> *Alphabet<br /> Alphabet is best used when you have enormous amount of data. For example words in a dictionary or names in a telephone. As usually everybody is familiar with the Alphabet, categorizing by Alphabet is recommendable when not all the audience is familiar with different kind of groupings or categories you could use instead.<br /> <br /> *Time<br /> Time is the best form of categorization for events that happen over fixed durations. Meeting schedules or our calendar are examples. The work of important persons might be displayed as timeline as well. Time is an easily framework in which changes can be observed and comparisons made.<br /> <br /> *Category<br /> Category is an organization type often used for goods and industries. Shops and services in the yellow pages are easy to find by category. Retail stores are divided into e.g. men- and woman-clothing. This mode works well to organizing items of similar importance. <br /> <br /> *Hierarchy<br /> Hierarchy organizes by magnitude. From small to large, least expensive to most expensive, by order of importance, etc. Hierarchy is to be used if you want to assign weight or value to the ordered information.<br /> <br /> ==Ressouces==<br /> <br /> [1] Richard Soul Wurman, “Information Anxiety 2“, Que Publishing, Indianapolis 2000&lt;br&gt;<br /> [2] Donny Truong, “Universal Principles of design” Access Date: 21. Oktober 2005 http://www.visualgui.com/index.php?p=1&lt;br&gt;<br /> [3] Richard Soul Wurman, “Information Architects“, Graphis Press Corp. 1996&lt;br&gt;<br /> [4] Mark Fischetti “Blueprint for Information Architects” Fastcompany Magazine, Issue 10 August/September 1997&lt;br&gt;<br /> [5] Richard Soul Wurman, “The Business of Understanding” Que Publishing, 2000. Taken from: http://www.informit.com/articles/article.asp?p=130881&amp;seqNum=6&amp;rl=1 Access Date: 21. Oktober 2005&lt;br&gt;<br /> <br /> <br /> <br /> ----<br /> Back to [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G3|G3]]</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Five_Hat_Racks&diff=6858 2005-10-25T18:55:55Z

<p>UE-InfoVis0506 0025081: /* Ressouces */</p> <hr /> <div>==Definitions==<br /> The concept of the „Five Hat Racks” was originally developed by Richard Soul Wurman in his book Information Anxiety [1]. In the definition of visualgui (www.visualgui.com) the concept sounds as follows:&lt;br&gt;<br /> <br /> There are five ways to organize information: category (similarity relatedness), time (chronological sequence), location (geographical or spatial references), alphabet (alphabetical sequence), and continuum (magnitude; highest to lowest, best to worse). [2]&lt;br&gt;<br /> <br /> Wurman is chairman and creative director of the TED Conferences who focus on technology, entertainment, and design. In 1976 Wurman defines the term &quot;information architect&quot;. In his book, Information Architects he presents the creations of 20 colleagues who've mastered the skill of presenting clear information. In this book he redefined his “Five Hat Racks” Concept slightly to form the LATCH Principle:&lt;br&gt;<br /> <br /> Information may be infinite, however...The organization of information is finite as it can only be organized by LATCH: Location, Alphabet, Time, Category, or Hierarchy. [3]&lt;br&gt;<br /> <br /> &quot;I've tried a thousand times to find other ways to organize,&quot; Wurman says, &quot;but I always end up using one of these five.&quot;&lt;br&gt;<br /> <br /> ==The LATCH Principle==<br /> <br /> *Location<br /> Location is chosen when the information who you are comparing comes from several different sources or locales. Doctors use different locations of the body to group and study medicine. Concerning an industry you might want to know where on the world goods are distributed.<br /> <br /> *Alphabet<br /> Alphabet is best used when you have enormous amount of data. For example words in a dictionary or names in a telephone. As usually everybody is familiar with the Alphabet, categorizing by Alphabet is recommendable when not all the audience is familiar with different kind of groupings or categories you could use instead.<br /> <br /> *Time<br /> Time is the best form of categorization for events that happen over fixed durations. Meeting schedules or our calendar are examples. The work of important persons might be displayed as timeline as well. Time is an easily framework in which changes can be observed and comparisons made.<br /> <br /> *Category<br /> Category is an organization type often used for goods and industries. Shops and services in the yellow pages are easy to find by category. Retail stores are divided into e.g. men- and woman-clothing. This mode works well to organizing items of similar importance. <br /> <br /> *Hierarchy<br /> Hierarchy organizes by magnitude. From small to large, least expensive to most expensive, by order of importance, etc. Hierarchy is to be used if you want to assign weight or value to the ordered information.<br /> <br /> ==Ressouces==<br /> <br /> [1] Richard Soul Wurman, “Information Anxiety 2“, Que Publishing, Indianapolis 2000&lt;br&gt;<br /> [2] Donny Truong, “Universal Principles of design” Access Date: 21. Oktober 2005 http://www.visualgui.com/index.php?p=1&lt;br&gt;<br /> [3] Richard Soul Wurman, “Information Architects“, Graphis Press Corp. 1996&lt;br&gt;<br /> [4] Mark Fischetti “Blueprint for Information Architects” Fastcompany Magazine, Issue 10 August/September 1997&lt;br&gt;<br /> [5] Richard Soul Wurman, “The Business of Understanding” Que Publishing, 2000. Taken from: http://www.informit.com/articles/article.asp?p=130881&amp;seqNum=6&amp;rl=1 Access Date: 21. Oktober 2005&lt;br&gt;<br /> <br /> <br /> <br /> ----<br /> Back to [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G3|G3]]</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Five_Hat_Racks&diff=6855 2005-10-25T18:55:38Z

<p>UE-InfoVis0506 0025081: </p> <hr /> <div>==Definitions==<br /> The concept of the „Five Hat Racks” was originally developed by Richard Soul Wurman in his book Information Anxiety [1]. In the definition of visualgui (www.visualgui.com) the concept sounds as follows:&lt;br&gt;<br /> <br /> There are five ways to organize information: category (similarity relatedness), time (chronological sequence), location (geographical or spatial references), alphabet (alphabetical sequence), and continuum (magnitude; highest to lowest, best to worse). [2]&lt;br&gt;<br /> <br /> Wurman is chairman and creative director of the TED Conferences who focus on technology, entertainment, and design. In 1976 Wurman defines the term &quot;information architect&quot;. In his book, Information Architects he presents the creations of 20 colleagues who've mastered the skill of presenting clear information. In this book he redefined his “Five Hat Racks” Concept slightly to form the LATCH Principle:&lt;br&gt;<br /> <br /> Information may be infinite, however...The organization of information is finite as it can only be organized by LATCH: Location, Alphabet, Time, Category, or Hierarchy. [3]&lt;br&gt;<br /> <br /> &quot;I've tried a thousand times to find other ways to organize,&quot; Wurman says, &quot;but I always end up using one of these five.&quot;&lt;br&gt;<br /> <br /> ==The LATCH Principle==<br /> <br /> *Location<br /> Location is chosen when the information who you are comparing comes from several different sources or locales. Doctors use different locations of the body to group and study medicine. Concerning an industry you might want to know where on the world goods are distributed.<br /> <br /> *Alphabet<br /> Alphabet is best used when you have enormous amount of data. For example words in a dictionary or names in a telephone. As usually everybody is familiar with the Alphabet, categorizing by Alphabet is recommendable when not all the audience is familiar with different kind of groupings or categories you could use instead.<br /> <br /> *Time<br /> Time is the best form of categorization for events that happen over fixed durations. Meeting schedules or our calendar are examples. The work of important persons might be displayed as timeline as well. Time is an easily framework in which changes can be observed and comparisons made.<br /> <br /> *Category<br /> Category is an organization type often used for goods and industries. Shops and services in the yellow pages are easy to find by category. Retail stores are divided into e.g. men- and woman-clothing. This mode works well to organizing items of similar importance. <br /> <br /> *Hierarchy<br /> Hierarchy organizes by magnitude. From small to large, least expensive to most expensive, by order of importance, etc. Hierarchy is to be used if you want to assign weight or value to the ordered information.<br /> <br /> ==Ressouces==<br /> <br /> [1]Richard Soul Wurman, “Information Anxiety 2“, Que Publishing, Indianapolis 2000&lt;br&gt;<br /> [2] Donny Truong, “Universal Principles of design” Access Date: 21. Oktober 2005 http://www.visualgui.com/index.php?p=1&lt;br&gt;<br /> [3] Richard Soul Wurman, “Information Architects“, Graphis Press Corp. 1996&lt;br&gt;<br /> [4] Mark Fischetti “Blueprint for Information Architects” Fastcompany Magazine, Issue 10 August/September 1997&lt;br&gt;<br /> [5] Richard Soul Wurman, “The Business of Understanding” Que Publishing, 2000. Taken from: http://www.informit.com/articles/article.asp?p=130881&amp;seqNum=6&amp;rl=1 Access Date: 21. Oktober 2005&lt;br&gt;<br /> <br /> <br /> <br /> ----<br /> Back to [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G3|G3]]</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Five_Hat_Racks&diff=6854 2005-10-25T18:54:03Z

<p>UE-InfoVis0506 0025081: </p> <hr /> <div>The concept of the „Five Hat Racks” was originally developed by Richard Soul Wurman in his book Information Anxiety [1]. In the definition of visualgui (www.visualgui.com) the concept sounds as follows:&lt;br&gt;<br /> <br /> There are five ways to organize information: category (similarity relatedness), time (chronological sequence), location (geographical or spatial references), alphabet (alphabetical sequence), and continuum (magnitude; highest to lowest, best to worse). [2]&lt;br&gt;<br /> <br /> Wurman is chairman and creative director of the TED Conferences who focus on technology, entertainment, and design. In 1976 Wurman defines the term &quot;information architect&quot;. In his book, Information Architects he presents the creations of 20 colleagues who've mastered the skill of presenting clear information. In this book he redefined his “Five Hat Racks” Concept slightly to form the LATCH Principle:&lt;br&gt;<br /> <br /> Information may be infinite, however...The organization of information is finite as it can only be organized by LATCH: Location, Alphabet, Time, Category, or Hierarchy. [3]&lt;br&gt;<br /> <br /> &quot;I've tried a thousand times to find other ways to organize,&quot; Wurman says, &quot;but I always end up using one of these five.&quot;&lt;br&gt;<br /> <br /> *Location<br /> Location is chosen when the information who you are comparing comes from several different sources or locales. Doctors use different locations of the body to group and study medicine. Concerning an industry you might want to know where on the world goods are distributed.<br /> Alphabet<br /> Alphabet is best used when you have enormous amount of data. For example words in a dictionary or names in a telephone. As usually everybody is familiar with the Alphabet, categorizing by Alphabet is recommendable when not all the audience is familiar with different kind of groupings or categories you could use instead.<br /> Time<br /> Time is the best form of categorization for events that happen over fixed durations. Meeting schedules or our calendar are examples. The work of important persons might be displayed as timeline as well. Time is an easily framework in which changes can be observed and comparisons made.<br /> Category<br /> Category is an organization type often used for goods and industries. Shops and services in the yellow pages are easy to find by category. Retail stores are divided into e.g. men- and woman-clothing. This mode works well to organizing items of similar importance. <br /> Hierarchy<br /> Hierarchy organizes by magnitude. From small to large, least expensive to most expensive, by order of importance, etc. Hierarchy is to be used if you want to assign weight or value to the ordered information.<br /> <br /> ==Ressouces==<br /> <br /> [1]Richard Soul Wurman, “Information Anxiety 2“, Que Publishing, Indianapolis 2000&lt;br&gt;<br /> [2] Donny Truong, “Universal Principles of design” Access Date: 21. Oktober 2005 http://www.visualgui.com/index.php?p=1&lt;br&gt;<br /> [3] Richard Soul Wurman, “Information Architects“, Graphis Press Corp. 1996&lt;br&gt;<br /> [4] Mark Fischetti “Blueprint for Information Architects” Fastcompany Magazine, Issue 10 August/September 1997&lt;br&gt;<br /> [5] Richard Soul Wurman, “The Business of Understanding” Que Publishing, 2000. Taken from: http://www.informit.com/articles/article.asp?p=130881&amp;seqNum=6&amp;rl=1 Access Date: 21. Oktober 2005&lt;br&gt;<br /> <br /> <br /> <br /> ----<br /> Back to [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G3|G3]]</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Five_Hat_Racks&diff=6853 2005-10-25T18:52:43Z

<p>UE-InfoVis0506 0025081: </p> <hr /> <div>The concept of the „Five Hat Racks” was originally developed by Richard Soul Wurman in his book Information Anxiety [1]. In the definition of visualgui (www.visualgui.com) the concept sounds as follows:<br /> There are five ways to organize information: category (similarity relatedness), time (chronological sequence), location (geographical or spatial references), alphabet (alphabetical sequence), and continuum (magnitude; highest to lowest, best to worse). [2]<br /> Wurman is chairman and creative director of the TED Conferences who focus on technology, entertainment, and design. In 1976 Wurman defines the term &quot;information architect&quot;. In his book, Information Architects he presents the creations of 20 colleagues who've mastered the skill of presenting clear information. In this book he redefined his “Five Hat Racks” Concept slightly to form the LATCH Principle:<br /> <br /> Information may be infinite, however...The organization of information is finite as it can only be organized by LATCH: Location, Alphabet, Time, Category, or Hierarchy. [3]<br /> <br /> &quot;I've tried a thousand times to find other ways to organize,&quot; Wurman says, &quot;but I always end up using one of these five.&quot;<br /> Location<br /> Location is chosen when the information who you are comparing comes from several different sources or locales. Doctors use different locations of the body to group and study medicine. Concerning an industry you might want to know where on the world goods are distributed.<br /> Alphabet<br /> Alphabet is best used when you have enormous amount of data. For example words in a dictionary or names in a telephone. As usually everybody is familiar with the Alphabet, categorizing by Alphabet is recommendable when not all the audience is familiar with different kind of groupings or categories you could use instead.<br /> Time<br /> Time is the best form of categorization for events that happen over fixed durations. Meeting schedules or our calendar are examples. The work of important persons might be displayed as timeline as well. Time is an easily framework in which changes can be observed and comparisons made.<br /> Category<br /> Category is an organization type often used for goods and industries. Shops and services in the yellow pages are easy to find by category. Retail stores are divided into e.g. men- and woman-clothing. This mode works well to organizing items of similar importance. <br /> Hierarchy<br /> Hierarchy organizes by magnitude. From small to large, least expensive to most expensive, by order of importance, etc. Hierarchy is to be used if you want to assign weight or value to the ordered information.<br /> Ressouces<br /> <br /> [1]Richard Soul Wurman, “Information Anxiety 2“, Que Publishing, Indianapolis 2000<br /> [2] Donny Truong, “Universal Principles of design” Access Date: 21. Oktober 2005 http://www.visualgui.com/index.php?p=1<br /> [3] Richard Soul Wurman, “Information Architects“, Graphis Press Corp. 1996<br /> [4] Mark Fischetti “Blueprint for Information Architects” Fastcompany Magazine, Issue 10 August/September 1997<br /> [5] Richard Soul Wurman, “The Business of Understanding” Que Publishing, 2000. Taken from: http://www.informit.com/articles/article.asp?p=130881&amp;seqNum=6&amp;rl=1 Access Date: 21. Oktober 2005<br /> <br /> <br /> <br /> ----<br /> Back to [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G3|G3]]</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Five_Hat_Racks&diff=6314 2005-10-21T19:51:37Z

<p>UE-InfoVis0506 0025081: </p> <hr /> <div>==Definition(s)==<br /> <br /> ==Introduction==<br /> <br /> ==Examples==<br /> <br /> ==Conclusion==<br /> <br /> ----<br /> Back to [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G3|G3]]</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=User:UE-InfoVis0506_0025081&diff=6095 2005-10-17T15:00:29Z

<p>UE-InfoVis0506 0025081: </p> <hr /> <div>== Userpage 0025081 - 188.308 Informationsvisualisierung - WS 2005/06 ==<br /> ----<br /> &lt;br&gt;<br /> &lt;br&gt;<br /> '''Personendaten''' <br /> &lt;br&gt;<br /> &lt;br&gt;<br /> * Nachname, Vorname: Rainer, Andreas<br /> * Matrikelnummer: 0025081<br /> * Studienrichtung: Magisterstudium Wirtschaftsinformatik<br /> * Studienkennzahl: E 066 926<br /> * Uebungsgruppe: Gruppe G3<br /> * E-mail Adresse: arainer@gmx.li<br /> &lt;br&gt;<br /> &lt;br&gt;<br /> &lt;br&gt;</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2005/06&diff=6094 2005-10-17T14:58:34Z

<p>UE-InfoVis0506 0025081: /* Gruppen */</p> <hr /> <div>[[Image:Aigner03infovis ue.gif]] &lt;big&gt;WS 2005/06&lt;/big&gt;<br /> <br /> '''LVA Nr:''' 188.308 ([http://tuwis.tuwien.ac.at/zope/_ZopeId/61534949A2B1pKks5u4/tpp/lv/lva_html?num=188308&amp;sem=2005W TUWIS++ Seite])<br /> <br /> '''LVA Homepage:''' http://www.asgaard.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html<br /> <br /> '''Leitung:''' [[Aigner, Wolfgang|Wolfgang Aigner]] [aigner (at) ifs.tuwien.ac.at]<br /> <br /> <br /> '''ACHTUNG:''' Namenskonventionen für Usernamen und Seiten einhalten! (siehe [http://www.asgaard.tuwien.ac.at/~aigner/teaching/infovis_ue/infovis_ue_aufgabe0.html Aufgabenstellung])<br /> <br /> '''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.)&lt;br&gt;<br /> *[[Das ist ein Stub]]<br /> *[[Main Page|Das ist ein Link auf eine Seite innerhalb des Wikis]] (kein Stub)<br /> *[http://www.asgaard.tuwien.ac.at/~aigner/teaching/infovis_ue/index.html Das ist ein Link auf eine Seite ausserhalb des Wikis] (kein Stub)<br /> <br /> '''FYI:''' Die E-mail Benachrichtigung funktioniert jetzt wieder.&lt;br&gt;<br /> -- [[User:Iwolf|Wolfgang Aigner]] 09:48, 14 October 2005 (CEST)<br /> <br /> Sollte jemand seine GruppenkollegInnen noch nicht kennen, <br /> entweder über das TUWIS Forum der LVA posten oder <br /> mich unter ''aigner (at) ifs.tuwien.ac.at'' kontaktieren.&lt;br&gt;<br /> -- [[User:Iwolf|Wolfgang Aigner]] 11:45, 17 October 2005 (CEST)<br /> <br /> == Gruppen ==<br /> *[[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G1|Gruppe G1 (Schwarz, Ledinek)]]<br /> *<br /> *[[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G3|Gruppe G3 (Kargl, Karim, Rainer, ???)]]<br /> *[[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G4|Gruppe G4 (Muster, Puchta, Rainer, Sölder)]]<br /> *<br /> *<br /> *[[Teaching:TUW - UE InfoVis WS 2005/06 -Gruppe G7|Gruppe G7 (Yim, Froschauer, Lehrer)]]<br /> *[[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G8|Gruppe G8 (Seyfang, Fritz, Schnabl, Winkelhofer)]]<br /> *[[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 09|Gruppe 09 (Glashütter, Tonkovic)]]<br /> *[[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe 10|Gruppe 10 (Minarik, Kals, Sahin, Slabschi)]]<br /> &lt;!-- <br /> Gruppenlinks hier einfügen!<br /> Beispiel:<br /> *[[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe XX|Gruppe XX]]<br /> &quot;XX&quot; durch Gruppennummer ersetzen!<br /> --&gt;</div>

UE-InfoVis0506 0025081 https://infovis-wiki.net/w/index.php?title=Teaching:TUW_-_UE_InfoVis_WS_2005/06_-_Gruppe_G3&diff=6093 2005-10-17T14:57:28Z

<p>UE-InfoVis0506 0025081: /* &#039;&#039;&#039;Gruppe G3&#039;&#039;&#039; */</p> <hr /> <div>== '''Gruppe G3''' ==<br /> <br /> <br /> Die Gruppe G3 besteht bis jetzt aus den folgenden Mitgliedern:&lt;br&gt;<br /> &lt;i&gt;The following people are part of the G3 group by now:&lt;/i&gt;<br /> <br /> *[[User:UE-InfoVis0506_9825503|Kargl, Horst]]<br /> *[[User:UE-InfoVis0506_0327350|Karim, Muhammad Shuaib]]<br /> *[[User:UE-InfoVis0506_0025081|Rainer, Andreas]]<br /> <br /> <br /> ----&lt;br&gt;<br /> [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G3 - Aufgabe 0|Aufgabe 0]]&lt;br&gt;<br /> [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G3 - Aufgabe 1|Aufgabe 1]]&lt;br&gt;<br /> [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G3 - Aufgabe 2|Aufgabe 2]]&lt;br&gt;<br /> [[Teaching:TUW - UE InfoVis WS 2005/06 - Gruppe G3 - Aufgabe 3|Aufgabe 3]]&lt;br&gt;</div>

UE-InfoVis0506 0025081