Martijn van Welie Users need to manage a set of objects Web based applications, banking applications, email readers, CMS-es. Basically registration systems....also graphical drawing applications?
From www.matrox.com
Allow users to manage sets of objects using overviews and detail-views When managing sets of objects, users basically work from one or more main . The objects can be anything such as emails, bills, work orders, notices, news texts, etc. Such overviews are often in combination with . When managing objects, the objects are the most important thing the users needs to see and is therefore presented on the . From the overview, the users can manage the set with typical operations such as

• Creating. This either creates an empty object only or users can create the item using a and/or a .
• Modifying. The details of the object can be changed, preferably in-place but otherwise in a new page. Usually some sort of is used.
• Deleting. Select one or more objects manually or by setting criteria like in an and then execute the deletion.
• Moving. Select one or more objects and more to a new location.
• Copying. Select and copy.
• Storing/retrieving. Can be online or to a local filesystem.
• Sorting. Either using or

The basic principle to use is "overview first". That often translates to seeing the result as far as it exists. Consider when novice users are asked to create something. The users work on a central canvas that is surrounded by functionality grouped in menu's or other navigational items. can help to allow users to manage groups of functionalities that need to be in sight or away. The basic principle at work is overview-by-detail. When viewing an overview, users can add, delete, copy