| US 7,590,663 B2 | ||
| Managing changes in a relationship management system | ||
| Terry Hamer, Naperville, Ill. (US) | ||
| Assigned to Reed Elsevier Inc., Waltham, Mass. (US) | ||
| Filed on Sep. 30, 2003, as Appl. No. 10/675,431. | ||
| Claims priority of provisional application 60/414713, filed on Sep. 30, 2002. | ||
| Prior Publication US 2004/0128321 A1, Jul. 01, 2004 | ||
| Int. Cl. G06F 12/00 (2006.01); G06F 7/00 (2006.01) | ||
| U.S. Cl. 707—200 [707/101; 707/104.1] | 49 Claims |

| 1. A relationship management system, comprising:
a first database that stores a plurality of user collections, wherein each user collection is accessible by a user of the
system and includes one or more first contact files, each different first contact file within a particular user collection
including contact data that is unique to that first contact file;
a second database that stores a firm collection, wherein each firm collection is accessible by an administrator of the system,
the firm collection including a second contact file for each different first contact file included in the plurality of user
collections, each second contact file having at least a portion of data in common with one of the first contact files; and
an administration routine stored in a memory and adapted to be executed on a processor to detect a change made to the common
data of one of the first contact files within one or more of the plurality of user collections, to generate an event action
in response to detecting the change, and to send a message including the event action to the administrator of the system,
wherein the changed common data includes contact data pertaining to one or more contacts other than the user with access to
the changed user collection;
a change management routine stored in the memory and adapted to be executed on the processor to receive a response to the
event action from the administrator, and to process the response by
making the change to the common data of the corresponding second contact file within the firm collection and to provide an
option to make the change to the common data of the remaining user collections.
|