World is now on Opti ID! Learn more

Per Nergård (MVP)
Nov 29, 2015
  1305
(0 votes)

Validation of media file attributes

As all of you know media files in EPiServer are IContent which lets us add properties to handle for example meta data. This is great but how do we make the editors fill in those fields...

I guess that it depends a lot of what type of target audience you have as well as what fits the site editors. 

The below could be alternatives to consider:

  • You don't do anything at all
    Obviously not recommended.

  • You add fallbacks in the code so atleast some is used.
    Could be ok, but "real" meta data is better.

  • You make the field required and disable auto publishing of mediafiles.
    I don't like this because it seems a bit to hard on the editors. It should be easy to add a bunch of images without needing to process them all at once.

  • You try to add som other validation before publishing pages or blocks that use media files.
    If you block publishing I guess this is basically as hard on the editors as the previous option but to me it still feels as a better way.

To solve the last option I did a small validation class that checks all ContentReference and ContentArea properties on a page, checks if it's an image and then checks if the Copyright attribute is empty or not (Did this in the Alloy demo site). If youn're using Url properties with a media file UIHint it's easy to add.

You can get the code over at Gist. You can see the result below where I added a image with no Copyright info into the Teaser Image property.

Image ValidateImageFileExample.jpg

Nov 29, 2015

Comments

Please login to comment.
Latest blogs
Make Global Assets Site- and Language-Aware at Indexing Time

I had a support case the other day with a question around search on global assets on a multisite. This is the result of that investigation. This co...

dada | Jun 26, 2025

The remote server returned an error: (400) Bad Request – when configuring Azure Storage for an older Optimizely CMS site

How to fix a strange issue that occurred when I moved editor-uploaded files for some old Optimizely CMS 11 solutions to Azure Storage.

Tomas Hensrud Gulla | Jun 26, 2025 |

Enable Opal AI for your Optimizely products

Learn how to enable Opal AI, and meet your infinite workforce.

Tomas Hensrud Gulla | Jun 25, 2025 |

Deploying to Optimizely Frontend Hosting: A Practical Guide

Optimizely Frontend Hosting is a cloud-based solution for deploying headless frontend applications - currently supporting only Next.js projects. It...

Szymon Uryga | Jun 25, 2025

World on Opti ID

We're excited to announce that world.optimizely.com is now integrated with Opti ID! What does this mean for you? New Users:  You can now log in wit...

Patrick Lam | Jun 22, 2025

Avoid Scandinavian Letters in File Names in Optimizely CMS

Discover how Scandinavian letters in file names can break media in Optimizely CMS—and learn a simple code fix to automatically sanitize uploads for...

Henning Sjørbotten | Jun 19, 2025 |