- As a user, I want to be able to add new keywords to the list so they are available to select on a listing
- As a user, I want to be able to add new cast member on listings so updated information can be send to listing providers
- As a user, I want to be able to remove cast member from a listings so information sent to listing providers is correct
- As a user, I want to be able to update the cast member > cast or crew image URL on a program/episode so updated information can be send to listing providers.
- As a user I want to be able to add new awards to the list of selected awards so updated information can be send to listing providers
- As an aggregator system, I want to display guiding text under each listings tab in the edit listings window
- As an aggregator system, I would like to reuse existing CTL store procedures/tables so I don't have to build from scratch
- As an Aggregator system, I want to send season/series titles and descriptions updates to Metadata Bank in real time so systems are in sync
- As a aggregator system, I want to push episode title and description updates to Metadata Bank in real time so systems are in sync
- As an Aggregator system, I want to send season/series cast updates to Metadata Bank in real time so systems are in sync
- As a aggregator system, I want to push episode cast updates to Metadata Bank in real time so systems are in sync
- As a aggregator system, I want to push series/season keywords updates to Metadata Bank in real time so systems are in sync
- Create an architectural plan to integrate Aggregator with Metadata Bank
- Discover how to integrate asynchronous Metadata Bank API call
- Derive a solution mechanism for Metadata Bank API failures
- Write use cases and payloads for sending data to Metadata Bank
- Discover how to implement SQS and Lambda for pushing data to MBank
- As a aggregator system, I will implement a process that will log alerts when the data fails to reach Metadata Bank

-

FIXES