Integration basics for SFTP

If another type of integration is required, email [e-mail]

GENERAL CONSIDERATIONS

• Integration will be done through CSV files that are copied to an SFTP unit, located in the Geoblink cloud (Amazon Web Services)
• All CSVs will have a header with all the required fields and they will be separated by a semicolon
• In case of a POI database Eg .: (ID, street, number, size, etc.)
• In case of a customer database Eg.: (ID, street, number, gender, etc.)
• In the case of semicolons appearing as part of a field, the field will be included in double quotes
• Eg .: (28853; "National II; km 25 "; male; 27)
• To escape double quotes, double quotes are suggested:
• Eg: (" "La Colina" ", Abascal 25 street)
• Geoblink will build a process that detects the insertion of a new CSV document to process it immediately
• The structure of directories of the unit will be the following (names always in lowercase):
• In case there is a bidirectional integration, in the root directory there will be two folders: [NAME TO BE DEFINED BY GEOBLINK] and [NAME TO BE DEFINED BY GEOBLINK]
• In case the integration is not bidirectional, there will be a folder [NAME TO BE DEFINED BY GEOBLINK]
• In each folder there will be two directories: new and processed
• The files will be exported to the folder new and once processed correctly they will be moved to the folder processed, which will contain the history of messages
• From now on, shops (or local outlets, etc.) will be called units and customers (or members, patients, etc.) will be called members

IMPORTANT: Not following these guidelines could potentially entail loss or corruption of information and / or incorrect operation when displaying data to the user. It’s important to add the corresponding logic and testing to ensure correct compliance.

Do you have problems escaping the data?

Some systems do not give the option to export the data in a simple way in CSV format. To adapt to the conditions of the CSV, we recommend following these steps:

• Remove the double quotes of all the fields. The user with address:
• CL / LEOPOLDO ALAS "CLARIN", 4
• Will have address:
• CL / LEOPOLDO ALAS CLARIN, 4
• Surround the fields with double quote:
• "CL / LEOPOLDO ALAS CLARIN, 4"

CREDENTIALS SFTP

• Server: [TO DEFINE BY GEOBLINIK]
• Port: [TO BE DEFINED BY GEOBLINIK]
• User: [TO DEFINE BY GEOBLINIK]
• Password: [TO BE DEFINED BY GEOBLINIK]

CLIENT CONNECTION → GEOBLINK

It is necessary to provide a master file that contains the information of the members or units to perform the initial load. In addition, the client could segment members or units and forward that segmentation to Geoblink in order to analyze only a set of data. This operation would require a segmentation file.

• File containing the Master of members or units

• Description: File Format for the update of Members / Units
• Update frequency: [TO BE DEFINED BY THE CUSTOMER]
• Format file name: timestamp_master_socios.csv

• Columns: 

Column name	Type
Member	char
Address	varchar
...	...
[TO BE DEFINED BY THE CLIENT]	[TO BE DEFINED BY GEOBLINIK]

• Segmentation File
• Description File for the upload of segmentations from the client DB to Geoblink
• Applies: [TO BE DEFINED BY THE CLIENT: Yes / No]
• Update frequency: Ad-hoc, (each time the user exports a segmentation in the Geoblink tool)
• Format filename: timestamp_segmentacion.csv
• Columns:

Name column	Type
Member / Unit	char

CONNECTION GEOBLINK → CUSTOMER

It is also possible to export the members / units from Geoblink to the client DB of once the segmentation of clients has been done in Geoblink.

• File that contains the export of Geoblink:

• Description: result of exporting a segmentation in Geoblink, for its visualization in the client DB
• Applies: [TO BE DEFINED BY THE CLIENT: Yes / No]
• Update frequency: Ad-hoc, (each time the user exports a segmentation in the Geoblink tool)
• Format file name: timestamp_segmentation-name.csv
• Eg: 20180403145932_members-active.csv

• Columns:
• Member
• area_id: Id of the census area where the
• zip member resides: Zipcode where the partner resides

Name column	Description
Member	ID of the member
area_id	ID of the census area where thepartner
zip	Zipcoderesides where the partner resides