Managing changes in a relationship management system

• US 8,935,202 B2
• Filed: 06/25/2004
• Issued: 01/13/2015
• Est. Priority Date: 09/30/2002
• Status: Expired due to Fees

• Current Assignee: RELX Inc. (RELX PLC)
• Original Assignee: RELX Inc. (RELX PLC)
• Inventors: Hamer, Terry, Brendler, Ralph Edward
• Primary Examiner(s): Mofiz, Apu
• Assistant Examiner(s): DAYE, CHELCIE L
• Application Number:
  US10/876,236
• Publication Number:
  US 20050004928A1
• Time in Patent Office: 3,854 Days
• Field of Search: 707/101, 707/104.1, 707/100, 707/610, 709/200, 709/225
• US Class Current: 707/610
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

A relationship management system stores multiple versions of contact information for a particular contact by storing the contact information that is available to all of the users of system that know a particular contact in a firm collection and by storing information about the particular contact that is available to a limited number of users that know the particular contact in one or more user collections. When changes are made to the user collection for a particular contact, the system detects the change, and based upon a number of administrative rules determines whether the change should be contributed to the firm collection. The system may automatically make the corresponding changes to each of the contact files within the firm collection or may recommend to the user whether the change should be promoted, allowing the users to accept or reject the recommendation. Preferably, each user will be provided with a default number of days to accept or reject the recommendation, after which the system may promote the contact information automatically.

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 unique contact files;

a second database that stores a firm collection, the firm collection including one or more second unique contact files, each second unique contact file having contact data in common with one or more of the first unique contact files;

a third database that stores one or more rules, each rule including data that matches the contact data in common with one or more of the first unique contact files, the one or more rules defining a strategy for managing a change to the one or more second unique contact files upon detecting a change to the common data of one or more of the first unique contact files within a particular user collection, the changed one or more first unique contact files corresponding to one of the second unique contact files, wherein the changed common data corresponds to one or more contacts other than the user with access to the changed user collection and the strategy includes presenting an option to add or not add the change to the firm collection when the changed common data corresponds to contact data of a first subset of the second unique contact files; and

a change routine stored in a memory and adapted to be executed on a processor to detect a match between one or more rules and the changed common data of the one or more first unique contact files and to make the change to the common data of a corresponding second unique contact file within the firm collection according to the one or more rules.

2. The relationship management system of claim 1, wherein the change routine includes the third database.

3. The relationship management system of claim 1, wherein the one or more rules are changeable by an administrator.

4. The relationship management system of claim 1, wherein, according to the one or more rules, the change routine specifies that the change made to the first unique contact file is recommended to be made to the second unique contact file, and wherein the change routine is adapted to present an option to allow or reject the recommendation by the change routine.

5. The relationship management system of claim 4, wherein, according to the one or more rules, the change routine is adapted to make the change to the second unique contact file automatically after a specified amount of time.

6. The relationship management system of claim 1, wherein the change routine is further adapted to process the detected change to detect the addition of a new first unique contact file for a contact within one of the user collections for which a further second unique contact file already exists within the firm collection.

7. The relationship management system of claim 1, wherein the change routine is further adapted to process the detected change to detect the addition of a new first unique contact file belonging to a subset for which the contact type already exists within the firm collection.

13. The relationship management system of claim 1, wherein the first and second subsets of the one of more second contact files includes one or more contact folders.

8. A method of storing information pertaining to a plurality of contacts in a relationship management system used by a multiplicity of users, comprising:

creating a user collection for each of the multiplicity of users;

creating a firm collection;

storing a first contact file for a particular contact within one or more user collections;

storing a second contact file for the particular contact within the firm collection;

wherein the first and second contact files include common data;

detecting a change made to the first contact file common data for the particular contact within one or more of the user collections wherein the changed first contact file common data corresponds to one or more contacts other than the user for which the user collection was created;

storing one or more change management rules wherein each of the one or more rules includes data that matches the first contact file common data and defines a strategy for managing a change to the one or more second contact files;

comparing the change made to the first contact file common data to the one or more change management rules; and

when the comparison of the change and the rule indicates that the change includes common data that is different than the second contact file common data;

presenting an option to modify the second contact file with the changed common data when the common data includes contact data of a first subset of the second contact files; and

saving the changed common data to the first contact file when the common data includes contact data of a second subset of the second contact files;

wherein the one or more subsets include one or more of a firm list contact, firm personnel, alumni, top clients, clients, or a company associated with a client.

9. The method of claim 8, wherein automatically modifying the second contact file with the changed common data includes notifying one of the multiplicity of users of the change.

10. The method of claim 9, wherein notifying one of the multiplicity of users of the change includes enabling the user to accept or reject the change to be made to the firm collection.

11. The method of claim 8, further including notifying one of the multiplicity of users of the change made to the first contact file common data for the particular contact within one of the user collections and enabling the user to accept or reject the corresponding change to be made to the second contact file of the firm collection.

12. The method of claim 8, wherein the change made to the first contact file common data for the particular contact within one of the user collections includes adding a new contact within one of the user collections.

14. The method of claim 8, wherein the one or more subsets of the plurality of second contact files includes one or more contact folders.