Interface

buzzaar GENERAL
Buzzaar webmap interface is divided into 2 parts to make a difference between operations that are managed on the server side, and functions managed by the applet on the maps edit.

1. the menu and functions at EPFL server level first visit: load login page and menu: login | register |  webmaps | about buzzaar  NO INDEX AT SERVER SIDE  index page is at buzzaar.net after logged in: menu: show nickname (should always be the email identity) and load a map (depending on what is the default behaviour chosen by user) after exit ( means that user quit the applet ) menu: user id | user profile | logout | webmaps | about buzzaar  

2. the menu and function of the Applet itself (the maps and list)

on the Applet: the menu concerning operations, functions, customization, and manipulation of the map itself

menu have menu list options, help menu is where the demo is found with tutorials

when users want to logout they first have to : quit the applet, then logout from the first menu (server level)

3. default behaviour at login

Users choose what kind of map they want to open at login:

1. blank webmap (i.e blank page with no data)

2. default webmap (i.e the webmap selected by the user as its default - each time they login, they will be asked if their default should be updated: merged with their up-to-date data

3. last opened webmap

4. last saved webmap

4. behaviour at very first login

depending on a. either users have data ( have downloaded the buzzaar toolbar and have data already sent on the server) or b. they have no data (no plugin installed or no data sent yet to the server)

a. the applet load the current webmap : the raw data visualization (no customization, no tags ...)

b. a blank page with a pop up message  warn them that there are several reasons if they have no data (see: popup messages)

OPERATIONS
merge add webmaps into logged in user's opened webmap. non symetric: i.e I merge my chosen opened map with another one: In  resulting webmaps, URLs, URL frequencies/co-frequencies and tags are cumulated. tags of the logged in users have the priority. colors and settings are kept.

projection

non symmetric operation that can be described as follows: the result of the projection of a webmap A into a webmap B is a webmap C s.t.: the central zone of C is the central zone of A (i.e. the visual identity of the user performing the projection is preserved); the default zone of C contains all the URL/URL domains common to A and B (thus allowing to easily spot commonalities); and the peripheral zone of C contains all the URL/URL domains of B that are co-occurring with some of the nodes in the default zone of C (thus allowing to easily identify information in B not present in A that is potentially the most relevant to A).

co-occuring nodes of B in the peripheral zone, have a different color, alpha transparency show their popularity for their user.

in the default zone the alpha transparency show the degree of relevance of this complementarity for A

INTERFACE
maps

The matrice is divided into zones:

1. central zone: user

2. expansion zone (for expanded domains or tags)

3. default zone: by default URL domains and tags are displayed here

4. peripheral zone: for projected co-freq nodes and tag names

when on rollover URL domains and nodes are a bit bigger

when on selected: URL domains and nodes change their border color and their co-freq nodes change their bg colors

Generally (except for co-freq nodes of the projected in map) the size of nodes show their popularity (frequencies) for their user.

Alpha transparency rules (both for domain and tag mode)

 URL domain and nodes in default zone have an opacity at 80%<(li>

expanded nodes in expansion zone have an opacity at 80%

co-freq nodes in default zone have an opacity at 30%

 co-freq nodes in the peripheral zone (projection operation) have an opacity depending on their popularity for their user 

on rollover and selected: opacity: 100%</li> </ul>

list design principles: simultaneity and synchronization with the map;

on the list we can: expand and colapse an URL domain or a tag;</li> select an URL domain, URL or tag (will show co-freq nodes on the map but not in the list);</li> delete a node, a tag an URL domain;</li> on tag mode: show tags but not nodes inside tags: we have to expand it to see nodes: on the contrary on the map we see nodes inside the tag without having to expand it ... </li> </ul>

Applet toolbar

button 1. expand-collapse

button 2: domain -tag mode

button 3: save

button 4,5,6 co freq all, from selected, none

button 7 merge with local map

button 8 project in a local map

button 9: upload

button 10 download

button 11: reset layout

button 12: undo

button 13: redo

user toolbar

this toolbar is divided into zones

1.user icon

2. merge or project information

3. URL identity

4. mode display and domain or tag info

5. bg color choice

FUNCTIONS </H1>
Domain mode by default: domain mode show only URL Domains

they are displayed in the default zone;

when expanded: an URL domain show only all nodes (no subdirectories)

They are displayed in the expansion zone and separated from the rest of the matrix by a border (following the same logic than in the tag mode when a tag is expanded

in the default zone are only the other URL domains that are co-frequent with the expanded domain

tag mode By default tags titles are shown but no border.

expanded tags: in the expanded zone:

co-freq nodes stay in their tags, in the default zone.

display  on rollover on a tag: its zone is colored (alpha transparency at 50%);</li> the border of the tag is shown when selected;</li> on the expanded zone: the border is by default;</li> margin between tags 5px;</li> tag name is placed at the middle of the tag; </li> when expanded the tag name disappear. (shown in the interface toolbar);</li>

</ul>

mapping archives - links
edition archivée des mapping

draft union - intersection differences

personnalisation du mapping

personnalisation et co-occurence

personnalisation et granularité - archives

merging maps - archive