UMN Search: Adding University Search to Static HTML
This guide details implementing the U search on an HTML site using the Google Search Appliance (GSA).
To get the official UMN HTML header, use the Header & Footer Template Builder.
Search form basics
A search bar, or search field, is a simple form with visible and hidden elements.
- Text field input
- Where the user types the search query
- Search button input
- Initiates the search
- Placeholder text
- The text in the search field that disappears once the user begins entering text
- Use to indicate what website a visitor is searching, i.e., “Search the Government Relations Website.”
The hidden elements tell the form which collections to search, how to style the results, and other options for filtering, sorting, and displaying results.
The input elements needed to create the search form are:
- Collection—Specify your campus collection. By specifying your campus collection here, and requesting result biasing for your own collection (the last step in the search set-up process), your search will prioritize your unit’s search results but still display campus results below unit results.
- Front end—Specify your unit’s front end. This is typically the same name as your collection.
- Proxy Style Sheet
- Enter the name of a front end
- The proxy style sheet (which is contained within the front end configuration) controls the visual output of the search results
- In most cases, this should be the same front end as specified in Front end. Cases where it could be useful to have separate style sheets would be if you have a front end for a unit but different front ends with specific keymatches and filters for sites within the unit. For example, a department within a college may want to specify its own front end in the proxy style sheet to display the department's heading and navigation in the site's search results.
- Other search parameters can be found in the Google documentation
Below is the basic html that should be used for your unit search.
It can also be found on the github repo for the project
Notes on the html
Site (collection), client (frontend), and proxystylesheet (frontend) should all specify your site’s collection and front end.
<form action="/%3Ca%20href%3D"http://google.umn.edu/search">http://google.umn.edu/search" id="" method="get" name="gs">
<!-- text field -->
<input name="q" type="text" aria-haspopup="true" autocomplete="off" class="q" maxlength="256" size="64" value="">
<!-- submit button -->
<input name="btnG" type="submit" value="Search">
<!-- site, client, proxystylesheet -->
<input name="site" type="hidden" value="collection">
<input name="client" type="hidden" value="frontend">
<input name="proxystylesheet" type="hidden" value="frontend">
<!-- filter value=0 means no filter, all results shown, generally the best option, but default is 1 -->
<input name="filter" type="hidden" value="0">
<!-- allow up to 5 keymatches. default is 3. we prefer 5 -->
<input name="numgm" type="hidden" value="5">