<< back to results



pimcore GmbH


Notice: All information has been provided by the vendors themselves.

Profile Navigator

Vendor Details

Contact Name
Dietmar Rietsch
Company Profile
Managing digital assets is a huge challenge, especially due to the exponential growth of digital assets in large and small organizations. As a solid and proven open-source DAM/MAM solution, pimcore offers a comprehensive and user-friendly toolbox to manage, enrich and distribute any type of digital asset.

Manage Anything Digital
Pimcore provides a powerful central repository for any type of digital asset and its meta-data. Compatible with more than a 100 different file formats, bitmap and vector images, Office documents, PDFs and video codecs pimcore is the open-source choice for managing your enterprise assets. It is a solid DMA/MAM framework for creating highly customizable enterprise applications such as marketing management and brand portals, press and media sites to content delivery networks.

Digital curation & meta data management
There is far more to a digital asset, than just the asset itself. It has to be curated, enriched and often optimized and edited. Pimcore supports your digital curation workflow by providing the needed tools. So adding any type of structured meta data to assets is a piece of cake. By the way: Of course pimcore automatically takes care of the existing EXIF data.

It integrates just perfectly
Pimcore is only one mouse click away from your desktop: Just use WebDAV (File System) to integrate pimcore directly into your Windows or Apple environment and use your existing IT knowledge to update and work with the assets. CTO or developer? Use the programmatic XML or JSON REST interfaces to connect pimcore asset management features directly to your existing applications. It just integrates.

Contact Telephone
+43 662 876 60 62 30
Contact Email
info@pimcore.com
Company Website
http://pimcore.com
Years Trading
4
Office Locations
  • Salzburg, Austria
  • Product Name
    pimcore
    Latest Version Number
    2.2.0
    Date Of Last Release
    11/04/2014
    Documentation URL
    http://www.pimcore.org/wiki/display/PIMCORE/Pimcore+Documentation
    User group URL
    http://www.pimcore.org/board/
    Online trial link
    http://www.pimcore.org/en/resources/try-now
    Trial download or sandbox link
    http://www.pimcore.org/en/resources/download
    Company LinkedIn URL
    https://www.linkedin.com/company/pimcore
    Company Facebook URL
    https://www.facebook.com/pimcore
    Partner Network
    If the vendor operates through a sales channel they may use intermediaries who have regional focus or additional specialisms in a given vertical market.
  • Yes
  • 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.
  • Open Source
  • Open Source OSI Licence Used
    If the vendor has indicated they offer an open source or split model licence (i.e. both open source and commercial options) then for the open source element, they should be able to provide an OSI (Open Source Initiative) approved licence. If one is not specified, their product may not be genuinely open source.
    BSD Licence
    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.
  • Product is fully open source and uses no non-open source components
  • Hosting

    Software Delivery Methods
  • Installed (On-Premise)
  • 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
  • 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.
  • Windows
  • Linux
  • Mac OSX
  • Web 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.
  • Apache
  • IIS
  • 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.
  • PHP
  • Database Technology
    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.
  • MySQL
  • Search Technologies
    This refers to third party search components that the vendor uses to provide the text search features (and sometimes other related search functions).
  • Lucene
  • Other
  • 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.
  • Yes
  • 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.
  • Metadata
  • Storage
  • Asset Media Processing
  • User Authentication
  • 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
  • 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.
  • Yes
  • Metadata

    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.
  • IPTC
  • XMP
  • EXIF
  • Dublin Core
  • Embedded metadata support (writing)
    See the reading question above for more details on what embedded metadata is. This question refers to whether embedded metadata can be written back to files if edited within the DAM system.
  • IPTC
  • XMP
  • EXIF
  • Dublin Core
  • 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.
  • Yes
  • 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
  • Text area (narrative)
  • Radio
  • Checkbox
  • Date
  • File attachment
  • Numbers
  • Other
  • Cataloguing Interface Notes
    Verify how the vendor has implemented a given cataloguing interface control. It is preferable if they can demonstrate with examples of how they have implemented interface options for cataloguing and metadata entry.
    Pimcore provides a flexible and customizable data model with more than 40 different data input widgets to create custom meta-data entry interfaces.

    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?".
  • Other reports (please specify)
  • Reporting Notes
    pimcore includes a reporting engine for defining custom reports.

    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.
  • Yes
  • 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.
  • Image re-sizing
  • Image cropping
  • Format conversion
  • Flip images
  • Rotate image
  • Change colorspace
  • Effects & filters
  • Batch manipulate groups of assets
  • 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.
  • Format conversion
  • Batch operations on multiple video assets
  • Integration

    API
    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.
  • REST
  • 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.
  • FTP
  • SFTP/SSH
  • WebDAV
  • 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.
  • Yes
  • Authentication

    Authentication Support
    If you need to integrate with an existing corporate authentication service then this option will be important for you.
  • Active Directory
  • LDAP
  • 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
  • Arabic
  • Chinese (Mandarin)
  • Russian
  • Polish
  • Other
  • French
  • Spanish
  • Italian
  • German
  • Dutch
  • Norwegian
  • Swedish
  • Finnish
  • Multilingual Metadata Support
    See previous question. Most DAM systems with multi-lingual support will provide it for metadata.
  • Yes
  • Multilingual Support Notes
    The pimcore community is providing various translations for the pimcore backend. More information concerning the provided languages can be found at http://www.pimcore.org/en/community/translations

    Product Screenshots

    Log in to view screenshots.

    Product Videos

    Log in to view videos.