System and method for providing analytics for a communities framework

• US 20070112856A1
• Filed: 03/07/2006
• Published: 05/17/2007
• Est. Priority Date: 11/17/2005
• Status: Abandoned Application

• Current Assignee: BEA Systems Incorporated (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Posner, Brad, McMullen, Cindy, Wille, Jason, Lannin, Joshua, Schram, Aaron
• Application Number:
  US11/369,545
• Publication Number:
  US 20070112856A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: G06F 2209/544 Remote
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

A community can be accessed via a portal and can maintain user membership during collaboration projects. Members of the community can access various resources stored in nodes within a repository. An event object can be provided that wraps a node within the repository such that data regarding the event object is persisted in the node. A developer can target a particular action within the system and associate the event object with that particular action. A set of event listeners can listen to the event objects and collect them as the targeted actions occur. These event objects can be placed into a buffer and subsequently persisted to the repository. The system can thus maintain a count of the occurrences of targeted events as they occur. In this manner the health, trends and behavior of the community can be monitored via created event objects.

Claims

1. A system of providing analytics for a communities framework, comprising:

a repository that contains data stored in nodes, each node containing data for a resource;

a server that provides an event object associated with an action occurring within the system, the action having been specified by a user;

wherein the event object is mapped to a node in the repository and wherein the node stores data associated with the event object.

2. The system of claim 1 further comprising:

an event listener configured to collect event objects upon the occurrence of the action.

3. The system of claim 2 further comprising:

.

an event buffer for receiving event objects from the event listener and for holding the event objects until they are persisted into the repository.

4. The system of claim 3 further comprising:

a first component for managing the event buffer; and

a second component for managing persisted analytics data and creating analytics charts.

5. The system of claim 1 wherein new event objects are created and associated with actions based on input from a user.

6. The system of claim 1 further comprising:

a community for maintaining user membership accessed via a portal and comprised of one or more members wherein the health of the community is monitored via maintaining a plurality of event objects and storing event object data in the nodes within the repository.

7. The system of claim 1 further comprising:

an extensible control for manipulating data in the node within the repository.

8. The system of claim 1 wherein the event object contains an event type attribute for specifying the corresponding node within the repository that holds information for the event object.

9. The system of claim 1 further comprising:

an analytics portlet for displaying selected event data including created charts.

10. The system of claim 1 wherein the event object contains at least one of event type, membership role and community identifier attributes.

11. The system of claim 1 wherein the node mapped to the event object maintains a count of occurrences of the action associated with the event object.

12. A method of providing analytics for a communities framework, comprising:

providing a repository containing data stored in nodes;

providing an event object for holding analytics information;

mapping the event object to a node within the repository;

receiving a specification of an event that will occur within the system;

associating the event object with the specified event in the system such that data regarding the specified event is stored in the node mapped to the event object;

collecting the event object upon the occurrence of the specified event in the system; and

persisting the event object data to the repository.

13. The method of claim 12 further comprising:

providing a set of event listeners configured to collect event objects upon the occurrence specified events.

14. The method of claim 13 further comprising:

providing an event buffer for receiving event objects from the event listener and for holding the event objects until they are persisted into the repository.

15. The method of claim 14 further comprising:

providing a first component for managing the event buffer; and

providing a second component for managing persisted analytics data and creating analytics charts.

16. The method of claim 12 wherein new event objects are created and associated with events in the system based upon input from a user.

17. The method of claim 12 further comprising:

providing a community for maintaining user membership accessed via a portal and comprised of one or more members wherein the health of the community is monitored via maintaining a plurality of event objects and storing event object data in the nodes within the repository.

18. The method of claim 12 wherein the event object contains an event type attribute for specifying the corresponding node within the repository that holds information for the event object.

19. The method of claim 12 wherein the node mapped to the event object maintains a count of occurrences of the specified event associated with the event object.

20. A computer-readable medium having instructions stored thereon that when executed by one or more processors cause the system to:

provide a repository containing data stored in nodes;

provide an event object for holding analytics information;

map the event object to a node within the repository;

receive a specification of an event that will occur within the system;

associate the event object with the specified event in the system such that data regarding the specified event is stored in the node mapped to the event object;

collect the event object upon the occurrence of the specified event in the system; and

persist the event object data to the repository.