Kavi® Status Tracker Help

Chapter 3. Reports and Views

Another advantage of storing your project and activity information in Kavi Status Tracker's centralized Web-friendly database is that this information is easily exported for display. Kavi Status Tracker provides configurable reports and default views that can be tailored to fit the organization's needs, or your website may have built-to-suit views that are unique to your organization. Your organization will have multiple views, aimed at different audiences such as specific groups within the organization, the organization's general membership and the public.

Member Area Reports

Like other Kavi applications, Kavi Status Tracker relies on the Kavi Report Builder for robust, extensible reports. The default Project Data and Activity Data reports are easily augmented by anyone with Status Tracker Super Admin access.

Once a report is created and activated, it immediately becomes available in the Reports Area, but in Kavi Status Tracker, reports can also be displayed on the Kavi Status Tracker Member landing page. All that a Super Admin has to do make an active report available on the Member landing page is select the report in the Member Accessible Reports tool. Reports on the Member landing page are accessible by anyone in the organization by default.

Back to top

Default Views

Kavi Status Tracker provides several default views, designed to be implemented in different locations, such as the Kavi® Groups Group Home tab, Member Area pages controlled by Kavi® Members and the Public Area of the website. These are plain-vanilla views, each acting as a framework on which your organization's views are built, so a default view described here as a public view may be implemented as a member-only view on your website, and vice versa.

Public Views

Most organizations use Kavi Status Tracker to display project information to the public. It is common to have multiple public views and to select projects for display in these views based on the Project State, so that projects that are ready for public comments are displayed through one view, and projects that have been approved for publication are displayed through another. Kavi Status Tracker includes a plain-vanilla default view for published standards. Like other default views, this one acts as a framework on which actual views can be built, so it is easily tailored to display bylaws or white papers.

Although the view is designed for display on public pages, it can just as easily serve as the basis for views displayed within protected areas of the website. Conversely, views described below in the sections Organization-Wide Views and Group Views can be modified for use on public pages.

Figure 3.1. Sample Public View of Published Standards

A screenshot of
	    http://sdo.demos.kavi.com/public/published_standards. A
	    page titled "Published Standards" displays a
	    list of published standards, along with a View Details
	    link that the user can click to go to a Single Project View that displays
	  information about the standard, possibly including a link to
	    view the standard as HTML or download it as a PDF. This page includes
	    several of the Kavi display widgets, so the Standard Name
	    column is sortable by clicking on the column title and the
	  results per page can be changed by the viewer. The page
	    includes a Back to
	    Public Area button at the bottom of the form and
	    breadcrumbs at the top of the form facilitate navigation.

In this example, a simple view displays list of published standards plus a View Details link that the user clicks to go to a Single Project View that provides more information about a particular standard or project (e.g., a link to view the standard as HTML or download it as a PDF). The Published Projects sample view has a sortable Standard Name column and the results per page can be changed by the viewer. The Back to Public Area button and breadcrumbs at the top of the form return the visitor to one of the main public landing pages.

Organization-Wide Views

Kavi Status Tracker has two default views that are designed for display on Member Area pages where they are accessible to logged-in account holders. These plain-vanilla default views are altered to fit the organization's needs before installation, so views based on these defaults may include other fields, may be installed in a different area or may only be available to certain types of users. For examples of the default organization-wide views, see the screenshots of the Kavi SDO Demo site in the Appendix document Organization-Wide Project Views.

Group Views

Another set of Kavi Status Tracker default views is designed to display projects that are associated with a specific group. Because the projects are group-specific, these views are usually displayed on a tab on the Owning Group's Group Home page, but these views can be used wherever a view of group-specific projects is wanted. For examples of the default group views, see the screenshots of the Kavi SDO Demo site in the Appendix document Group Project Views.

Back to top

Built-to-Suit Views

The default views can be used as the basis for any number of different views, but sometimes an organization requires a view that can't be created by tailoring any of the default views, which are fairly simple and straightforward in structure and content. In this case, your organization may have a view that is built-to-suit by Kavi or an authorized channel partner. These views can contain any data fields that are available in the Kavi Status Tracker database and sometimes include data from Kavi Groups, Kavi Members or other application database. These views may select projects for display based on Project State, and access may be restricted so that they are only displayed to certain types of users.

Back to top