US 6,496,835 B2Grant
Methods for mapping data fields from one data set to another in a data processing environment
Issue Date:2002-12-17
•20 Claims
•13 Drawing Sheets
Abstract
A rule-based methodology is described which supports automatic mapping of data fields between different data sets in a data processing environment. If a field cannot be mapped or matched based on name alone (e.g., an identical match), the methodology employs rules to determine a type for the field, based on the field's name. The determined type of the field is then used for matching. The methodology can be employed to match fields which appear dissimilar phonetically but are otherwise appropriate for matching. In the currently-preferred embodiment, rules are stated in form of: regular expression=type. Here, the regular expression member lists the text strings or substring(s) for the field. The rules are ordered in descending preference according to the likelihood that a given rule will correctly identify a field. In this mariner, the methodology allows the task of mapping fields from one data set to another to be entirely automated.
Metadata
Assignee
- Starfish Software, Inc.
Inventors
- Gwoho Liu
- Eric O. Bodnar
- Philippe R. Kahn
Application Information
Application Number:US 09/778,219
Filing Date:2001-02-06
Priority Date:1998-02-06
Art Unit:7
Classifications
IPC:
G06F 1730
Field of Search:
707102
Patent Drawings (13 sheets)
Description
[0002] This is a continuation of U.S. application Ser. No. 09/020,047, filed Feb. 6, 1998 now U.S. Pat. No. 6,216,131.
Background of the Invention
[0003] The present invention relates generally to the area of information processing and, more particularly, apparatus and methods for mapping or translating information from one data set to another.
[0004] Successful management of one's schedule and contacts is a goal that every successful professional must achieve. One's business day may be swept away in a deluge of meetings and appointments, all of which must be somehow managed. An attempt to manage this task on paper, such as with a simple wall calendar, is unworkable for all but the simplest of schedules. More likely, such unsophisticated aids to managing one's time will lead to scheduling conflicts, missed appointments, botched deadlines, and angry clients.
[0005] The first allies that professionals discovered were portable “organizers,” such as the Day Timer™ or the Lafax™. However, an increasing number are discovering the power of personal computers for managing appointments, contacts, and “to do” tasks. For instance, several scheduling packages are available for the PC. While not as portable as paper organizers, scheduling packages offer increased flexibility in other areas. For example, one may view his or her schedule from a variety of views—by month, week, day, or priority—and attach detailed notes to appointments. Additional options available include the ability to automatically schedule a meeting for the first Monday of every other month, or display horizontal bars which graphically represent one's weekly schedule, so that free time can be quickly pinpointed. Other options include the ability to easily edit an entry, and set alarms as a reminder of important appointments.
[0006] With ever increasing emphasis on miniaturization and portability, several of the features of personal information management (PIM) packages may now be found in handheld information processing devices, such as the Sharp Wizard™, REX™, Casio BOSS™, and Palm Pilot™. Being roughly the size of a handheld calculator, these electronic organizers are often carried when one is away from the office. As a tradeoff for portability, however, these devices typically forego several of the more desirable features found on desktop personal computers (e.g., full color graphics display). As a result, it is common for a professional to employ a personal computer to manage his or her time, yet carry a portable organizer when he or she is away from the office. Upon returning to the office, the information in the personal computer is then updated with the new information in the portable organizer.
[0007] Updating or reconciling two sets of information, whether between a PC and an organizer, or between two computers joined by a communication network, has never been easy. The reconciliation of user scheduling and contact information has been particularly difficult. A particular problem faced by a user of information management programs is the difficulty of translating or mapping data fields from one device to those of another. Consider, for instance, a user device having the following source data fields:
[0008] First Name
[0009] Last Name
[0010] Street Address 1
[0011] Street Address 2
[0012] City
[0013] State
[0014] Zip Code
[0015] Phone
[0016] FAX
[0017] Now, suppose the user also has a portable device with the following destination data fields:
[0018] First
[0019] Last
[0020] Home Address 1
[0021] Home Address 2
[0022] Home City
[0023] Home State
[0024] Home ZIP
[0025] Telephone
[0026] Telephone 2
[0027] As it can be seen, some of the fields are identical, others are somewhat similar, and finally still others are completely different.
[0028] A conventional approach to mapping fields between two devices is to display a user interface dialogue allowing the user to select pairs of fields. In such an approach, fields which are identical are already selected by the system, thereby leaving the user with some number of remaining fields to pair up. Such an approach works reasonably well if only a small number of fields are involved. Often, however, each set of data fields comprise a multitude of fields, hence making it very inconvenient for the user to manually match or pair up fields which are not identical, or at least very similar. A better approach is therefore desired.
[0029] What is needed is a system which allows a user of an information processing device to readily map or translate user information, such as user-supplied contact lists, from one data set on one device into another data set, either on the same device or on another device. The present invention fulfills this and other needs.
Summary of the Invention
[0030] Computers have found a variety of applications for the management of one's time, including tracking meetings and appointments. With increased availability of portable information processing devices, many of the scheduling features found on personal computers are now available with handheld electronic organizers. Because handheld organizers sacrifice features for portability, professionals will often manage their time at the office with a personal computer, reserving the portable for when they are away. Upon returning to the office, however, one must reconcile the information stored in the portable with that already present in the personal computer. Often, there is a need to translate or map data fields from one device to those of another.
[0031] According to the present invention, improved rule-based methodology in a data processing environment is provided supporting automatic matching of data fields between different data sets, thus allowing the task of mapping fields from one data set to another to be entirely automated. If a field cannot be matched based on name alone (e.g., an identical match), the methodology of the present invention employs rules to determine a type for the field, based on the field's name. The determined type of the field is then used for matching. In this manner, the methodology can be employed to match fields which appear dissimilar phonetically but are otherwise appropriate for matching.
[0032] In the currently-preferred embodiment, rules are stated in the form of:
[0033] regular expression=type
[0034] Here, the regular expression member lists the text strings or substring(s) for the field. To support substring matching, the regular expression may contain *, <, > and ? characters, where “*” matches any string, “<” and “>” match the beginning and ending of a word, respectively, and “?” matches any character, with matching being performed in a case insensitive manner. The type member consists of four or fewer characters (e.g., “name” for a name type), optionally preceded by a “−” character for indicating a “negative” type. A negative type indicates that the system should not map more than one field to a given field. The rules are ordered in descending preference according to the likelihood that a given rule will correctly identify a field. Alternatively, the rules may be ordered according to other desired criteria, or may be entirely unordered (i.e., a simple list).
[0035] A preferred user interface for mapping data fields from one device (e.g., desktop PC) to another (e.g., REX™ hand held device) is also provided. In accordance with the present invention, an exemplary system includes a TrueSync™ Wizard panel providing a “SmartMap”—that is, a mechanism whereby the system automatically detects and sets up mappings for each cardfile that the user selected to synchronize. By default, the system has already “smart mapped” the fields from source to destination. The user can override this mapping, as desired. If the user changes the default mappings and then want to restore them, he or she just clicks a SmartMap button. If preferred, the user can choose his or her own mappings by selecting a field in each column and clicking a Map button, or by clicking a field in the left column and then double-clicking a field in the right column to map it. To remove all mappings, the user clicks a Clear All Mappings button. To remove a particular field mapping, the user clicks a field in each column and then clicks an Unmap button.
[0036] After configuring the mapping, the user selects a Synchronize button, whereupon the system performs synchronization between two devices, according to the configuration information defined by the user. Data from source data fields is mapped according to the established mapping to corresponding data fields in the destination data set, with synchronization performed by the system.
Brief Description of the Drawings
[0037] FIG. 1 is a block diagram of a computer system in which the present invention may be embodied.
[0038] FIGS. 2A-C are bitmap screen shots illustrating a general desktop user interface for the personal information management system in which the present invention is embodied.
[0039] FIGS. 3A-G are bitmap screen shots illustrating a “wizard” user interface for configuring synchronization information in the system, wherein the interface includes a “smart mapping” wizard for automatically mapping data fields between source and destination data sets.
[0040] FIG. 4 is a bitmap screen shot illustrating a configuration table for configuring a plurality of devices such that the methodology of the present invention can be extended to map between any arbitrary number of devices.
[0041] FIG. 5 is a flow chart illustrating general methodology of the present invention for mapping data fields from one data set to another in a data processing system or environment.
Detailed Description
[0042] General System Hardware and Software
[0043] The present invention may be embodied on an information processing system such as the system 100 of FIG. 1 which comprises a central processor 101, a main memory 102, an I/O controller 103, a keyboard 104, a pointing device 105 (e.g., mouse), a screen or display device 106, a mass storage 107, (e.g., hard disk), a printing device 108, and an interface 109. The various components of the system 100 communicate through a system bus 110 or similar architecture. In addition, the system 100 may communicate with other devices through the interface or communication port 109, which may be an RS-232 serial port or the like. Devices which will be commonly connected to the interface 109 include a network 151 (e.g., LANS), a laptop 152, a handheld organizer 154 (e.g., REX™, available from Franklin Electronic Publishers of Burlington, N.J.), a modem 153, and the like.
[0044] In operation, program logic (implementing the methodology described below) is loaded from the storage device or mass storage 107 into the main memory 102, for execution by the processor 101. During operation of the program (logic), the user enters commands through the keyboard 104 and/or pointing device 105 which is typically a mouse, a track ball, or the like. The computer system displays text and/or graphic images and other data on the display device 106, such as a cathode-ray tube or an LCD display. A hard copy of the displayed information, or other information within the system 100, may be obtained from the printing device 108. In a preferred embodiment, the computer system 100 is an IBM PC-compatible personal computer (available from a variety of vendors, including IBM of Armonk, N.Y.) running Windows 9x or Windows NT (available from Microsoft Corporation of Redmond, Wash.).
[0045] In this interactive computer system, the user enters scheduling and other time information with the keyboard 104 and/or pointing device 105. Alternative sources of information are available through the interface 109. Once entered, the information is stored in the memory 102 where it may be analyzed by processor 101. After appropriate formatting, the information is conveyed to the user by the display device 106 and/or printing device 108. The information may be saved for future use by storing it to the mass storage 107.
[0046] As shown in FIG. 2A, the system 100 provides a window or work space 200 for display on the screen 106. Window 200 is a rectangular, graphical user interface for viewing and manipulating textual and graphical information. Window 200 contains a main menu 210 for invoking a plurality of submenus. From the submenus, the user may select a desired choice with the keyboard 104 or the pointing device 105.
[0047] Window 200 also includes a client area 220 for the display of time, scheduling, and contact information. Client area 220 may be partitioned into individual modules of information, such as the scheduling window 240, to-do list window 250, and calls window 260. Additional information may be viewed in the windows 240, 250, 260 by activating scroll bars 245, 255, 265, respectively. Window 200 also includes a plurality of other virtual work surfaces (e.g., such as the Weekly view) which are accessible by selecting an appropriate tab 270 with the keyboard or pointing device.
[0048] Within the window 240, a plurality of fields is available for the display of event or scheduling information. For example, field 242 is a text field for indicating the nature of the scheduling event. Field 241, on the other hand, lists the start time associated with the event. As shown, field 241 lists start time at a user-selected interval, e.g., thirty minutes; in addition, irregular start times (those not falling exactly on the defined intervals) are also accommodated. Additional screen indicia, such as screen icons, colors, or particular fonts, may be employed to convey additional information, such as the setting of an alarm for an event.
[0049] The interface 200 includes icons along one side, such as TrueSync icon 273 and Contacts icon 271. User selection of Contacts icon 271 invokes display of the Contacts work surface. As shown in FIG. 2B, the work surface includes pocketed index card view 280 and detail view 281. The detail view 281 displays data fields 283 for each card. Upon the user selecting a different card or information file, for example by selecting among tabs 290, the work surface displays a different cardfile 281ain FIG. 2C having a different set of data fields 283aas shown in FIG. 2C. User selection of the TrueSync icon 273 invokes a synchronization process. Since mapping occurs prior to actual synchronization of user data, the mapping methodology of the present invention can be employed with a variety of synchronization techniques. In an exemplary embodiment, TrueSync synchronization is employed. For a detailed description of TrueSync synchronization, see commonly-owned patent application Ser. No. 08/923,612, filed Sep. 4, 1997, the disclosure of which is hereby incorporated by reference.
[0050] Preferred User Interface
[0051] The following description will focus on interface and techniques for mapping fields among disparate data sets in an electronic personal information management system. The present invention is, however, not limited to such a specific application but, instead, may be applied advantageously to map or translate a variety of table or set-oriented information. Thus, the following is offered for purposes of illustration and not limitation.
[0052] FIGS. 3A-G illustrate a preferred user interface for mapping data fields from one device (e.g., desktop PC) to another (e.g., REX™ hand held device). As shown in FIG. 3A, the system presents an opening Wizard panel 300aasking the user to enter a user name. This is used for storing configuration information. The (REX) User Name is the identification associated with a specific REX card. One can add additional user names to the list for individuals sharing the same Information Manager to synchronize to their own REX cards. To add another user name, the user clicks the New button 301. To change a name, the user selects the user name and clicks the Rename button 303. To remove a user, the user selects the user name and clicks the Delete button 305.
[0053] Next, in FIG. 3B, the system presents a Wizard panel 300bfor selecting the Calendar and Contacts files the user wants to synchronize. The user can also synchronize To Do items and Calls. To synchronize calendar events, the user checks the Synchronize Calendar box 311. Single day, multi-day, special day, and recurring events will all be synchronized. To select the calendar file desired to be synchronized, the user employs the drop-down list 313. This list displays all user calendar files from the user's (REX) userdata folder. Thus, the user simply clicks the desired calendar file he or she wants to synchronize.
[0054] The Starting From date list 315 displays time period options from which to begin synchronization, such as: Today (from the beginning of the current day); This Month (from the beginning of the current month); and Last Week (from the beginning of last week). The current day on the user's computer is determined by the system date. The Through date list 317 gives the user time period options with which to end synchronization, such as: Next Week (through the end of the following week), and This Quarter (marked by January-March, April-June, July-September, October-December). The user's data will be synchronized through the end of the specified time period. To synchronize user To Do items and Calls, the user checks the Synchronize To Do List and Calls checkbox 319. Because To Do items and Calls are part of one's calendar in the Information Manager, they will be synchronized as a part of the Calendar file the user selected.
[0055] To synchronize Contacts information, the user checks the Synchronize Cardfiles box 312. To select the cardfile(s) the user wants to synchronize, he or she checks the box next to the desired cardfile(s) in the list 314, which displays all the cardfiles in one's REX userdata folder. To select a cardfile that is located in a different folder, the user clicks the accompanying Cardfiles Folder button, and selects the desired folder. The cardfiles contained in that folder will be added to the Select Cardfiles display list. The user can simply select the appropriate cardfile to synchronize.
[0056] To synchronize Memos and Preferences, the user proceeds to the Wizard panel 300c,shown in FIG. 3C, to specify the Memos and Preferences information desired to be synchronized. To synchronize one's memos, the user checks the Synchronize Memos box 321. To select the memo file the user wants to synchronize, the user clicks the desired memo file in the drop-down list 323. This list displays all the memo files in one's REX userdata folder. If the user wants to select a memo file located in another folder, he or she clicks the accompanying Memos Folder button and selects the desired folder. The memo files contained in that folder will be added to the Select Memo File drop-down list. The user can simply select the appropriate memo file to synchronize.
[0057] To synchronize the current preferences settings to the user's REX card, the user checks the Synchronize Preferences box 325. The user can use the drop-down list 327 for each setting to change individual preferences:
[0058] Date Display: Click the arrow and select the format desired for the date display.
[0059] Time Display: Click the arrow and select 12-hour or 24-hour for the time display.
[0060] Auto Shut-Off: Click the arrow and specify how long desired for the REX card to wait before shutting off automatically.
[0061] Alarm Sound: Click the arrow and specify whether a short alarm sound, a long alarm sound, or no alarm sound.
[0062] Key Click: Click the arrow and select whether the key click sound is on or off.
[0063] When the user selects the option to synchronize his or her cardfiles, the system will need to map cardfile fields to the fields on the user's REX card. In accordance with the present invention, the system includes a TrueSync Wizard panel 300d,shown in FIG. 3D, which provides a “SmartMap”—that is, a mechanism whereby the system automatically detects and sets up mappings for each cardfile that the user selected to synchronize. By default, the system has already “smart mapped” the fields from source to destination. The user can override this mapping, as desired. If the user changes the default mappings and then want to restore them, he or she just clicks the SmartMap button 333. If preferred, the user can choose his or her own mappings by selecting a field in each column and clicking the Map button 335, or by clicking a field in the left column and then double-clicking a field in the right column to map it. To remove all mappings, the user clicks Clear All Mappings 339. To remove a particular field mapping, the user clicks a field in each column and then clicks the Unmap button 337.
[0064] As shown, the system has smart mapped several fields from the source data set to the destination data set. For instance, the system has mapped “Last_Name” to “Last Name”. More importantly for the user, the system has also automatically mapped several fields which are not so similar, but are otherwise appropriate. For instance, the fields of “Address 1” and “Address 2” have been mapped into “Work Address” and “Suite/PO Box”, respectively. As shown in FIG. 3E for panel 300e,the system automatically mapped other fields to appropriate counterparts.
[0065] After the user is satisfied with the mapping, he or she proceeds to Wizard panel 300f,shown in FIG. 3F, to enter personal information that will help protect the user's REX card. Here, the user enters personal details 341, such as name, address and telephone number. The information serves as owner identification. These personal details are transferred to the REX card during synchronization. Drop-down list 343 is employed to select the location of the REX card for synchronization. By default, this is set to the PC card slot; alternatively, synchronization can be performed via a serial port.
[0066] After completion of configuration, the user proceeds to the next Wizard panel 300g,as shown in FIG. 3G. Upon the user selecting the Synchronize button 351, the system performs synchronization between the two devices, according to the configuration information defined by the user. Data from source data fields is mapped according to the established mapping to corresponding data fields in the destination data set, with synchronization performed by the system. Since the mapping occurs prior to actual synchronization of the data, the mapping methodology can be employed with a variety of synchronization techniques.
[0067] Internal Operation
[0068] According to the present invention, improved rule-based methodology is provided supporting automatic matching of data fields between different data sets, thus allowing the task of mapping fields from one data set to another to be entirely automated. If a field cannot be matched based on name alone (e.g., an identical match), the methodology of the present invention employs rules to determine a type for the field, based on the field's name. The determined type of the field is then used for matching. In this manner, the methodology can be employed to match fields which appear dissimilar phonetically but are otherwise appropriate for matching.
[0069] In the currently-preferred embodiment, rules are stated in the form of:
[0070] regular expression=type
[0071] Here, the regular expression member lists the text strings or substring(s) for the field. To support substring matching, the regular expression may contain *, <, >and ? characters, where “*” matches any string, “<” and “>” match beginning and end of word, respectively, and “?” matches any character, with matching being performed in a case insensitive manner. The type member consists of four or fewer characters (e.g., “name” for a name type), optionally preceeded by a character for indicating a “negative” type. A negative type indicates that the system should not map more than one field to given field. The rules are ordered in descending preference according to the likelihood that a given rule will correctly identify a field. This is perhaps best illustrated by way of example.
[0072] In a user data set from a personal information manager, the most likely type of data field is name—that is, a field type storing some sort of name information. In the system of the present invention, therefore, a first set of rules is established for mapping name-related fields, specifically the last name field and the first name field (if any). The rules are as follows.
[0073] last=−name
[0074] name=−name
[0075] *<last>*<name>*=−name
[0076] *<lastname>*=−name
[0077] first=−firs
[0078] *<first>*<name>*=−firs
[0079] *<firstname>*=−firs
[0080] Here, a field named “last”, “name”, or substring combinations thereof (i.e., rule of *<last>*<name>* or *<last name>*) is determined to be of type name. Since this type is a “negative” type, the system will not map this field more than one time. Similarly, a field named “first” or substring combinations of “first” and “name” (i.e., rule of *<first>*<name>* or *<firstname>*) is determined to be of type firs (i.e., “first name” type). Again, since this type is a “negative” type, the system will not map this field more than one time.
[0081] Next, a set of rules is established for mapping phone-related fields. These are divided into the following types of phones: home (i.e., home phone), main (i.e., main phone), and other (i.e., other phone). The rules are as follows.
[0082] *<home*phone>*=home
[0083] *<house*phone>*=home
[0084] *<personal*phone>*=home
[0085] *<private*phone>*=home
[0086] *<main*phone>*=main
[0087] *<primary*phone>*=main
[0088] *<work*phone>*=main
[0089] *<business*phone>*=main
[0090] *<other*phone>*=othe
[0091] *<assistant*phone>*=othe
[0092] *<altern*phone>*=othe
[0093] *2*<phone>*=othe
[0094] *3*<phone>*=othe
[0095] *<phone>*2*=othe *<phone>*3*=othe
[0096] As shown, any field having string or substring combinations of “home”, “house”, “personal”, or “private” with “phone”, will be determined to be of type home (i.e., home phone). In a like manner, any field having string or substring combinations of “main”, “primary”, “work”, or “business” with “phone”, will be determined to be of type main (i.e., main phone). Finally, other string or substring combinations with “phone” are determined to be of type othe (i.e., other phone), in the manner indicated above.
[0097] E-mail fields can be handled in a similar fashion by defining the following set of rules.
[0098] *<compuserv*=emai
[0099] *<m*<exchange>*=emai
[0100] *<eudora>*=emai
[0101] *<aol>*=emai
[0102] *<e*<mail>*=emai
[0103] *<net*<mail>*=emai
[0104] *<web>*<mail>*=emai
[0105] *<computer>*<mail>*=emai
[0106] *<pc>*<mail>*=emai
[0107] Note that the system of the present invention can match up a field entitled “CompuServe” (i.e., having the substring compuserv) as an e-mail field type (i.e., type=emai), despite the fact that the word “CompuServe” is phonetically unrelated to “e-mail”. In a similar manner, the system can match up other seemingly unrelated fields as e-mail fields, including AOL (rule: *<aol>*), Microsoft Exchange (rule: *<m*<exchange>*), and Eudora (rule: *<eudora>*), among others.
[0108] Perhaps the most troublesome data fields to handle are those involving address-type information. This is due to the seemingly endless number of ways that one can represent address information. Further complicating this process is the occurrence of separate home and work address information. The present invention defines a set of address rules as follows.
[0109] *<home>*<street>*2*=−had2
[0110] *<home>*<street>*<two>*=−had2
[0111] *<home>*<addr*2*=−had2
[0112] *<home>*<addr*<two>*=−had2
[0113] *<home>*<unit>*=−had2
[0114] *<home>*<po>*=−had2
[0115] *<home>*<p.o>*=−had2
[0116] *<home>*<p. o>*=−had2
[0117] *<home>*<p o>*=−had2
[0118] *<home>*<post*office>*=−had2
[0119] *<apt>*=−had2
[0120] *<apart *=−had2
[0121] *<home>*<street>*=−had1
[0122] *<home>*<addr*=−had1
[0123] *<home>*<town>*=−hcit
[0124] *<home>*<village>*=−hcit
[0125] *<home>*<city>*=−hcit
[0126] *<home>*<province>*=−hsta
[0127] *<home>*<district>*=−hsta
[0128] *<home>*<state>*=−hsta
[0129] *<home>*<zip*=−hzip
[0130] *<home>*<postal*=−hzip
[0131] *<home>*<country>*=−hcou
[0132] *<home>*<nation>*=−hcou
[0133] *<home>*<common*wealth>*=−hcou
[0134] *<home>*<territory>*=−hcou
[0135] #
[0136] *<street>*2*home>*=−had2
[0137] *<street>*<two>*<home>*=−had2
[0138] *<addr*2*<home>*=−had2
[0139] *<addr*<two>*<home>*=−had2
[0140] *<unit>*<home>*=−had2
[0141] *<po>*<home>*=−had2
[0142] *<p.o>*<home>*=−had2
[0143] *<p. o>*<home>*=−had2
[0144] *<p o>*<home>*=−had2
[0145] *<post*office>*<home>*=−had2
[0146] *<street>*<home>*=−had1
[0147] *<addr*<home>*=−had1
[0148] *<town>*<home>*=−hcit
[0149] *<village>*<home>*=−hcit
[0150] *<city>*<home>*=−hcit
[0151] *<province>*<home>*=−hsta
[0152] *<district>*<home>*=−hsta
[0153] *<state>*<home>*=−hsla
[0154] *<zip*<home>*=−hzip
[0155] *<postal*<home>*=−hzip
[0156] *<country>*<home>*=−hcou
[0157] *<nation>*<home>*=−hcou
[0158] *<common*wealth>*<home>*=−hcou
[0159] *<territory>*<home>*=−hcou
[0160] #
[0161] *<street>*2*=−wad2
[0162] *<street>*<two>*=−wad2
[0163] *<addr*2*=−wad2
[0164] *<addr*<two>*=−wad2
[0165] *<po>*=−wad2
[0166] *<p.o>*=−wad2
[0167] *<p. o>*=−wad2
[0168] *<p o>*=−wad2
[0169] *<post*office>*=−wad2
[0170] *<suite>*=−wad2
[0171] *<street>*=−wad1
[0172] *<department>*=−wad2
[0173] *<dept>*=−wad2
[0174] *<addr*=−wad1
[0175] *<unit>*=−wad1
[0176] *<town>*=−wcit
[0177] *<village>*=−wcit
[0178] *<city>*=−wcit
[0179] *<province>*=−wsta
[0180] *<district>*=−wsta
[0181] *<state>*=−wsta
[0182] *<zip*=−wzip
[0183] *<postal*=−wzip
[0184] *<country>*=−wcou
[0185] *<nation>*=−wcou
[0186] *<common*wealth>*=−wcou
[0187] *<territory>*=−wcou
[0188] As shown, addressing information is divided into “home” and “work” types. Within those types, subtypes appear, such as a home city (hcit), home state (hsta), and home zip code (hzip). In this manner, the system can appropriately map address information into home and/or work address fields on a target device.
[0189] Although the foregoing example has focused on the currently preferred embodiment of mapping between multiple devices (e.g., PIMs running on PCs) to a single device (e.g., REX device), the methodology of the present invention can be modified to map between any arbitrary number of devices. This is illustrated by table 400 in FIG. 4. As shown, the table includes field mapping rules for three separate devices. Here, any device in the table can map to any other device in the table. The approach works better when synchronizing data between a number of PIMs, but provides less specificity for mapping data fields to a specific device. In an embodiment targeting mapping to a single device, therefore, the linear or single mapping approach (previously described) is preferred.
[0190] Referring to FIG. 5, flow chart 500 summarizes the overall methodology of the present invention for mapping data fields from one data set to another in a data processing system or environment. At step 501, a rule format is defined comprising a plurality of field types, where each type is associated with one or more string or substring expressions. At step 502, certain types are specified as “negative types” for indicating that the system should not map more than one field for the given type. At step 503, the rules are ordered in descending preference according to the likelihood that a given rule will correctly identify a field. Alternatively, the rules may be ordered according to other desired criteria, or may be entirely unordered (i.e., a simple list). At step 504, a source data set comprising a plurality of data fields is received. At step 505, the source data fields are “smart” mapped to destination data fields by determining a field type for each source data field, based on application of the rules in descending order. At step 506, the system can (optionally) receive user input for changing the mapping. Finally, at step 507, the system performs synchronization, such that values from source data fields are synchronized with field values from corresponding destination data fields (which have been previously mapped).
[0191] Source Code Implementation
[0192] Appended herewith as Appendix A is a source code listing illustrating program logic for matching expressions in accordance with the present invention. A suitable C/C++ compiler for compiling the source code is available from a variety of vendors, including Microsoft of Redmond, Wash. and Borland International of Scotts Valley, Calif. Appended herewith as Appendix B is a data file illustrating expressions for mapping fields in an exemplary embodiment in which data fields are mapped for synchronizing from a (number of) PIM(s) to a fixed PIM, such as the REX™ PC Companion.
[0193] While the invention is described in some detail with specific reference to a single preferred embodiment and certain alternatives, there is no intent to limit the invention to that particular embodiment or those specific alternatives. For example, those skilled in the art, enabled by the teachings of the present invention, will understand that the list of rules may be ordered according to other criteria, or may be entirely unordered. The true scope of the invention is defined not by the foregoing description but by the appended claims.
| APPENDIX A |
|---|
| // match_expression( ) |
| // a is a (non standard) regular expression with the following special |
| // symbols: |
| // < and > match start and end of word. |
| // * matchs anything. |
| // ? matches any single character. |
| // = indicates end of expression. Stuff after = is what we return. |
| // |
| // We check if b matches pattern a. If it does, return stuff after the =. |
| // Otherwise return zero. |
| // |
| // This routine assumes ASCII. |
| static int |
| match_expression_helper(const char *a,const char *b) |
| { |
| int i,j; |
| for (; *a!=‘=’; a++) { |
| // Check for line without an =. |
| if (*a == 0) |
| return 0; |
| if (*a == ‘*’) { |
| a++; |
| // This could get ugly with exponential branching, but mostly it shouldn't. |
| // Just don't put something like ‘a***********************b’ into the file. |
| while ((i=match_expression_helper(a,b)) == 0) |
| if (*b++ == 0) |
| break; |
| return i; |
| } |
| if (*a == ‘<’) { |
| if (b[−1]>=‘a’ && b[−1]<=‘z’) |
| return 0; |
| continue; |
| } |
| if (*a == ‘>’) { |
| if (*b>=‘a’ && *b<=‘z’) |
| return 0; |
| continue; |
| } |
| if (*a == ‘?’) { |
| if (*b++) |
| continue; |
| return 0; |
| } |
| if (*a == *b++) |
| continue; |
| return 0; |
| } |
| if (*b) |
| return 0; |
| // We suck off minus sign. |
| j = *++a==‘−’; |
| a += j; |
| // We encode the after the ‘=’ in an int. |
| for (i=0; *a; a++) |
| i = i<<8|*a&0x7f; |
| return j ? −i : i; |
| } |
| static int |
| match_expression(const char *a,const char *b) |
| { |
| char *d = (char *)_alloca(strlen(b)+2),*dd = d; |
| // convert case and prepend b with ‘ ’. |
| for (*dd++=‘ ’; *dd=*b++; dd++) |
| if (*dd>=‘A’ && *dd<=‘Z’) |
| *dd += ‘a’−‘A’; |
| return match_expression_helper(a,d+1); |
| } |
| // a is CString containing the name of a field (either on BCO or SK). |
| // We read the file which contains rules to determine the |
| // type of a. |
| static struct l { |
| struct l *n; |
| char *s; |
| } *l_root = NULL; |
| static l_root_initialized = 0; |
| static void |
| init_find_type_of_cstring( ) |
| { |
| FILE *f; |
| char l[1000],*t; |
| HKEY hRegKey; |
| char szBuffer[MAX_PATH]; |
| struct l *m, **mm; |
| int i; |
| if ((hRegKey=Reg_Open(NULL)) == NULL) |
| return; |
| i=Reg_ReadString(hRegKey, REGKEY_INSTALLDIRECTORY,szBuffer,MAX_PATH-20); |
| Reg_Close(hRegKey); |
| if (!i) |
| return; |
| t = szBuffer+strlen(szBuffer); |
| if (t > szBuffer) |
| if (t[−1] != ‘\\’) { |
| *t++ = ‘\\’; |
| *t = 0; |
| } |
| strcpy(t,FIELDSRULES_FILENAME); |
| if ((f=fopen(szBuffer,“r”)) == NULL) |
| return; |
| mm = &l_root; |
| while (fgets(l,1000,f)) { |
| if (1[0]== ‘#’) |
| continue; |
| for (t=1; *t; t++) |
| if (*t>=‘A’ && *t<=‘Z’) |
| *t += ‘a’−‘A’; |
| else if (*t==‘\n’ || *t ==‘\r’) { |
| *t = 0; |
| break; |
| } |
| m = (struct l *)malloc(sizeof(struct l)); |
| memset (m,0,sizeof(struct l) |
| *mm = m; |
| mm = &m−>n; |
| m−>s = strcpy((char *)malloc(strlen(l)+1),l); |
| } |
| fclose(f); |
| } |
| static int |
| find_type_of_cstring(CString &s) |
| { |
| int i; |
| struct l *l; |
| if (!l_root_initialized) |
| l_root_initialized = 1; |
| init_find_type_of_cstring( ); |
| } |
| for (l=l_root; l; l=l−>n) |
| if (i = match_expression(l−>s,s)) |
| return i; |
| return 0; |
| } |
| APPENDIX B |
|---|
| # A line starting with # is a comment. |
| # |
| # This file contains rules to determine type of a field based on its |
| # name. The type of a field is used to match fields. |
| # |
| # We match lines with lines in this file to deterine type. |
| # Lines are of the form (regular expression)=(type). |
| # Type consists of 4 or fewer characters, optionally preceeded by a ‘−’. |
| # |
| # Negative type indicates that we should not map more than one field to |
| # given field. |
| # |
| # Regular expressions may contain ‘*’, ‘<’, ‘>’ and ‘?’. |
| # ‘*’ matches any string. ‘<’ and ‘>’ match beginning and end of word. |
| # ‘?’ matches any character. |
| # |
| # The order of the following lines is important. |
| # |
| # First, things we are almost absolutely sure about. |
| last=-name |
| name=-name |
| *<last>*<name>*=-name |
| *<lastname>*=-name |
| *first=-firs |
| *<first>*<name>*=-firs |
| *<firstname>*=-firs |
| # |
| *<home*phone>*=home |
| *<house*phone>*=home |
| *<personal*phone>*=home |
| *<private*phone>*=home |
| *<main*phone>*=main |
| *<primary*phone>*=main |
| # |
| *<other*phone>*=othe |
| *<assistant*phone>*=othe |
| *<altern*phone>*=othe |
| *2*<phone>*=othe |
| *3*<phone>*=othe |
| *<phone>*2*=othe |
| *<phone>*3*=othe |
| # |
| *<company*name>*=-comp |
| # |
| *<home>*<page>*=www |
| *<homepage>*=www |
| # |
| *<email>*=emai |
| *<e-mail>*=emai |
| *<inter*<mail>*=emai |
| # |
| *<assist*<title>*= |
| *<asst*<title>*= |
| *<assist*<name>*= |
| *<asst*<name>*= |
| *<office>*<location>*= |
| *<alt>*<phone>*=othe |
| *<altern*<phone>*=othe |
| *<asst>*<phone>*=othe |
| *<assistant>*<phone>*=othe |
| *<tty>*<phone>*=othe |
| # |
| #Second, things that are not so clear. |
| # |
| *<compuserv*=emai |
| *<m*<exchange>*=emai |
| *<eudora>*=email |
| *<aol>*=emai |
| *<e*<mail>*=emai |
| *<net*<mail>*=emai |
| *<web>*<mail>*=emai |
| *<computer>*<mail>*=emai |
| *<pc>*<mail>*=emai |
| # |
| *<home>*<street>*2*=-had2 |
| *<home>*<street>*<two>*=-had2 |
| *<home>*<addr*2*=-had2 |
| *<home>*<addr*<two>*=-had2 |
| *<home>*<unit>*=-had2 |
| *<home>*<po>*=-had2 |
| *<home>*<p.o>*=-had2 |
| *<home>*<p. o>*=-had2 |
| *<home>*<p o>*=-had2 |
| *<home>*<post*office>*=-had2 |
| *<apt>*=-had2 |
| *<apart*=-had2 |
| *<home>*<street>*=-had1 |
| *<home>*<addr*=-had1 |
| *<home>*<town>*=-hcit |
| *<home>*<village>*=-hcit |
| *<home>*<city>*=-hcit |
| *<home>*<province>*=-hsta |
| *<home>*<district>*=-hsta |
| *<home>*<state>*=-hsta |
| *<home>*<zip*=hzip |
| *<home>*<postal*=-hzip |
| *<home>*<country>*=-hcou |
| *<home>*<nation>*=-hcou |
| *<home>*<common*wealth>*=-hcou |
| *<home>*<territory>*=-hcou |
| # |
| *<street>*2*<home>*=-had2 |
| *<street>*<two>*<home>*=-had2 |
| *<addr*2*<home>*=-had2 |
| *<addr*<two>*<home>*=-had2 |
| *<unit>*<home>*=-had2 |
| *<po>*<home>*=-had2 |
| *<p.o>*<home>*=-had2 |
| *<p. o>*<home>*=-had2 |
| *<p o>*<home>*=-had2 |
| *<post*office>*<home>*=-had |
| *<street>*<home>*=-had1 |
| *<addr*<home>*=-had1 |
| *<town>*<home>*=-hcit |
| *<village>*<home>*=-hcjt |
| *<city>*<home>*=-hcit |
| *<province>*<home>*=-hgta |
| *<district>*<home>*=-hsta |
| *<state>*<home>*=-hsta |
| *<zip*<home>*=-hzip |
| *<postal*<home>*=-hzip |
| *<country>*<home>*=-hcou |
| *<nation>*<home>*=-hcou |
| *<common*wealth>*<home>*=-hcou |
| *<territory>*<home>*=-hcou |
| # |
| *<street>*2*=-wad2 |
| *<street>*<two>*=-wad2 |
| *<addr* 2 * =-wad2 |
| *<addr*<two>*=-wad2 |
| *<po>*=-wad2 |
| *<p.o>*=-wad2 |
| *<p. o>*=-wad2 |
| *<p o>*=-wad2 |
| *<post*office>*=-wad2 |
| *<suite>*=-wad2 |
| *<street>*=-wad1 |
| *<department>*=-wad2 |
| *<dept>*=-wad2 |
| *<addr*=-wad1 |
| *<unit>*=-wad1 |
| *<town>*=-wcit |
| *<village>*=-wcit |
| *<city>*=-wcit |
| *<province>*=-wgta |
| *<state>*-wsta |
| *<zip*=-wZip |
| *<postal*=-wzip |
| *<country>*=-wcou |
| *<nation>*=-wcou |
| *<common*wealth>*=-wcou |
| *<territory>*=-wcou |
| # |
| *<home>*<fax>*=hfax |
| *<personal>*<fax>*=hfax |
| *<private>*<fax>*=hfax |
| *<home>*<facsimile>*=hfax |
| *<personal>*<facsimile>*=hfax |
| *<private>*<facsimile>*=hfax |
| *<fax>*=fax |
| *<facsimile>*=fax |
| # |
| *<cell>*=mobi |
| *<mobile>*=mobi |
| *<cellular>*=mobi |
| *<portable>*=mobi |
| *<qsm>*=mobi |
| *<pcs>*=mobi |
| *<radio>*=mobi |
| *<call*sign>*=mobi |
| # |
| *<car>*car |
| *<auto>*=car |
| *<automo*=car |
| # |
| *<www>*=www |
| *<ftp>*=www |
| *<http>*=www |
| *<web>*=www |
| *<url>*=www |
| #*<inter*net>*=www |
| *<inter*net>*=email |
| # |
| *<pager>*=page |
| *<page>*=page |
| *<beep>*=page |
| *<alpha>*=page |
| *<sms>*=page |
| *<beeper>*=page |
| # |
| *<title>*=titl |
| *<alias>*=titl |
| *<position>*=titl |
| *<occupation>*=titl |
| *<profession>*=titl |
| *<vocation>*=titl |
| *<job>*=titl |
| # |
| *<toll*free>*=othe |
| # |
| # Next, Wild guesses. |
| # |
| *<other>*=othe |
| *<data>*=othe |
| *<modem>*=othe |
| *<isdn>*=othe |
| *<alt>*=othe |
| *<altern*=othe |
| *<service>*=othe |
| *<custom>*=othe |
| # |
| *<comment>*=note |
| *<account>*=note |
| *<acct>*=note |
| *<birthday>*=note |
| *<birth>*=note |
| *<hobby>*=note |
| *<hobbies>*=note |
| *<kids>*=note |
| *<children>*=note |
| *<child>*=note |
| *<friends>*=note |
| *<friend>*=note |
| *<spouse>*=note |
| *<dob>*=note |
| *<log>*=note |
| *<misc*=note |
| *<notes>*=note |
| *<directions>*=note |
| *<discussion>*=note |
| *<conversation>*=note |
| *<note>*=note |
| *<reminder>*=note |
| # |
| # Next, wild guesses with adjectives. |
| # |
| *<direct*line>*=work |
| *<office*phone>*=main |
| *<work>*=work |
| *<office>*=work |
| *<ext>*=work |
| *<extension>*=work |
| *<business>*=work |
| *<home>*=home |
| *<house>*=home |
| *<personal>*=home |
| *<private>*=home |
| *<phone>*=main |
| *<main>*=main |
| *<first>*=-firs |
| # |
| *<corporation>*=-comp |
| *<company>*=-comp |
| *<university>*=-comp |
| *<college>*=-comp |
| *<institution>*=-comp |
| *<organizatian>*=-comp |
| *<employer>*=-comp |
| *<association>*=-comp |
| *<group>*=-comp |
| *<society>*=-comp |
| *<league>*=-comp |
| *<club>*=-comp |
| *<guild>*=-comp |
| *<school>*=-comp |
Claims
What is claimed is:
1. In an electronic apparatus, a method of mapping a first data field of a first data set with a data field of a second data set, the method comprising the steps of:
defining a plurality of field types for commonly used types of data fields;
associating one or more text substrings with each of said field types;
searching for said text substrings in a name for said first data field;
assigning a first field type to said first data field, based on the text substrings, if any, that are contained in said name for said first data field; and
automatically mapping said first data field to a second data field of the second data set that also has said first field type, without requiring user intervention.
2. The method of claim 1, wherein the searching for said text substrings is performed according to a set of rules.
3. The method of claim 2, wherein said rules are ordered in descending preference, according to how likely a given rule will correctly identify a field.
4. The method of claim 2, wherein each rule is stored in the system in the form of:
wherein said regular expression comprises at least one text substring describing a particular field.
regular expression=type
5. The method of claim 4, wherein said at least one text substring includes wild card characters for matching text strings having unknown characters.
6. The method of claim 5, wherein said wild card characters comprise *, <, > and ? characters, where “*” matches any string, “<” and “>” match the beginning and ending of a word, respectively, and “?” matches any character.
7. The method of claim 5, wherein matching occurs in a case insensitive fashion.
8. The method of claim 1, wherein said plurality of field types includes at least one negative field type, for indicating that no more than one data field of the first data set should be mapped for the particular field type.
9. The method of claim 1, further comprising the step of:
receiving input for changing mapping of said first data field from said second data field.
10. The method of claim 1, further comprising the step of:
displaying a dialogue indicating that said first data field is mapped to said second data field.
11. The method of claim 10, further comprising the steps of:
receiving at the dialogue user input for changing mapping of the first data field from the second data field; and
in response to said user input, updating display of the dialogue for showing the user-specified mapping.
12. The method of claim 1, wherein the first and second data sets contain PIM data.
13. A synchronizing apparatus for synchronizing a first data field of a first data set with a data field of a second data set, the apparatus comprising:
means for defining a plurality of field types for commonly used types of data fields;
means for associating one or more text substrings with each of said field types;
means for searching for said text substrings in a name for said first data field;
means for assigning a first field type to said first data field, based on the text substrings, if any, that are contained in said name for said first data field;
means for automatically mapping said first data field to a second data field of the second data set that also has said first field type, without requiring user intervention; and
means for synchronizing said first data field of said first data set with said second data field of said second data set.
14. The apparatus of claim 13, wherein the searching for said text substrings is performed according to a set of rules that are ordered in descending preference, according to how likely a given rule will correctly identify a field.
15. The apparatus of claim 14, wherein each rule is stored in the system in the form of:
wherein said regular expression comprises at least one text substring describing a particular field.
regular expression=type
16. The apparatus of claim 15, wherein said at least one text substring includes wild card characters for matching text strings having unknown characters.
17. The apparatus of claim 16, wherein said wild card characters comprise *, <, > and ? characters, where “*” matches any string, “<” and “>” match the beginning and ending of a word, respectively, and “?” matches any character.
18. The apparatus of claim 16, wherein matching occurs in a case insensitive fashion.
19. The apparatus of claim 13, wherein said plurality of field types includes at least one negative field type, for indicating that the apparatus should not map more than one data field of the first data set for the particular field type.
20. The apparatus of claim 13, further comprising:
means for displaying a dialogue indicating that said first data field is mapped to said second data field;
means for receiving at the dialogue user input for changing mapping of the first data field from the second data field; and
means for updating display of the dialogue for showing the user-specified mapping, in response to said user input.
Patent Citations (17)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US5111398(A) | 1992-05-01 | Numberg et al. | Examiner |
| US5491796(A) | 1996-02-01 | Wanderer et al. | Examiner |
| US5519606(A) | 1996-05-01 | Frid-Nielsen et al. | Examiner |
| US5526477(A) | 1996-06-01 | McConnell et al. | Examiner |
| US5602963(A) | 1997-02-01 | Bissonnette et al. | Examiner |
| US5768578(A) | 1998-06-01 | Kirk et al. | Examiner |
| US5802533(A) | 1998-09-01 | Walker | Examiner |
| US5835667(A) | 1998-11-01 | Wactlar et al. | Examiner |
| US5873108(A) | 1999-02-01 | Goyal et al. | Examiner |
| US5970490(A) | 1999-10-01 | Morgenstern | Examiner |
| US6006242(A) | 1999-12-01 | Poole et al. | Examiner |
| US6032111(A) | 2000-02-01 | Mohri | Examiner |
| US6049796(A) | 2000-04-01 | Siitonen et al. | Examiner |
| US6102969(A) | 2000-08-01 | Christianson et al. | Examiner |
| US6199068(B1) | 2001-03-01 | Carpenter | Examiner |
| US6216131(B1) | 2001-04-01 | Liu et al. | Examiner |
| US6279017(B1) | 2001-08-01 | Walker | Examiner |