Skip to main content

How to handle hierarchical scope data with simultaneous source usage restrictions?

Premeditation​

Suppose you have federal-level data, and the funding agency allows you to combine it with state-level data, but the requirements ban the use of two or more states simultaneously.

Principle​

How can you work with this data without moving it?

The solution is using the power of projects in three steps:

  • Set a parent project.
  • Set a child project.
  • Separate the data access with security levels between them.

Practice​

To achieve a complete architecture for hierarchical scope data where users have access to more data sets without being able to combine them, you can use the following workflow.

  1. Create a Project.
  2. Create a Subproject from the previous project.
  3. Add a description in the main project stating that users cannot mix data from source A and source B.
  4. Create a security level for the main project.
  5. Create a distinct security level for the subproject.
    • Add security requirements.
    • Certify the appropriate users.

Now you have an enforced policy that allows users to operate in the same project without combining any data sets.