Watson Marketing Ideas

Submit new product ideas for Campaign, Interact, Marketing Operations, Marketing Platform, Campaign Managed Hosted, interact Managed Hosted, Marketing Operations Managed Hosted, Digital Analytics, Tealeaf, Universal Behavior Exchange, Watson Customer Experience Analytics, Watson Marketing Insights, Watson Content Hub, Web Content Manager and WebSphere Portal solutions. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed.

Connect with your peers and IBM experts on the Watson Marketing and Commerce Community

Submit ideas for other Watson Customer Engagement Products:

•  Watson Campaign Automation
Watson Commerce
Watson Supply Chain

Ability to Add Custom Meta Data Fields to Assets

We would like to attach meta data fields beyond tags and categories to include fields such as the date an asset was last requested from one of our websites in order to automate usage trackingAnother example, would be to maintain a list of website URLs where the asset is being called. Due to the nature of that data, we do not want to use categories or tags for this information as this would add data clutter. Ideally, we would use automation scripts to populate this data and be able to view / filter this data via the web UI.  

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Dec 10 2018
  • Under Consideration
How will this idea be used?

The ability to populate asset usage and filter this data through the web UI or JSON structure would allow us to easily identify which assets are not being called so we can retire unused assets and maintain our DAM’s integrity. 

What is your industry? Education
What is the idea priority? Urgent
DeveloperWorks ID
Link to original RFE
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    31 Jan 00:04

    I would suggest using a content item to 'wrap' the asset here. The content item can contain any additional meta data for the asset that you like. 

    Treat the assets plus the wrapping content as the "DAM". 

    For instance, the content item could have a multiple value link element that lists where the asset is used. This element can be made searchable to query on this element. The Public API can be used to automate management of the content. The "View associations" ui can be used to navigate between the asset and the wrapping content. The wrapping content would have an image/video/file element to reference the asset that it is wrapping.

    A date element in the content can be used to track the usage.

    Does this satisfy the requirement? Suggest we close this item if so.