You can import bulk audio metadata to the Content Library in your CMS. First, you need to create a CSV or XML file, which will contain all the metadata information of the content that you want to add to your Content Library. This CSV/XML file must contain information including, Content Type, Content Name, Content Category, Release/Record Date, Genre etc. in a specific order for each content. You can also import Custom Metadata to Content Library through this feature. After creating the CSV/XML file you can import the content metadata to the Content Library through the Import feature in the CMS.
Creating CSV/XML File
While creating the CSV/XML file for content metadata, you need to follow some guidelines.
- Column headings in the CSV/XML file must be the same of the metadata fields in the “Add Content” page. (For example, Genre should have column header as “Genre”. Otherwise, the corresponding metadata won’t be imported).
- In a CSV/XML file, columns are metadata fields and the rows contain the values of the content. (For example, under column “Content Name” type the name of the content. It can be a song name, audio clip name or audio album name, depending the content type. Under column, “Genre” type Pop if it is a Pop song, Jazz, if it’s a Jazz song etc.)
- If column names are valid and row name with the “Title/Name” doesn’t exist, then a new Content with that title will be created.
- There are certain values defined for “Content Type” and Metadata Type”, which you need follow while creating content metadata.
- For AOD (Audio on Demand) content, type “3”
- For Metadata Type, you need to put different values. “5” for “AOD Single Part”, “6” for “Multi-Part Parent” and “7” for “Multi-Part Child”. (Please view the below table)
- You can import Custom Metadata to Content Library. To import custom metadata, you need to create new columns according to the custom metadata field names and add values to the corresponding custom metadata fields. (Note: Please do not change the column name "Custom Metadata Form".)
Note: All the metadata field names are case sensitive. So, when you add the field names in the CSV/XML file type exactly the name that is present in the content form. When you add Genre, make sure to type the exact values which you have mention in the content form. For example, if you have mentioned Genre name "Jazz", then you need to type "Jazz". If you will type "jazz" then you will not be able to import.
|Content Name||Text : Alphanumeric||Yes||For Example: Despacito||The Name or Title of the Content|
3 for Audio on Demand
|Metadata Type||Numeric||Yes||5, 6 or 7||
5 for AOD Single Part Content
6 for Multi-Part Parent Content
7 for Multi-Part Child Content
|Release / Record Date||Date||No||MM-DD-YYYY||Add the Record or Release Date in MM-DD-YYYY format|
|Content Category||Text||Yes||For Example: Movie||The Name of the Content Category. This must be a valid name created prior to import For example; Pop, Rock, Jazz, Vocal etc.|
This is how your CSV/XML file will look, once you create it by following the above-mentioned instructions. (See Below Screenshot). To download Sample Metadata MS Excel file Click Here After downloading the sample file, insert the metadata information and save it. Then import the file.
Note: Please do not change/delete the column names and order in the sample MS Excel file. The columns in red color are mandatory. You need to mention the Custom Metadata fields after URL column as it is mentioned in the sample Excel. If you don't have data for other sections (For example, Genre, Language, Censor Ratings) then you can leave them blank.
How to Import Metadata
- To import content metadata, go to “Manage Content” --> “Content Library”.
- In the Content Library page, click on “Import”
- A window will open. Click on “Browse”.
- Select the CSV/XML file (Content Metadata File) from your computer
- Click on “Preview” to preview the Metadata File (Before uploading the metadata, you can check here the accuracy of the data)
- Finally, click on “Upload”. The content metadata will be added to the Content Library page of your CMS.