This is a list of our configuration changes too deegree-csw - specifically version 2.3-pre (missing link) with an PostgreSQL backend.

Follow instructions in deegree's documentation

See deegree_csw_2.0.2_documentation_en.pdf. Make sure the document is in a version corresponding to your version of deegree-csw (in this case "deegree Web Catalogue Service v.2.2").

As a minimum, you will have to configure the database connection parameters in deegree-csw\WEB-INF\conf\csw\featuretypes\csw.xsd.
If you want any other computers besides localhost to access deegree-csw, you will have to replace it with an IP address or domain name in deegree-csw\WEB-INF\conf\csw\csw_capabilities.xml and wfs_capabilities.xml.

Set <gmd:title><gco:CharacterString> to greater than varchar(200)

By default, deegree limits the title element string value to 200 characters which is too short for many of our metadata records (especially for Maps).  The deegree folks encouraged us changing the length of the title field as well as other VARCHAR fields.  Following is the error deegree gives you on insert if your title is too long:

Error performing insert: ERROR: value too long for type character varying(200)

You can either change the string length in your DB creation scripts (create_database.sql and create_serachTables.sql?) or directly in the DB - public.ci_citsation.title.  I chose an arbitrary size of varchar(400).

 Use all fields for anyText searches (PostgreSQL)

By default, deegree only uses the title field for anyText searches which is apparently an Oracle limitation. Go to deegree-csw\WEB-INF\conf\csw\xslt\iso19115_transaction.xsl and iso19119_transaction.xsl and search for "Oracle."

Change above to the following: