Features - Custom Tagging
Go beyond key-value pairs and enforce business logic.
A Different Take on Tags
In Daturic, tagging is the core mechanism that allows organizations to group their data. Tags are globally created, and can be used on any folder in any data lakes registered within the system. Tags can be used to make finding data easier and are ultimately used when creating data sets for policies.
Apply tags at any level
Tags have no restrictions on where they can be applied on your data lakes. Use them at any level in your data lake hierarchy
Tags have inheritance
Folder hierarchy in your data lakes already group data in a certain way. Daturic tags inherit from parent folder to child folder, so you don't have to duplicate that work.
Tags allow for controlled vocabularies
Because you define your tags in a central location, use this mechanism to create a controlled vocabulary for the catagorization of your data.
No tagging limits
Connect as many tags as you need to enforce your business rules.
Combine different tag types
Combine different tag types to create the right representations for your business.
Different tag types to meet business needs
For when data can be classified in more than one way
There are many cases where the same set of data can logically belong to multiple groups of data. On the data lakes, the folder structure can only help with one of those logical organizations. Gregarious tags allow users to use the same tag type (with different tag values) on a target folder.
The example shows how gregarious tags could be used. Water contains both the oxygen element and the hydrogen element. Gregarious tags allow users to tag the same folder with element=hydrogen and element=oxygen tags.
Another example would be when a particular data set can be used by more than one department. Administrators within daturic could create multiple department tags, for example department=marketing and department=finance, and attach it to the same folder.
For when data can only be classified in a single way
Highlander tags are designed to only allow a single assignment on a given set of data. As the example shows, this type of tag can be used to govern the visibility of a set of data. You'd never want a folder to be tagged as both public and private from a visibility perspective, and highlander tags enforce that at tag application time.