Method for mapping, translating, and dynamically reconciling data between disparate computer platforms

• US 5,701,423 A
• Filed: 04/07/1994
• Issued: 12/23/1997
• Est. Priority Date: 04/10/1992
• Status: Expired due to Term

• Current Assignee: Intellisync Corporation (Nokia Corporation)
• Original Assignee: Puma Technology Inc.
• Inventors: Crozier, Keith
• Primary Examiner(s): Amsbury, Wayne
• Assistant Examiner(s): Alam, Hosain T.
• Application Number:
  US08/224,329
• Time in Patent Office: 1,356 Days
• Field of Search: 395/600, 395/161, 395/159, 395/500, 395/650, 395/200, 395/611, 395/612, 395/613, 395/335, 395/766, 395/228-242, 395/200.01, 395/200.19, 395/200.16, 364/DIG. 1
• US Class Current: 715/762
• CPC Class Codes: G06F 15/0208 for combination with other devices having a different main function, e.g. watches, pens
• CPC Class Codes: G06F 15/0266 for time management, e.g. calendars, diaries
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• CPC Class Codes: G06Q 10/087 Inventory or stock management, e.g. order filling, procurement or balancing against orders
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 20/203 Inventory monitoring
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing
• CPC Class Codes: Y10S 707/99948 Application of database or data structure, e.g. distributed, multimedia, or image
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99954 Version management
• CPC Class Codes: Y10S 715/963 Calendar or scheduling
• CPC Class Codes: Y10S 715/971 Cooperative decision support systems for group of users

Abstract

Traditionally, it has been difficult to share data among diverse computer applications and platforms because of underlying differences in data formats. Although the meaning or purpose of the data may be similar or identical (for example, two appointments entered using separate computer applications), the differences in data formats required by the various computer applications and platforms renders such sharing difficult. A method is disclosed for the translation of dissimilarly-formatted data between disparate computer applications and platforms. The method also provides for the dynamic reconciliation of conflicts in the data (for example, two appointments scheduled at the same time) based on both the content of the data and on specific preferences indicated by the user of the translation facility. First, the data is translated to a common format based on the user-specified mapping of data fields (identifying handheld and desktop fields to be translated) and considering the characteristics of the handheld or desktop computer application. Then, if the specific data item (such as an appointment, telephone book entry, or memo entry) already exists on the desktop computer application or platform, the user is optionally notified of the conflict and given the opportunity to replace the existing data, ignore the incoming data, or modify the incoming data. The criteria for determining the existence of conflicts is disclosed for updating schedule information and keyed databases.

Claims

1. A computer implemented method for translating computer data from a source record structure, in which information in a source file is arranged, to a destination record structure different from said source record structure, each of said source and destination record structures comprising a plurality of fields, each having a name, the method comprising

(a) presenting the names of the fields of each of said source and destination record structures on a display

(b) allowing a user to interactively select a field from said source record structure and a corresponding field from said destination record structure, thereby establishing a mapping between said fields, and

(c) translating the information of the source file, which is arranged in said source record structure, into a form compatible with said destination record structure in accordance with said mapping,

wherein said destination record structure differs from said source record structure in at least one of the following ways:

(a) field name, or

(b) field order, or

(c) one-to-many or many-to-one field correspondence, wherein said source file exists on a first computer and said destination record structure is specified by a program for execution on a second computer.

2. The method of claim 1 wherein said selecting comprises said user clicking a pointer device on a displayed name of a source field of said source record structure and clicking said pointer device on a displayed name of a destination field of said destination record structure, thereby establishing a mapping between said source field and said destination field.

3. The method of claim 2 wherein said mapping between said source field and said destination field is displayed on said display.

4. The method of claim 3 wherein said displaying of said mapping comprises displaying the name of said destination field adjacent to the name of said source field.

5. The method of claim 1 wherein said field names are acquired by a first program for said presenting by examining a second program, the second program comprising an application that operates on files having at least one of said source and destination record structures.

6. The method of claim 5 wherein said examination is performed by an inter-application communication facility.

7. The method of claim 1 wherein said field names are acquired by a program for said presenting by examining data dictionary records in a file.

8. The method of claim 1 wherein said field names are acquired by a program for said presenting from a description of one of said record structures which is hard-coded into the program for said presenting.

9. The method of claim 1 wherein said field names for said source and destination record structures are acquired by a program for said presenting by techniques chosen from the list comprising:

(a) examining a program that operates on files having at least one of said source and destination record structures,

(b) examining data dictionary records stored in a file, or

(c) hard-coding a description of said record structure into a program for said establishing,

the method further comprising determining, for each of said source and destination record structures, which of said techniques to use for said acquiring.

10. The method of claim 1, wherein said mapping comprises mapping a source field of said source record structure to a destination field of said destination record structure, said destination field being of a different data format from the data format of said source field, and wherein said translating comprises data format conversion.

11. The method of claim 1 wherein said mapping comprises mapping one field of said source record structure to more than one field of said destination record structure.

12. The method of claim 1 wherein said mapping comprises mapping more than one field of said source record structure to one field of said destination record structure.

13. The method of claim 1, wherein a destination file of said destination record structure exists, further comprising the steps of

comparing the translated information of said source file to the information of said destination file.

14. The method of claim 13 further comprising

establishing a correspondence between records of said source file and records of said destination file, said correspondence based on comparisons of keys of said records,

performing said translating on the information of each said record of said source file, thereby producing a translated record, and

allowing a user, immediately after each said comparison in which a difference is discovered, to interactively select either said translated record or the corresponding records of said destination file, or both, or neither, and

writing said selected records to an output file.

15. The method of claim 1, wherein said translating proceeds in two phases, the first phase being a translation from said source record structure to a common intermediate record structure, and the second phase being a translation from said common intermediate record structure to said destination record structure.