Difference between revisions of "Talk:Interface Draft: Breadcrumb Concept"

From MPDLMediaWiki
Jump to navigation Jump to search
 
Line 1: Line 1:
=Definition=
'''NOTE''': This discussion page was not longer in sync with the corresponding article (compare definition). Therefore, I only kept the discussion part and removed all further content.
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'.
=Discussion of Assumption=


=Overview on 'Click Levels'=
'''Assumption''': 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.
The rough overview shows main functional areas and click levels (this is a diagram only, not a specification of the page flow R4).
 
[[Image:levels.gif|center|framed|Diagram of functional areas]]
 
==Why the following breadcrumbs do not make sense ==
 
'''Path'''
 
Path breadcrumbs are dynamic and show the path that the user has taken to arrive at a page [http://en.wikipedia.org/wiki/Breadcrumb_%28navigation%29 Wikipedia on Breadcrumbs].
 
*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 true for static content. 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
 
'''Simple Search'''
*is anyway provided persistently inside header
*is not clear where breadcrumb leads to (revise search via advanced search?)
 
'''Advanced Search'''
*is anyway provided persistently inside header
 
'''Organisation Search'''
*is anyway provided persistently inside header
 
'''Export'''
*will mostly appear at the end of the breadcrumb
*will automatically be available after any search
 
'''Item Details (Revisions, Attachements, ...)'''
*will mostly appear at the end of the breadcrumb
 
'''Submission(methods)'''
*is 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=
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.


This additional navigation should not be called breadcrumb or be offered in a breadcrumb manner/stype in the interface because it is different.
This additional navigation should not be called breadcrumb or be offered in a breadcrumb manner/stype in the interface because it is different.


well, sounds like a simple context menu to me, not?[[User:Robert|Robert]] 20:12, 20 October 2008 (UTC)
well, sounds like a simple context menu to me, not?[[User:Robert|Robert]] 20:12, 20 October 2008 (UTC)
==Examples==
In most cases the labels are not so long. Example shows the longest possible labels.
{|{{Prettytable}} id='35'
|- bgcolor = #ccccff
!Click Level!!Label!!Tooltip
|- bgcolor = #eeeeff
|1-2||Results List (1234)||Page 2: Hits 25-50
|- bgcolor = #eeeeff
|3||Results List (1234) > escidoc:1707:1||Page 2: Hits 25-50 > Titel of item
|- bgcolor = #eeeeff
|4||Results List (1234) > escidoc:1707:1 > Workspace (1234 Pending)||Page 2: Hits 25-50 > Titel of item > Page 1: Hits 0-25
|- bgcolor = #eeeeff
|}
The 'Listtrail' vanishes if any other functionality is triggered or any item state is changed. The list contains not more than 3 entries. If more than 3 entries are available the first entry will dissapear.
[[Category:Interface Conception & Design]]
[[Category:User Interface Engineering]]

Latest revision as of 15:14, 21 October 2008

NOTE: This discussion page was not longer in sync with the corresponding article (compare definition). Therefore, I only kept the discussion part and removed all further content.


Discussion of Assumption[edit]

Assumption: 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.

This additional navigation should not be called breadcrumb or be offered in a breadcrumb manner/stype in the interface because it is different.

well, sounds like a simple context menu to me, not?Robert 20:12, 20 October 2008 (UTC)

Publication Management

Coordinated Universal Time

Retrieved from "https://colab.mpdl.mpg.de/mw010/index.php?title=Talk:Interface_Draft:_Breadcrumb_Concept&oldid=22635"