METHOD AND SYSTEM FOR RECEIVING NORMALIZING CONTENT DATA IN A CONTENT PROCESSING SYSTEM USING A WORKFLOW SYSTEM

• US 20090030941A1
• Filed: 07/26/2007
• Published: 01/29/2009
• Est. Priority Date: 07/26/2007
• Status: Abandoned Application

• Current Assignee: The DIRECTV Group, Inc. (AT&T, Inc.)
• Original Assignee: The DIRECTV Group, Inc. (AT&T, Inc.)
• Inventors: Jacobs, Mitch C.
• Application Number:
  US11/828,938
• Publication Number:
  US 20090030941A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising

Abstract

A methods and system for normalizing data in a content processing system includes a content receiving system receiving a content file having content file metadata in metadata categories associated therewith and an asset management system in communication with the receiving system and having a required metadata category list and a provider metadata category list. The asset management system generates a failure signal when the metadata for each metadata category in the metadata category list is not present and forms provider metadata from the content file metadata when the metadata for a provider metadata category in the metadata category is not present.

Claims

1. A method comprising:

receiving a content file having metadata in metadata categories associated therewith;

establishing a required metadata category list and a provider metadata category list;

when the metadata for each metadata category in the metadata category list is not present generating a failure signal; and

when the metadata for each provider metadata category in the metadata category is not present generating a failure signal.

2. A method as recited in claim 1 wherein the provider metadata category list comprises a service category.

3. A method as recited in claim 1 wherein the provider metadata category list comprises a guide category.

4. A method as recited in claim 1 wherein the provider metadata category list comprise a program type category.

5. A method as recited in claim 1 wherein the provider metadata category list comprise a purchase terms category.

6. A method as recited in claim 1 wherein after receiving the content file, validating the content file.

7. A method comprising:

receiving a content file having content file metadata in metadata categories associated therewith;

establishing a required metadata category list and a provider metadata category list;

when the metadata for each metadata category in the metadata category list is not present generating a failure signal; and

when the metadata for a provider metadata category in the metadata category is not present, normalizing the content metadata.

8. A method as recited in claim 7 wherein normalizing content file metadata includes forming provider metadata from the content file metadata.

9. A method as recited in claim 7 wherein the provider metadata category list comprises a service category.

10. A method as recited in claim 7 wherein the provider metadata category list comprises a guide category.

11. A method as recited in claim 7 wherein the provider metadata category list comprise a program type category.

12. A method as recited in claim 7 wherein the provider metadata category list comprise a purchase terms category.

13. A method as recited in claim 7 wherein forming provider metadata from the content file metadata comprises forming provider metadata from a provider identification metadata.

14. A system comprising:

a content receiving system receiving a content file having content file metadata in metadata categories associated therewith; and

an asset management system in communication with the receiving system and having a required metadata category list and a provider metadata category list, said asset management system, generating a failure signal when the metadata for each metadata category in the metadata category list is not present and forming provider metadata from the content file metadata when the metadata for a provider metadata category in the metadata category is not present.

15. A system as recited in claim 14 wherein the provider metadata category list comprises a service category.

16. A system as recited in claim 14 wherein the provider metadata category list comprises a guide category.

17. A system as recited in claim 14 wherein the provider metadata category list comprise a program type category.

18. A system as recited in claim 14 wherein the provider metadata category list comprise a purchase terms category.

19. A system as recited in claim 14 wherein the workflow system forms provider metadata from a provider identification metadata.