Method for translating computer data from one record structure to another
First Claim
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, the method comprising:
- using a previously established and stored field mapping;
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;
writing the translated information to a destination record having the destination record structure,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; and
translating the schedule data from a source database having the source record structure to a destination database having the destination record structure, wherein the translating further comprisesreading the schedule data from the source database, wherein the schedule data comprises at least one single appointment record and at least one repeating appointment record,translating the single appointment record in the source database into a single appointment record in the destination database, andtranslating the repeating appointment record in the source database into a plurality of single appointment records in the destination database.
4 Assignments
0 Petitions
Accused Products
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.
135 Citations
2 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, the method comprising:
-
using a previously established and stored field mapping; 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; writing the translated information to a destination record having the destination record structure, 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; and translating the schedule data from a source database having the source record structure to a destination database having the destination record structure, wherein the translating further comprises reading the schedule data from the source database, wherein the schedule data comprises at least one single appointment record and at least one repeating appointment record, translating the single appointment record in the source database into a single appointment record in the destination database, and translating the repeating appointment record in the source database into a plurality of single appointment records in the destination database. - View Dependent Claims (2)
-
Specification