Magnolia 4.5 reached end of life on June 30, 2016. This branch is no longer supported, see End-of-life policy.

Page tree
Skip to end of metadata
Go to start of metadata

Digital assets such as documents, images and videos can be stored in the document management system (DMS). Assets stored in the DMS can be used on Web pages, for example to display an image on the page or to link to a downloadable document. DMS asset metadata is based on the Dublin Core standard. The dms workspace is also accessible using CMIS.

Benefits

The benefits of storing files in the DMS and using them on the website are:

  • Centralization: The DMS provides a centralized location for assets that can be used across different pages in a website or different websites in a Magnolia instance.
  • Time saving: STK components take advantage of the meta data defined in the DMS asset such as using the title of an image asset as its caption when displaying the image on a page.
  • Re-use: The same asset can be used in many locations of the site.
  • Consistency: Updating a single asset in the DMS propagates to all pages where the asset is used.
  • Standardization: The same file properties are used each time the file is referenced. You can make the metadata fields mandatory to ensure editors include relevant content.
  • No broken links: When assets are moved within the DMS, links pointing to them are updated automatically.

Integration

The dms workspace can be accessed with Content Management Interoperability Services (CMIS). This specification is aimed at improving interoperability between enterprise content management systems. CMIS makes it possible to access and edit documents in the DMS using applications such as SharePoint, Alfresco and Photoshop. Further information on CMIS can be found at the OASIS website and the CMIS page on Wikipedia. Watch a video on CMIS integration.

Customizing the DMS

The DMS is a community module and its source code is freely available. A typical customization task is to set restrictions on the file size or type that users can upload into the DMS. This is not configurable behavior but a developer can change the code.

Customizing typically involves the following steps:

  1. Locate the Java class that is responsible for the behavior you want to change.
  2. Extend the class with your custom code.
  3. Add a configurable property such as allowedFileExtensions in AdminCentral so that changes are easier the next time.

For example, to get the file type and size of an object stored in the DMS:

import info.magnolia.module.dms.beans.Document
content = MgnlContext.getHierarchyManager("dms").getContent("/your/path");
Document doc = new Document(content);
doc.getFileSize()
doc.getMimeType() or doc.getFileExtension()

Digital assets such as documents, images and videos can be stored in the document management system (DMS). Assets stored in the DMS can be used on Web pages, for example to display an image on the page or to link to a downloadable document. DMS asset metadata is based on the Dublin Core standard. The dms workspace is also accessible using CMIS.

Benefits

The benefits of storing files in the DMS and using them on the website are:

  • Centralization: The DMS provides a centralized location for assets that can be used across different pages in a website or different websites in a Magnolia instance.
  • Time saving: STK components take advantage of the meta data defined in the DMS asset such as using the title of an image asset as its caption when displaying the image on a page.
  • Re-use: The same asset can be used in many locations of the site.
  • Consistency: Updating a single asset in the DMS propagates to all pages where the asset is used.
  • Standardization: The same file properties are used each time the file is referenced. You can make the metadata fields mandatory to ensure editors include relevant content.
  • No broken links: When assets are moved within the DMS, links pointing to them are updated automatically.

Integration

The dms workspace can be accessed with Content Management Interoperability Services (CMIS). This specification is aimed at improving interoperability between enterprise content management systems. CMIS makes it possible to access and edit documents in the DMS using applications such as SharePoint, Alfresco and Photoshop. Further information on CMIS can be found at the OASIS website and the CMIS page on Wikipedia. Watch a video on CIMIS integration.

Customizing the DMS

The DMS is a community module and its source code is freely available. A typical customization task is to set restrictions on the file size or type that users can upload into the DMS. This is not configurable behavior but a developer can change the code.

Customizing typically involves the following steps:

  1. Locate the Java class that is responsible for the behavior you want to change.
  2. Extend the class with your custom code.
  3. Add a configurable property such as allowedFileExtensions in AdminCentral so that changes are easier the next time.

For example, to get the file type and size of an object stored in the DMS:

import info.magnolia.module.dms.beans.Document
content = MgnlContext.getHierarchyManager("dms").getContent("/your/path");
Document doc = new Document(content);
doc.getFileSize()
doc.getMimeType() or doc.getFileExtension()

See also the DMS module Javadoc and Creating custom controls.

  • No labels