# US 2017/0255524 A1 · Data Repository Configured for Facilitating Point-in-Time Retrieval of Content

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

- Number: US 2017/0255524 A1
- Document ID: US20170255524A1
- Status: Published application
- Kind: A1
- Application number: 15/468,319
- Filed: 2017-03-24
- Published: 2017-09-07
- Earliest claimed: 2012-08-09
- Assignees: Propylon, Inc.
- Applicants: Propylon, Inc.
- Inventors: Sean McGRATH
- Web page: https://patentgrep.com/patent/US20170255524A1

## CPC

- G06F 11/1451: {by selection of backup contents}
- G06F 16/93: Document management systems
- G06F 16/9566: {URL specific, e.g. using aliases, detecting broken or misspelled links}
- G06F 2201/84: Using snapshots, i.e. a logical point-in-time copy of the data
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A data repository configured for storing original content and modified content which are addressable for point-in-time retrieval thereof. The data repository comprising one or more digital files which are associated with the original content. A log is provided which records actions implemented on the one or more of the digital files. A versioned repository is generated after an action is implemented on the one or more digital files. The versioned repository comprising one or more modified digital files which are associated with the modified content. A version identifier is associated with the versioned repository for facilitating point-in-time retrieval thereof.

## Claims

### Claim 1

A data repository configured for storing original content and modified content, the original and modified content being addressable for facilitating fully-consistent point-in-time retrieval thereof without the use of locks or replicas; the data repository comprising:
a first corpus defined by two or more digital files which are associated with the original content, the two or more digital files being inter-related to one another at a first point-in-time, the first corpus including hypertext links that allow users to traverse links, moving from one digital file at the first point-in-time to another inter-related digital file at the same first point-in-time via a web browser, the first corpus defining a snapshot of the two or more digital files as they existed at the first point-in-time;
a log detailing actions implemented on the two or more of the digital files;
a second corpus defined by two or more digital files which are associated with the original content, the two or more digital files being inter-related to one another at a second point-in-time, the second corpus being defined by a versioned repository generated after an action is implemented on the one of the two or more digital files of the first corpus, wherein the versioned repository includes an updated version of the entire first corpus at the second point-in-time, the updated version including one or more modified digital files which are associated with the modified content and hypertext links that allows users to traverse links, moving from one digital file at the second point-in-time to another inter-related digital file at the second point-in-time via a web browser, the second corpus defining a snapshot of the two or more digital files as they existed at the second point-in-time; and
a point-in-time version identifier defining a revision number associated with each corpus such that the first corpus is defined by a first revision number and the second corpus defined by a second different revision number, each revision number providing a point-in-time identifier and retrieval point of the totality of digital files defined by each of the first corpus and the second corpus respectively, and
wherein the data repository is configured:
to use the revision number for each of the first and second corpus in combination with the hypertext links within each of the first corpus and the second corpus to constrain a user traversal of the hyperlinks defined within each of the first corpus and the second corpus to those documents that are defined wholly within the first corpus and the second corpus respectively; and
to use the revision numbers in generating point-in-time hyperlinks such that retrieved query result sets can be traversed at any particularly retrieved point-in-time using the generated point-in-time hyperlinks which are specific to that retrieved query result set.

### Claim 2 (depends on 1)

A repository as claimed in claim 1, wherein the log includes time data.

### Claim 3 (depends on 1)

A data repository as claimed in claim 1, wherein the log includes a timeline.

### Claim 4 (depends on 1)

A data repository as claimed in claim 1, wherein the log includes biographic data of an editor.

### Claim 5

A data repository as claimed 4, wherein the log includes biographic data of a plurality of editors.

### Claim 6 (depends on 5)

A data repository as claimed in claim 5, wherein the biographic data includes at least one of a name, title, professional qualification, role and address.

### Claim 7 (depends on 1)

A data repository as claimed in claim 1, wherein the log is tabulated.

### Claim 8 (depends on 1)

A data repository as claimed in claim 1, wherein the repository is part of a geographic information software application.

### Claim 9 (depends on 8)

A data repository as claimed in claim 8, wherein the two or more digital files include a base map and a plurality of associate digital files.

### Claim 10 (depends on 1)

A data repository as claimed in claim 1, wherein the repository is part of an accounting software application.

### Claim 11 (depends on 10)

A data repository as claimed in claim 10, wherein the two or more digital files include a plurality of inter-related spreadsheets.

### Claim 12 (depends on 1)

A data repository as claimed in claim 1, wherein the repository is part of a word processing software application.

### Claim 13 (depends on 12)

A data repository as claimed in claim 12, wherein the two or more digital files comprises a plurality of inter-related word processor documents.

### Claim 14 (depends on 1)

A data repository as claimed in claim 1, wherein the versioned repository has an associated time stamp.

### Claim 15 (depends on 1)

A data repository as claimed in claim 1, wherein the repository forms part of a web application.

### Claim 16 (depends on 1)

A data repository as claimed in claim 1; wherein the repository is in a format suitable for publishing on the internet.

### Claim 17 (depends on 1)

A data repository as claimed in claim 1, wherein the versioned repository has an associated hyperlink address for facilitating retrieval thereof via the internet.

### Claim 18 (depends on 1)

A data repository as claimed in claim 1, further comprising metadata.

### Claim 19 (depends on 1)

A data repository as claimed in claim 1, wherein the actions includes at least one of updating, deleting, editing, and creating.

### Claim 20 (depends on 1)

A data repository as claimed in claim 1, configured for facilitating trend analysis and regression model creation utilizing a change history contained in the log.

### Claim 21

An article of manufacture, comprising: a non-transitory computer readable storage medium having machine readable instructions embodied thereon which, when executed by a processor, cause the processor to provide a data repository comprising:
a first corpus defined by two or more digital files with associated content, the two or more digital files being inter-related to one another at a first point-in-time, the first corpus including hypertext links that allow users to traverse links, moving from one digital file at the first point-in-time to another inter-related digital file at the same first point-in-time via a web browser, the first corpus defining a snapshot of the two or more digital files as they existed at the first point-in-time;
a log detailing actions implemented on at least one of the two or more of the digital files;
a second corpus defined by two or more digital files which are associated with the original content, the two or more digital files being inter-related to one another at a second point-in-time, the second corpus being a versioned repository being generated after an action is implemented on the at least one of the two or more digital files of the first corpus; the versioned repository comprising an updated version of the entire first corpus at the second point-in-time, the updated version including one or more modified digital files which are associated with modified content and hypertext links that allows users to traverse links, moving from one digital file at the second point-in-time to another inter-related digital file at the second point-in-time via a web browser, the second corpus defining a snapshot of the two or more digital files as they existed at the second point-in-time; and
a version identifier being associated with the versioned repository for facilitating point-in-time retrieval thereof, wherein the versioned repository comprises revision numbers allocated to each corpus as opposed to revision numbers allocated to individual files of each of the corpus so as to allow a user view the totality of individual digital files within each corpus as they were at whatever time point is set by the user; and further
wherein the machine readable instructions are configured to cause the processor to:
use the revision number for each of the first and second corpus in combination with the hypertext links within each of the first corpus and the second corpus to constrain a user traversal of the hyperlinks defined within each of the first corpus and the second corpus to those documents that are defined wholly within the first corpus and the second corpus respectively, and
to use the revision numbers in generating point-in-time hyperlinks such that retrieved query result sets can be traversed at any particularly retrieved point-in-time using the generated point-in-time hyperlinks which are specific to that retrieved query result set.

### Claim 22

A method of creating a data repository the method comprising:
providing a first corpus defied by two or more digital files with associated content, the two or more digital files being inter-related to one another at a first point-in-time, the first corpus including hypertext links that allow users to traverse links, moving from one digital file at the first point-in-time to another inter-related digital file at the same first point-in-time via a web browser, the first corpus defining a snapshot of the two or more digital files as they existed at the first point-in-time;
providing a log detailing actions implemented on at least one of the two or more of the digital files;
providing a second corpus defined by two or more digital files which are associated with the original content, the two or more digital files being inter-related to one another at a second point-in-time, the second corpus being defined by generating a versioned repository when an action is implemented on at least one of the two or more digital files of the first corpus; the versioned repository comprising an updated version of the entire first corpus at the second point-in-time, the updated version including one or more modified digital files which are associated with modified content and hypertext links that allows users to traverse links, moving from one digital file at the second point-in-time to another inter-related digital file at the second point-in-time via a web browser, the second corpus defining a snapshot of the two or more digital files as they existed at the second point-in-time;
providing a point-in-time version identifier being associated with the versioned repository for facilitating point-in-time retrieval thereof wherein the versioned repository comprises revision numbers allocated to each corpus as opposed to revision numbers allocated to individual files of each of the corpus so as to allow a user view the totality of the individual digital files within each corpus as they were at whatever time point is set by the user;
storing the versioned repository;
using the revision number for each of the first and second corpus in combination with the hypertext links within each of the first corpus and the second corpus to constrain a user traversal of the hyperlinks defined within each of the first corpus and the second corpus to those documents that are defined wholly within the first corpus and the second corpus respectively; and
using the revision numbers in generating point-in-time hyperlinks such that retrieved query result sets can be traversed at any particularly retrieved point-in-time using the generated point-in-time hyperlinks which are specific to that retrieved query result set.

### Claim 23 (depends on 1)

A data repository as claimed in claim 1, in which the one or more digital files comprise associated application logic and where the application logic is also stored so that the versioned repository is viewed for the time set by the user, it will appear as it would have looked, rendered with the application logic as it also looked at that time.

### Claim 24 (depends on 22)

A method as claimed in claim 22, wherein the first and second corpus comprise hypermedia objects.

### Claim 25 (depends on 24)

The method of claim 24, comprising parsing one of the first and second corpus to generate a result set, the method further comprising caching the result set, the result set being associated with a corpus revision identifier to facilitate subsequent retrieval and interrogation of the result set.

### Claim 26 (depends on 25)

The method of claim 25, further comprising querying the result set to generate hierarchical and recursive query patterns that yield composite result sets.

### Claim 27 (depends on 26)

The method of claim 26, comprising outputting from a result set at least one singular retrieved artifacts that comprises a corpus pointer to other artifacts within the corpus.

### Claim 28 (depends on 27)

The method of claim 27, comprising using a plurality of corpus pointers in conjunction with a corpus revision identifier to allow hypermedia graph traversal at a point-in-time, without requiring the creation of a result set.

### Claim 29 (depends on 24)

The method of claim 24, wherein tabular data is hosted in document-centric containers as metadata fields to facilitate contemporaneous storage of non-tabular data and tabular data.
