Metadata can be written once and saved into a preset so it can then applied to any or all of the elements of a release.
This saves the time from having to write these fields individually.
Additionally, once an item is employing a metadata preset, any changes to the preset are also made to the items using it. In that way, it is easy to make metadata changes to multiple items at once.
Users can also apply a metadata preset to an item and then select to overwrite a portion of it to make it custom for that element.
Creating a new Metadata Preset
To create a metadata preset, click the hamburger menu to open the Dashboard.
Find and click the Manage Metadata Presets button.
The will open the Metadata Presets tab.
If there have been no presets created, the interface will display "No metadata presets yet! Add some to get started."
Click the New Preset button to do so.
A box will appear allowing you name your new preset. Fill that out and hit the save button.
This will open a page with all the fields you can apply to multiple items in your project. They appear in both the right and left panes.
Fill out the plank to your preferences and click the Save button.
Note: The account's Organization Settings automatically are filled into a new Metadata Preset when it's created.
These can be edited as they are added to the preset, or accepted or modified once the preset is added to an element.
You now have a preset that you can apply to multiple items inside the MediaStorm Platform.
Editing an existing Metadata Preset
If there are existing metadata presets in your Platform account, you can select to edit them by navigating to the Manage Metadata Presets panel as outlined above.
There will be a list of existing presets listed in the tab.
Click the blue code for the preset to open it to edit it.
This will open the preset with any metadata you have added.
Modify it to your preference and click the Save button.
This preset can now be applied to multiple items inside the MediaStorm Platform.
Adding a preset to Media, Title or Release
The process of applying a Metadata Preset to a media element, a title or a release is the same.
To do so, find the item you'd like to modify by finding it in the Platform and either clicking it's unique ID or its name.
This will open the item's General tab, which contains metadata fields.
Find the Metadata Preset pulldown in the top center of this tab.
Use the pulldown to display the available presets and select the one you'd like to apply to the item.
Once the preset is applied to the item, all the fields that are referencing the preset's metadata appear grayed out so they aren't editable.
At this point, any changes to the preset metadata are made to this item.
Disabling Metadata Presets on individual fields
You can choose to disable the use of a metadata preset on any of the individual fields.
To do this, find the Use Preset slider at the right of the field and turn it off by sliding it to the left.
The field is no longer grayed out, and it's editable so custom information can now be added.
Note: If you’ve created a MetaData Preset and leave the Internal Domain, Analytics and Publisher Details fields empty, this will overwrite any data you may have entered into your global Organization Settings tab.
If they are left empty in the preset, they will be empty for any items using the presets.
As such, you will need to fill these fields out for each preset, or disable these fields when applying the preset to your release.
Deleting Metadata Presets
You can delete metadata presets by navigate to the Manage Metadata Presets tab as described in the top of this document.
Once the tab is open, find the checkboxes next to the left of each presets name.
To delete one or more items, check the box and then click the Actions button at the top right of the interface and then the Delete button.
The preset will be permanently removed from the list.
Note: Any items using the deleted preset will have its metadata fields reverted to custom text, so these items will need to be assigned a new preset, or new custom text should be added.
Watch MediaStorm Founder Brian Storm discuss this feature: