[Inso Home Page] [Home] [Collection] [Book] [Expand] [Collapse] [Search Forms] [Previous Section with Hits] [Next Section with Hits] [Clear Search] [Preferences] [Print] [Help]

 inside  Expand Search


Creating a Nested Configuration File [Table of Contents] Referencing a Nested Configuration File

DynaWeb Publishers Guide

[-] 4. Managing DynaWeb Collections
[-] Grouping Collections in DynaWeb
[-] Placing Configuration Files

Placing Configuration Files

Unattached Configuration Files

Configuration files do not have to be attached to a specific collection or book. You can use a nested configuration file to provide a specific "look and feel", or to restrict searches to a specific subset of collections without actually placing the configuration file with the collection(s). By using absolute paths when referring to the configuration file and the nested collections, the nested configuration file does not need to reside with the collections it modifies.

Collection-Level

For collection-level configuration files, the file is placed in the collection directory. If you modify any templates or scripts in a collection-level configuration file, the changes will only affect the books contained in the collection. The configuration file can take the name of the collection (i.e., dwebdoc.dwc) or can remain dynaweb.dwc.

Book-Level

When placing a configuration file in a book, the file is placed inside the book's directory, at the same level as the ebt, figures, and index directories. Unlike collection-level configuration files, the name of the file must be dynaweb.dwc.

Configuration files placed at the book level only affect the book. The contents of the book-level configuration file override any other configuration files.


Creating a Nested Configuration File [Table of Contents] Referencing a Nested Configuration File