Data Security Officer would like to restrict access to certain asset information to a group or division of people. Being able to publish discovered assets into catalog would be a big step towards achiveing zoning.
|Who would benefit from this IDEA?||Data Security Officer would like to restrict access to certain asset information to a group or division of people|
How should it work?
During the publish option, data stewards can pick catalog manually or even could be driven by rules for automation.
Assets can be published to one or more catalogs. This is useful for making common data assets available to everyone.
Assets while being published can be marked to be tracked or independent. This is similar to git branches. it could be desirable that when assets are being tagged/termed/commented on, these information is made available to every catalog where this asset is published. While another scnario could be to make such changes private only to the catalog where its been commented.
Zoning is the feature which would provide these feature but seems that its not untill Q3
|Priority Justification||Verizon has been stating this as one of the most important feature.|