In order for us to make sense of Connect assets in an environment with hundreds of users; thousands of canvasses and databases etc - we need to strongly categorise and describe every asset using mandatory tags.
Every asset needs to have mandatory tags
- The admin team set up the list of tags which are required for different types of assets
- For example - every Alteryx Canvas may need Product; Process; Team - every DB table may need Product and Tech Team
Admin team need to be able to define these tags and the acceptable values (which can be a tree)
When searching for assets - these meta-tags need to be available as filters
Example:
- Asset is identified by the scanners and brought into Connect
- Owner is then required to describe their asset using the mandatory tags set up by the admin team
- Product (this is a tree that would be controlled centrally – admin can add or update this list; users have to select 1 or more products that this canvas relates to)
- Business line
- Team (tree based)
- Is this regulatory (Y/N)
- Public / Private
- Plain-text description
- In this case – every asset needs 6 tags; with the taxonomy(valid values) controlled centrally
CC: @DavidM @Arianna_Fuller
