Database Search API Integration Guide
Scott Wojtowicz, Last modified by Scott Wojtowicz August 14 2017 10:45 AM
With the abundance of electronic resources available today, many schools prefer to access their educational assets in one place. Federated Search Engines and other Discovery Tools allow libraries to do just that - easily browse through multiple content sources in their catalog at the same time.
The Infobase Search API provides a much needed “Communication Bridge” between our content and any Discovery Tool that our mutual customers may be using. Api.infobase.com quickly indexes search results from our Online Databases in a universal XML format. These customizable XML search results can then be parsed with search results from other outside sources by an Infobase Discovery Tool partner.
In this Search API Integration Guide, you will find everything you need to know to get started as an Infobase Discovery Tool partner.
The Infobase Database Search API is currently available for the following online products:
History Research Center
More of our products will be continually added to the API and new connections are actively being developed now. This guide will be updated accordingly.
In order to utilize the API, there are certain query parameters that must be added to the URL routing:
This is the customer’s Infobase Account ID. If you are using the API to harvest
This is the Discovery Tool Partner ID that will be provided once a connection has been established with Infobase.
This is the Product ID for what Infobase products you would like to query. Here are the currently available product IDs:
This is the key word(s) you are attempting to search by. In order to get all results, please leave this blank.
This is the desired output format you would like the results to be returned in. The available formats are:
After you have submitted a search query to the API,
Please note: The Account ID in the Record URL will match the Account ID provided in the original Search Query. Using a customer’s correct account ID is the only way for any authentication settings and usage statistics recording to work properly.
Here is an example of a Search Query for the term “frogs”:
The Account ID and Vendor ID have been set to 0 for this example.
Once completed, the XML end result would look like this for the first record returned:
<Database>History Research Center</Database>
<Title>Walleye (Sander vitreus)</Title>
North America,Percidae,Sport fish,Walleye,Spawn (biology),Frog,Egg (biology),Blue walleye,Sauger,Environment,Fish,Sander,Fauna of the United States,Environment
Record URL Authentication
It is Discovery Tools partner responsibility to ensure that the customer’s Infobase Account ID is used in the provided Record URLs. When harvesting for meta-data, the Account ID
If you have any