CollectiveAccess uses a fairly extensive set of configuration files, listed below. Click on a file to see a detailed description of the file and its directives. Information on the syntax of CA configuration files see ConfigurationFileSyntax.
General configuration files
||General application configuration, including pointers to all of the other configuration files described here (except global.conf), is set in this file.
||Contains definitions for values used in other configuration files - values defined in this file are available for use in all other configuration files located in the same directory. As such all of the most commonly changed configuration values, such as file paths and database login information, are defined in this file and then "inherited" by other files.
||Defines the formats used by the MultiPartIDNumber id number processing plug-in to support structured entry and management of accession numbers and the like.
||Configures display parameters for dates and times in your system. Also configures expressions and their equivalent parsable dates for use as shortcuts.
||Defines settings for the CA search engine
||Defines indexing rules for various fields and attributes in the CA database. Only fields marked for indexing in this file are searchable.
Faceted browse configuration
Handling of uploaded media and files
||Lists the available storage areas ("volumes") for uploaded files. "Files" are non-media uploads that are stored as-is with no parsing, processing or generation of derivatives.
||Defines rules for displaying media.
||Defines rules for extracting and embedding media metadata.
||Lists the available storage areas ("volumes") for uploaded media. Unlike "files", uploaded media must be in a format supported by the media processing subsystem and undergoes parsing, processing and conversion into derivatives
||Defines rules for processing and transforming uploaded media.
||Several components of CollectiveAccess employ external applications to perform tasks such as processing of uploaded media or extraction of embedded content and metadata. The external_applications.conf file defines the locations of these applications on your server.
These files are used to govern internal functions of CA and, in general, should not be edited unless you know what you're doing.
||Defines the tables in the CA relational database and the relationships between those tables.
||Defines system navigation structure including menus and side navigation.
||Defines navigation back to results for various types of "find" operations.
||Lists all implemented attribute data types - the different types of "fields" CA supports.
||Defines actions users can be allowed (or disallowed) privileges for.
||Defines available user preferences and their possible values.
||Defines the default icon graphics to use for uploaded media when it is not possible to derive a thumbnail from the media itself (for example, when processing an audio file).
Please note there is a conf directory within each theme whose files override those in app/conf. You do not need to include the complete set of configuration files and the files in your theme's conf directory do not have to include every variable, they can contain only the setting you would like to override for that theme. This provides a simple way to have theme specific settings.
The following configuration files are specific to the Pawtucket public front-end web-application:
||Defines how and where Pawtucket output is cached to improve performance.
||Contains settings to customize the configuration and display of Pawtucket.
||Contains settings to configure Pawtucket to function within your server environment and to connect with your database and mail server.
||Contains settings to configure the form or forms used in Pawtucket's Advanced Search.