Report Vendor Profile

<< Back to Vendors


  All profile information has been provided by the vendors themselves and they are responsible for both its accuracy and validity.

Edisen

Profile Index

    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.

    Vendor Details

    Contact Name
    Anne Davis
    Company Profile
    Edisen is an easy-to-navigate digital asset management platform where organizations can centralize their creative content and workflows. With Edisen, users can securely store, share, and repurpose all forms of marketing collateral, such as images, videos, PDFs, and office files. Organizations can also use Edisen to collaborate worldwide to streamline the creation and distribution of content and campaigns. By enabling a more efficient marketing process,Edisen allows companies to save significant time and money and get campaigns to market faster.

    Store, Search & Share

    With Edisen, organizations can store and share a variety of media types including images, videos, PDFs, and office files. Keywords and metadata can be added to each piece of content and library to ensure fast and efficient search.

    Collaboration,Commenting, & Notifications

    Edisen features a strong feedback system for global teams. Users can comment directly on assets and libraries to maintain a centralized communication loop.

    Libraries & Channels

    Organizations have the option to organize assets via user-named Libraries. For additional organizational purposes, users can create Folders within the Library space.

    Security & Permissions

    Edisen is focused on industry-leading safety and security of content and media. Users have the ability to set permissions on assets and allow only certain people to view, edit, or administer designated content.

    Contact Telephone
    1-844-433-4736
    Contact Email
    info@edisen.com
    Company Website
    https://edisen.com
    Company Turnover Category
    The turnover of the vendor can give an indication of their size. US Dollars is used as common currency to allow comparisons. Note that turnover is not necessarily any indicator of financial stability but as part of any procurement due diligence you are obliged to carry out by your organisation, any vendors who have not agreed to show their turnover here might be required to do so if subsequently appointed.
    • $500k - $1m
    Percentage of Revenue From DAM Software
    A vendor might have a large turnover and many employees, but their DAM software division is a very small element of what they offer. If a large proportion of their revenue comes from DAM solutions (licenses, support, hosting, consulting etc) then this may mean they are more specialised, but also there are risks to their overall financial stability if there is a downturn in the DAM software market.
    100
    Number of Full-Time Employees
    Along with turnover, the number of full-time employees gives an indication of the size of the vendor. Note that although a firm might have many employees, not all of them might be dedicated to developing DAM solutions, so this cannot be relied on in isolation.
    40
    Office Locations
    • San Diego, CA
    Product Name
    Edisen
    Company LinkedIn URL
    https://linkedin.com/company/edisen-llc/
    Company Facebook URL
    https://facebook.com/Edisen-1026494320824837/

    Licensing

    Licensing Model
    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.
    • Proprietary
    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.
    • No open source components used

    Hosting

    Software Delivery Methods
    • Cloud/SaaS

    Technology

    Client
    Client refers to the type of hardware or software device that can be used to access or control the DAM system.
    • Web client
    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.
    • No
    Service Oriented Architecture Definition
    Some vendors have widely differing opinions of what Service Oriented Architecture means. Their response to this question allows you to understand if their definition concurs with your own. If you are not contemplating a large scale DAM implementation or one with many complex integration requirements, SOA may not be relevant to your needs.
    N/A

    Microservices
    Microservices are similar in nature to Service Oriented Architecture (SOA) with the key difference being that they can be deployed entirely independently of the platform that uses them. Microservices are usually prevalent in Digital Asset Supply Chain projects.
    • No
    Microservices Definition
    As with Service Oriented Architecture (SOA) some vendors have different opinions of what microservices are. Their response to this question allows you to understand if their definition concurs with your own. If you are not contemplating a Digital Asset Supply Chain project, large scale DAM implementation or one with many complex integration requirements, microservices may not be relevant to your needs.
    NA

    Search

    Search Features
    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.
    • Keyword
    • Folders
    • Filters
    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.
    • No

    Metadata

    Controlled Vocabularies
    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.
    • No
    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.
    • Yes
    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
    • Checkbox
    • Other

    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.
    • Yes
    Audit Trail
    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.
    • Yes
    Built-In Reports
    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?".
    • No reporting features

    Asset Processing

    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.
    • No
    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.
    • No

    Asset Manipulation

    Image Manipulation
    Many DAM systems allow users to manipulate images by resizing, cropping etc. Choose any features which are important to your users.
    • No image manipulation features
    Video Manipulation
    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.
    • No video manipulation features

    Data Import/Export

    Importing Metadata
    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).
    • Yes
    Exporting Metadata
    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).
    • No metadata export capability

    Integration

    Hooks
    Hooks are related to APIs but are initiated by the application rather than by an external application making the request. Hooks allow other actions to be initiated based on events, for example if a user downloads an asset, an action can be commenced to notify another application that this has taken place (along with the ID number of the asset, date/time etc).
    • No
    Hooks Targets Supported
    In most DAM applications that support them, hooks are initiated as web requests, so the system will call a given external URL and provide some parameters. Some solutions also support initiating scripts or applications which can run on the server where the system is hosted.
    • N/A (hooks not supported)
    Hooks Definition
    If the vendor claims support for hooks, check how they define them and see if their interpretation concurs with your own. A reasonably detailed explanation along with citations/links should be given here.
    NA

    Storage Integration
    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.
    • Amazon S3

    Scripting & Plug-Ins

    Scripting Capabilities
    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.
    • No
    Plug-In Support
    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.
    • No

    Multi-Lingual Options

    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.
    • English
    Multilingual Metadata Support
    See previous question. Most DAM systems with multi-lingual support will provide it for metadata.
    • No

    Version Control

    File versioning
    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.
    • Yes
    Metadata versioning
    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.
    • No
    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.
    • No

    Profile Last Updated: 24/10/2018
    Top

    << Back to Vendors



      All profile information has been provided by the vendors themselves and they are responsible for both its accuracy and validity.