Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Discovery Based on Report Usage Patterns

IP.com Disclosure Number: IPCOM000198613D
Publication Date: 2010-Aug-10
Document File: 2 page(s) / 24K

Publishing Venue

The IP.com Prior Art Database

Abstract

This invention provides a novel way to find and record data and metadata usage in a computer software system and use these patterns to bring like minded people together. The key aspects of the invention are the combination of: 1) Recording and comparing usage patterns in order to determine how "alike" a set of users are with one another 2) Introducing the more "alike" users to one another through the system; and 3) Continually updating the usage patterns over time in order to maintain a current and accurate picture of the relationship between users

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 2

Discovery Based on Report Usage Patterns

Disclosed is a process for examining and comparing usage patterns of users in a system. Using the disclosed system users can be evaluated as to degree of "alikeness" using interactions with the system. Users who are deemed to be "alike" can then be introduced to one another by embodiments of the disclosed process, allowing the users to share knowledge and expertise.

In a software system,

                                               , touching data and metadata in arbitrarily complex manners. Examining and comparing these usage patterns within a system using the disclosed process can evaluate users as to their degree of "alikeness" in their interactions with the system. Users who are deemed to be "alike" can then be introduced to one another by the system, allowing them to share knowledge and expertise.

For example in a typical case of a reporting system, the reporting system consists primarily of reports, which can be broadly split into two parts. A query specification part defines the data being viewed and a layout specification part presents the data in a certain manner. The manner and frequency in which users interact with objects of these parts forms a usage pattern between the user and the system.

Once a usage pattern of a user is recorded, the usage pattern can be compared to usage patterns of others to determine how "alike" the patterns are to one another. The definition of "alike" can be quite complex, using different components of the query and layout specifications to form a determination.

The definition of "alike" can be implemented in many possible ways, but in this example of the reporting system determination of "alike" consists of data such as time of access to the reports, frequency of access, layout elements present (for example, charts vs. list reports), query subjects, calculated...