We built a connector for a Customer (a veterinary clinic) and it was advised we use the location entity since it has a lot of the pre-built profile fields available, instead of creating a custom field. However, the customer is using the GET Entities Schema Endpoint and based on the documentation if it’s a pre-built entity type, then it pulls the specific correlated schema type for that entity type, so locations entity type pulls the localBusiness schema type. I couldn’t find a way to change that, but the customer wants to instead use the VeterinaryCare - Schema.org Type, but I wasn’t able to find where the customer could update their schema type. They are using this to be able to build their own pages.
Looks like prebuilt Location Entity Type with a few added custom fields will work for you.
So since prebuilt Location Entity Type will be having some of te fields available, you will be needed to add other fields to accomplish the desired schema. Then you can use the location type in connector and sync respective fields from the source. So whenever connector will run successfully, data would be fetched from the source and save in the content (KG) on platform.
Feel free to make me correct if I understood something else or missed anything.
Thank you! What specific custom fields would I add in order to have the customer pull the desired Schema type? I’m a little confused, would you mind elaborating a bit more, how does it understand the specific schema property for Veterinary Clinic?
Hi @Holden_Ottolini,
Sure, Let me elaborate and try for helping you to understand.
Connector Base:
Using Legacy Get Entity End Point for fetching the data from Yext platform
OR
For fetching the data from Platform with any desired fields can be done via creating connector using Entities: GET end point
Custom Field add into Location Entity Type:
Using prebuilt Entity Type also, you can add desired Custom fields basis on the defined “Expected Type” from VeterinaryCare - Schema.org Type for adding the validated data properly.
The desired Schema type:
Data Map: During the process Load — Map & Run | Hitchhikers, each of the elements you extracted would be manageable for mapping. So you will be able to map the data with custom fields.
There should not be any boundations basis on the schema types. However if the fetched data need to clean for being validated, the transform step Transforms | Hitchhikers will provide the option for handling that.