# US 2012/0254237 A1 · Content transfer

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2012/0254237 A1
- Document ID: US20120254237A1
- Status: Published application
- Kind: A1
- Application number: 13/494,966
- Filed: 2012-06-12
- Published: 2012-10-04
- Earliest claimed: 2001-07-18
- Assignees: Tralee Software Pty. Ltd.
- Inventors: Jonathon Peter Irons
- Web page: https://patentgrep.com/patent/US20120254237A1

## CPC

- G06F 16/258: {Data format conversion from or to a database}
- Y10S 707/99942: Manipulating data structure, e.g. compression, compaction, compilation
- Y10S 707/99953: Recoverability
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- Y10S: TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS

## Abstract

The present invention provides a method of transferring content from a file and a database. In this case, the file includes content instances, each content instance being associated with a respective field, and each field having a respective type. The transfer is achieved by determining the type of each field, and then storing each content instance in a store in accordance with the determined field type of the associated field. Each content instance can then be transferred to the database in accordance with the determined field type. A similar procedure is provided for creating XML files based on content within the database.

## Claims

### Claim at position 1

1-30. (canceled)

### Claim 31

A method of extracting content from a database, the database including content instances associated with database fields having a respective database field type, the method including:
a) creating a plurality of files, each file including file fields having a respective file field type;
b) retrieving at least one content instance from the database;
c) storing the at least one content instance in a store in accordance with the database field type of the associated database field;
d) transferring the at least one content instance into at least one file so that the content instance is associated with a file field of at least one of the files in accordance with the database field type of the associated database field.

### Claim 32 (depends on 31)

A method according to claim 31, wherein at least one of:
a) at least one processing system creates a number of files; and,
b) at least two processing systems generate respective files.

### Claim 33 (depends on 31)

A method according to claim 31, wherein at least one of:
a) each file contains respective content instances; and,
b) each content instance is stored in at least one file.

### Claim 34 (depends on 31)

A method according to claim 31, wherein the method includes storing content instances in a respective store for each of the plurality of files.

### Claim 35 (depends on 31)

A method according to claim 31, wherein the method includes:
a) in a first processing system, transferring at least one content instance from the database to a first file; and,
b) in a second processing system, transferring at least one content instance from the database to a second file.

### Claim 36 (depends on 31)

A method according to claim 31, wherein the method includes:
a) determining data relating database fields to corresponding file fields; and,
b) transferring at least one content instance between the database and the file, via the store, in accordance with the data.

### Claim 37 (depends on 36)

A method according to claim 36, wherein the file is a mark-up language file and the data includes a document type definition.

### Claim 38 (depends on 36)

A method according to claim 36, wherein the data includes a mapping.

### Claim 39 (depends on 38)

A method according to claim 38, wherein the mapping includes mapping rules defining how content instances should be transferred between the file and the database.

### Claim 40 (depends on 38)

A method according to claim 38, wherein the method includes determining the mapping in accordance with at least one of:
a) a document type definition defining file fields; and,
b) a database structure.

### Claim 41 (depends on 31)

A method according to claim 31, wherein content instances are transferred between the file and the database in accordance with mapping rules, and wherein the mapping rules define manipulations to be performed on content instances.

### Claim 42 (depends on 41)

A method according to claim 41, wherein the manipulations are performed as content instances are stored in the store.

### Claim 43 (depends on 41)

A method according to claim 41, wherein the manipulations include at least one of combining and splitting content instances.

### Claim 44 (depends on 31)

A method according to claim 31, wherein the method includes:
a) creating a store field associated with each content instance; and,
b) storing the content instance in the store field.

### Claim 45 (depends on 44)

A method according to claim 44, wherein the method includes creating the store field in accordance with at least one of:
a) a database field type;
b) a file field type; and,
c) data relating database fields to corresponding file fields.

### Claim 46 (depends on 31)

A method according to claim 31, wherein the method is for transferring content from a first database to a second database, the method including:
a) transferring at least one content instance from the first database to a file, via a store, in accordance with a first mapping; and,
b) transferring at least one content instance from the file to the second database, via a store, in accordance with a second mapping.

### Claim 47 (depends on 46)

A method according to claim 46, wherein the method includes:
a) transferring at least one content instance from the first database to a file using a first processing system;
b) transferring at least one content instance from the file to the second database using a second processing system.

### Claim 48 (depends on 47)

A method according to claim 47, wherein the first and second databases include respective first and second database fields for storing content instances, each database field having a respective field type, and wherein the method includes:
a) In a first processing system:
i) retrieving at least one content instance from the first database;
ii) storing the at least one content instance in a store in accordance with the database field type of the associated first database field;
iii) transferring the at least one content instance into a respective file field in accordance with the database field type of the first database field; and,
b) In a second processing system:
i) determining the type of each file field;
ii) storing each content instance in a store in accordance with the field type of the associated field; and,
iii) transferring each content instance to the second database in accordance with the determined field type.

### Claim 49 (depends on 31)

A method according to claim 31, wherein the method includes transferring at least one content instance between the store and the database using a respective query, the query being generated in accordance with the file field type and the database field type.

### Claim 50 (depends on 31)

A method according to claim 31, wherein the method includes extracting content instances from the database by:
a) creating the query including one or more vacant locations;
b) applying the query to the database to thereby transfer the at least one content instance into a respective vacant location; and,
c) transferring the at least one content instance to the store.

### Claim 51 (depends on 31)

A method according to claim 31, wherein the file is a mark-up language file, each content instance being stored as a respective node in a file field and the file field type of each file field being defined by a document type definition.

### Claim 52 (depends on 31)

A method according to claim 31, wherein the database is at least one of:
a) a relational database; and,
b) a hierarchical database.

### Claim 53 (depends on 31)

A method according to claim 31, wherein the method is performed at least in part using at least one of:
a) a processing system having a processor coupled to a store; and,
b) a specialised hardware processor.

### Claim 54

A method of importing content into a database, the database including database fields having a respective field type, and the method including, for each of a plurality of files:
a) retrieving at least one content instance from the file, the file including content instances associated with file fields having a respective file field type;
b) storing the at least one content instance in a store in accordance with the field type of the associated file field; and,
c) transferring the at least one content instance into the database so that the content instance is associated with a respective database field in accordance with the field type of the associated file field.

### Claim 55 (depends on 54)

A method according to claim 54, wherein the method includes receiving a plurality of files.

### Claim 56 (depends on 55)

A method according to claim 55, wherein each file is received by a respective processing system.

### Claim 57 (depends on 54)

A method according to claim 54, wherein at least one of:
a) each file contains respective content instances; and,
b) each content instance is stored in at least one file.

### Claim 58 (depends on 54)

A method according to claim 54, wherein the method includes storing content instances in a respective store for each of the plurality of files.

### Claim 59 (depends on 54)

A method according to claim 54, wherein the method includes:
a) in a first processing system, transferring at least one content instance from a first file to the database; and,
b) in a second processing system, transferring at least one content instance from a second file to the database.

### Claim 60 (depends on 54)

A method according to claim 54, wherein the method includes:
a) determining data relating database fields to corresponding file fields; and,
b) transferring at least one content instance between the database and the file, via the store, in accordance with the data.

### Claim 61 (depends on 60)

A method according to claim 60, wherein the data includes a mapping.

### Claim 62 (depends on 61)

A method according to claim 61, wherein the mapping includes mapping rules defining how content instances should be transferred between the file and the database.

### Claim 63 (depends on 61)

A method according to claim 61, wherein the file is a mark-up language file and the data includes a document type definition.

### Claim 64 (depends on 61)

A method according to claim 61, wherein the method includes determining the mapping in accordance with at least one of:
a) a document type definition defining file fields; and,
b) a database structure.

### Claim 65 (depends on 54)

A method according to claim 54, wherein content instances are transferred between the file and the database in accordance with mapping rules, and wherein the mapping rules define manipulations to be performed on content instances.

### Claim 66 (depends on 65)

A method according to claim 65, wherein the manipulations are performed as content instances are stored in the store.

### Claim 67 (depends on 65)

A method according to claim 65, wherein the manipulations include at least one of combining and splitting content instances.

### Claim 68 (depends on 54)

A method according to claim 54, wherein the method includes:
a) creating a store field associated with each content instance; and,
b) storing the content instance in the store field.

### Claim 69 (depends on 68)

A method according to claim 68, wherein the method includes creating the store field in accordance with at least one of:
a) a database field type;
b) a file field type; and,
c) data relating database fields to corresponding file fields.

### Claim 70 (depends on 54)

A method according to claim 54, wherein the method is for transferring content from a first database to a second database, the method including:
a) transferring at least one content instance from the first database to a file, via a store, in accordance with a first mapping; and,
b) transferring at least one content instance from the file to the second database, via a store, in accordance with a second mapping.

### Claim 71 (depends on 46)

A method according to claim 46, wherein the method includes:
a) transferring at least one content instance from the first database to a file using a first processing system;
b) transferring at least one content instance from the file to the second database using a second processing system.

### Claim 72 (depends on 47)

A method according to claim 47, wherein the first and second databases include respective first and second database fields for storing content instances, each database field having a respective field type, and wherein the method includes:
a) In a first processing system:
i) retrieving at least one content instance from the first database;
ii) storing the at least one content instance in a store in accordance with the database field type of the associated first database field;
iii) transferring the at least one content instance into a respective file field in accordance with the database field type of the first database field; and,
b) In a second processing system:
i) determining the type of each file field;
ii) storing each content instance in a store in accordance with the field type of the associated field; and,
iii) transferring each content instance to the second database in accordance with the determined field type.

### Claim 73 (depends on 54)

A method according to claim 54, wherein the method includes transferring at least one content instance between the store and the database using a respective query, the query being generated in accordance with the file field type and the database field type.

### Claim 74 (depends on 73)

A method according to claim 73, wherein the method includes importing content instances into the database by:
a) creating one or more vacant locations in the query in accordance with the field type;
b) transferring the at least one content instance into a respective vacant location; and,
c) applying the query to the database to thereby transfer the at least one content instance to the database.

### Claim 75 (depends on 54)

A method according to claim 54, wherein the file is a mark-up language file, each content instance being stored as a respective node in a file field and the file field type of each file field being defined by a document type definition.

### Claim 76 (depends on 54)

A method according to claim 54, wherein the database is at least one of:
a) a relational database; and,
b) a hierarchical database.

### Claim 77 (depends on 54)

A method according to claim 54, wherein the method is performed at least in part using at least one of:
a) a processing system having a processor coupled to a store; and,
b) a specialised hardware processor.
