Now you can use Connectors to easily ingest Multi-Language data and store it in corresponding Language Profiles. The updated Connectors workflow now allows users to specify the language of the Primary Profile and create and edit Alternate Language Profiles for Connectors from any source.
To specify the Language of your profile, you should add a column to your Connector that contains the locale code (e.g. “en”, “en_US”, “es”, etc.). This will designate the primary language for the entity, so any new entities created will be created with this language as their primary language profile.
Depending on where you are pulling your data in from, or where the data is stored - this data may come from your source data (e.g., a crawled website, an API response, etc.) or you may add it via a transform, like an “Add Column” transform.
Once you have a column that contains the locale for each profile, you can map that column to the new “Locale Code” field in the mapping step.
If you are adding or editing Alternate Language Profiles (either by itself or in addition to Primary Profiles), you must also include a column to indicate whether or not the row in the Connector corresponds to an alternate language profile.
To do this, you will need to have another column of data with “true” or “false” values that will designate whether the corresponding language is the alternate language or not.
You will then map this column to the new “Is Alternate Profile” field, so you should use the value “true” for any rows that contain an alternate language profile and the value “false” for any rows that contain a primary profile.
In the example below, the en_US is the Alternate Language profile for the entities. Meaning, an additional language profile will be created for that entity or the data on the additional en_US language profile will be updated.
This step is only needed for entities with multiple language profiles. If your Connector is only interacting with Primary Language Profiles, you can omit the “Is Alternate Profile” field and we will assume by default that the row contains a primary profile.
Note that for a given entity, you can only mark one row as “false” for “Is Alternate Profile” because each entity can only have one primary profile. Also, note that you cannot include Primary Only fields when adding or editing alternate language profiles.
To learn more about Connectors, visit the Data Connectors module. Or, to learn more about Multi Language Profiles, visit the Multi-Language Profiles in the Knowledge Graph module.