# US 2012/0254260 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/0254260 A1
- Document ID: US20120254260A1
- Status: Published application
- Kind: A1
- Application number: 13/494,962
- 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/US20120254260A1

## 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 storing content in a database from a store, the store including content instances associated with store fields having a data store field type, the method including:
a) determining database fields into which content instances are to be stored in accordance with a mapping;
b) creating one or more vacant locations in a query in accordance with the database field type of the database field in which content instances are to be stored;
c) transferring each content instance from the store into a respective vacant location; and,
d) applying the query to the database to thereby transfer the content instance(s) to the database in accordance with the database field type.

### Claim 32 (depends on 31)

A method according to claim 31, the query being an SQL query.

### Claim 33 (depends on 31)

A method according to claim 31, wherein the method includes transferring content instances associated with a parent node and any associated child nodes into the database before transferring content instances associated with a next parent node.

### Claim 34 (depends on 31)

A method according to claim 31, wherein the method is for transferring content between a database and a mark-up language file, the method including:
a) determining a mapping between database fields and file fields at least partially in accordance with the document type definition; and,
b) transferring at least one content instance between a database field and a file field, via a store, in accordance with the mapping.

### Claim 35 (depends on 34)

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

### Claim 36 (depends on 34)

A method according to claim 34, 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 37 (depends on 34)

A method according to claim 34, wherein each content instance is stored as a respective node in a corresponding file field.

### Claim 38 (depends on 34)

A method according to claim 34, 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 39 (depends on 38)

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

### Claim 40 (depends on 38)

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

### Claim 41 (depends on 31)

A method according to claim 31, wherein the method is for transferring content between a database and files, the method including includes at least one of:
a) exporting content instances from a database to a plurality of files; and,
b) importing content instances from a plurality of tiles into a database.

### Claim 42 (depends on 41)

A method according to claim 41, wherein the method includes 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 43 (depends on 41)

A method according to claim 41, wherein the method includes storing the at least one content instance in a respective store for each of the plurality of files.

### 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 46)

A method according to claim 46, 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 database is at least one of:
a) a relational database; and,
b) a hierarchical database.

### Claim 50 (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 51 (depends on 31)

A method according to claim 31, wherein the method is for transferring content from a file to a database, the method including:
a) determining the type of each file field;
b) storing each content instance in a store in accordance with the field type of the associated file field; and,
c) transferring each content instance to the database in accordance with the determined field type.

### Claim 52 (depends on 51)

A method according to claim 51, wherein the method includes extracting content from the file by:
a) determining a mapping in accordance with a file type of the file;
b) creating a data store including store fields specified in the mapping;
c) retrieving at least one parent content instance corresponding to a next a parent node from the file;
d) storing the at least one parent content instance in a store field in the store in accordance with the file field type of the associated file field and the mapping;
e) retrieving at least one child content instance corresponding to a child node of the next parent node; and,
f) storing the at least one child content instance in a store field in the store in accordance with the file field type of the associated file field and the mapping.

### Claim 53 (depends on 51)

A method according to claim 51, wherein the method includes:
a) retrieving each parent and child content instance for a given parent node and any child node;
b) storing each parent and child content instance in a respective store field; and,
c) repeating steps a) and b) for each parent node.
