Resource URLs with Dynamic Content from the Coverage Database (Secondary Lookups)

Some target resource URLs require dynamic content that is not in the OpenURL passed from the external origin. You can load this content into the coverage database and retrieve it with a "secondary lookup." A secondary lookup means that when the WebBridge resolution server generates the resource URL, the server includes data that exists only in the coverage database (secondary data) as well as meta tag data from the OpenURL (primary data).

For example, some resource vendors have proprietary journal IDs that must be used when linking to their site. The journal IDs are not included in the OpenURL (because they are proprietary, they are not known to the requesting external origin). If these journal IDs are loaded into the coverage database, the WebBridge resolution server can retrieve the journal ID in a secondary lookup and use it as dynamic content in the resource URL.

1. Identify the OpenURL elements required by the resource URL.
2. Determine the coverage database fields that are required by the resource URL.
3. Enter or verify the data in the coverage database.
4. Create field selectors for the OpenURL elements.
5. Construct a resource URL, using the format $#@<FIELDSELECTOR1>##@<COLUMNNAME>#$ where the secondary lookup dynamic content is required.
   
   The COLUMNNAME is the name of the column in the coverage database that contains the secondary lookup field.
   
   Put field selectors before coverage database column names.
   
   For example:
   
   http://www.vendor.com/cgi-bin/query?q=$#@ISSN##@JOURNALID#$

   NOTE

   To use secondary lookups, you must use a match data test and choose an option in the Match against this resource drop-down menu of the resource definition.