DIGITAL ASSET MANAGEMENT SYSTEM

• US 20110191320A1
• Filed: 02/02/2011
• Published: 08/04/2011
• Est. Priority Date: 02/02/2010
• Status: Abandoned Application

• Current Assignee: Game Plan Technologies, Inc.
• Original Assignee: Game Plan Technologies, Inc.
• Inventors: Glover, David A.
• Application Number:
  US13/019,472
• Publication Number:
  US 20110191320A1
• Time in Patent Office: Days
• US Class Current: 707/706
• CPC Class Codes: G06F 16/00 Information retrieval; Database structures therefor; File system structures therefor
• CPC Class Codes: G06F 16/13 File access structures, e.g. distributed indices arrangements of input from, or output to, record carriers G06F3/06

Abstract

The present disclosure describes a digital asset management system directed to a portable container, decentralized, and distributed database approach to asset management. The digital asset management system described is also directed to a system that is designed to be format-neutral and compatible with any file formats available in the art. In an implementation, the digital asset management system includes an importer module configured to import one or more files for storage in a storage volume. A metadata module creates metadata for the imported files and attaches the metadata to the imported files. A distributor module configured to direct the one or more files to a container included in the storage volume. The digital asset management system also includes an editor module configured to create a compressed proxy version of an original source file of at least one of the files for proxy editing.

Claims

1. A system comprising:

at least one processor;

at least one memory;

an importer module, stored on the at least one memory, configured to cause the at least one processor to import one or more files for storage in a storage volume and configured to map a network location for the one or more files stored in the storage volume, the one or more files including an original source file;

a metadata module, stored on the at least one memory, configured to cause the at least one processor to create metadata for the one or more imported files and attach the metadata to the one or more imported files;

a distributor module, stored on the at least one memory, configured to cause the at least one processor to direct the one or more files to a container of the storage volume; and

an editor module, stored on the at least one memory, configured to cause the at least one processor to create a compressed proxy version of the original source file for proxy editing of the compressed proxy version.

2. The system of claim 1, further comprising a publishing module, stored on the at least one memory, configured to cause the at least one processor to convert one or more data files from a first file type to a second file type;

and a search engine configured to return one or more results based upon a search query.

3. The system of claim 2, further comprising a user interface configured to receive the search query.

4. The system of claim 1, further comprising a back-up module configured to generate one or more copies of the one or more files.

5. The system of claim 1, wherein the storage volume comprises a decentralized, distributed storage volume configured to store a first file of the one or more files in a first container of the storage volume and configured to store a second file of the one or more files in a second container of the storage volume, where the first container is distinct from the second container.

6. The system of claim 1, wherein the metadata further comprises at least one of:

environmental data scraped from the one or more files;

project metadata created during the importation of the one or more files;

or custom metadata created by a user.

7. The system of claim 1, wherein the editor module is further configured to create an edit file that includes edit notations and metadata that reflects any edits to the one or more files.

8. A system comprising:

at least one processor;

at least one memory;

an importer module, stored on the at least memory, configured to cause the at least one processor to import one or more files for storage in a storage volume, the one or more files including an original source file;

a metadata module, stored on the at least memory, configured to cause the at least one processor to create metadata for the one or more imported files and attach the metadata to the one or more imported files;

a distributor module, stored on the at least memory, configured to cause the at least one processor to direct the one or more files to a container of the storage volume;

a publishing module, stored on the at least memory, configured to cause the at least one processor to convert the one or more files from a first file type to a second file type; and

an editor module, stored on the at least memory, configured to cause the at least one processor to create a compressed proxy version of the original source file for proxy editing of the compressed proxy version.

9. The system of claim 8, wherein the importer module is configured to cause the at least one processor to create an Asset Data List, the Asset Data List including a Unique Media Identifier for each file of the one or more files created during the importation of the one or more files, the Unique Media Identifier being a hash value that remains with the one or more files for the life of the one or more files.

10. The system of claim 9, wherein the importer module utilizes a verification algorithm to create the Unique Media Identifier.

11. The system of claim 9, wherein the Unique Media Identifier of a derivative file includes metadata of the original source file and is combined with the Unique Media Identifier generated by the verification algorithm from the derivative file to create a new combined Unique Identifier Hash Value.

12. The system of claim 9, wherein the importer module is further configured to cause the at least one processor to create a Project Data List, the Project Data list being a data structure including a relationship between a first file of the one or more files and a second file of the one or more files, the relationship including metadata associated with the first file and the second file.

13. The system of claim 12, further comprising a viewer module, stored on the at least memory, configured to cause the at least one processor to create a Presentation Asset List, the Presentation Asset List including at least one of the Asset Data List, the Project Data List, or metadata created by the importer module.

14. The system of claim 13, wherein the viewer module launches content associated with the Presentation Asset List in a hypermedia player for display and manipulation of the content without moving an original source file of the content from a first container to a second container.

15. The system of claim 14, wherein the manipulation of the content further comprises creating a playlist of the content so the content is editable without altering a source material of the content.

16. The system of claim 14, further comprising a user interface, stored on the at least memory, configured to receive the one or more files.

17. The system of claim 16, wherein the importer module is further configured to cause the at least one processor to import a video file from the user interface and extract user-supplied data associated with the video file, the video file having a first size, and the editor module is further configured to cause the at least one processor to convert the video file into a proxy file, the proxy file having a second size, the second size being smaller than the first size.

18. The system of claim 8, wherein the storage volume comprises a decentralized, distributed storage volume configured to store a first file of the one or more files in a first container of the storage volume and configured to store a second file of the one or more files in a second container of the storage volume, where the first container is distinct from the second container.

19. A digital asset management system comprising:

at least one processor;

at least one memory;

an importer module, stored on the at least memory, configured to cause the at least one processor to import one or more files for storage in a decentralized, distributed storage volume, the one or more files including an original source file;

a metadata module, stored on the at least memory, configured to cause the at least one processor to create metadata for the one or more imported files and attach the metadata to the one or more imported files;

a distributor module, stored on the at least memory, configured to cause the at least one processor to direct the one or more files to a first container of the decentralized, distributed storage volume;

a publishing module, stored on the at least memory, configured to cause the at least one processor to convert the one or more files from a first file type to a second file type;

a search engine configured to cause the at least one processor to return one or more results based upon a search query;

a user interface configured to receive the search query; and

an editor module, stored on the at least one memory, configured to cause the at least one processor to create a compressed proxy version of the original source file for proxy editing of the compressed proxy version.

20. The system of claim 19, wherein the importer module is further configured to cause the at least one processor to convert the one or more files having a same type into a selected default file type that is a member of the same type of the one or more files.