# US 8,280,865 B1 · Web site content change management

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

- Number: US 8,280,865 B1
- Document ID: US8280865B1
- Status: Granted
- Kind: B1
- Application number: 12/433,683
- Filed: 2009-04-30
- Granted: 2012-10-02
- Earliest claimed: 2002-12-30
- Assignees: Amazon Technologies, Inc.
- Inventors: Alexandre Edelman; Gus Lopez; Douglas Treder
- Web page: https://patentgrep.com/patent/US8280865B1

## CPC

- G06F 16/958: Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
- Y10S 707/99943: Generating database or data structure, e.g. via user interface
- Y10S 707/99954: Version management
- 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

A facility for specifying and previewing changes to a web site is described. Sets of changes to a web site are scheduled for release at a specified time. While the changes are being specified using a tool/interface, methods for showing the change as it will appear on the live web site are implemented. Inconsistencies between specified changes and changes in future releases may be identified as the changes are specified. Web page preview functionality is provided to allow any release to be viewed before publication to a live web site. The preview further allows inconsistencies between selected changes and changes in other future releases to be identified.

## Claims

### Claim 1

A computer-implemented method for specifying changes to a web_site, the method comprising:
performing, by one or more computers:
receiving a request for a first change to the web site, the web site including multiple web pages; wherein some of said web pages include item detail pages offering items for sale; wherein the first change is scheduled for release at a first specified time; wherein said web site includes a browse data structure distinct from the web pages of the web site, the browse data structure indicating a hierarchy of categories and different ones of the items for sale categorized under different categories of the hierarchy; wherein said first change is directed to a first portion of the browse data structure;
prior to the first specified time for release of the first change, receiving a request for a second change to the web site, the second change scheduled for release at a second specified time different than said first specified time; wherein said second change is directed to a second portion of the browse data structure, the second portion being different than the portion of the browse data structure to which the first change is directed; wherein prior to the first specified time and the second specified time, the second portion of the browse data structure has a dependency with said first portion; wherein the dependency is specified within the browse data structure;
subsequent to receiving the requests for the first and second changes, automatically determining whether said dependency between the first and second portions of the browse data structure would be broken by the release of the first change or the second change; wherein said automatically determining is performed without releasing said first and second changes on a live version of the website; and
if it is determined that the release of the first change or the second change would break said dependency, providing an indication of the broken dependency.

### Claim 2 (depends on 1)

The method of claim 1 wherein the first change is scheduled for release prior to the second change.

### Claim 3 (depends on 1)

The method of claim 1 wherein the second change is scheduled for release prior to the first change.

### Claim 4 (depends on 1)

The method of claim 1, further comprising receiving an indication of the requests for change via a tool configured to receive an indication of products to display on the web site.

### Claim 5 (depends on 1)

The method of claim 1 further comprising, receiving an indication of the requests for change via a tool configured to receive an indication of a browsing structure of the web site.

### Claim 6 (depends on 1)

The method of claim 1 further comprising, receiving an indication of the requests for change via a tool configured to add images to the web site.

### Claim 7 (depends on 1)

The method of claim 1 further comprising, receiving an indication of the requests for change via a tool configured to add new products to the web site.

### Claim 8 (depends on 1)

The method of claim 1 wherein the indication of the broken dependency is a warning message.

### Claim 9 (depends on 1)

The method of claim 1 wherein the first change is scheduled for release prior to the second change and wherein the first change is a deletion of a parent browse node of the browse data structure and the second change is an addition of a child browse node to the parent browse node deleted by the first change; wherein the parent browse node indicates a category of items offered for sale on the website, wherein the child browse node indicates a sub-category of items offered for sale or a specific item offered for sale.

### Claim 10 (depends on 1)

The method of claim 1 wherein the second change is scheduled for release prior to the first change and wherein the first change is an addition of a child browse node of the browse data structure to a parent browse node of the website and the second change is a deletion of the parent browse node from the browse data structure; wherein the parent browse node indicates a category of items offered for sale on the website, wherein the child browse node indicates a sub-category of items offered for sale or a specific item offered for sale.

### Claim 11 (depends on 1)

The method of claim 1 wherein the first change is scheduled for release prior to the second change and wherein the first change is a relocation of a parent node from an old location to a new location within the browse data structure and the second change is an addition of a child node to that parent node at the old location; wherein the parent browse node indicates a category of items offered for sale on the website, wherein the child browse node indicates a sub-category of items offered for sale or a specific item offered for sale.

### Claim 12 (depends on 1)

The method of claim 1 wherein the determining includes:
retrieving data associated with the first change according to a process for generating the web site as specified by the first change; and
analyzing the second change to determine if data associated with the second change is consistent with the retrieved data.

### Claim 13

A non-transitory computer-readable medium storing instructions to cause a computing system to provide services for creating content changes for a website, the program instruction when executed by the computing system cause:
receiving a request for a first change to the web site, the web site including multiple web pages; wherein some of said web pages include item detail pages offering items for sale; wherein the first change is scheduled for release at a first specified time; wherein said web site includes a browse data structure distinct from the web pages of the web site, the browse data structure indicating a hierarchy of categories and different ones of the items for sale categorized under different categories of the hierarchy; wherein said first change is directed to a first portion of said browse data structure;
prior to the first specified time for release of the first change, receiving a request for a second change to the website, the second change scheduled for release at a second specified time different than said first specified time; wherein said second change is directed to a second portion of the browse data structure, the second portion being different than the portion of the browse data structure to which the first change is directed; wherein prior to the first specified time and second specified time, the second portion of the browse data structure has a dependency with said first portion; wherein the dependency is specified within the browse data structure;
subsequent to receiving the information related to the first and second changes, automatically determining whether said dependency between the first and second portions of the browse data structure would be broken by the release of the first or second changes, wherein said automatically determining is performed without releasing said first and second changes on a live version of said website; and
in response to determining that the release of the first change or the second change would break said dependency, providing an indication of the broken dependency.

### Claim 14 (depends on 13)

The non-transitory computer-readable medium of claim 13 wherein the first change is scheduled for release prior to the second change.

### Claim 15 (depends on 13)

The non-transitory computer-readable medium of claim 13 wherein the second change is scheduled for release prior to the first change.

### Claim 16 (depends on 13)

The non-transitory computer-readable medium of claim 13, wherein said contents are configured to receive an indication of the requests for change via a tool configured to receive an indication of products to display on the web site.

### Claim 17 (depends on 13)

The non-transitory computer-readable medium of claim 13 wherein said contents are configured to receive an indication of the requests for change via a tool configured to receive an indication of a browsing structure of the web site.

### Claim 18 (depends on 13)

The non-transitory computer-readable medium of claim 13 wherein said contents are configured to receive an indication of the requests for change via a tool configured to add images to the web site.

### Claim 19 (depends on 13)

The non-transitory computer-readable medium of claim 13 wherein said contents are configured to receive an indication of the requests for change via a tool configured to add new products to the web site.

### Claim 20 (depends on 13)

The non-transitory computer-readable medium of claim 13 wherein the indication of the broken dependency is a warning message.

### Claim 21 (depends on 13)

The non-transitory computer-readable medium of claim 13 wherein the first change is scheduled for release prior to the second change and wherein the first change is a deletion of a parent browse node of the browse data structure and the second change is an addition of a child browse node to the parent browse node deleted by the first change; wherein the parent browse node indicates a category of items offered for sale on the website, wherein the child browse node indicates a sub-category of items offered for sale or a specific item offered for sale.

### Claim 22 (depends on 13)

The non-transitory computer-readable medium of claim 13 wherein the second change is scheduled for release prior to the first change and wherein the first change is an addition of a child browse node of the browse data structure to a parent browse node of the website and the second change is a deletion of the parent browse node from the browse data structure; wherein the parent browse node indicates a category of items offered for sale on the website, wherein the child browse node indicates a sub-category of items offered for sale or a specific item offered for sale.

### Claim 23 (depends on 13)

The non-transitory computer-readable medium of claim 13 wherein the first change is scheduled for release prior to the second change and wherein the first change is a relocation of a parent node from an old location to a new location within the browse data structure and the second change is an addition of a child node to that parent node at the old location; wherein the parent browse node indicates a category of items offered for sale on the website, wherein the child browse node indicates a sub-category of items offered for sale or a specific item offered for sale.

### Claim 24 (depends on 13)

The non-transitory computer-readable medium of claim 13 wherein to perform said determination the program instructions are executable to:
retrieve data associated with the first release according to a process for generating the web site as specified by the first release; and
analyze the second release to determine if data associated with the second release is consistent with the retrieved data.

### Claim 25

A system for specifying changes to a web_site, the system comprising:
a memory; and
one or more processors coupled to the memory, wherein the memory comprises program instructions executable by the one or more processors to:
receive a request for a first change to the web site, the web site including multiple web pages; wherein some of said web pages include item detail pages offering items for sale; wherein the first change is scheduled for release at a first specified time; wherein said web site includes a browse data structure distinct from the web pages of the web site, the browse data structure indicating a hierarchy of categories and different ones of the items for sale categorized under different categories of the hierarchy; wherein said first change is directed to a first portion of the browse data structure;
prior to the first specified time for release of the first change, receive a request for a second change to the web site, the second change scheduled for release at a second specified time different than said first specified time; wherein said second change is directed to a second portion of the browse data structure affected by the second change, the second portion being different than the portion of the browse data structure to which the first change is directed; wherein prior to the first specified time and the second specified time, the second portion of the browse data structure has a dependency with said first portion; wherein the dependency is specified within the browse data structure;
subsequent to receiving the requests for the first and second changes, automatically determine whether said dependency between the first and second portions of the browse data structure would be broken by the release of the first change or the second change; wherein that automatic determination is performed without releasing said first and second changes on a live version of the website; and
in response to determining that the first change or the second change would break said dependency, provide an indication of the broken dependency.

### Claim 26 (depends on 25)

The system of claim 25 wherein the first change is scheduled for release prior to the second change.

### Claim 27 (depends on 25)

The system of claim 25 wherein the second change is scheduled for release prior to the first change.

### Claim 28 (depends on 25)

The system of claim 25, wherein the program instructions are executable to receive an indication of the requests for change via a tool configured to receive an indication of products to display on the web site.

### Claim 29 (depends on 25)

The system of claim 25 wherein the program instructions are executable to receive an indication of the requests for change via a tool configured to receive an indication of a browsing structure of the web site.

### Claim 30 (depends on 25)

The system of claim 25 wherein the program instructions are executable to receive an indication of the requests for change via a tool configured to add images to the web site.

### Claim 31 (depends on 25)

The system of claim 25 wherein the program instructions are executable to receive an indication of the requests for change via a tool configured to add new products to the web site.

### Claim 32 (depends on 25)

The system of claim 25 wherein the indication of the broken dependency is a warning message.

### Claim 33 (depends on 25)

The system of claim 25 wherein the first change is scheduled for release prior to the second change and wherein the first change is a deletion of a parent browse node of the browse data structure and the second change is an addition of a child browse node to the parent browse node deleted by the first change; wherein the parent browse node indicates a category of items offered for sale on the website, wherein the child browse node indicates a sub-category of items offered for sale or a specific item offered for sale.

### Claim 34 (depends on 25)

The system of claim 25 wherein the second change is scheduled for release prior to the first change and wherein the first change is an addition of a child browse node of the browse data structure to a parent browse node of the website and the second change is a deletion of the parent browse node from the browse data structure; wherein the parent browse node indicates a category of items offered for sale on the website, wherein the child browse node indicates a sub-category of items offered for sale or a specific item offered for sale.

### Claim 35 (depends on 25)

The system of claim 25 wherein the first change is scheduled for release prior to the second change and wherein the first change is a relocation of a parent node from an old location to a new location within the browse data structure and the second change is an addition of a child node to that parent node at the old location; wherein the parent browse node indicates a category of items offered for sale on the website, wherein the child browse node indicates a sub-category of items offered for sale or a specific item offered for sale.

### Claim 36 (depends on 25)

The system of claim 25 wherein to perform the determination the program instructions are executable to:
retrieve data associated with the first change according to a process for generating the web site as specified by the first change; and
analyze the second change to determine if data associated with the second change is consistent with the retrieved data.
