Difference between revisions of "Interface Draft: Breadcrumb Concept"
m (→Examples) |
|||
| Line 64: | Line 64: | ||
Click Level | Breadcrumb | Click Level | Breadcrumb | ||
1-2 | Lists: Searchresult (10) | 1-2 | Lists: Searchresult (10) | ||
| Line 85: | Line 83: | ||
[[Category:Interface Conception & Design]] | [[Category:Interface Conception & Design]] | ||
[[Category:User Interface Engineering]] | [[Category:User Interface Engineering]] | ||
Revision as of 12:29, 12 June 2008
Definition[edit]
A breadcrumb should provide a trail for users navigating within a page structure. It provides an easy way to access previously seen pages within the page structure. Users sometimes do not have in mind how to navigate to a certain page via multi level menu(s).
Problem
For web applications - where items are irrepealable be changed - there is no way back. Once an item has been changed it would not make sense to return to a previous view. And if so, the user needs to know the difference between 'back' and 'undo'.
Overview on 'Click Levels'[edit]
The rough overview shows main functional areas and click levels (this is a diagram only, not a specification of the page flow R4).
Why the following breadcrumbs do not make sense Wikipedia on Breadcrumbs[edit]
Path
Path breadcrumbs are dynamic and show the path that the user has taken to arrive at a page.
- PubMan does not provide a strict hierarchical structure. In many cases there is no single path to a page.
History of pages/Action history
- This is not, what a breadcrumb is expected to be. If items change at one point in time it does not make sense to jump to a page reflecting a state which is different from the current/real one.
Attribute
Attribute breadcrumbs give information that categorizes the current page.
- Would make sense, but as pages are role dependent the attribute might reflect a wrong categorization
Why a breadcrumb makes no sense for the following functionality:
Most pages are anyway redundantly displayed in a breadcrumb or inconsistent in use, because[edit]
Simple Search
- Anyway provided persistently inside header
- Not clear where breadcrumb leads to (revise search via advanced search?)
Advanced Search
- Anyway provided persistently inside header
Organisation Search
- Anyway provided persistently inside header
Export
- Will mostly appear at the end of the breadcrumb
- Autoamtically available after any search
Item Details (Revisions, Attachements, ...)
- Will mostly appear at the end of the breadcrumb
Submission(methods)
- Inconsistent because item changed in status
Actions
- Will be a mixture of structural breadcrumb and action history
- As actions lead to modifications the breadcrumb is rather a undo history (not possible!!)
Assumption[edit]
There is a certain functional area, where items do not change and where a breadcrumb could provide help (see Diagram). PubMan should provide a breadcrumb only for item lists, view item version, item details.
Examples[edit]
Public:
Click Level | Breadcrumb
1-2 | Lists: Searchresult (10)
3 | Lists: Searchresult (10) > View Item (x)
4 | Lists: Searchresult (10) > View Item (x) > Revision (x)
Logged in:
Click Level | Breadcrumb
0 | Lists: Workspace (Pending, alternatively in Tooltip)
3 | Lists: Workspace (Pending) > View Item (x)
4 | Lists: Workspace (Pending) > View Item (x) > Item Log