Introduction to Reporting

Reports are used to track project progress and activity within the Management Center. Reports can be generated for uPerform and managed documents. Once a report is generated, the results can be exported or viewed online.

Reporting now includes an Analytics database for increased report performance and greater flexibility in building reports. The Analytics database sync task runs hourly to update the Analytics database with information from the Collab database. When adding information to the Analytics database, the information will not show up in the database until you are able to search for the information on the Management Center; however, deleting information happens in real time.

The following standard, non-editable reports are available within the Management Center:

1. Assessment Performance - Displays a detailed report for courses and assessments assigned to a project. Assessment information, including completion percentage and scores, are tracked for SCORM packages from non-uPerform sources and uPerform courses and simulations with templates that have SCORM 1.2 or SCORM 2004 packaging enabled. For more information, refer to Specifying New Template Settings: Publications.

   NOTE:

   Only the simulation assessment output results are displayed on the Assessment Performance report, even though all the simulation outputs work with an LMS and can be tracked.

   NOTE:

   The start and end dates on the Assessment Performance report are based on the user's time zone.

2. Document Tracking - Displays a detailed report of the documents assigned to a project.

   NOTE:

   The File Name field in the Document Tracking Report is the source file for managed documents.

3. Help Request - Displays a detailed report of context-sensitive help requests received.
4. Published Content - Displays a detailed report of the published documents assigned to a project.
5. User Data - Displays a detailed report of users and their roles.
6. Website Usage - Displays a detailed report of Learning Library end user website usage. Available usage information includes hit counts, username (if enabled), date, and content type.

In addition to the standard reports, individuals can create custom reports from the ground up or by starting with a copy of a standard report. The columns and filters for a custom report can be edited to fit an organization’s needs. Custom reports can contain uPerform properties as well as hit counts on uPerform content.

A few guidelines to consider regarding Server reports:

1. System and project administrators have access to all reports; however, what project administrators see is limited by their project permissions. Authors do not have access to reports, but can see the Document Tracking report on the Projects page.
2. Punctuation is ignored in content filtering with the exception of keywords separated by a comma or an asterisk used to denote the presence or the absence of a value.
3. Stemming is incorporated on all filters. For example, if you enter "general" into a filter field, you will receive a return for "generic."
4. The maximum number of hits that can be returned from a report is 2,000,000.
5. Reports do not support Server-side paging; therefore running large reports can negatively impact performance of the Server.