Project: talenddataquality
Issue TDQ-8785: Add support to  Cloud connector for address validation as one component.
Component name: tCloudAddressRow # Develop the Loqate Address Provider to be included in the Address Verification API # Develop a tLoqateCloudAddressRow component that uploads data to the cloud and retrieves the corrected data. h1. Technical reference documentation https://www.everythinglocation.com/api-references/ We develop first the transactional processing: https://www.everythinglocation.com/api-rest-transactional/ Before launching the address correction requests, we may check the status of the server with "https://devsaas1/rest/version/?lqtkey=[APIKEY]". See also https://help.talend.com/display/TalendComponentsReferenceGuide54EN/tLoqateAddressRow The component category is the same as the existing address components (Data Quality/Address ?) We'll design one component for all Address providers. The first version of the component focuses only on the available fields provided by the Adddress API. The fields define the output schema. *Notes*: - Automatically Define an output schema that contains all the columns available in the API. - only use the "synchronous" calls of the API. (will use async calls in a later version) - like tLoqateRow, define an input mapping in the properties - like in tLoqateRow, do define an output mapping. But auto fill this mapping with all the fields available in the API (they are the same as the output schema). The user is able to rename fields or remove fields in the output schema. - dropdown list option in the component to choose the provider between : Loqate, Melissadata (Google only for developers) - the output schema is currently given by the list of fields from the API (address1, address2, country, ....). *Output code*: use vendor code for accuracy code, status code, geocoding code *Advanced settings*: - keep the same loqate advanced settings as in the tLoqateRow (check whether the other providers work the same way).
Story points: 20