Organizing data

Think about how the database will be used before you start to create projects, folders, and modules. You can rearrange the hierarchy, but not when users are accessing the data.

Each project in the database must have a unique name. Folder names and module names must be unique within the parent project or folder.

Access controls determine the data that individual users and groups can see. To see an item in the hierarchy, users must have access to the item, and to the parents of the item.

If you plan to archive data, the data structure determines whether links are included in the archive.

If there will be links between two projects, create the projects inside a parent project. When you archive the parent project, the links between the child projects are preserved.
Note: The link module must be within the parent project for the links to be preserved.

If you plan to partition your data, and you want to include modules from different projects in the same partition, create all the projects within a parent project. You can then create the partition in the parent project, and select modules from any project or folder in the hierarchy below the project. Links between modules that are included in the partition are preserved if you include the link module in the partition.


Feedback