...
Section | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||
These single space use cases are typically not very common, if the organization allows to share configuration and information. In these cases, no space is an island! The projectdoc Toolbox allows configuration on space level using space properties. The configuration of space properties can be delegated to another space – a delegate space. Multiple spaces may share the same delegate space. In fact the projectdoc Toolbox assumes such a default space to have the space key
Sharing configuration is one aspect of a delegate space. The other aspect is the provision of homepages for doctypes. Index spaces define categorizing document types like tags, categories, subjects, and types, including topic type and tag type. These categories help readers to navigate a site. This categories are often shared between spaces. Usually there are some categories that are used in every space.
Since index spaces have typically sitewide access. For a public facing website this information is by default open to anonymous users. You may restrict the access to particular pages, but the users with least privileges have access to the homepage of the space and therefore to the configuration of this space. To hide sensitive information or information that is not relevant to every space visitor, the information architect may decide to store information with higher access levels in separated spaces. These spaces are called attachment spaces since they are attached to another space. In many cases this central space for attachment spaces is an index space. Attachment spaces are responsible to store information of a given kind. The library stores resources. The addressbook address book stores persons and stakeholders.
To attach a space to an index space, the space key is listed by the delegate-space property.
|
...
Section | ||
---|---|---|
| ||
|
...