If you’re already a Hitchhiker, log in to access this content.
Mapping to an Entity Field| Hitchhikers Platform
What You’ll Learn
In this section, you will learn:
- How it works
- Use Cases
Mapping to an entity field allows you to pull information from the Knowledge Graph for the corresponding entity, so it will update dynamically on each page. This option would be used for entity-specific information like address, phone number, etc.
You can map to existing fields in the Knowledge Graph, or create custom fields if you would like to include information that is not already stored in the Knowledge Graph.
Mapping to an entity field is typically the most common option, as these pages are intended to display information about each entity.
When you select a field to map to, you will see a preview of that content next to the field name in the sidebar. Once you click Save, the content will appear in the Live Preview on the right. If the field you selected does not have any content, the module field will not appear in the preview until the content is added in the Knowledge Graph.
- Any entity-specific information like address, phone number, or date that will change based on the entity.
Considerations when mapping data to fields in the Knowledge Graph
When selecting fields to map to, you will only see options of the same field type. For example, if you are mapping a URL field, you can only select a URL field as a mapping option. Similarly, if you are adding text, you will only be able to select a text field as a mapping option.
Updates to the content in the Knowledge Graph will automatically be reflected on your Pages. If content is added or removed from a field in the Knowledge Graph that is mapped to your pages, that content will automatically be added or removed from your Page. This emphasizes the importance of previewing the page for each entity to ensure that each page has the correct information.