Documentation Center

Collective Spaces configuration overview

Most of Collective Spaces is predefined. However, you may choose to modify the default values for certain options, either in Organize Space or by editing the configuration files on the Content Manager server.

Configuration options in Organize Space

Under the top-level Settings tab, configure the following options as needed:

  • Under the second-level XML Settings tab, in the third-level Collective Spaces tab, you will find settings that affect Collective Spaces overall, Draft Space only settings and Review Space only settings.
    The following are some examples of things you can change:
    • Enable or disable the uploading of images via Draft Space.
    • Make the reason field optional when creating suggestions (required by default).
    • Specify whether or not providing a resolution comment is required when resolving an annotation.
    • Specify the image resolution that is used in Collective Spaces whenever a user chooses the option to view an image in the review resolution.
    • Specify whether to show relationship tables or not (relationship tables are disabled by default).

    Separate topics in this section describe how to perform the various configuration tasks.

  • Under the second-level System tab, in the third-level Lists of Values tab, you can modify the Annotation types list of values and the Annotation resolution types list of values. The default lists of values, in both cases, are intended as examples.

Configuration options on the Content Manager server

Out of the box, Collective Spaces is set up so that you can successfully open documents that are valid against SDL DITA 1.3, OASIS DITA 1.3 or OASIS DITA 1.2. However, if you use your own custom DITA specializations, then on the Content Manager server, in the Web\InfoShareCS\custom\ folder, you will need to extend configuration files:
  • Collective Spaces uses a compiled version of the DTD/Schema files. The compiled schema's (in json format) can be found in the schemas subfolder.
  • The SchemaLocationConfig.xml file contains the file locations of the schemas together with their matching compiled schema location and their DTD Public ID or schema URN. Every time an XML document is opened in Collective Spaces, the system will try to find a matching entry in this file for the PublicId of the DTD used in the XML document. The location of the matching entry is used to load the corresponding compiled schema.
  • The BehaviorConfig.xml file contains the configuration that can be applied on top of the out-of-the-box configuration in order to do the following:
    • Describe how DITA XML elements should be rendered for a certain XML document.
    • Define which contextual menu items to show when the user is positioned on a certain XML element in Draft Space.
    • Define which additional menu items to show in the top menu.
    • Define which specialized XML elements a user is able to conref. (Note that the out-of-the-box elements can always be conrefed, but an element in an XML document can only be conrefed if it has its id attribute set.)
    Initially the BehaviorConfig.xml file is empty, because the out-of-the-box configuration provides a proper default, but it can be used to overwrite the out-of-the-box configuration or to configure behavior for your own custom DITA specialized elements.