The model is the framework where the user works and takes actions using the tap. Each model is associated with a unique tap.
From a model, the user can:
- Get the schema of the tap and compare it with older versions.
- Identify PII elements and analyze the sensitivity of your data.
- Create PDF reports with results of the analysis.
- Create transformation rules.
- Anonymize real data.
- Generate new synthetic data using tap schema.
- Create and download new datasets.
- Load datasets into existing sinks.
All these tasks are divided into different Model sections.
On the home page of the model you will be able to see the current status of the model.
4 different elements are shown:
- Show schema: Shows the different versions of the schema of the tap.
- Risk: Shows information about the number of PII elements discovered.
- Coverage: Indicates the % of the number of confirmed entities.
- Jobs: List showing the last jobs executed in the model.
When you create a new model, it is necessary to run a quick scan to the database to get the DDL. Here we will display some relevant information from your database, schema, size, etc.
Get more info about Schema here.
Scan or discover the tap when creating a model. Once Gigantics gets the database schema, you will be able to take actions like mask data on any table in the tap.
In this section, you will check the risk status of the tap based on the identified labels.
In this section you will be able to:
- Classify fields using labels.
- Set the PII fields and their risk severity.
- Confirm entities to avoid changes.
Get more details about this section in Discover.
You can generate reports of the current status of your datasource. These reports can be signed and downloaded as PDF files.
You can visit the Audits page for more information.
From Rules you can create transformations rules in order to generate new datasets. The rule contains operations that modify the data output from your tap. Read more about rules here
Datasets generated by rules will be displayed in this here. These datasets can be downloaded, dumped into a sink or shared using a link.
Shows the sinks available in the model. You can select one sink to load a dataset or dump tap data applying a rule.
Sinks are created in the project
Only sinks that have the same driver as the tap are shown.
Allows the user to run a job periodically and/or using a public link. Check Pipelines documentation for more details.
Many of the actions performed within the model require a job. In this page you can see all the Jobs that have been created and those which are scheduled.
In Events you will have a list of the actions that have been generated in the model. You will be able to check the date, the user who has performed the action and what type of action has been performed.