DNG tags in artifacts and module views
![](http://jazz.net/_images/myphoto/682c2d0848d73f4dd72a5d2b1aeb1a23.jpg)
We had users creating tags against various artifacts. Some create these in a artifacts view (base artifact) and some within a module view.
Withing a module view, they can't see that tags that where created in a artifacts view and vis versa.
They are new users to DNG and are still learning its intricates.
Can someone explain to me this behavior.
Accepted answer
![](http://jazz.net/_images/myphoto/682c2d0848d73f4dd72a5d2b1aeb1a23.jpg)
You can make comments and apply tags to an aritifact (1) in the context of a module or (2) to the base artifact. If you do it on the base artifact, the comment and tags will be available in all modules that include that artifact. If you do it in the context of a module, they will be localized to that module.
This provides a scope for reuse. Comments and tags are most likely to have a narrow scope (one product variant or product release). But if you want them to have universal scope, then make them on the base artifact.
What if you want more control ... something between "only this module" and "all modules"? In that case check out the work we are doing to enable version management / configuration management natively in the RM application and across a linked data system:
Manage configurations in and across the CLM tools in the 5.x M6 beta
This provides a scope for reuse. Comments and tags are most likely to have a narrow scope (one product variant or product release). But if you want them to have universal scope, then make them on the base artifact.
What if you want more control ... something between "only this module" and "all modules"? In that case check out the work we are doing to enable version management / configuration management natively in the RM application and across a linked data system:
Manage configurations in and across the CLM tools in the 5.x M6 beta