Metadata folder schemas

Transcript

Folder Metadata Schema has defined the interface for managing properties of asset folders. Folder Metadata is only for the folder and does not cascade down to assets, nor does it show up it in asset properties. As metadata first and foremost describes the container that is the folder the values may logically apply to assets in the folder, but the data resides on and is maintained at the folder level, and does not natively augment asset metadata. The primary use cases of folder properties are providing an in-context interface that helps AEM users understand the purpose of a folder, helping search and discovery of asset folders in AEM beyond research, and also provides a way to describe assets in the folder or sub folders such that custom code can then process the assets based on whatever logic is needed.

Folder metadata schemas are managed via tools, assets, folder metadata schemas. This console lists any existing folder metadata schemas, and allows them to be created, edited, or deleted. Let’s create a new folder metadata schema for a magazine article related assets, which are all stored in folders under the magazine folder. Type create, give a meaningful title, and remember, folder metadata schemas can be applied to any number of folders. So, pick the name accordingly. Now that we’ve created an empty folder metadata schema, let’s edit it.

Schemas need at least one tab so let’s make one.

Drag fields from the build form tab on the right, into the schema editor on the left to compose the metadata schema.

For each field added, select it, and tap settings to configure it. The field label provides AEM users with a context of what the field represents. The mac two property is important as it defines the JCR property under the folder the field value will be stored. A custom property path can be typed in, or common AEM asset properties can be selected via the property finder, via the button on the right of the field. Folder metadata is not naturally written back to access XMP metadata, so, depending on how this metadata will be used it may not benefit from property named space. Here we’ll leave name space off and simply name the field article ID. Since this is a text field, we can define a placeholder that helps insure authors enter the value in the desired format. And optionally, more complex rules can be applied to the field via the rules tab. Different field types have different options. For example, text fields have placeholders in descriptions, while drop-downs allow you to specify available options. Let’s create a drop-down field that allows us to set the editor for a particular article folder.

When satisfied, click save, and remember you can always edit it later by selecting it and tapping edit. Once a definition is complete, the folder metadata schema needs to apply to folders for it to be useful. Select the folder metadata schema and tap apply to folders, and select all the folders to which this folder metadata schema should apply to. In this case, let’s select all of the article folders under our magazine folder.

This approach tends to be used when setting up new folder structures by AEM asset administrators, or when a new schema is created and needs to be used across existing folders such as this use case.

AEM users can also select and apply folder metadata schemas during folder creation as we’ll see in a moment. Folder metadata schemas can be removed from a folder by selecting them, tapping remove from folders, which opens a UI which lists all folders in AEM the schemas apply to. Simply select the folders from which to remove the schema, and save your changes if desired.

Okay, let’s quickly review the folder metadata schemas in action. For this, we’ll jump over to assets, files, and then navigate down into our magazine folder.

And let’s make a new folder to see how AEM users can select folder metadata schemas to apply during folder creation.

We can see here there’s a new drop-down that lists all of the folder metadata schemas in AEM, allowing us to apply them as the folder’s created. Now let’s look at one of the existing folders we apply the schema to via the folder metadata schema console. Select the folder, tap properties, select the folder metadata tab, and here we can see our applied folder metadata schema and edit the values as necessary. So, before we go, let’s review the three primary use cases as discussed earlier. The folder metadata visible the folder properties provides a well-organized UI for exposing and managing folder metadata via the schema definition. Administrators are able to allow who can edit or read folder metadata via AEM’s permissions. AEM search can be customized to filter in specific metadata fields to find for the folders making assets folders truly a first-class citizen when it comes to search in AEM. Lastly, and likely the most powerful application is folder properties provide a great way for AEM users to define content or data on a folder, and then allow custom processes acting on assets in the folder to programmatically read the folder properties and make decisions or perform actions as required by customer requirements. -