Dataprep

https://dataprep.dacoval.com/ -> Michelin in-house tool for data processing and feeding websites

URL: https://dataprep.dacoval.com/

REQUEST AN ACCOUNT

To request an account for you or someone in your team, please raise a JIRA ticket in the appropriate project: https://michelingdic.atlassian.net/jira/core/projects

Title: Access to GlobalDB interface Description: I would like to request access to Dataprep interface. Please find below my details: Name: Last Name: Entity Name: Email address: Scope (countries/brand/Business Lines) Assignee: anne.field-pannetier @Anne-Karine Bervas

TOOL OVERVIEW

Overview of how GlobalDB tool is working

GlobalDB is the in-house tool. It is made of: - Front-end interface for users to upload their files and download the latest imported file - Back office for the engineering team to develop treatment pipelines - Transformation pipelines that contain functions, transformation rules, mapping, and validation schemas. We have as many pipelines as we have files with different transformation rules. - Export functions to push to the website data module 'datastream'

What happens within a pipeline?

Example of what a tyre pipeline does

globalDB is working like an ETL (Extract Transform Load) tool. In this example, we receive several files (commercial catalog, product template, price list...). globalDB is: - Merging the files, taking information from the 3 of them (attaching articles/sizes to the product level) - Transforming entry data (concatenate, unit transformation, activation/deactivation, data cleaning, display size formatting...). - Completing data (adding tyreID, checking the latest status and updating etc) - Mapping data: from the entry files to the accepted format by the datastream and the website