Multi-layered data model for generating audience-specific documents

• US 7,657,511 B2
• Filed: 05/31/2005
• Issued: 02/02/2010
• Est. Priority Date: 05/31/2005
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Tinari, Philip A., Yospe, Nathan F., Brookler, David E., Weinberg, Paul N., Sullivan, Dave L., Endo, Richard T.
• Primary Examiner(s): Vital; Pierre M
• Assistant Examiner(s): OBISESAN, AUGUSTINE KUNLE
• Application Number:
  US11/142,809
• Publication Number:
  US 20060271571A1
• Time in Patent Office: 1,708 Days
• Field of Search: 707/1, 707/100
• US Class Current: 715/265
• 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/948 Product or catalog

Abstract

One or more embodiments of invention are directed to a multi-layered data model for generating audience-specific documents will now be described. The invention is used in the context of generating a document such as a catalog or web page for publication across regions and cultures comprising multiple languages. It allows users to rapidly generate multi-language, multi-culture and multi-region documents since fields flagged as multi-lingual may utilize existing buckets that comprise pre-filled multi-language, multi-culture and multi-region values without requiring the user to specify every multi-value when creating a record.

Claims

1. In a computer system, a method for utilizing a multi-layered data model comprising database tables that minimize data redundancy to identify audience specific data to use in generating an audience specific document comprising:

constructing a first audience order database table that is updated to allow for a traversal to another audience when entries are not found for a given audience;

constructing a second main database table for said document that does not need to be altered in order to add support for a new audience;

constructing a third data attribute database table that is augmented with values that are unique to said new audience;

accepting a subset of data for said new audience with respect to said given audience into said third data attribute database table wherein said subset of data is unique to said new audience with respect to said given audience, wherein new audience data not contained in said subset of data is inherited from at least one other parent audience, and wherein said new audience and said given audience differ in one or more of language, country, region, regulatory or cultural designations;

determining an audience for an audience specific document;

determining an audience identifier for said audience;

obtaining a first audience order identifier from said first audience order database table comprising audience order using said audience identifier;

obtaining an audience-independent reference identifier from said second main database table as required by said audience specific document;

searching said third data attribute database table for a matching entry comprising both said audience order identifier and said audience-independent reference identifier, and where said searching fails,

searching said first audience order database table and retrieving a next audience order identifier based on a hierarchy of audience order identifiers for said audience identifier, substituting said first audience order identifier with a next audience order identifier, and repeating said searching until said searching successfully identifies said matching entry in said third data attribute database table;

identifying audience specific data in said matching entry;

generating said audience specific document using said audience specific; and

,

wherein said first audience order database table, said second main database table, and said third data attribute database table are configured to utilize the same data for multiple audiences when the data is the same for each audience.

2. The method of claim 1 further comprising:

adding a second audience comprising adding second audience data only to said third data attribute database table.

3. The method of claim 1 further comprising:

accessing said first audience order database table to determine if a first audience is enabled.

4. The method of claim 1 further comprising:

accepting payment for access to said audience specific data.

5. The method of claim 1 further comprising:

setting said first audience order identifier equal to a second audience identifier in said first audience order database table.

6. The method of claim 1 further comprising:

identifying said audience specific data for said audience specific document where said audience specific document is a web page.

7. The method of claim 1 further comprising:

identifying said audience specific data for said audience specific document where said audience specific document is a catalog.

8. The method of claim 1 further comprising:

determining said audience for said audience specific document further comprising obtaining information regarding said audience from a user interface.

9. The method of claim 1 further comprising:

determining said audience for said audience specific document further comprising obtaining information from an environment variable.

10. The method of claim 1 further comprising:

determining said audience for said audience specific document further comprising obtaining information from a browser session variable.

11. In a computer system, a method for utilizing a multi-layered data model comprising database tables that minimize data redundancy to identify audience specific data to use in generating an audience specific document comprising:

constructing a first audience order database table that is updated to allow for a traversal to another audience when entries are not found for a given audience;

constructing a second main database table for said document that does not need to be altered in order to add support for a new audience;

constructing a third data attribute database table that is augmented with values that are unique to said new audience;

wherein said first audience order database table, said second main database table, and said third data attribute database table are configured to utilize the same data for multiple audiences when the data is the same for each audience;

accepting a subset of data for said new audience with respect to said given audience into said third data attribute database table wherein said subset of data is unique to said new audience with respect to said given audience, wherein new audience data not contained in said subset of data is inherited from at least one other parent audience, and wherein said new audience and said given audience differ in one or more of language, country, region, regulatory or cultural designations;

determining an audience for an audience specific document;

determining a first audience identifier for said audience;

determining if said first audience identifier is enabled, if said first audience identifier is enabled, setting audience identifier to a value of said first audience identifier;

wherein if said first audience identifier is not enabled, determining a next enabled audience identifier, and setting audience identifier to a value of said next enabled audience identifier;

obtaining a first audience order identifier from said first audience order database table comprising audience order using said audience identifier;

obtaining an audience-independent reference identifier from said second main database table as required by said audience specific document;

searching said third data attribute database table for a matching entry comprising both said audience order identifier and said audience-independent reference identifier, and where said searching fails, searching said first audience order database table and retrieving a next audience order identifier based on a hierarchy of audience order identifiers for said audience identifier, substituting said first audience order identifier with a next audience order identifier, and repeating said searching until said searching successfully identifies said matching entry in said third data attribute database table;

identifying audience specific data in said matching entry; and

,

generating said audience specific document using said audience specific data.

12. The method of claim 11 further comprising:

identifying said audience specific data for said audience specific document where said audience specific document is a web page.

13. The method of claim 11 further comprising:

identifying said audience specific data for said audience specific document where said audience specific document is a catalog.

14. The method of claim 11 further comprising:

determining said audience for said audience specific document further comprising obtaining information regarding said audience from a user interface.

15. The method of claim 11 further comprising:

determining said audience for said audience specific document further comprising obtaining information from an environment variable.

16. The method of claim 11 further comprising:

determining said audience for said audience specific document further comprising obtaining information from a browser session variable.

17. In a computer system, a method for utilizing a multi-layered data model comprising database tables that minimize data redundancy to identify audience specific data to use in generating an audience specific document, comprising:

constructing a first audience order database table that is updated to allow for a traversal to another audience when entries are not found for a given audience;

constructing a second main database table for said document that does not need to be altered in order to add support for a new audience;

constructing a third data attribute database table that is augmented with values that are unique to said new audience;

wherein said first audience order database table, said second main database table, and said third data attribute database table are configured to utilize the same audience specific data structure in memory when the data is the same for each audience;

determining an audience for an audience specific document;

determining an audience identifier for said audience;

obtaining a first audience order identifier from said first audience order database table comprising audience order using said audience identifier;

obtaining an audience-independent reference identifier from said second main database table as required by said audience specific document;

searching said third data attribute database table for a matching entry comprising both said audience order identifier and said audience-independent reference identifier, identifying audience specific data in said matching entry;

and generating said audience specific document using said audience specific data.

18. The method of claim 17, in which utilizing the same audience specific data structure in memory is done by using at least one integer identifier to point to text strings that are stored only once regardless of the number of audiences that use said text strings.

19. The method of claim 17, in which at least the first audience order database table is configured in an audience hierarchy for each audience;

wherein for each audience a list of nearest match audiences is provided that is ranked in order;

and if a current layer of data for said audience is not available, then at least a primary layer of data is referenced in said order of said ranking to determine what said ranked in order nearest match audience to use.

20. The method of claim 19, wherein at least one audience in said list of nearest match audiences may be enabled or disabled, and if said at least one audience in said list of nearest match audiences is disabled, said at least one audience is not referenced in order to determine what ranked in order nearest match audience to use.