Create a Digital Asset Type

A digital asset type defines the file media types that a digital asset or business document can store and the structure of attributes (metadata) to describe the asset. You must be a content administrator to create digital asset types and share them with others.

Oracle Content Management includes several digital asset types out-of-the-box with predefined groups of media types:

Image—this asset type supports all known to Oracle Content Management media types for images. You can use it out-of-the-box for managing image files in repositories.
Video—this asset type supports all known to Oracle Content Management media types for videos. You can use it out-of-the-box for managing video files in repositories.
Video Plus (for use in digital asset repositories only)—this asset type supports the same file media types as Video type, but it is designed to support managing advanced videos. Video Plus isn't supported in business asset repositories.
File—this asset type allows managing any file other than images or videos. Note that you can preview only supported file formats.

You can restrict custom digital asset types to support only specific file media types and add custom attributes as required for managing digital assets in your organization.

You can copy an existing asset type or create a new one. For example, you can copy the seeded Image type to create a custom asset type that extends the asset type with attributes.

Sign in as a content administrator in your browser and click Content under Administration in the left navigation menu.
Select Asset Types from the drop-down menu.
To create a new digital asset type, click Create, then select Digital Asset Type.
Enter a name for your asset type.
Edit the display name as needed. The display name is used in the user interface, for example, on the Assets page.
Optionally, add a description to help users understand what this asset type is used for.
Click Create.
On the Media Types tab, select the media types you want to support for this digital asset type. Search for and select an extension, and then click Add. If you don't see the extension you want, you can add it, but don't include the "." (for example, "jpg", not ".jpg"). Note that you can preview only supported file formats.
If you select one or more video types that support Video Plus, you can enable Video Plus. Video Plus supports advanced video capabilities, including optimized streaming, automatic transcoding, conversion, and video editing. Video Plus isn't supported in business asset repositories.
Click the Definition tab. The data fields you add here will appear in the Attributes pane when adding or viewing the asset.
1. Drag a data field into the digital asset type definition.
2. The settings page for the data field opens:
  - Enter a display name and optional description for your data field.
  - Optionally, edit the field name. This name must be unique.
  - If you selected text, media, or reference, select whether the field allows only a single value or multiple values and the number of values allowed.
  - Select if the field is required before the asset can be used.
  - If you selected text, large text, or embedded content, optionally provide a comment or note that provides additional instructions for the translator.
  If this asset type will be used in digital asset repositories, configure these additional settings:
  - If you selected media or reference, select whether the dependent asset is always published with the parent asset or only when the dependent asset isn't already published.
  - Select if the field values should be inherited from the master type. For example, you may want a text field to display the company name or stock symbol as entered when a digital asset is created using this asset type across all languages. Or you may want to prepopulate an image field to always use the approved company logo for all languages. If you want the field to be translatable, you must disable Inherit from master and Do not translate.
    
    Note:
    When selecting Inherit from master, Do not translate is automatically selected. If editing an asset type that has been used to create assets of different languages already, selecting Inherit from master causes the field values in the existing draft items to use the value in the master item. If the languages have already been published, then the preexisting value will remain in use until a new draft item of that language is published.
  - If you selected text, large text, or embedded content, select whether or not to translate the data entered into the fields. For example, a product description may be translated, but the product name or brand name might only be valid in the original language.
3. On the appearance page for the data field, set what your data field will look like and if you want to apply any kind of validation. Each data field has different appearance values, such as validation, minimum or maximum length, the type of text editor to use (text area or rich-text editor), or if the data needs to follow a particular pattern, such as a valid email address or zip code. For details on the available out-of-the-box data fields and their options, see Data Fields. You can also custom field editors.
  When you add a large text field and set the appearance to rich-text editor, you can select the type of toolbar: standard, basic, or custom. For custom rich-text editor, see Customize the Rich-Text Editor Toolbar.
4. In the digital asset type definition, you can group related fields to make it easier for contributors to work with digital asset forms.
  - To create a group, click Add Group, and then name the grouping. Drag data fields to the groups as desired.
  - Select whether you want the group to be expanded by default, collapsed by default, or hidden when viewed in the digital asset editor. For example, you might have mandatory fields that are in a group that is expanded by default and optional fields that are in a group that are collapsed by default, or you might need to edit an asset type at some point to hide a group of fields that have become obsolete.
  - To edit a group name, click .
  - To delete a group, click . Select whether you want to remove the data fields along with the group, or if you want to move the data fields to another group.
On the Friendly URL tab, you can enable a readable URL for digital assets created using this asset type.
1. Select Enable friendly item name for URL to enable friendly URLs.
2. If you're going to provide a custom prefix for the friendly URL and you want to include forward slashes in the prefix, select Allow forward slash.
3. If you want to provide a custom prefix for the friendly URL, choose Provide custom prefix for item name from the drop-down list, and then enter your prefix in the text box.
  Digital assets created from this asset type will have a friendly URL in the format <custom-prefix>-<digital-asset-name>. For example, if you enter marketing/blog-images as the prefix and Coffee Beans.jpg is the name of the digital asset, the friendly URL would be http://www.example.com/../../marketing/blog-images-coffee-beans.
  Note:
  - The prefix can't contain any of the following characters: " # % & : ; < > = ? @ [ ] \ ^ ` { } | ~ and / (unless you select to allow forward slash)
    If you allow forward slashes in your friendly URL, you must URL-encode the slashes when making an API call or the call will fail.
  - Spaces in the prefix and in the content item name are replaced with hyphens (-) in the friendly URL.
  - The friendly URL will be all lower-case.
  - File extensions aren't included in the friendly URL.
  - You don't need to include a forward slash before or after your prefix. The forward slash before your prefix will be included automatically in the friendly URL. A hyphen (-) will be added between your prefix and the content item name.
  - Friendly URLs aren't created for items in business asset repositories, only items in digital asset repositories.
On the Content Layout page for the digital asset type, select the layouts, form, and preview pages you want to be available for this digital asset type. When a digital asset is created using this digital asset type, the person creating the asset will use the form you choose to enter the attributes for the asset and can preview how the asset will appear using any of the chosen layouts.
- Site Builder layouts: (for use in digital asset repositories only) Choose desktop and mobile layouts for each layout style used in Site Builder. If the digital asset created using this type will be used on a website, the layouts should be created and uploaded prior to creating the digital asset type.
- Custom and precompiled layouts: (for use in digital asset repositories only) Add custom layout styles that can be published through the API and optionally used to publish HTML renditions for the published assets.
  1. Click Add Layout Style.
  2. Enter a style name.
  3. An API name is automatically generated, but you can edit it as desired. The API name must be unique.
  4. Select desktop and mobile layouts.
  5. If you want to publish HTML renditions of the content in this layout when the asset is published, select Publish HTML. When the asset is published an HTML rendition of the asset will be created automatically. Repository administrators can also manually republish HTML renditions for all published assets of this asset type.
- Default preview layout: Choose the default layout to be used by default to view and preview digital assets of this asset type in the web client.
  If you want asset users to preview these digital assets in a site page layout by default, you must first select the site page as described below and save the asset type. Then you can edit the asset type, return to the Content Layout tab, and the selected site page will appear in the default preview layout drop-down list.
- Attribute editor form:
  1. Choose the formform to be used as the attribute editor when adding or editing attributes for digital assets of this asset type.
  2. Choose whether you want the attribute editor to be displayed in a slide-out panel (drawer) or in the sidebar panel.
  3. If the form supports editing attributes across multiple selected assets, leave the checkbox selected.
- In-place and external site previews: (for use in digital asset repositories only) If you want the digital asset creator to be able to see what the digital asset will look like on a particular site page, select the Oracle Content Management-created site and page, or enter an external site and page URL. External URLs can include placeholders for id, type, language, and slug. For example, http://www.example.com/mypage/{id}/{type}/{language}/{slug} or http://www.example.com/mypage?id={id}&lang={language}&type={type}&slug=(slug).
On the Tile View page for the asset type, you can specify a custom tile view. Custom tile views let you configure how the data fields of digital assets are displayed on the Assets page, based on asset type. By default, the tile displays the thumbnail of your digital asset, though some media may not have a thumbnail representation.
- Under the Display area, select an option. In the available options, media data fields are represented by gray rectangles, title data fields are shown as thick gray bars, and text data fields are shown as thin gray bars.
- Under the Configuration area, select the asset type fields to be used for each piece of data shown in the tile view (title, text, media).
- If you selected a tile view that includes a thumbnail, you can select Contain Media Thumbnail to scale the thumbnail so that the entire thumbnail is shown in the media area. Otherwise the thumbnail will be zoomed and cropped to fill the media area.
For asset types that will be used in digital asset repositories, select the translation settings for the native media file. By default the media file will be inherited from the master language and will be set to not translatable, so that all languages use the same media file. If you need to have localized media files, on the General tab for the asset type, disable Inherit from master and Do not translate.

Note:
When selecting Inherit from master, Do not translate is automatically selected. If editing an asset that has been used to create assets of different languages already, selecting Inherit from master causes the field values in the existing draft items to use the value in the master item. If the languages have already been published, then the preexisting value will remain in use until a new draft item of that language is published.
On the Renditions page, add rendition policies to define the required renditions you want to be automatically generated for images that use this asset type. You can create a new policy or add an existing policy. An asset type can include a maximum of twenty rendition policies, including system rendition policies (images have four system rendition policies), so you can add up to sixteen custom rendition policies.
- To view the details of a rendition policy, click .
- To edit a rendition policy, click .
- To delete a rendition policy, click

To view the digital asset type's properties, click .

You must associate the digital asset type with at least one repository and grant users at least the contributor role on the repository so the digital asset type can be used to create digital assets.