System and process of managing media content

A non-hierarchical user file system, comprising:

• a storage device;
• a user file storage area;
• and
• a processor programmed to;
• unload 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;
• and
• wherein the processor is further programmed to provide a user interface, 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 in the user, file storage area.

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;
• and
• wherein the processor is further 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 user storage area 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 user storage area.

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;
• saving the created project;
• 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.

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;
• saving the created project;
• approving the created project;
• and
• generating the created project.

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;
• saving the created project;
• 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.

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;
• saving the created project;
• creating a project;
• 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 page and popper for association with the created promote;
• and
• saving the created promoted;
• wherein the created promoted inherits the meta-data from the associated pages and poppers.

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;
• saving the created project;
• 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.

A system for organizing content relating to a created project into a hierarchy, comprising at least one processor programmed to:

• attach meta-data to the created project;
• provide a library of assets, the assets being selectable for association with the created project;
• providing means that allow a user to select at least one asset for association with the created project;
• schedule the created project;
• and
• save the created project;
• wherein the at least one processor is further programmed for:
• providing a library of poppers, the poppers being selectable for association with the created project;
• and
• providing means that allow a user to select a popper for association with the created project.

A system for organizing content relating to a created project into a hierarchy, comprising at least one processor programmed to:

• attach meta-data to the created project;
• provide a library of assets, the assets being selectable for association with the created project;
• providing means that allow a user to select at least one asset for association with the created project;
• schedule the created project;
• and
• save the created project;
• wherein the at least one processor is further programmed for:
• providing selectable templates for creating a popper;
• creating a popper based on a selected template;
• 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.