Expose different data to different teams
You can use AML Extend to reuse the same model but hide certain fields for different purposes.
Let’s say that you have a data model that represents employee information that you want to let the HR department and the Finance department use for different purposes.
Model employeeInfo {
// Details of this dimension are omitted for brevity
dimension employeeID {}
dimension first_name {}
dimension last_name {}
dimension email {}
dimension salary {}
}
You can put this data model into a dataset and share that to both departments.
However, the Finance department may be interested in certain dimensions, such as employee’s ID and salary, so that they can calculate relevant financial metrics. Exposing names/emails are not necessary, and can pose a security risk to your company.
You can duplicate the data model into one for HR and one for Finance, but you’ll have to pay extra efforts to ensure consistency when introducing new dimensions or changing existing dimensions.
With AML Extend, you can define the base model for employee information:
Model employeeInfo {
// Details of this dimension are omitted for brevity
dimension employeeID {}
dimension first_name {}
dimension last_name {}
dimension email {}
dimension salary {}
}
Then you can extend the base model and define additional dimensions or metrics for HR team.
Model employeeInfoHR = employeeInfo.extend({
dimension employeeEngagementScore {}
dimension recruited_from {}
})
// Add this model into a dataset and then expose the dataset to HR team
You can also extend the base model and hide irrelevant fields for Finance team.
Model employeeInfoFinance = employeeInfo.extend({
// Note that you need to specify all properties
dimension first_name {
// other properties
hidden: true
}
dimension last_name {
// other properties
hidden: true
}
dimension email {
// other properties
hidden: true
}
dimension performanceMetric {}
})
// Add this model into a dataset and then expose the dataset to Finance team