Editorial Checklist for Merlin & COVE

This section displays best practices when handling metadata.


Metadata best practices

Metadata Label


Titles should follow the AP Style Guide and read like headlines to engage the user. For full episodes with disparate segments, such as a weekly news program, use this convention: “Friday, Mar. 25, 2011.

Don’t include station call letters, the content channel title, or episode numbers. Avoid using just one or two parts of speech, such as “Native American Textiles.” (Are they valuable, rare, complex - what?) Don’t only use names “Alessandro Ragonese - Part 1.”

Short Descriptions

Short descriptions should express the essence of the piece written as a full sentence.

Don’t repeat the title or just list items (names or keywords).

Long Descriptions

Should lead with a hook (a quote, trends, event.) Close by describing the feature and engaging the user, such as “In this interview / panel / episode, find out more about x.”

Don’t just list the biographies of interview subjects; lead with their comments.


Should be limited to two and explicitly reflect the concepts expressed in the title, image, and description.

Don't dilute content by over selecting topics.


Should be JPG or PNG files at a 16X9 ratio sized at 640x360 px, 1280x720 px, or 1920x1080 px.

Don’t repeat images, include text, such as the program title, or use blurry screen grabs.


Include three choices that can all be selected, if desired.

  • Publish date is the time of backend ingestion and the default to go live. 
  • Availability date goes live at a designated time in the past, present or future.
  • Expiration date pulls the content from the front end. Removing the expiration date refreshes the content on the front end.

Don't forget to select a date.