Content Security Metadata Management Use Cases – Fusion Data Mapper
A full explanation of how to administer Content Security rules is beyond the scope of this guide. However, details of some of the key use cases are given here.
Use Case – Restricting Who Can Browse Specific Datasets
Create rules to restrict access to specific Structure Sets.
- Create one or more separate Structure Sets to hold the datasets that need to be restricted.
- Create Content Security Structure rules to restrict access on each Structure Set to specific user groups.
- A Structure Set can be browsed by all users (including anonymous / unauthenticated users) if no Content Security rules are specified for it.
Use Case - Restricting Visibility of Certain Series in a Dataset
Series are only visible to users if all of the Codes used in the mapping are accessible.
Use Structure Rules to restrict access to specific Codes in Codelists used by the dataset.
Example 1
| SERIES_CODE | FREQ | DATA_SOURCE | SUBJECT |
|---|---|---|---|
| A_SERIES | A (Annual) | FM (Finance Ministry) | NA (National Accounts) |
| ANOTHER_SERIES | A (Annual) | CBS (Statistics Office) | ED (External Debit) |
| A_THIRD_SERIES | D (Daily) | CBS (Statistics Office) | ED (External Debit) |
Restricting the code ‘ED’ in the CL_SUBJECT Codelist which is used by the SUBJECT component to just the SUPERUSER group means that neither the ‘ANOTHER_SERIES’ or ‘A_THIRD_SERIES’ series will not be visible to other users.
Example 2
| SERIES_CODE | FREQ | DATA_SOURCE | SUBJECT |
|---|---|---|---|
| A_SERIES | A (Annual) | FM (Finance Ministry) | NA (National Accounts) |
| ANOTHER_SERIES | A (Annual) | CBS (Statistics Office) | ED (External Debit) |
| A_THIRD_SERIES | D (Daily) | CBS (Statistics Office) | ED (External Debit) |
Visibility of individual series can be controlled by restricting access to their Series Codes. In the above example, restricting access to the code ‘A_SERIES’ in the CL_SERIES_CODE Codelist to the SUPERUSER group will hide just that series from other users.
