Overview of Components

Before you begin, it is important to understand the main components of the MediaStorm Platform. They are:

1. Dashboard
2. Media
3. Projects
4. Titles
5. Playlists
6. Player Templates
7. Players and Embeds

COMPONENT	DESCRIPTION
Dashboard	The dashboard serves as a general summary of your Platform account. From the dashboard, you can access every page of the Platform and view the five most recent Projects that you’ve worked on.
Media	All video used in the MediaStorm Platform is uploaded and managed here.
Projects	A Project is a body of work comprising many elements, including: Titles associated with your Project, including video assets and other media types. The relationship of Projects to Titles in the MediaStorm Platform can be seen as albums are to songs. Metadata associated with your project including general information, organizations, related links, recognitions, and a roll-up of all the credits aggregated from your project’s titles. Images, including the project's poster. Merchandise roll-up of products added to a project's title
Titles	Titles are added within a Project and allow you to associate supporting metadata with a video. This metadata includes credits, transcripts, subtitles and related images.
Playlists	Playlists allow you to group one or more titles together to create an ordered sequence in which to view a Project’s Titles.
Player Templates	Player Templates make it easier to store branding and style information for reuse in other Players.
Players and Embeds	A Player is the container that presents the content from your Projects. One of the benefits of using the MediaStorm Platform is that you can distribute your Project through your all-in-one Player in a variety of ways--upload to your websites or other sites, share via social media platforms or email--and in every instance all the components--metadata, media assets, associated content--go everywhere the player goes. This means that you have the ability to monitor, track and measure its footprint as it moves across the Internet. By using the embed codes provided for each Player, every instance of your Project has a unique URL that can be monitored and tracked over time to measure impact. Embeds are singular instances of a Player embedded somewhere. Each embed is derived from a single Player, and as such can be managed either individually or via the parent Player they are created from. For instance, a single Embed of a Player can be disabled if you choose without affecting the rest of the parent Player's Embeds, or the parent Player itself can be disabled to disable all Embeds created from it.