Browsing - Overview and Contents

Through a combination of database tables and collmgr field configuration, dynamic browsing is available through the DLXS middleware. When the proper CGI-based URL is received, the middleware checks for certain metadata in the database tables, packages some of it in XML, uses some of it, as is in its stored format of XML, and lets XSLT format the results. At run time, no XPAT queries are needed, only MySQL queries are run against the item browse tables in the dlxs database.

After the tables are prepared, that is, populated with item metadata through the $DLXSROOT/bin/browse/ script (aka "database populator"), configuration for the behavior of dynamic browsing is accomplished by modifying certain collmgr fields.

Provisions will soon be made for creating static HTML browse pages with the database populator script.


Item browse database tables

There are three tables in the dlxs database that are specifically used for dynamic browsing in the middleware:

The ItemColl table holds, for each item/document and collection combination, one row containing the following columns:

The ItemBrowse table holds, for each item/document's browseable field (e.g., author, title, etc.):

The ItemBrowseCounts table holds, for each collection, a list of rows containing:

Collmgr fields for configuration

The main fields in the collmgr that need to be set properly are:

See Configure the collmgr fields below for more information.

Preparing collections for browsing

Configure the collmgr fields

Start collmgr and change the following fields:

Populating the item browse tables

To initially populate or to update the item browse tables, there is a script called which is located in $DLXSROOT/bin/browse. Running this program will populate or update the rows necessary in each of the three ItemBrowse related tables. These tables will be queried when the user requests browsing from the middleware.

However, please note: unless you are making changes to or need to debug, you should use the "wrapper" shell script provided in the same subdirectory. This wrapper is called ub and was written to ensure that

$DLXSROOT/bin/browse/ub -C class -c collection [ -r row [ -h host ] ] [ -f ] [ -p ]

If, for any reason, you must override the assumptions made by the "wrapper" script, you can always run the directly by entering:

$DLXSROOT/bin/browse/ class=AAA c=BBB host=CCC row=DDD

where AAA is either "text" or "image";; BBB is the collection id of the collection you want to create browsing for; CCC is the name of the host on which resides the XPAT index for the collection (this is not relevant to ImageClass, which uses MySQL for all queries); and DDD is key to the row in the database you wish to use (production, dlxsadm, or an individual developer's id). For example, you may want to point the script at new or test data on a machine that is different from your production machine. You could accomplish this by changing the host or devhost field for the collection in the collmgr. NOTE: If DLPS_DEV is set when you invoke (without the wrapper ub), the devhost field will be used; otherwise, the host field will be used.