Constructing URLs for Resources
Any URL can be a target resource. Target resource URLs do not have a standard format.
To construct a target resource URL correctly, obtain the resource's URL or its "link to" syntax from the resource vendor or another reliable source. CSDirect's WebBridge Link Syntax page lists the "link to" URL syntax of many resources that have been tested with WebBridge.
For a resource that does not accept dynamic content (such as search parameters) in its URL, simply enter its URL in the appropriate resource definition. For more information, see:
- Entering URLs and Hyperlink Text for WebPAC Full Record Displays
- Entering URLs and Hyperlink Text for WebPAC Browse Screens
- Entering a URL and Hyperlink Text for Links from Sierra Full Record Displays
- Entering a URL and Hyperlink Text for Links from Sierra Browse Displays
A resource that accepts URLs with dynamic content, such as search parameters, uses "link to" syntax. The "link to" syntax describes any static portions of the URL and the order in which the dynamic elements must appear. Resources that provide "link to" syntax instead of a static URL usually directly link to articles or pass queries to the resource.
When a resource accepts dynamic content in its URL, you must:
- determine the source of the dynamic content
- construct the URL with variables representing the dynamic content
- enter the URL in the appropriate resource definition
The source of the dynamic content needed to construct the resource URL depends on the origin of the request for the resource.
- For requests for resources from external origins, the dynamic content needed to construct the resource URL is contained in the OpenURL (the request).
- For requests for resources from a Sierra or WebPAC origin, the dynamic content needed to construct the resource URL is contained in the displayed record.
The variables used to represent dynamic content are called field selectors.
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."
The term "secondary lookup" simply refers to additional dynamic content variables that represent coverage database fields (instead of OpenURL elements). The variables used to represent dynamic coverage database content are called field selectors.
Secondary lookups are not needed when the resource is requested from Sierra and WebPAC origins. The displayed record contains all the information necessary to construct the resource URL.
- See also:
- The Proxy Rewrite Method