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.
- In Database view, users must have access
to all the items in the hierarchy, from the database root down to
the project, folder, or module.
- In Project view, projects that users have
access to are listed in the left pane. Users must have access to all
the items in the hierarchy, from the parent project down to the folder
or module.
If you plan to archive data, the data structure determines whether
links are included in the archive.
- When you archive a module, links are not preserved.
- When you archive a project, links within the project that use
link modules in the project are preserved. Links to modules in other
projects, or links that use a link module that is in a different project,
are not preserved.
- You cannot archive folders.
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.