The DAM Playbook
This vendor does not appear in the in the DAM Playbook.
DAM 10 Core Accreditation
This vendor is not 10 Core accredited.
Contact NameJulien Fauvel
Damdy is a software provider dedicated to digital asset management and online video platforms. Built on Microsoft Azure technology, Damdy develops SaaS solutions that allow companies to manage, convert, edit and distribute their digital content to targeted audiences on all type of devices (desktop, smartphone, tablet, connected TV…).
With a centralized and secured administrative interface, companies can easily control their assets and workflows. Based in Paris and New York, Damdy has developed long-term relationships with clients in a wide range of industries: L'Oréal, Covéa, Hasbro...
Contact Telephone+33 (0)1 81 66 47 62
This is the actual turnover of the vendor in US Dollars.
Product NameCloud Media Drive
Latest Version NumberCMD v.2
Date Of Last Release23/03/2016
Online trial linkhttps://damdy.com/en/contact
Trial download or sandbox linkhttps://damdy.com/en/contact
Company LinkedIn URLhttps://www.linkedin.com/company/damdy
Clients & Customers
- Boehringer Ingelheim
- Berluti Paris
- Credit Agricole
- Banque Populaire
- Covea Group
If the vendor operates through a sales channel they may use intermediaries who have regional focus or additional specialisms in a given vertical market.
Partner Network Notes
This refers to the type of licence the DAM system software is supplied under. Proprietary means that the developer restricts access to the source code (the instructions used to generate the software). Open source means that the developer provides full access to the code so you can modify it yourself. Split model is hybrid and means they may offer both options with some restrictions removed (or added) depending on the model chosen. If split is selected, it is advisable to verify the differences with the vendor.
Licence is provided only in OPEX mode (annual rental).
Use of Open Source Components
Many DAM systems use freely available open source components to deliver key functionality. The products themselves may not be open source, however. This question will help to identify to what extent they are open source.
- Some open source components used, but core product is not open source
Software Delivery Methods
- Installed (On-Premise)
Client refers to the type of hardware or software device that can be used to access or control the DAM system.
Server Operating Systems supported
This only applies for installed or hybrid DAM systems and refers to what types of OS they can be run on. This question is less relevant for DAM systems where a third party will be hosting it for you.
Server Operating System Notes
As a SaaS solution, an internet connection is required to access to server.
The type of web server software that the DAM system can operate with. Not all DAM systems use a web server and for pure SaaS products the question is irrelevant. If you either want SaaS or non-web DAM systems, do not choose an option.
Software Development Technologies Used
This means the programming language or development technology used to implement the DAM system. This question is more important for open source software or if you have IT policy restrictions that require you to use (or not use) some technologies. It may not be relevant if you require a hosted DAM and never intend to host the system in-house.
The Database that the DAM system uses. All DAM systems require some kind of storage for asset metadata and they are usually based on an existing technology - but that may not always be a conventional database. If the DAM will be hosted by someone else (e.g. SaaS/Cloud) this question may not be relevant.
This refers to third party search components that the vendor uses to provide the text search features (and sometimes other related search functions).
Service Oriented Architecture
Service Oriented Architecture (SOA) means the vendor's product uses a modular architecture where each core DAM function is delivered as a service which can be separated out independently from other functions. It is important for large-scale Digital Asset Management implementations or more complex integration requirements.
Unique SOA Services
If the vendor uses a Service Oriented Architecture, they should be able to identify a number of unique services that are isolated from each other. Note there is overlap between with question and the one about scalable asset processing. Some vendors do not have an SOA but do offer large scale asset processing capabilities.
- Asset Media Processing
- User Authentication
SOA Other Services
- Asset Sharing
- Tracking / Analytics
- Version control
- Filtered / Keyword Search
This describes the search strategies that can be used to find assets. If you do not understand any of them, leave the options de-selected. Most DAM systems should support at least keyword search at a minimum.
- Linked Asset Search
Index/Search Text Content Of Documents
Some DAM systems can search the text content of document assets and that might be important for your DAM solution.
Embedded metadata support (reading)
Embedded metadata refers to information stored within asset files which can be searched from the DAM system. There are different standards for this type of metadata. Some image cataloguing software like Adobe Lightroom will write this data to asset files and a device like a camera may capture details also such as GPRS coordinates where an photo was shot. XMP metadata is often used with other types of files such as InDesign or PDF. If you are unsure whether this applied to you, do not check any options.
Controlled Vocabularies are predefined lists of search terms. They can be realised in many different ways but the common factor is the user picks from a restricted selection rather than enters a keyword. Most DAM systems will usually support both controlled vocabularies and keywords.
User Defined Metadata Fields
The ability to configure metadata your own metadata fields is important for DAM systems so you can assign a dedicated field for certain items of information rather than using a generic classification method or one of the vendor's own standard fields.
Cataloguing Interface Options
When cataloguing assets with custom fields, some metadata will be controlled selections, others will be free text. There are further choices like date fields, file attachments etc.
- Text field
- Text area (narrative)
- File attachment
Business Intelligence & Reporting
Asset Usage Records
To enable reports to be generated, DAM solutions must retain records of asset usage, including searching, download and editing of records. The reporting should include the user who carried out the activity and the date/time it occurred.
A detailed audit trail that logs every user action in a central record is useful to gain insight into user behaviour. Comprehensive audit trails allow DAM system users to produce reports that address their unique needs.
A range of built-in reports that you can quickly generate is useful to answer common questions such as the "what is our most popular asset?".
- Most popular assets by download
- Most active users by uploads
- Most active users by downloads
- Average number of search results returned over a given period
- Asset search to download ratio
- Download activity over a given period
- Login activity over a given period
- Popular search terms
Thanks to our reporting system, we can provide on-demand dashboards and reports.
Dedicated/Scalable Proxy or Derivative Asset Generation
Nearly all DAM systems will generate thumbnails and previews of media, including more dynamic types like video or audio. Some products use a separate server to do this which usually makes them more suitable for large scale asset ingestion and processing.
Multi-Page Document Asset Previews
If you deal with document oriented assets, having a solution which can generate multi-page previews (and also zoom in on them) can save the hassle of downloading a file only to discover it is not the one you need. For assets with very similar content, this can be a useful feature.
Many DAM systems allow users to manipulate images by resizing, cropping etc. Choose any features which are important to your users.
Some DAM systems may allow video assets to be converted or modified. If that is a potential requirement for you, specify those features which are likely to be needed. EDL = Edit Decision List and refers to providing in/out points when editing video footage.
- Format conversion
- EDLs and editing features
- Timeline metadata
- Batch operations on multiple video assets
Importing metadata is an important feature if you have either legacy assets or metadata is generated using some other tools (for example a spreadsheet). Not all systems offer this, but usually if the feature is not available, the vendor will be able to carry out batch importing for you via professional services (note: this will usually incur a cost, unlike a built-in capability).
Metadata Import Formats
This question only applies if the vendor has features to import metadata. There are common formats like CSV, XML and Excel which DAM solutions may support. If this is a requirement you are likely to make frequent use of, it is essential to verify whether the product supports the formats you typically work with.
- CSV (or any delimited file)
- Excel (XLS or XLSX)
As well as importing metadata, sometimes it is important to be able to export sections of it to conduct further analysis in third party applications. Not all products support this, but usually it will be possible to request the vendor provides an export via professional services (although a fee may be charged).
Metadata Export Formats
This question only applies if the vendor has features to export metadata. There are common formats like CSV, XML and Excel which DAM solutions may support. If this is a requirement you are likely to make frequent use of, it is essential to verify whether the product supports the formats you typically work with.
- CSV (or other delimited file)
- Excel (XLS or XLSX)
API means Application Programming Interface and allows third party software to control a DAM system. If you intend to integrate your DAM with another existing solution then you need to choose the API protocol that is compatible with that.
Many DAM solutions will now allow assets to be stored on the server of Cloud storage providers. This allows asset files to be distributed and/or integrated with other solutions. Some third party services use generic protocols like FTP, others are proprietary.
Scripting & Plug-Ins
Some advanced DAM solutions have a scripting capability that allows users or third parties to add functionality which the vendor did not originally envisage. Usually programming skills will be required to use this, but some tools have visual interfaces also.
In addition to scripting (or sometimes instead of), some DAM solutions will have a plug-in architecture that allows third party developers to extend the core platform.
If you need to integrate with an existing corporate authentication service then this option will be important for you.
Multilingual Application Interface Support
The interface means the controls to use the DAM system. This is different from the metadata support which is usually entered by end users when cataloguing assets.
Multilingual Metadata Support
See previous question. Most DAM systems with multi-lingual support will provide it for metadata.
Multilingual Support Notes
Our back office is avalaible in English and in French.
Our front-end can be in any language.
File versioning refers to the digital media associated with an asset record. This is usually the minimum requirement for a DAM system to claim support for versioning assets. See also responses to the related question about metadata versioning below.
Metadata versioning is separate from the files associated with assets. Many DAM solutions will track updated digital assets but only retain a single current version of the metadata. Since metadata is likely to be edited many more times than assets get replaced, this can be an important point to check.
Independent Metadata And File Versioning
This questions assesses whether the solution allows versions of either the file or metadata to be reverted independently or if both are linked to a single shared version instance.