Document Actions
1.
Navigation Overview
Up one level
The site may be navigated using the navigation tree, the My Workspace tool, searching, using the Recent Items portlet, or using the links in the Entities or Documents tabs in Areas, Entities, or Sections.
Usually users can use any means to navigate the site, but where there are large volumes of content, there will be times when some means and not others are appropriate.
Most sites would generally have a small number of Areas, Sections and Engagements within their respective containers. The significant volume issue is usually the potential number of Entities within an Area. In this case there may be hundreds or thousands.
At all levels, other than levels containing large numbers of Entities, the navigation tree is useful to navigate. The Navigation tree is also necessary to demonstrate to users the tree structure of the site, on which the security model is based. Therefore, the OpenEngagement DMS, at all times, shows the complete navigation tree, going to the document level (assuming the Navigation Settings have their default values).
When looking for, say, an Engagement, within an Area, Entity, and Section, the navigation tree may not always be useful to find the Engagement. For example, if the user is currently located on an Area, and wishes to go to an Engagement, and this Engagement is in a Section, which is within a Entity, which is within the Area, and if the Area contains 5,000 Entities, which each contain four Sections, it would be difficult to use the navigation tree to navigate down the tree to the desired Engagement. This would require scrolling through up to 5,000 Entities in the Area to get to the relevant Entity.
However, the navigation tree will always be useful to show where in the tree (i.e., in the site) the user currently is. For users with very few permissions, this may be irrelevant (e.g., they can only prepare a few engagements, all of which are deep in the tree, and it is not relevant to them where in the overall site organization these Engagements are), but since it's impossible to programmatically determine who will wish to see the navigation tree and who will not, the OpenEngagement DMS shows the navigation tree for everyone at all times. The breadcrumbs have a similar purpose and limitations, but may be optionally disabled in the OpenEngagement configuration. This will disable the breadcrumbs, until they are re-enabled, site-wide for all users.
When a user navigates to an Area which has, say, 5,000 Entities, the navigation tree will show where the user currently is, but won't help them find the Entity they are looking for. To do this, the user is better to use either the OpenEngagement DMS's searching functionality, the My Workspace tool, the Area's Entities tab, or to select the Documents tab for the Area, and apply a filter to the contents displayed on the View tab of the Area. Using the filter, possibly in combination with the tables' sort functionality, may be a very practical method to navigate to the desired Engagement.
Where sites do not have large volumes of content at any level, navigating entirely using the navigation tree may be perfectly satisfactory. In this case the other means of navigation may be convenient, but are not necessary.
Future releases of the DMS will also allow users to define favorites, so they can mark certain Documents in a favorites list they maintain. In the meantime, it is possible to bookmark Documents or other objects within the DMS using a web browser's bookmarks.