36 results found
-
Set Focal Point by API
Allow focal point to be configured by API
Currently it can only be set from the CMP UI which makes an API call to
PUT https://cmp.optimizely.com/api/v3/library/image/<id> with the body:
{ "focal_point": { "x": <value>, "y": <value> } }
The DAM API endpoint https://docs.developers.optimizely.com/content-marketing-platform/reference/patch_images-id should allow us to send this as well.
4 votes -
Free text/number fields do not show in the filtering panel in DAM
Note from Rob Driscoll in https://optimizely-ext.atlassian.net/browse/DAM-4268 - "Free text/number fields do not show in the filtering panel. Will need a feature request to support that."
2 votes -
Display Out of the Box Metadata in Column View in DAM For Auditing
Make OOB fields like "Enable Search Engine Indexing," "Description," and "Alt Text" available to add to the columns in the Library. I need to audit these fields and there are limitations on reporting. I would like to use the columns to visually audit assets as well as exporting a csv.
2 votes -
Support for renditions for .eps files
Request to be able to create renditions from uploaded .eps files in the DAM. Currently only supports PNG, JGP, and WEBP
4 votes -
Selecting All Assets Requires One Asset To Be Selected
In order for the select all option to appear, one asset needs to be selected first. Can the select all just always be available?
4 votes -
Enable Drag-and-Drop Folder Navigation and Asset Relocation After Bulk Upload
When users perform a bulk upload of assets into the DAM, they typically upload all files into a single, temporary folder (e.g., “Bulk Upload”). Afterward, users need to organize these assets into their proper folders within the DAM catalog structure.
Currently, the process requires opening multiple folders and manually moving each file, which is time-consuming and inefficient, especially when dealing with large batches of assets.
Users need an intuitive and efficient way to organize assets after bulk upload. This should include:
1)The ability to see the folder structure as a tree view in the DAM interface.
2)The ability to drag…
2 votes -
I want to have the assets which have been uploaded into the DAM tagged by the ai
We are going live with CMP and loading all our existing Assets into the DAM, but none of the assets which are loaded using the API are being automatically tagged by AI with the contents of the images.
1 vote -
Create ability to duplicate collections
It would be helpful to be able to copy a collection to retain the cover photo and description and simply updating the collection name.
4 votes -
Collection view filters collapse when moving between collections
The filters collapse when moving from once collection to the next. It would be helpful for them to remain intact from the previous search.
3 votes -
Switching between views consistency
When switching between List view and Grid view in the Library, the system does not retain the current page position.
Steps to Reproduce:
Navigate to the Library.
Go to a later page (e.g., page 638).
Switch the view from Grid to List (or vice versa).
Expected Result:
The system should stay on the same page (e.g., page 638) after switching views.Actual Result:
The system resets to page 1, causing the user to lose their place in the list of assets.Impact:
This significantly disrupts workflows when managing assets across multiple pages, especially for large libraries.1 vote -
Public URL for collection based on rendition
When sharing a URL based on a rendition if the user selects all and downloads the zip file, the files are not based on the rendition. The files in the zip file are the original file. The user can only get the rendition image by clicking each file and downloading them individually.
If a URL is based on a rendition, the end user should be able to download all files in that rendition and NOT the original image.
2 votes -
Collections download one image and it's zipped
When looking at a collection via the public link, you can select one or more files. If you select just one file, that file is zipped. It would be preferred to download just the single file not in a zipped folder.
3 votes -
add non-mandatory fields to the uploader
Currently only mandatory fields can be shown during the upload function. It would be very helpful to also have not mandatory fields which can be filled already during the upload.
If you upload multiple assets it is very time consuming that you need to edit the assets afterwards once again in order to fill all the non-mandatory fields as well.1 vote -
collections - Upload
The ability to create a collection with the option to upload content, this would be more efficient for content for specific events or projects removing the complications of email or ftp/dropbox
1 vote -
collections - uploads
We have used in other DAM systems and would like to have in this one the ability to share a collection with the ability for our clients to upload to a collection. Extremely handy for event or project specific content and much easier than email file transfer or dropbox.
1 vote -
Brand template remove non-related brand assets
Controls for admins to remove non-brand fonts, colours, templates (or at least to hide)
1 vote -
Related assets removal on the image level
Each image in the library includes a set of related assets with various crop formats (e.g., portrait 9:16, square 1:1, etc.). However, not all crop types are suitable for every image — some may only support landscape or portrait orientations. The system should therefore allow users to remove any related assets or crop variations that are not applicable to a specific image.
1 vote -
When creating the template, the Library should show the folders structure
When users create a template in Optimizely DAM and select an Element that requires choosing an asset (via the Library option), the current behavior displays all assets from Optimizely DAM in a single view.
This makes it difficult to find specific assets, especially in large repositories, as users must scroll through an unfiltered, unstructured list.
Requirement: Improve the asset selection experience by displaying the DAM root catalog structure with nested folders (as configured in Optimizely DAM) instead of showing all assets at once.1 vote -
Make Name & Alt text mandatory fields when user uploads the asset
Currently, when users upload an asset (e.g., image, video, or document) into Optimizely DAM, they can click “Apply” and complete the upload process without filling in key metadata fields such as Name and Alt Text.
This results in inconsistent metadata, accessibility gaps, and difficulty in content management and asset retrieval. Ensure all assets uploaded to Optimizely DAM contain complete and standardized metadata by making the fields “Name” and “Alt Text” mandatory during the upload process.This change will:
Improve content accessibility and compliance with WCAG standards.
Enhance searchability and asset management within DAM.
Support brand consistency across all markets.
1 vote -
Request for Enhanced Flexibility in Asset Ownership Settings
We’d like to suggest adding more flexibility around asset ownership assignment. Currently, the person who uploads an asset is automatically set as the owner, but we want the ability to preset or designate asset owners separately. This is important because asset owners receive “request to edit” emails, and we want to prevent these notifications from going to non-admin users that might be the asset owners. Typically, users request edit access when they actually only need to download the asset, leading to unnecessary owner involvement and incorrect permission assignments. Allowing preset ownership would help streamline this process. reduce confusion and ensure…
2 votes
- Don't see your idea?