Field Mapping Between Google Drive and SearchUnify
This article visualizes the mapping between the fields found on the Google Drive frontend and the SearchUnify fields under the tab Drive Content Source > 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 createdDate in Drive but its name in SearchUnify is post_time.
| Search Field Name | Fields from API Response & Description | Visual Representation at Google Drive Front-End |
| Title (d) | Title (Name of the file) | |
| post_time (d) | createdDate (Created Date of the file.) | |
| author_name (d) | author_name (List of names of owners of file) | |
| author_email (d) | author_email (List of Emails of owners of file) | List of emails of owners mentioned in the previous row. |
| embedLink | embedLink (embed link. Preview link for the file, returned by API) | Preview link for the file, returned by API |
| file_url (d) | file_url (File path of the file from root folder (ex. mine Folders/folder2/folder1/file111) | File path (ex. mine Folders/folder2/folder1/file111) |
| folder_name (d) | folder_name (Folder in which the file exists) | |
| html_body | Contains the name of the file and text content inside the file | |
| content (d) | Contains text content inside the file | |
| View_href (d) | embedLink (embed link. Preview link for the file, returned by API) | |
| etag | etag (Tag returned by drive API) | Tag returned by drive API |
| lastModifyingUserName | lastModifyingUserName (last modifying user’s UserName) | |
| comments | Comments on files (are only crawled if the field is added and the comment toggle in crawlFields key is true in drive crawler config) | |
| commentCount | Count of comments on a particular file. | Count of comments mentioned in the above point |
