Simple file handling can be improved when meta data is available, moreover the database based storage of meta data allows new features. As example we want to show assets can be used as reference.

TYPO3 regular technique to handle file content is to create a copy for each content element (record) where the file is inserted. This is a safe solution and there's no problem removing the original file. But this is also very limited when an editor wants to know where assets are in use on the website. Using references instead of copies gives more control over the available asset.

The DAM has experimental support for references which can be enabled with the extension manager. The submodule Media>Info>References displays a list of used assets. While the assets itself is listed it can be seen to which page and to which record the asset is linked to.

Deleting an assets which is in use as reference gives a warning and show the records where the assets is in use.

As stated in the beginning, meta data and their handling by the DAM serve many purposes associated with automatic retrieval of assets by criteria matching attributes of assets. Classic examples are image galleries and download areas, but the next step are product data management systems (PDM), like online product catalogues, e-commerce shops and the complete range of media management for print and other channels. One more hot topic is the integration with document management systems. As of today examples of almost all of these types of applications already exist and further development leading to standard DAM modules for these purposes are to surface in the mid-term.

The future of the DAM, given the rather complete list of features already or close to publication, might rather lie with the aspirations of it's parts than with the ongoing development of the whole. The core DAM will be still refined and grow through extensions built on it's API, but the most thrilling prospects are offered by applying innovations and principles introduced to TYPO3 by the DAM to other field of application. Examples might be a coherent global meta data management no longer limited to assets but stretching to generic content generated in the CMS and layered from meta data used in authoring workflows to formats catering to public display and information retrieval by external systems, such as semantic browsers.