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

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

The DAM provides full functionality to manage assets.

Views

The view icons open different views of the assets stored in the DAM:

  • Tree view: Displays a hierarchical tree, including the folder structure.
  • List view: Displays the items individually. You can sort them alphanumerically by clicking the column headings.
  • Thumbnail view: Displays thumbnail images of the assets. There is a zoom control at the top for resizing.

Searching

The search box provides a simple search. The asset name, metadata and content of documents are indexed for search. You can use the search function in any view. Type the search term in the box and Enter or click . The results display in list view and a Path column is included to help you locate the asset in the tree. If you select an item in the results and return to tree view the item remains selected.

Uploading

Single assets

To upload an asset:

  1. Select a parent folder or upload the image at the root level.
  2. Click Upload asset.
  3. Select a file to upload or drag and drop it into the Media field.
  4. The file uploads.
  5. For images, the image details and a thumbnail displays. You can edit the image in Magnolia.
  6. For other assets, the file details and an asset type icon displays.

Multiple assets

Multiple asses can be uploaded in ZIP format. Magnolia extracts the files to the DAM.

To upload multiple files in zip format:

  1. Select the parent folder or upload the zip at the root level. 
  2. Click Upload Zip Archive.
  3. In the Encoding field select your operating system - Windows (CP437) or Mac (UTF-8).
  4. Save.

Uploading images in other apps

You can upload and edit images directly in other apps that use them. For example when creating a new contact in the Contacts app. The procedure and actions are identical to those in the Assets app and function in exactly the same way. (warning) App-specific metadata fields are available. These differ from the metadata fields available when uploading in the Assets app.

Downloading

(warning) Magnolia 5.2.5+

To download an asset from the DAM, use the Download asset action in the browser or edit dialog. The action opens the download dialog of your operating system where you can save the file to your computer.

Deleting

Versioning is enabled in the DAM. This allows you to restore previous versions of an asset or folder. The delete action marks the node for deletion and the deletion is completed on publication of the deletion.

To delete an asset or folder:

  1. Select an item.
  2. Click Delete folder/asset.
  3. Confirm your action in the dialog.This marks the node for deletion and creates a restorable version. The item icon (folder or node) is replaced with the trash bin.
  4. Click Publish deletion to complete the deletion. At this point you can cancel the deletion by clicking Restore previous version.

Metadata

The metadata fields are located in the Asset dialog. You can set metadata when uploading or add/edit it by clicking Edit asset to open the dialog.

Magnolia metadata

The system records certain data automatically and the content of these fields typically cannot be edited and are disabled. By default, the following fields cannot be edited (those marked with an * are not currently used) :

  • Describe asset using *: The supported metadata standard. By default, the Simple Dublin Core Metadata Element Set (DCMES) is supported. You can customize Magnolia to support different standards.
  • Identifier: An unambiguous reference to the resource within a given context. An alphanumerical string is used to identify and reference the asset. Editors can move assets without breaking links in the DAM.
  • Type *: The nature or genre of the resource.
  • Creation Date: Date of upload.
  • Modification Date: Date of last modification.
  • Creator *: An entity primarily responsible for making the resource..

Dublin Core metadata

Magnolia supports the Simple Dublin Core Metadata Element Set (DCMES) standard by default and the following fields are available:

  • Caption: The asset caption.
  • Language: Language tag of the asset. Recommended best practice is to use a controlled vocabulary such as RFC 4646.
  • Title: Asset title.
  • Subject: The topic of the asset. Typically, the subject will be represented using keywords, key phrases, or classification codes.
  • Coverage: Scope of the asset. Typically this refers to a place, period or jurisdiction.
  • Description: Full description of the asset.
  • Publisher: Original publisher of the asset if being republished from another source.
  • Contributor: Use to name asset contributors.
  • Rights: Type of copyright.
  • Source: A related asset from which this asset is derived.
  • Relation: Related assets. 

Setting alt attributes

The alt attribute of the img tag specifies alternative text for an image when that image cannot be displayed on a page. The standard rule is to use concise text that serves the same function as the image. The Standard Templating Kit (STK) offer multiple possibilities for setting alt attributes. Where no specific alt attribute is set by an editor, the STK uses either the title information or other metadata to derive an alt attribute. It achieves this by working through a chain of properties.

The following tables show how alt values are derived for areas and components. For example, the stkPromo component first looks for an alt text in the Title field in the Promo edit dialog. If it doesn't find a value, it takes the title of the target page. If the target page does not have a title either, then the component uses the name of the target page.

Area or componentAlt value chain
areas/branding/areas/logo
  1. Alternative Logo Text field in the home page properties dialog.
  2. Site Title field field in the home page properties dialog.
areas/main/areas/intro
  1. Subject field in the asset properties dialog.
  2. The page title prefixed by an Image string.
  3. The page name.
/extras/stkExtrasDownloadFile
  1. Title field in the component dialog.
  2. Title of the target document in the asset properties dialog.
  3. Name of the target document in the DMS.
/features/stkImageGallery
  1. Title of target image.
/features/stkNewsOverview
  1. Title of the target item in the component dialog.
  2. Name of the target item in the DMS.
/footer/stkFooterAbout
  1. Title of the target image in the component dialog.
  2. Name of the target image.
/macros/image macro
  1. Image Caption field in the Text & Image component dialog.
  2. Subject field in the asset properties dialog.
  3. Title "field" in the DMS.
/promos/stkPromo
  1. Title field in the promo dialog.
  2. Title of the target page.
  3. Name of the target page.
/stages/stkStageXL
  1. Title field in component dialog.
  2. Title of the target page.
  3. Name of the target page.
/teasers/stkTeaserContact
  1. Photo Alt Text field of the Contact data image dialog.
/teasers/stkTeaserCarouselItem
  1. Title field in component dialog.
  2. Title of the target page.
  3. Name of the target page.
/extras/stkExtrasExternalPage
  1. Title field in component dialog.
  2. Link to the external page.
/teasers/stkTeaserFingerTabbedItem
  1. Title field in component dialog.
  2. Title of the target page.
  3. Name of the target page.
/teasers/stkTeaser
  1. Title field in component dialog.
  2. Title of the target page.
  3. Name of the target page.
/teasers/stkTeaserNewsList
  1. Title of the target item.
  2. Name of the target item.
/teasers/stkTeaserPureLinkList
  1. Teaser Title field in component dialog (required).