# US 9,646,013 B2 · System and method for file management

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

- Number: US 9,646,013 B2
- Document ID: US9646013B2
- Status: Granted
- Kind: B2
- Application number: 13/471,440
- Filed: 2012-05-14
- Published: 2012-09-06
- Granted: 2017-05-09
- Earliest claimed: 2011-02-16
- Assignees: Docbert, LLC
- Applicants: Paul Stuart Swengler
- Inventors: Paul Stuart Swengler
- Web page: https://patentgrep.com/patent/US9646013B2

## CPC

- G06F 16/13: File access structures, e.g. distributed indices (arrangements of input from, or output to, record carriers G06F3/06)
- G06F 16/168: {Details of user interfaces specifically adapted to file systems, e.g. browsing and visualisation, 2d or 3d GUIs (query results presentation G06F16/156)}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Embodiments of the invention provide, among other things, an improved system and method for building logical associations (links) between files and for assigning attributes to the files and/or links. In embodiments of the invention, such attribute data is indexed in a data store according to Universally Unique Identifiers (UUIDs) in each file header.

## Claims

### Claim 1

A specially-configured computer comprising a processor and a file management system, the file management system configured to perform a file copying process, the file copying process including the steps of:
reading a first Universally Unique Identifier (UUID) in a header of a parent file, the parent file being an original file, the header of the parent file being a portion of the parent file;
generating a second UUID;
writing the second UUID to a header of a child file, the child file being a copy of the original file, the header of the child file being a portion of the child file; and
forming a lineage record in at least one of the header of the child file and the header of the parent file, the lineage record associating the first UUID and the second UUID, the lineage record thus associating the parent file and the child file without reference to a filename of the parent file or a filename of the child file.

### Claim 2 (depends on 1)

The specially-configured computer of claim 1, wherein forming the lineage record includes writing the first UUID to the header of the child file.

### Claim 3 (depends on 2)

The specially-configured computer of claim 2, wherein forming the lineage record further includes:
reading Operating System (OS) data from the header of the parent file; and
writing the OS data to the header of the child file.

### Claim 4 (depends on 1)

The specially-configured computer of claim 1, wherein forming the lineage record includes writing the second UUID to the header of the parent file.

### Claim 5 (depends on 4)

The specially-configured computer of claim 4, wherein forming the lineage record further includes:
reading Operating System (OS) data from the header of the child file; and
writing the OS data to the header of the parent file.

### Claim 6 (depends on 1)

The specially-configured computer of claim 1, the copying process further including the step of associating non-lineage attribute data of the parent file with the child file.

### Claim 7 (depends on 6)

The specially-configured computer of claim 6, wherein associating non-lineage attribute data includes copying non-lineage attribute data from the header of the parent file to the header of the child file.

### Claim 8 (depends on 1)

The specially-configured computer of claim 1, the copying process further including the step of associating non-lineage attribute data of the child file with the parent file.

### Claim 9 (depends on 8)

The specially-configured computer of claim 8, wherein associating non-lineage attribute data includes copying non-lineage attribute data from the header of the child file to the header of the parent file.

### Claim 10 (depends on 6)

The specially-configured computer of claim 6, wherein the non-lineage attribute data includes a label relating to a subject matter classification.

### Claim 11 (depends on 6)

The specially-configured computer of claim 6, wherein the non-lineage attribute data includes a tag relating to one of a planned action and a use restriction.

### Claim 12 (depends on 6)

The specially-configured computer of claim 6, wherein the non-lineage attribute data includes reference to a linked file, the linked file not being associated with lineage.

### Claim 13 (depends on 8)

The specially-configured computer of claim 8, wherein the non-lineage attribute data includes a label relating to a subject matter classification.

### Claim 14 (depends on 8)

The specially-configured computer of claim 8, wherein the non-lineage attribute data includes a tag relating to one of a planned action and a use restriction.

### Claim 15 (depends on 8)

The specially-configured computer of claim 8, wherein the non-lineage attribute data includes reference to a linked file, the linked file not being associated with lineage.