An import requires an understanding of the source, the transformation rules and the objects expected upon arrival. Dtouch prepares correspondence, checks and recoveries for the project.
Interfaces used to organize work, prepare data and track files. Each screen shows a specific function, with presentation data.
Enlarge screen The GPdis interface presents the statistics, the target category and the choice of the selling price before import.
Real interface · test environment · demo data.
Enlarge screen The search accepts a name, identifier or address, with filters on the nature of the third party and the activity.
Real interface · test environment · demo data.
Enlarge screen Autocompletion offers matches during entry to make it easier to complete a file.
Real interface · test environment · demo data.The data can come from files, a database, an export or an API. We look at fields, identifiers, types and relationships before defining processing.
The mapping specifies what corresponds to an existing object and what can be created or updated. Ambiguous values are identified to avoid silently transforming uncertainty into reference data.
Date formats, units, separators and encodings require explicit rules. Fields calculated or resulting from matches must be explainable.
Tests on a sample make it possible to verify hypotheses before passing them to a batch. The results are compared to the source and the uses that will exploit the data.
A resumption may be interrupted or require a second passage. Identifiers and update rules determine how to restart without multiplying objects.
The logs distinguish between processed, ignored, and rejected items. Errors must be attached to a line or object to allow targeted correction.
The number of imported objects is not enough to evaluate the recovery. We verify relationships, research, documents and operations that depend on the transferred data.
The transmission of mappings, reports and reminder conditions allows the teams to understand and maintain the processing.
Example of a path with deferred processing: the connector prepares the data, organizes their transfer and keeps the results of the exchanges for monitoring and recovery.
Enlarge the diagram API, files and databases
Identifiers • formatsBusiness correspondence
Fields • units • referencesOrganize requests
Priority • planningTreating tasks
Controls • matchesApplication or ERP
Objects • management rulesControl returns
Journal • status • reminderEnlarge the diagram Keep the reference of the source and that of the target application.
Describe correspondences and distinguish direct calls from deferred processing.
Find the state and context of an exchange to be retired.
Founder's Experience · Reymann
Traces incorporated into JPEGs, Apoove annotations, images and attachments: processing to make information usable between applications.
Explore the caseFounder's Experience · Reymann
A back-engineering around Universal Type Server to make typographies available in the InDesign Server generation chain.
Explore the caseProject Dtouch
References, categories, rates and images: A useful catalogue also depends on how its data is fed.
Explore the caseUnderstand and prepare
The lines that require a decision are part of the project: unknown reference, possible duplicate, missing document or price corrected by a user. We prepare the treatment to make these situations visible and enable targeted recovery.
A file of a few clean lines gives an incomplete view. The work sample must also represent the variants, particular characters, attachments and missing values encountered in the activity. For a supplier catalogue, it may include already known items, new references and category changes. People who use the data help to recognize cases where automatic creation is acceptable and those who request a decision.
The same reference may already have a corrected description, a chosen price and an internal category. The mapping must specify which fields remain the source and which local information should be kept. The preparation distinguishes creation, updating and possible deactivation. In a business application, this rule protects the work of users while allowing the updating of the data received. Deletions and changes in sensitive status are explicitly decided.
Tracking reconciles received items with items processed, refused or left on hold. It must make it possible to find the reference concerned and the reason for a deviation. A reminder can only include the necessary elements, with a rule defined for the data already present. The logs are designed for the people who will use the connector: information useful to the developer and a report readable by the team meet additional needs.
The project can include the correspondence table, the transformation rules, a test batch and its results, then the conditions for transition to real data. The recipe checks the relationships and uses after import: search, file, document or order depending on the subject. Agedis prepares backups and system prerequisites when needed; Cloudlab completes the home pane of the application. The processing is transmitted with its resumption conditions and its known limits.
A specific need, a software to evolve, a project to frame.
Stations, servers, access and backups: Agedis supports the IT environment on which the application is based.
Discover Agedis servers and systemsCloudlab covers the data center and hosting component. The resources and operating conditions are prepared with the application project.
Understanding the Cloudlab data center baseComplementary expertise, the same high standards.