Adding a hero description field on asset level

More Details from customer 2022-09-06

Last Friday Anders Lindberg and the team (Lukas Skoglund and Johan Spaedtke) had a quick meeting with the customer to better understand the request.

It is now reasonably clear what they want:

• One more description field on the assets that they may use for this “promotional” text.

• The text should be set during the asset ingestion process but also possible to manual edit in the customer portal

• Client apps will retrieve the new description by requesting the asset metadata (no need to have this data surface as part of the hero banner metadata)

Given above, the following work (at least) would be required

• Add one more asset field for the description. If I understood correctly, there is already a field call extendedDescription that is suitable to use but this field need to be configured and enabled for Nordisk Film (it is currently not available)

• Adapt the asset ingestion adapter to support this new metadata field. The adapter would need to pick this data from the NF metadata API and set it per asset on RBM side.

• Something else

First request from the customer:

On our hero components we add a free text description about the movie, in order to make it more compelling to the user to watch the movie.

Currently for WEB, iOS and Android we write this description in to the component itself, but that will not work for TV apps which we introduce in September. Also, we wish to control this from one place, so that we don’t need to add and edit this text multiple times.

We request that you add a free text field on assets in our CMS, which our frontend vendor, then can use to retrieve the text for all our platforms.
It could be added under “Basic Information”.

We have texts ready for this field from our product database, PDB, and we would like to have texts from PDB imported to this field for our assets, just like we do on other fields on assets.

If possible, it would be great if we can overwrite the description from assets in the components if needed, in case we show the asset on another channel where another description may be more compelling.