How Field Mapping Works Between Adobe Experience Manager (AEM) and SearchUnify
This article visualizes the mapping between the fields found on the Adobe Experience Manager (AEM) frontend and the SearchUnify fields under the tab Content Sources > Adobe Experience Manager > Edit > Rules. Using this document you can pick the right fields for crawling and indexing in SearchUnify.
Here's an example: The highlighted area in the image is called dc:title in AEM but its name in SearchUnify is Title.
| Search Field Name | Fields from API Response & Description | Visual Representation at AEM Front-End |
| id | URL (It is a unique identification of files.) | |
| url | URL (It is a unique endpoint of files or documents) | |
| Description | (It stores all the data of files, including .doc, .pdf, .txt, and othes) | |
| Folder Name | folder_name (It is the folder name selected for crawling data in the rules tab in the SearchUnify admin panel) | |
| Action | action (It stores the information of documents indicating whether they contain any data or not) | |
| Title | dc:title (It stores the title of meta-information stored in the particular files) | |
| Modified At | modifiedAt (It stores the modification date of files) | |
| Mix Type | jcr:mixinTypes (The page URL path) | |
| Format | dc:format (It stores information about the kind of document being stored) | |
| Tags | cq:tags (It includes the tags assigned to the document) | |
| Last Replication Action | cq:lastReplicationAction | |
| Created By | jcr:createdBy (It includes the name of the person who created the asset) | |
| Contact Name | contactName (It includes the name of the person) | |
| Language | language (It stores the language added to meta properties.) | |
| Uuid | jcr:uuid (It includes the unique ID of files set in the meta properties) | |
| Status | status (It includes the status set in the meta properties) | |
| Asset Type | assettype2 (It stores the type of asset, such as a photo, a document, etc) | |
