OpenURL is an industry-standard way of encoding resource metadata into a URL. Ares OpenURL is installed and functional as a part of the standard Ares Server installation and can be used in the Ares Client and through the web pages.
- Requesting items from the web pages via OpenURL: If your Ares web pages are functional and Ares OpenURL is functional, generally no further installation should be required.
- Submitting requests from within the Ares Client: Using the Submit via OpenURL button, staff users can submit requests to external systems via OpenURL.
Configuring Ares Requesting From Your Electronic Resources
While the Ares side of OpenURL is functional immediately, in order to allow instructors to request materials from your electronic resources, you will need to configure your OpenURL system to create a link to Ares.
The following target will need to be added to the OpenURL system at your institution: https://YourAresServerName/ares/ares.dll/OpenURL (example: http://training2.atlas-sys.com/ares/ares.dll/OpenURL).
The Ares OpenURLMapping Table
The OpenURLMapping table is found in the Ares Customization Manager under Web | OpenURL. It is pre-seeded with a setup that should work with most default OpenURL systems. If you need to change the behavior of how OpenURL interprets certain fields or genres, this is where you can make those changes. The OpenURLMapping table consists of the following fields:
ID | The order number of the OpenURL mapping items. |
URL_Ver |
This field has a default value of Default and rarely needs to be changed. Additional entries can be configured in the OpenURLMapping table with modified URL_Ver values targeting a specific OpenURL version if you would like to have separate mappings available based on the version of OpenURL used to place the request. An example of the value for OpenURL version 1.0 would be "Z39.88-2004". |
rfr_id |
This field has a default value of Default and rarely needs to be changed. Additional entries can be configured in the OpenURLMapping table with modified rfr_id values if you would like to have separate mappings available based on the source of the OpenURL link used to place the request. For example, to have all requests of a specified OpenURL genre considered a Book when submitted from FirstSearch, but to have those same requests considered an Article when submitted from Ovid, you could configure separate OpenURLMapping table entries for each of these behaviors with the rfr_id setting on the entries specifying which mappings to use for FirstSearch and which mappings to use for Ovid. Please contact your OpenURL source provider to determine the rfr_id value that should be used for that source. An example of the value used for FirstSearch is info:sid/firstsearch.oclc.org:WorldCat. This value will be stored in the CitedIn field in Ares if it is passed over via OpenURL (with the info:sid/ part removed).
|
Ares Action |
This field is configured with different values based on the direction of the OpenURL request: Converting a URL to an Ares Item Three actions requiring separate OpenURLMapping table entries are used to convert an OpenURL request to an Ares item: As these three actions work in conjunction with each other, please ensure that you create separate entries for each Ares Action below when adding new entries to the OpenURLMapping table targeting a specific rfr_id or URL_Ver value.
Building a URL from an Ares Item Three actions requiring separate OpenURLMapping table entries are used to build an OpenURL link from an Ares item record: As these three actions work in conjunction with each other, please ensure that you create separate entries for each Ares Action below when adding new entries to the OpenURLMapping table targeting a specific rfr_id or URL_Ver value.
|
Ares Field Name |
See the Ares Action documentation above for more detailed guidance on configuring the Ares Field Name for each action.
|
Open URL Field Values |
See the Ares Action documentation above for more detailed guidance on configuring the Open URL Field Values for each action.
Assigning Multiple OpenURL Values to the Same Ares Field Entries in the OpenURLMapping table configured to use the Ares Action 'Replace' can have separate OpenURL values assigned to the same Ares field in a single OpenURLMapping table entry. This is useful for handling different OpenURL mappings that end up going to the same Ares fields. You can separate these values with a pipe character (|). When Ares sees the pipe, it interprets everything up to that point in the expression. If it has no values for the OpenURL fields up to that point in the expression, then it continues and uses the next expression. If it already has a value, then it ignores everything after the pipe. You can have as many pipe/field value combinations as you need. Example: This example uses the default OpenURL Field Values configuration in the OpenURLMapping table entry for the Author field: <#rft.au>|<#rft.aulast>, <#rft.aufirst> <#rft.auinitm>|<#aulast>, <#aufirst> <#auinitm>
|
Ares Value |
The value in this column is configured differently for each Ares Action type. See the Ares Action documentation above for more detailed guidance on configuring the appropriate Ares Value for each action. Entries with action types of Replace or ReverseReplace do not need a value configured in this column.
|
Linking from the Ares Client to another OpenURL System
You can configure Ares to send requests from the Client to another OpenURL system such as ILLiad.
The OpenURLDestinations Table
The OpenURLMapping table is accessed in the Ares Customization Manager. If a site has placed values in the OpenURLDestinations table, they can send a request from the client to any external system to be filled (including ILLiad) via OpenURL. Ares will build an appropriate URL from the citation info in Ares, send it to the external system you select, then forward the Ares Item request to the status designated in the table.
The OpenURLDestinations table can have multiple entries for the external systems you may want to use. The OpenURLDestinations table consists of the following fields: Destination, DestinationURL and Destination Status.
Destination |
The name of the external system. |
---|---|
Destination URL |
The OpenURL formatted URL for the external system. |
Destination Status |
The status queue that the Ares Item request should move to when |
To include ILLiad in your OpenURLDestinations table, the Destination value must be ILLiad and the DestinationURL value would be the OpenURL formatted URL of the ILLiad server: http://your.illiad.server/illiad/illiad.dll/OpenURL. The Destination Status would be Awaiting ILL Processing.