Content management system and process

• US 20020194194A1
• Filed: 07/13/2001
• Published: 12/19/2002
• Est. Priority Date: 06/15/2001
• Status: Active Grant

• Current Assignee: Sony Corporation (Sony Group Corp.)
• Original Assignee: Sony Corporation (Sony Group Corp.)
• Inventors: Thai, Holly, Mannarino, Michael F., Shmelev, Alex, Manaster, Jacob S., Byer, John Jeffrey, Newby, Rodney C., Schneider, Andrew, Dayley, Marlowe J., Fenton, Nicholas W., Springer, Wendy
• Granted Patent: US 6,910,049 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: H04N 21/2743 Video hosting of uploaded data from client
• CPC Class Codes: H04N 21/426 Internal components of the client ; Characteristics thereof H04N5/44 takes precedence
• CPC Class Codes: H04N 21/47205 for manipulating displayed content, e.g. interacting with MPEG-4 objects, editing locally
• CPC Class Codes: H04N 21/4782 Web browsing , e.g. WebTV
• CPC Class Codes: H04N 21/8173 End-user applications, e.g. Web browser, game
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing
• CPC Class Codes: Y10S 707/99948 Application of database or data structure, e.g. distributed, multimedia, or image

Abstract

A content management system and process for programming, scheduling, uploading, storing and managing content on a website. The content management system and process attaches meta-data to website elements and sorts the elements into a hierarchy based on the meta-data. The content management system and process may then perform off-line generation and association of all associated website elements, through the meta-data, into a data package. The data package may then be scheduled for on-line availability at defined times. The content management system and process also enables the setting forward of an internal clock so that the data package may be tested within the context of the website before the data package may actually be available on the website. The content management system and process may automatically ingest content based on a naming convention and may also ingest website user content and inherit all meta-data that was associated with user content.

Claims

1. A content management system, comprising:

a storage device;

a display device; and

a processor programmed to;

store and maintain content in the storage device;

sort the content into a hierarchy;

attach meta-data to selected high-level content within the hierarchy;

pass the meta-data from the selected high-level content to selected low-level content within the hierarchy, the selected low-level content thereby becoming associated with the selected high-level content;

integrate associated high-level and low-level content into a data package; and

generate a display of the data package on the display device.

2. The content management system recited in claim 1, wherein the processor is further programmed to sort the content according to the meta-data.

3. The content management system recited in claim 1, wherein the display device is connected locally to the processor.

4. The content management system recited in claim 1, further comprising at least one server network device, the at least one server network device communicating with the processor and being programmed to provide a user interface;

and

at least one user network device communicatively coupled to the at least one server network device via a network, the at least one user network device being programmed to access the user interface.

5. The content management system recited in claim 4, wherein the display device is connected locally to the at least one user network device.

6. The content management system recited in claim 1, wherein the content comprises at least one of projects, poppers, promotes, and pages.

7. The content management system recited in claim 6, wherein the meta-data comprises information about at least one of the projects, the poppers, the promotes, and the pages.

8. The content management system recited in claim 7, wherein the information comprises at least one of a name, a title, an artist'"'"'s name, an author'"'"'s name, credits, keywords, a description, a file type, copyright information, and a summary.

9. The content management system recited in claim 4, wherein the network comprises the Internet and the user interface comprises a website.

10. The content management system recited in claim 9, wherein the high-level and low-level content are integrated into the data package off line.

11. The content management system recited in claim 9, wherein the data package is displayed on-line via the website.

12. The content management system recited in claim 10, wherein the data package comprises at least one of a Web page, a popper, and a promote.

13. The content management system recited in claim 12, wherein

the Web page is programmed in Flash.

14. The content management system recited in claim 12, wherein the promote comprises a graphic image.

15. The content management system recited in claim 12, wherein the promote comprises a text link.

16. The content management system recited in claim 12, wherein the Web page comprises at least one promote, the at least one promote being linked to at least one of media content, a page, a popper, an advertisement, and an external link.

17. The content management system recited in claim 16, wherein the external link is selectable for linking to a website.

18. The content management system recited in claim 16, wherein the media content comprises at least one of audio, video, photos, animation, and music.

19. The content management system recited in claim 16, wherein the popper comprises a media player for playing media content.

20. A user interface for use with a content management system, comprising:

a project creating page, comprising;

means for creating a project;

means for attaching meta-data to the created project;

means for browsing a library of assets, the assets being selectable for association with the created project;

means for browsing a library of poppers, the poppers being selectable for association with the created project;

means for browsing a library of links, the links being selectable for association with the created project;

means for scheduling the created project;

means for saving the created project;

21. The user interface recited in claim 20, further comprising:

means for approving the created project; and

means for generating the created project.

22. The user interface recited in claim 20, further comprising:

a popper creating page, comprising;

means for selecting a template for creating a popper;

means for creating the popper;

means for associating the created popper with the created project;

means for associating at least one media player with the created popper;

means for scheduling the created popper;

means for previewing the created popper; and

means for saving the created popper;

wherein the created popper inherits the meta-data attached to the created project.

23. The user interface recited in claim 22, further comprising:

means for approving the created popper; and

means for generating the created popper.

24. The user interface recited in claim 22, wherein the means for previewing the created popper further comprise:

means for setting forward an internal clock to a time when the created popper is scheduled; and

means for viewing the popper at the set time.

25. The user interface recited in claim 22, further comprising:

means for associating together in a data package at least two media players; and

means for associating the data package with the created popper.

26. The user interface recited in claim 25, wherein the means for associating together in a data package at least two media players further comprise means for associating the at least two media players through meta-data.

27. The user interface recited in claim 22, further comprising:

a promote creating page, comprising;

means for creating a promote;

means for browsing a library of pages and poppers, the pages and poppers being associated with the meta-data and being selectable for association with the created promote;

means for browsing a library of images, the images being selectable for association with the created promote; and

means for saving the created promote;

wherein the created promote inherits the meta-data from the associated pages and poppers.

28. The user interface recited in claim 27, further comprising:

means for approving the created promote; and

means for generating the created promote.

29. The user interface recited in claim 27, further comprising:

a page creating page, comprising;

means for selecting a template for creating a page;

means for creating the page;

means for associating the created page with the created project;

means for associating the created page with at least one promote, the at least one promote being associated with at least one of a page, a popper, and a link;

means for scheduling the created page;

means for previewing the created page; and

means for saving the created page;

wherein the created page inherits the meta-data attached to the created project.

30. The user interface recited in claim 29, further comprising:

means for approving the created page; and

means for generating the created page.

31. The user interface recited in claim 29, wherein the means for previewing the created page further comprise:

means for setting forward an internal clock to a time when the created page is scheduled; and

means for viewing the created page at the set time.

32. The user interface recited in claim 29, further comprising means for editing and duplicating at least one of a project, a popper, a promote, and a page.

33. The user interface recited in claim 29, further comprising means for searching for at least one of a project, a popper, a promote, and a page.

34. The user interface recited in claim 29, further comprising:

an asset page, comprising;

means for associating an asset with the created project;

means for disassociating an asset from the created project;

means for browsing a library of assets, the assets being selectable for association with the created project; and

means for ingesting outside assets;

wherein the outside assets are ingested based on a naming convention.

35. The user interface recited in claim 34, wherein the means for ingesting the outside assets further comprise a“

magic upload”

user-selectable operator.

36. The user interface recited in claim 34, wherein the naming convention comprises a plurality of data fields, each of the plurality of data fields representing a type of the meta-data and comprising a plurality of bits.

38. The content management system recited in claim 37, wherein the modified file comprises at least one of a newly created file and a newly edited file.

40. The non-hierarchical user file system recited in claim 39, wherein the processor is further programmed to pseudo-randomly generate the unique identification number.

37. A content management system, comprising:

a storage device;

a database; and

a processor programmed to;

associate with a modified file a unique identifier;

store the modified file in the storage device;

search the storage device periodically for the modified file;

access the modified file on the storage device;

read and parse the unique identifier associated with the modified file;

assign the modified file to the database based on the unique identifier;

create a reference file, the reference file comprising meta-data associated with the modified file; and

store the reference file in the database.

39. A non-hierarchical user file system, comprising:

a storage device;

a user file storage area; and

a processor programmed to;

upload a file from the storage device;

generate a unique identification number;

associate the unique identification number with the file; and

store the file in the user file storage area;

wherein files are stored in the user file storage area in a non-hierarchical manner based on the unique identification number.

41. A data package, the data package comprising:

data representing display code for at least one Web page, the Web page display code data being associated with meta-data; and

data representing display code for at least one promote displayed within the at least one Web page, the promote display code data being associated with the meta-data;

wherein the Web page display code data and the promote display code data are packaged together based on the meta-data.

42. The data package recited in claim 41, further comprising:

data representing display code for at least one popper, the popper display code data being associated with the meta-data;

wherein the popper display code data, the Web page display code data, and the promote display code data are packaged together based on the meta-data.

43. The data package recited in claim 42, further comprising:

data representing display code for at least one external link, the external link display code data being associated with the meta-data;

wherein the external link display code data, the popper display code data, the Web page display code data, and the promote display code data are packaged together based on the meta-data.

44. The data package recited in claim 43, further comprising:

data representing media content, the media content data being associated with the meta-data;

wherein the media content data, the external link display code data, the popper display code data, the Web page display code data, and the promote display code data are packaged together based on the meta-data.

45. The data package recited in claim 44, wherein the meta-data is project meta-data.

47. The process recited in claim 46, further comprising:

browsing a library of poppers, the poppers being selectable for association with the created project; and

selecting a popper for association with the created project.

48. The process recited in claim 46, further comprising:

browsing a library of links, the links being selectable for association with the created project; and

selecting a link for association with the created project.

49. The process recited in claim 46, further comprising:

approving the created project; and

generating the created project.

50. The process recited in claim 46, further comprising:

selecting a template for creating a popper;

creating the popper;

associating the created popper with the created project; and

saving the created popper;

wherein the created popper inherits the meta-data attached to the created project.

51. The process recited in claim 50, further comprising:

scheduling the created popper; and

previewing the created popper.

52. The process recited in claim 50, further comprising:

approving the created popper; and

generating the created popper.

53. The process recited in claim 51, wherein previewing the created popper comprises:

setting forward an internal clock to a time when the created popper is scheduled; and

viewing the created popper at the set time.

54. The process recited in claim 50, further comprising associating at least one media player with the created popper.

55. The process recited in claim 54, further comprising:

associating together in a data package at least two media players; and

associating the data package with the created popper.

56. The process recited in claim 55, wherein associating together in a data package at least two media players comprises associating the at least two media players through the meta-data.

57. The process recited in claim 46, further comprising:

creating a promote;

browsing a library of pages and poppers, the pages and poppers being associated with the meta-data and being selectable for association with the created promote;

selecting at least one of a page and popper for association with the created promote; and

saving the created promote;

wherein the created promote inherits the meta-data from the associated pages and poppers.

58. The process recited in claim 57, further comprising:

browsing a library of images, the images being selectable for association with the created promote; and

selecting an image for association with the created promote.

59. The process recited in claim 57, further comprising:

approving the created promote; and

generating the created promote.

60. The process recited in claim 46, further comprising:

selecting a template for creating a page;

creating the page;

associating the created page with the created project;

associating the created page with at least one promote, the at least one promote being associated with at least one of a page, a popper, and a link; and

saving the created page;

wherein the created page inherits the meta-data attached to the created project.

61. The process recited in claim 60, further comprising:

scheduling the created page; and

previewing the created page.

62. The process recited in claim 60, further comprising:

approving the created page; and

generating the created page.

63. The process recited in claim 61, wherein previewing the created page further comprises:

setting forward an internal clock to a time when the created page is scheduled; and

viewing the created page at the set time.

64. The process recited in claim 60, further comprising at least one of editing and duplicating at least one of a project, a popper, a promote, and a page.

65. The process recited in claim 60, further comprising searching for at least one of a project, a popper, a promote, and a page.

66. The process recited in claim 60, further comprising:

browsing a library of assets, the assets being selectable for association with the created project; and

selecting an asset for association with the created project.

68. The process recited in claim 67, wherein associating with the modified file a unique identifier further comprises associating with the modified file a name, the name comprising a plurality of data fields, each of the plurality of data fields representing a type of the meta-data.

69. The process recited in claim 67, wherein the modified file comprises at least one of a newly stored file and a newly edited file.

46. A process for organizing content into a hierarchy, comprising:

creating a project;

attaching meta-data to the created project;

browsing a library of assets, the assets being selectable for association with the created project;

selecting at least one asset for association with the created project;

scheduling the created project; and

saving the created project.

67. A process for ingesting a file into a database, comprising:

modifying a file;

associating with the modified file a unique identifier;

storing the modified file in a storage device;

searching periodically for the modified file on the storage device;

accessing the modified file on the storage device;

reading and parsing the unique identifier associated with the modified file;

assigning the modified file to a database based on the unique identifier;

creating a reference file, the reference file comprising meta-data associated with the modified file; and

storing the reference file in the database.

70. A process for ingesting selected user files into a database, comprising:

providing a storage area to a user for storage of user files;

enabling the user to attach meta-data to the user files and to store the user files in the storage area;

selecting at least one user file for ingestion into a database;

attaching a prefix to the at least one selected user file;

searching the storage area for prefixed files; and

assigning found prefixed files to the database based on the attached meta-data.

71. A process for storing files in a user file system, comprising:

uploading a file from a user storage device;

generating a unique identification number;

associating the unique identification number with the file; and

storing the file in a user file storage area;

wherein files are stored in the user file storage area in a non-hierarchical manner based on the unique identification number.

72. The process recited in claim 71, wherein the unique identification number is a pseudo-random number.