Abstract: A community that is accessed via a portal is disclosed, for maintaining user membership during collaboration on a project. A repository containing resources is provided wherein the data is stored nodes and each node is associated with a collaboration resource. The resources can each have a set of properties or attributes. A content object can be provided for wrapping each node and for specifying what type of resource the node holds data for. A generic control can be implemented in order to handle various business logic for the developer in terms of the collaboration resources. The generic control can deal with the content object wrappers instead of nodes. Developers can use the generic controls in order to obtain an abstracted interface to the content management system API. The generic control can also contain an extensible control for performing CRUD operations on the data nodes.

Abstract: A community that is accessed via a portal is disclosed, for maintaining user membership during collaboration on a project. A repository containing resources is provided wherein the data is stored nodes and each node is associated with a collaboration resource. The resources can each have a set of properties or attributes. A content object can be provided for wrapping each node and for specifying what type of resource the node holds data for. A generic control can be implemented in order to handle various business logic for the developer in terms of the collaboration resources. The generic control can deal with the content object wrappers instead of nodes. Developers can use the generic controls in order to obtain an abstracted interface to the content management system API. The generic control can also contain an extensible control for performing CRUD operations on the data nodes.

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.

Abstract: A community of various members can be provided for maintaining user membership in the collaborative computing environment. Members can have access to a repository containing various resources. Each resource can have various properties or attributes. Data within the repository can be stored in nodes. Each node can be further wrapped by a content object which designates the type of resource stored in the node. A unique key can be created, based in part on the resource's attributes contained in the node. The unique key can be associated with the content object and used to uniquely identify the node within the repository. An extensible control can be further provided for allowing a developer to specify which properties or attributes are to be used in creating the unique key.