4 results found
-
Browser back in library
Navigating folders isn't as intuitive as you might expect. Specifically browser back doesn't take you back up a level of the structure and instead to the page viewed before the library.
This is a fundamental usability flaw of the system behaviour not aligning with the user's mental model. As I user if I have progressed one step deeper into folders then the back button should do the reverse.
We've had many internal users report frustration with this
8 votesThis idea has caught our attention and is now being reviewed by our product and design teams. We're assessing what’s possible, mapping out user journeys, and considering how this could fit into the overall experience. More updates to come as we explore solutions.
-
Face Recognition Capability for Asset Management and GDPR Compliance
We manage a large number of digital assets (images and videos) containing identifiable individuals. Under GDPR, these assets are considered personal data and require proper consent management, traceability, and the ability to identify and remove or restrict usage upon request.
Currently, there is no functionality in the DAM to automatically identify individuals within assets, which makes manual compliance checks time-consuming and prone to human error.
Functional Requirements
Automatic Detection:
The DAM should automatically identify human faces in uploaded assets (images/videos).
Detected faces should be visually highlighted and optionally labeled.
Consent Linking:
Each identified individual should be linkable to a stored…
3 votesThis idea has caught our attention and is now being reviewed by our product and design teams. We're assessing what’s possible, mapping out user journeys, and considering how this could fit into the overall experience. More updates to come as we explore solutions.
-
Rendition selection as URL parameter
As a Solution Architect, I see how a lot of customers and prospects select assets from the DAM and it's a common use case to select a main image for a page and then want different renditions for things like page listings and teasers to that page. Currently the author would have to select a series of renditions manually. It would be much easier to be able to add the rendition name to the URL like this: https://images.cmp.optimizely.com/assets/rob?rendition=teaser
6 votesThis idea has caught our attention and is now being reviewed by our product and design teams. We're assessing what’s possible, mapping out user journeys, and considering how this could fit into the overall experience. More updates to come as we explore solutions.
-
Ability to add alt text in multiple languages in DAM
We are using the CMS asset picker to select images from the CMP DAM.
Currently, the alt text can be added to assets in the DAM in one language only.
We operate in 27 languages (= 33 distinct country websites and often re-use images in the DAM across markets. As it stands, there is no easy way for us to add alt text in multiple languages to an asset.
Our product recommendation:
* Alt text field to allow a default language + multiple language translations, generated with AI and editable.
* Alt text translations to automatically pull through to the…8 votes
- Don't see your idea?