Asset types define what information is needed for your assets. The asset information is saved separately from the layout (the way the asset is presented). That way, the assets users create can be used on a website, or in a brochure, or wherever they might be needed, appearing in a way that fits the situation.
There are two main asset types: digital asset types and content types.
A digital asset type defines what information is included with a digital asset such as an image, a video, or a file. For example, an image might include EXIF information from the camera (date, time, location, resolution, and such), system settings (asset creation date, last updated, status, version, and such), and custom metadata. That custom metadata is where the digital asset type comes in. You might want to collect copyright, permitted use, and contact information for each of your images. Oracle Content and Experience includes several out-of-the-box digital asset types: file, image, and video.
A content type is a framework used to specify what information is included in a content item. The image below shows that content types (1) can also have layouts (2) associated with them, which determine how they appear and what information is used in that particular layout. For example, you may only want a subset of information to appear on an employee contact list, but you might want an employee picture, location, and job title appear in another location on your website. When you create a content item using a content type, you can preview how it will look with different layouts.
If you have the appropriate privileges, you can define asset types in the Oracle Content and Experience web interface under Administration > Content.
Each asset type consists of a set of field definitions. In the preceding example, four fields have been defined for a content type named 'Article': title, body, author, and picture. These fields show in the data entry form users fill out when they create an asset based on the asset type.
Once an asset type is defined, it needs to be added to a repository so that users can create assets of that type in the repository. You must also share the asset type with the users you want to be able to create assets. Then the assets can be managed, published, and used in any channel.