Space Groups

...

Section

title	Hierarchy of Spaces

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 IDX. This is only a default. The delegate spaces for a particular space are defined by the space property delegate-space.

Example Box

title	Commonly used Configuration

Assume that for each space you want the short description of a document to be rendered in front of the property table.

Set the space property extract-short-description-from-metadata-table to the value true in the index space, then every space will automatically use this property and render the short description as instructed.

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.

Example Box

title	Resource Types commonly used

If you have resource types like books, article, magazine, there is no need to duplicate this information. In case you put this information in a sitewide index space, every team can reuse this information in their spaces to organized their content.

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.

Note Box
A library should not store resource types. While a team may not be interested in sitewide resources, they may want to reuse the organization of resources. So consider to store the resource types in an index space.

To attach a space to an index space, the space key is listed by the delegate-space property.

Note Box

title	Reusing some types?

It is a bit cumbersome to ruse only some of the types in a downstream space. One approach is to establish a new homepage for the doctypes and use delegate documents. A delegate document references an existing document and reuses a subset of properties and sections.

This approach is very selective. A team can pick what information they want to use in their work. It also allows the team to have their navigation pages local in their space, not in a sitewide index space.

On the other hand this approach is also requiring much manual work. For each page another page needs to be created and the properties and sections to delegate to need to be selected.

...

Section

title	Spaces in an Organization

Example Box

Consider the following relationships of spaces.

Three teams use the sidewide index space with three attachment spaces. Team A decided to have an index space and an attachment space on their own. Team B only needs a configuration space (Index B), and Team C only uses a single topic space for their collaboration results.

When a team member adds a person document and sends it to its homepage, the projectdoc toolbox will find the sitewide address book.

Image Added

When a member of Team B adds a new document for a book description while working on Workspace 2 (WS2), this document will be send to the sitewide library.

Since Team A has established their own library in their space group, a new resource would be stored in their library space. If the team member decides to move this resource to the sidewide library, this would need to be done manually.

Since Team A does not use a glossary in their space group, a new glossary item is contributed to the sidewide glossary.

...

Space shortcuts

Page tree

Docs

Support

Free Blueprints

Tooling for Blueprints

Free Extensions

Spaces

Plugins for Maven

Incubator

Libraries for Java

Incubator

Add-ons for Confluence

Tools

Support

Team

Legal

Versions Compared

Old Version 20

New Version 21

Key

About

Keep up-to-date!

Powered by