Use the Metadata Server to Store the Data Catalogue Information Pages - SuperWEB2

If you have configured SuperWEB2 to use the metadata server for multilingual datasets, then you can choose to store the data catalogue text in the metadata database instead of static HTML pages.

When this option is activated, SuperWEB2 will automatically use the description text from the metadata database, if a description is present. It will fall back to using the appropriate static HTML page if there is no text for the currently selected dataset and language.

This setting only applies for datasets where the multilingual property has been set to true in SuperADMIN.

Step 1 - Activate the Metadata Description Setting

To activate this option, you need to change a setting in the configuration.properties file:

1. Open <tomcat_home>\webapps\webapi\WEB-INF\classes\configuration.properties in a text editor.

2. Locate the following setting:

   CODE

   catalogue.infoPanel.displayDatabaseMetadataDescription=

3. Change the setting to true:

   CODE

   catalogue.infoPanel.displayDatabaseMetadataDescription=true

4. Save your changes and restart Tomcat or the SuperWEB2 service.

Step 2 - Populate the Metadata Database with Descriptions

Once you have activated the option, populate the db_domain table in the metadata database with your descriptions. Each row in this table relates to one of your SXV4 datasets. Populate the <id>_desc column with the description you want to appear on the catalogue page for that language (where <id> is the language code).

You can either use simple plain text, or you can insert full HTML content into this database column. Before starting, make sure that the data type of the <id>_desc column is set to something that allows enough characters to be inserted into that column. This is particularly important if you are using full HTML pages, as these may require a large number of characters. For example, you may wish to set the data type to something like varchar(MAX).

The Metadata Server and SuperWEB2 both cache information from the database for performance reasons. If you make changes to the descriptions in the metadata database, you may need to clear both these caches to see those changes in SuperWEB2. See Clear Metadata Cache for more details.