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 NameDedrick Wright
Pixfolia is a lightweight web based Digital Asset Management solution built using Microsoft technology for businesses and organizations who require a simple and easy to use digital asset management solution. Our asset management solution was designed to take the burden of managing digital assets and make it easier to organize, search, share, categorize and view all your assets in one place. Dynamically change current streamlined processes for the better with a solution that will improve productivity, better asset organization and easy distribution of your digital assets.
Whether you are in need of a SaaS (Software as a Service) or In-House digital asset management solution, we got you covered. Pixfolia can either be installed on one of our dedicated servers with top of the line security to secure your assets or easily deployed in-house.
With simplicity in mind to not only streamline the workflow of managing digital assets, our solution also increases productivity by giving users the ability to quickly search for specific assets. Our asset management solution provides the ability to re-purpose, share and redistribute virtually any in-house media type to external and internal customers.
Product NamePixfolia Enterprise
Latest Version Number4.0
Date Of Last Release10/07/2013
Online trial linkhttp://www.pixfolia.com/products/getting-started/
If the vendor operates through a sales channel they may use intermediaries who have regional focus or additional specialisms in a given vertical market.
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.
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.
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).
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.
- IPTC Core
- 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 Core
- Dublin Core
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.
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.
Many DAM systems allow users to manipulate images by resizing, cropping etc. Choose any features which are important to your users.
- Image re-sizing
- Format conversion
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
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.
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.