David Scott Blackburn

Tracking Usage System Reports The reports created for the Tracking Usage System were developed using SQL Server Reporting System. All of the reports use stored procedures to extract data from the database source. Cached data is mostly used as to reduce traffic and improve performance. The table used in the reports comes primarily from the Tracking table, however, some data is also used from the Notebook, Notes, and Contact tables as well. Other tables used are specifically developed for the reporting system. This document explains the purpose and the data used for each of the reports. Contact & Comment Detail This report shows all of the comments, names, and emails entered by users who have entered such information on the contact and comment web page. It has been designed to also track information currently not tracked by the system. However, the absence of the currently untracked data does not distract from the information that is tracked. This is an important report for a more utilized system as it would keep web masters abreast on what the public thought of the site, possible unknown bugs, and what the system or using company may need to immediately address. The stored procedure uses a date range for its parameters, so that the data retrieved can be finely tuned. The data for this report solely comes from the Contact table. Notebook App Usage This report shows the usage of the Notebook app. It shows how many new users have signed up to use the notebook application, how many times someone has landed on its welcome page, how many times someone has logged into the it and the number of new notes created. The date range for the report can be changed by adjusting the parameters used by the stored procedure. Weekly Usage This shows the weekly usage of each of the applications and the number of accesses to resume, either by downloading or using the resume option on the portfolio site. This is a simple line graph. The stored procedure is controlled by a supplied date range. The data is retrieved once, multiple retrievals are made from the cached data. User Visit This is an important report in that it shows the sites top users. This would be important information for a variety of reasons. The usage trend is important as well as it tells the site’s owner’s when the site has been most used and by who. General Application Usage This shows the total multiweek usage of all the site’s apps. It breaks down the main site’s usage. It then breaks down that usage to per week. This is useful in that it allows for trends to be easily seen. Visitation Key Process Indicator This report is very different from the rest. It is the UNIQUE visits to the key areas for the current and previous week. The trend summary is shown at the bottom. The average unique visits is also shown. This is a Key Process Indicator. This would be the most important information required by the organization using this web site as it tells how many individual users (as best as possible) have accessed the system within the current week (so far). The Key areas of the system is the Resume, Profiles, Gallery, and Document areas. These are key areas because it is in these areas that detailed information is shown. Clicking anywhere on the indicator brings up the Key Area Visitation Details. Key Area Visitation Details This is the most important report in the whole series. It not only shows the same information displayed in the Visitation KPI, but shows that information for the past 5 weeks, and shows the key area visitations as well. It shows the combined number of visits to those areas as in the All area. The Any area is merely the recording of a single visit to any of the key areas. The top row shows the combined breakdown. The detailed areas, shows the total, a comparison to the previous week, and a comparison to the average. The first week also show the average that the report is comparing the week’s total to. Both of these reports use a reporting table that is created weekly and updated thought out the week. Stored procedures are run to create and update these tables. These stored procedures do not take parameters as the date ranges are fixed, the initialization report and update report are run prior to loading the report with data. Usage Dashboard This is a series of reports that is displayed as one report. Cached data is used when possible. Also, certain summary data is returned by one stored procedure call. Much of the data, however, uses the same stored procedure for that larger report call. Clicking in the Total Application Visits area, will bring up that report entire report. Clicking the Number of Visitors to Key Areas, however, will bring up the Key Area Details report. Clicking the Weekly Application Visits, Top Users, and Latest Visitor Comments will bring up the Weekly Application Visit, User Visit, and Contact and Comment Detail reports. This would be the key screen implemented in a real-life situation. It is also a good way to implement the sub-reports. An alternative to bring up the individual reports would be to have a menu option from this same screen that would allow a user to bring up any of the desired reports. Future changes Soon there will be additions to this system. Foreseen changes are: 1. The WhoID issue resolved. Please refer to the Tracking System document for further information about this. 2. Automatic updating of the reports seen in the Gallery. That is a system of automatically updating the reports displayed in the gallery. This would be done by the system generating the reports and the report results FTP up to the server via a SSIS package. 3. Report subscription. This would be copies of the reports or links to the latest generated reports sent to those who would like to receive such updates. 4. Migrating the system to a Host that allows for Report System to be run from it. Currently, reports have to be run on a local host and then the result of the report copied to where it is displayed.