Digital asset management data model

• US 9,275,084 B2
• Filed: 03/11/2015
• Issued: 03/01/2016
• Est. Priority Date: 11/14/2006
• Status: Active Grant

• Current Assignee: Accenture Global Services Limited (Accenture PLC)
• Original Assignee: Accenture Global Services Limited (Accenture PLC)
• Inventors: Macchietti, Alessandra, El Haffar, Karim
• Primary Examiner(s): Mackes, Kris
• Application Number:
  US14/644,984
• Publication Number:
  US 20150186431A1
• Time in Patent Office: 356 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/164 File meta data generation
• CPC Class Codes: G06F 16/21 Design, administration or maintenance of databases
• CPC Class Codes: G06F 16/48 Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually

Abstract

A digital asset management system effectively provides full control of compound media assets and their specific components. The digital asset management data model supports the creation and management of multiple levels of granularity or metadata enrichment, and different sets of file types or renditions used throughout the digital asset processing life-cycle. The extensible digital asset management data model allows telecommunications service providers to augment or enrich compound media asset metadata, and thereby, optimize the relationship between media assets, and enhance storage and retrieval functionalities. The digital asset management system solves the technical problems arising from ingesting, storing, and managing rich media assets economically and efficiently.

Claims

1. A digital asset management system comprising:

a communication interface;

a digital asset management database comprising a data model with three related hierarchies that together organize all media asset data and media asset metadata of a specified media asset that includes one or more media asset types and one or more delivery destinations, prior to controlling delivery of the specified media asset, wherein the three hierarchies of the data model include;

an asset description hierarchy comprising asset description objects for a media asset, wherein the asset description objects are populated with attributes that include at least media asset data and media asset metadata;

a compound media asset type description hierarchy comprising compound media asset type description objects that define different types of media assets associated with the media asset and comprise metadata attributes that associate media types to the media asset;

a compound media asset type file hierarchy for the media asset comprising compound media asset type file objects that correspond to the objects in the compound media asset description hierarchy, said compound media asset type file objects include;

media asset data attributes and media asset metadata attributes that associate a media asset data file to one of the compound media types; and

media asset files comprising physical data representations of renderings associated with the compound media types;

a memory comprising;

an ingestion program for creating the three hierarchies of the data model for a specified media asset, which is operable to;

obtain source media asset data and source media asset metadata through the communication interface and ingest the source media asset data and the source media asset metadata by;

normalizing the source media asset data and the source media asset metadata with respect to a defined object format by populating;

 

the asset description objects;

 

at least one of the compound media asset type description objects; and

 

at least one of the compound media asset type file objects; and

enriching the media asset data and the media asset metadata of the specified media asset with additional media asset data and additional media asset metadata from subsequent obtaining and ingesting of additional source media asset data and source media asset metadata; and

a processor coupled to the communication interface, database and the memory, and operable to execute the ingestion program.

2. The digital asset management system of claim 1, comprising:

a one-to-many relationship between a selected asset description object and objects of the compound media asset type description objects from the compound media asset type description hierarchy; and

a many-to-many relationship between objects of the compound media asset type file objects from the compound media asset type file hierarchy and objects of the compound media asset type description objects from the compound media asset type description hierarchy.

3. The digital asset management system of claim 1, where the asset description hierarchy comprises:

a media asset package description object comprising asset data and metadata;

a channel description object comprising asset source information;

an electronic program guide object comprising enhanced functionality metadata; and

an exceptions object comprising asset metadata exceptions identified while ingesting, storing and managing the media asset.

4. The digital asset management system of claim 1, where the compound media asset type description hierarchy comprises:

a movie description object comprising metadata relating a movie to the media asset;

a trailer description object comprising metadata relating a trailer to the media asset;

a cover description object comprising metadata relating a cover to the media asset;

an audio description object comprising metadata relating audio to the media asset; and

an abstract compound media asset type object comprising metadata relating other compound media asset types to the media asset.

5. The digital asset management system of claim 1, where the compound media asset type file hierarchy comprises:

a movie file object comprising;

metadata defining a movie file associated with the media asset, the movie file comprising a physical data representation of a rendering associated with the media asset;

a trailer file object comprising;

metadata defining a trailer file associated with the media asset, the trailer file comprising a physical data representation of a rendering associated with the media asset;

a cover file object comprising;

metadata defining a cover file associated with the media asset, the cover file comprising the physical data representation of a rendering associated with the media asset;

an audio file object comprising;

metadata defining an audio file associated with the media asset, the audio file comprising the physical data representation of a rendering associated with the media asset.

6. The digital asset management system of claim 1, where the compound media asset type file hierarchy comprises:

an abstract compound media asset type file object comprising;

metadata defining other file types associated with the media asset, the abstract file-type file comprising the physical data representation of a rendering associated with the media asset.

7. The digital asset management system of claim 1, where the memory further comprises a media management program operable to:

edit and repurpose the media asset by;

updating the media asset metadata; and

creating an asset rendition from the asset data and metadata;

publish an asset rendition of the media asset by;

creating an asset bundle comprising the asset rendition;

associating the asset bundle with a delivery channel by;

identifying a delivery channel and delivery platform; and

formatting the asset bundle for delivery to a delivery platform; and

scheduling and deploying the asset bundle to the delivery platform, where;

the processor is operable to execute the media management program.

8. The digital asset management system of claim 7, where the media management program is further operable to:

search the digital asset management database, and retrieve asset data and metadata based on user selection criteria; and

administer the digital asset management system by provisioning a media asset source, and where;

the processor is operable to execute the media management program.

9. The digital asset management system of claim 1, where the ingestion program is further operable to enrich the asset metadata by:

defining unique media asset data and media asset metadata not originally associated with the media asset; and

defining unique combinations of compound media asset type description objects and compound media asset type file objects not originally associated with the media asset.

10. The digital asset management system of claim 1, where the memory further comprises search, storage, and retrieval optimized combinations of compound media asset type description objects and compound media asset type file objects.

11. A computer implemented method of ingesting a media asset, the method comprising:

defining a digital asset management database comprising a data model with three related hierarchies that together organize all media asset data and media asset metadata of a media asset that includes one or more media asset types and one or more delivery destinations, prior to controlling delivery of the media asset, wherein the three hierarchies of the data model include;

an asset description hierarchy comprising asset description objects for a media asset, wherein the asset description objects are populated with attributes that include at least media asset data and media asset metadata;

a compound media asset type description hierarchy comprising compound media asset type description objects that define different types of media assets associated with the media asset and comprise metadata attributes that associate media types to the media asset;

a compound media asset type file hierarchy compound media asset type file objects that correspond to the objects in the compound media asset description hierarchy, said compound media asset type file objects comprising;

media asset data attributes and media asset metadata attributes that associate a media asset data file to one of the compound media types; and

media asset files comprising physical data representations of renderings associated with compound media types;

obtaining source media asset data and source media asset metadata for a specified media asset through the communication interface;

ingesting the source media asset data and the source media asset metadata to create the three hierarchies of the data model for the specified media asset, by;

normalizing the source media asset data and the source media asset metadata with respect to a defined object format by populating;

the asset description objects;

at least one of the compound media asset type description objects; and

at least one of the compound media asset type file objects; and

defining unique media asset data and media asset metadata from subsequent obtaining and ingesting of additional source media asset data and additional source media asset metadata; and

defining unique combinations of compound media asset type description objects and compound media asset type file objects not originally associated with the media asset; and

editing and repurposing the specified media asset by;

updating the media asset metadata; and

creating an asset rendition from the media asset data and media asset metadata;

publishing an asset rendition of the specified media asset by;

creating an asset bundle comprising the asset rendition;

associating the asset bundle with a delivery channel by;

identifying a delivery channel and delivery platform; and

formatting the asset bundle for delivery to a delivery platform; and

scheduling and deploying the asset bundle to the delivery platform; and

searching the digital asset management database, and retrieving media asset data and media asset metadata based on user selection criteria; and

provisioning a media asset source.

12. The method according to claim 11, further comprising:

defining a one-to-many relationship between a selected asset description object and objects from the compound media asset type description hierarchy; and

defining a many-to-many relationship between objects from the compound media asset type file hierarchy and objects from the compound media asset type description hierarchy.

13. The method according to claim 11, where defining an asset description hierarchy comprises:

establishing a media asset package description object comprising asset data and metadata;

establishing a channel description object comprising asset source information;

establishing an electronic program guide object comprising enhanced functionality metadata; and

establishing an exceptions object comprising asset metadata exceptions identified while acquiring, ingesting, storing, publishing and managing the media asset.

14. The method according to claim 11, where defining a compound media asset type description hierarchy comprises:

establishing a movie description object comprising metadata relating a movie to a media asset;

establishing a trailer description object comprising metadata relating a trailer to a media asset;

establishing a cover description object comprising metadata relating a cover to a media asset;

establishing an audio description object comprising metadata relating audio to a media asset; and

establishing an abstract compound media asset type object comprising metadata relating other compound media asset types to a media asset.

15. The method according to claim 11, where defining a compound media asset type file hierarchy comprises:

establishing a movie file object comprising;

metadata defining a movie file associated with a media asset, the movie file comprising a physical data representation of a rendering associated with the media asset;

establishing a trailer file object comprising;

metadata defining a trailer file associated with a media asset, the trailer file comprising a physical data representation of a rendering associated with the media asset;

establishing a cover file object comprising;

metadata defining a cover file associated with a media asset, the cover file comprising the physical data representation of a rendering associated with the media asset;

establishing an audio file object comprising;

metadata defining a audio file associated with a media asset, the audio file comprising the physical data representation of a rendering associated with the media asset; and

establishing an abstract compound media asset type file object comprising;

metadata defining other file types associated with the media asset, the abstract file-type file comprising the physical data representation of a rendering associated with the media asset.

16. A product comprising:

a machine readable medium; and

instructions encoded on the medium which cause a data processing system to perform a method comprising;

defining a digital asset management database comprising a data model with three related hierarchies that together organize all media asset data and media asset metadata of a media asset that includes one or more media asset types and one or more delivery destinations, prior to controlling delivery of the media asset, wherein the three hierarchies of the data model include;

an asset description hierarchy comprising asset description objects for the media asset, wherein the asset description objects are populated with attributes that include at least media asset data and media asset metadata;

a compound media asset type description hierarchy that defines different types of media assets associated with the media asset and comprises compound media asset type description objects comprising metadata attributes that associate compound media types to the specified media asset; and

a compound media asset type file hierarchy for the specified media asset comprising compound media asset type file objects that correspond to the objects in the compound media asset description hierarchy, said compound media asset type file objects comprising;

media asset data attributes and media asset metadata attributes that associate a media asset data file to one of the compound media types; and

media asset files comprising physical data representations of renderings associated with compound media types;

performing for a selected media asset the following steps;

obtaining source media asset data and source media asset metadata for the selected media asset through a communication interface;

ingesting the source media asset data and source media asset metadata by;

normalizing the source media asset data and source media asset metadata with respect to a defined object format by populating;

the asset description objects;

at least one of the compound media asset type description objects; and

at least one of the compound media asset type file objects; and

defining unique media asset data and media asset metadata from subsequent obtaining and ingesting of additional source media asset data and additional source media asset metadata; and

defining unique combinations of compound media asset type description objects and compound media asset type file objects not originally associated with the media asset; and

editing and repurposing the selected media asset by;

updating the media asset metadata; and

creating an asset rendition from the media asset data and media asset metadata;

publishing an asset rendition of the selected media asset by;

creating an asset bundle comprising the asset rendition;

associating the asset bundle with a delivery channel by;

identifying a delivery channel and delivery platform; and

formatting the asset bundle for delivery to a delivery platform; and

scheduling and deploying the asset bundle to the delivery platform; and

searching the digital asset management database, and retrieving asset data and metadata based on user selection criteria; and

provisioning a media asset source.

17. The product of claim 16, further comprising:

defining a one-to-many relationship between a selected asset description object and objects from the compound media asset type description hierarchy; and

defining a many-to-many relationship is defined between objects from the compound media asset type file hierarchy and objects from the compound media asset type description hierarchy.

18. The product of claim 16, where defining an asset description hierarchy comprises:

establishing a media asset package description object comprising asset data and metadata;

establishing a channel description object comprising asset source information;

establishing an electronic program guide object comprising enhanced functionality metadata; and

establishing an exceptions object comprising asset metadata exceptions identified while acquiring, ingesting, storing, publishing and managing.

19. The product of claim 16, where defining a compound media asset type description hierarchy comprises:

establishing a movie description object comprising metadata relating a movie to the media asset;

establishing a trailer description object comprising metadata relating a trailer to the media asset;

establishing a cover description object comprising metadata relating a cover to the media asset;

establishing an audio description object comprising metadata relating audio to the media asset; and

establishing an abstract compound media asset type object comprising metadata relating other compound media asset types to the media asset.

20. The product of claim 16, where defining a compound media asset type file hierarchy comprises:

establishing a movie file object comprising;

metadata defining a movie file associated with the media asset, the movie file comprising a physical data representation of a rendering associated with the media asset;

establishing a trailer file object comprising;

metadata defining a trailer file associated with the media asset, the trailer file comprising a physical data representation of a rendering associated with the media asset;

establishing a cover file object comprising;

metadata defining a cover file associated with the media asset, the cover file comprising the physical data representation of a rendering associated with the media asset;

establishing an audio file object comprising;

metadata defining a audio file associated with the media asset, the audio file comprising the physical data representation of a rendering associated with the media asset; and

establishing an abstract compound media asset type file object comprising;

metadata defining other file types associated with the media asset, the abstract file-type file comprising the physical data representation of a rendering associated with the media asset.