Difference between revisions of "DataVault"
m |
m |
||
| Line 6: | Line 6: | ||
== DataVault Builder == | == DataVault Builder == | ||
To generate json files to be imported into DataVaultBuilder, some work is involved. After your environment is set up, and your model annotated, you can simply use ''File\Export\DataVault Builder'' to generate an archive with files for uploading. | To generate json files to be imported into DataVaultBuilder, some work is involved. After your environment is set up, and your model annotated, you can simply use ''File\Export\DataVault Builder'' to generate an archive with files for uploading. | ||
=== Custom Attributes === | === Custom Attributes === | ||
Custom attributes need to be defined for the staging tables to be provided. These are required for the loading of hubs. | Custom attributes need to be defined for the staging tables to be provided. These are required for the loading of hubs. | ||
| Line 15: | Line 16: | ||
The last is optional, since you may also provide these names when using with satellite containers as mentioned in the following paragraph. | The last is optional, since you may also provide these names when using with satellite containers as mentioned in the following paragraph. | ||
=== Satellite Containers === | === Satellite Containers === | ||
When adding a container with the schema ''DVSAT'', the name of the container is used as a satellite identifier. After adding the container to the model with the appropriate naming, from this container relations may be added to fact types which are to be included in this satellite group. | When adding a container with the schema ''DVSAT'', the name of the container is used as a satellite identifier. After adding the container to the model with the appropriate naming, from this container relations may be added to fact types which are to be included in this satellite group. | ||
=== Using the Data Explorer Mapping === | |||
With the 13.4.1 version you can set DataVault Builder API credentials in the Preferences under the services tab. With that account, the source mappings may be linked. This functionality will skip the need for custom attributes for it'll link the source to staging to hub and satellite loading. | |||
[[File:Dvsat.png|DV Satellite Container]] | [[File:Dvsat.png|DV Satellite Container]] | ||
Latest revision as of 09:18, 16 September 2024
Disclaimer: This page is about the datavault support you may find in your version of CaseTalk. It also talks about features which may only be available in the beta channel. While we're hard at work to bring it all to production, some of it is still considered early alpha/beta development. Please be patient.
Diagram Style settings
To visualize the datavault hubs, links and satellites, the diagram style needs the coloring set to Ensemble.
DataVault Builder
To generate json files to be imported into DataVaultBuilder, some work is involved. After your environment is set up, and your model annotated, you can simply use File\Export\DataVault Builder to generate an archive with files for uploading.
Custom Attributes
Custom attributes need to be defined for the staging tables to be provided. These are required for the loading of hubs. Please create a custom attribute folder named "DataVault" and the following attributes:
- Staging System ID
- Staging Table ID
- Staging Column ID
- Satellite ID
The last is optional, since you may also provide these names when using with satellite containers as mentioned in the following paragraph.
Satellite Containers
When adding a container with the schema DVSAT, the name of the container is used as a satellite identifier. After adding the container to the model with the appropriate naming, from this container relations may be added to fact types which are to be included in this satellite group.
Using the Data Explorer Mapping
With the 13.4.1 version you can set DataVault Builder API credentials in the Preferences under the services tab. With that account, the source mappings may be linked. This functionality will skip the need for custom attributes for it'll link the source to staging to hub and satellite loading.
