Difference between revisions of "Content Security Caveats – Fusion Data Mapper"
(Created page with "Category:Data Mapping Category:Fusion Data Mapper Take care when creating Content Security rules to avoid unintentionally denying users access to browse and maintain...") |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
[[Category:Fusion Data Mapper]] | [[Category:Fusion Data Mapper]] | ||
| − | Take care when creating Content Security rules to avoid unintentionally denying users access to browse and maintain the metadata on datasets | + | [[File:Triangle.jpg|frameless|30px]] Take care when creating Content Security rules to avoid unintentionally denying users access to browse and maintain the metadata on datasets |
The key thing to remember is that restricting access to a structure will cause all structures that reference it to also be restricted. | The key thing to remember is that restricting access to a structure will cause all structures that reference it to also be restricted. | ||
Latest revision as of 05:30, 11 September 2023
Take care when creating Content Security rules to avoid unintentionally denying users access to browse and maintain the metadata on datasets
The key thing to remember is that restricting access to a structure will cause all structures that reference it to also be restricted.
Restricting a Codelist, for instance, could result in users being denied access to an entire Structure Set if that Codelist is a descendent. (A ‘descendent’ of a structure is one that is referenced by other structures on which the first depends).
The example shown illustrates now restricting the CL_FREQ Codelist also causes Categorisations, Concept Schemes, Content Constraints, Data Structures, Dataflows, Provision Agreement and Structure Sets that reference it to be restricted.
