Creation and management of content-related objects

• US 7,631,257 B2
• Filed: 09/15/2004
• Issued: 12/08/2009
• Est. Priority Date: 09/15/2004
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Kogan, Daniel E., Miller, Patrick C.
• Primary Examiner(s): Ly; Cheyne D
• Application Number:
  US10/941,549
• Publication Number:
  US 20060059465A1
• Time in Patent Office: 1,910 Days
• Field of Search: 707/10, 707/100, 707/103, 707/200, 707/203, 715/234, 715/239, 717/122
• US Class Current: 715/239
• CPC Class Codes: G06F 16/38 Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

A web content management server allows for the automatic creation, management and publication of variant objects from a parent object. The variant object is created as a copy of the corresponding parent object and may then be modified. Each object includes a pages list that identifies all associated objects and the content type of each object listed in the pages list. The relationship between parent and variant objects is maintained regardless of the location where the objects are stored. When changes are made to the parent page, the changes are also implemented in any corresponding variant pages. The parent object tracks any corresponding variant objects with an identifier stored in the pages list. When the parent page is modified, a workflow is triggered to modify the corresponding variant pages identified by the identifier and the content type in the pages list.

Claims

1. A computer-implemented method for automatically creating and managing content-related webpages, comprising:

generating a parent webpage, wherein the parent webpage includes a pages list stored with the parent webpage, wherein the pages list includes a variant container and a source container, wherein upon generating the parent webpage setting the source container to null;

generating a variant webpage of the parent webpage by forming a copy of the parent webpage, wherein the variant webpage includes a pages list stored with the variant webpage, wherein the pages list of the variant webpage includes a variant container and a source container, wherein upon generation of the variant webpage, populating the source container of the pages list of the variant webpage with an identifier of the parent webpage and populating the variant container of the pages list of the parent webpage with an identifier of the variant webpage;

upon receiving a modification to the parent webpage, causing a computer processor to access the pages list of the parent webpage to obtain the identifier of the variant webpage located in the variant container of the pages list of the parent webpage;

locating the variant webpage via the obtained identifier; and

causing the computer processor to automatically populate the received modification to the variant webpage based on the obtained identifier.

2. The computer-implemented method of claim 1, further comprising initiating a workflow to convert the variant webpage to a form different than the parent webpage.

3. The computer-implemented method of claim 1, wherein the variations of the parent webpage are selected by a web site manager.

4. The computer-implemented method of claim 1, wherein the parent webpage includes parameters having at least one of a group comprising:

languages supported by a web site, applications supported by an operating system, devices supported by an operating system and a variation targeting rule that establishes behavior associated with accessing the variant webpage.

5. The computer-implemented method of claim 1, further comprising displaying the variant webpage in accordance with a template associated with the parent webpage, wherein the template is related to the variant webpage by a content type identifier of the pages list of the parent webpage.

6. A system for automatically creating and managing content-related webpages, comprising a web content configuration server being configured to:

generating a parent webpage, wherein the parent webpage includes a pages list stored with the parent webpage, wherein the pages list includes a variant container and a source container;

generating a variant webpage of the parent webpage by forming a copy of the parent webpage, wherein the variant webpage includes a pages list stored with the variant webpage, wherein the pages list of the variant webpage includes a variant container and a source container, wherein upon generation of the variant webpage, populating the source container of the pages list of the variant webpage with an identifier of the parent webpage and populating the variant container of the pages list of the parent webpage with an identifier of the variant webpage;

upon receiving a modification to the parent webpage, accessing the pages list of the parent webpage to obtain the identifier of the variant webpage located in the variant container of the pages list of the parent webpage;

locating the variant webpage via the obtained identifier; and

automatically populating the received modification to the variant webpage based on the obtained identifier.

7. The system of claim 6, wherein a content type identifier is included in metadata corresponding to the parent webpage.

8. The system of claim 6, wherein a workflow is initiated to convert the variant webpage to a form different than the parent webpage.

9. The system of claim 6, wherein the variant webpage is displayed in accordance with a template associated with the parent webpage, and wherein the template is related to the variant webpage by a content type identifier of the pages list of the parent webpage.

10. A computer-readable storage medium having computer-executable instructions for automatically creating and managing content-related webpages, comprising:

generating a parent webpage, wherein the parent webpage includes a pages list stored with the parent webpage, wherein the pages list includes a variant container and a source container;

generating a variant webpage of the parent webpage by forming a copy of the parent webpage, wherein the variant webpage includes a pages list stored with the variant webpage, wherein the pages list of the variant webpage includes a variant container and a source container, wherein upon generation of the variant webpage, populating the source container of the pages list of the variant webpage with an identifier of the parent webpage and populating the variant container of the pages list of the parent webpage with an identifier of the variant webpage;

upon receiving a modification to the parent webpage, accessing the pages list of the parent webpage to obtain the identifier of the variant webpage located in the variant container of the pages list of the parent webpage;

locating the variant webpage via the obtained identifier; and

automatically populating the received modification to the variant webpage based on the obtained identifier.

11. The computer-readable storage medium of claim 10, further comprising initiating a workflow to convert the variant webpage to a form different than the parent webpage.

12. The computer-readable storage medium of claim 10, further comprising displaying the variant webpage in accordance with a template associated with the parent webpage, wherein the template is related to a content type identifier of the pages list of the parent webpage.