![]() The estimated total of all documents that match the query. The number of documents returned with this request. The index of the last result document returned. The index of the first result document returned. This hash represents the search query response. The portion of the search query entered in the input box, excluding attribute filters. The search query to be displayed, usually for the page title and the hit statistics. This hash represents the search query request. If an error occurred, this variable holds the error message. The logout URL, if the user is logged in.īoolean value that indicates whether the result clustering sidebar should be shown. The login URL, if the user is not logged in. This hash contains variables that contain the URL of pages in the query application. This sequence is a list of hashes, each representing one source group active on the instance. It is an HttpRequestParameterHashModel, as provided by the FreeMarker API. This hash contains the URL query parameters for the request. If isLoggedIn is set to false, then this parameter does not hold any value.īoolean value that indicates whether secure search is enabled. If isloggedIn is set to true, then this parameter holds the user name. This hash contains information related to secure login and authentication.īoolean value that indicates whether the current user is logged in. Table 10-2 Data Models for the Main Search Pages Variable The results are returned in the text format from the csv page. ![]() The default template renders the data in the RSS 2.0 format.Ĭsv.ftl: This provides the search results in a comma-delimited format. The results are returned in the text or XML format from the feed page. ![]() Rss.ftl: Provides an RSS feed of the search results. The default template renders the data in the ATOM Feed 0.3 format. This is done by specifying the option feed?output=atom. These pages can be customized using the following template files:Ītom.ftl: Provides an ATOM feed of the search results, which are returned as text or XML from the feed page. These output pages display the search results as RSS feeds or in a comma-delimited format. The header, footer, and CSS files for the supplemental pages can be customized by modifying the following template files: inc_supplemental_header.ftl, inc_supplemental_footer.ftl, and inc_supplemental_includes.ftl The cache page logo can be customized using the file web.xml.Į-mail result browser: mail.jsp and pmail.jsp This page acts as the header for pages displayed from the cache. Inc_header.ftl, inc_footer.ftl: These template files are used to customize the header and footer information of the main search pages You can customize it to provide useful query suggestions to the user.Įrror.ftl: Displays an error message for invalid search queries, such as invalid syntax. Noresults.ftl: This page is displayed when a search query returns no results. Results.ftl: Displays the search results page. Can be customized to display a splash screen. Query.ftl: The initial page displayed before a user enters a search query. The following template files are used to customize the main search pages: These pages display the query box, search results, and any search errors and offer the most customization possibilities. Table 10-1 List of Template Files UI Pages These components are provided as FreeMarker macros in the template library. The internal rendering logic for the various visual components on the search results pages. Then, the results data is used to render the search results using customized template files. The search query on the text index is performed first. The Oracle SES query engine full-text search pipeline. The search results list, which is handled by the List Advanced Configuration Style Sheets. The following aspects of the Query UI cannot be customized using template files and style sheets: Modifying certain behavior of Oracle SES JavaScript components, such as result clustering. Using common header and footer templates that can be included by all pages. Supporting RSS, Atom, and CSV formats on the result list. These skins can be selected using a URL parameter. Modifying the page header and footer including static text and links to other pages The changes that can be made to the UI include:Ĭhanging the look and feel including the colors and fonts See the FreeMarker Web site for information about FreeMarker template files. To customize the UI using the template files and style sheets, you must know how to use the FreeMarker Template language and CSS style sheets. You can also create style sheets (CSS files) that define how the pages are visually styled and then provide a link to the CSS files from the template files. These template files can then be used by the application logic to render the Oracle SES query UI. You can customize the Oracle SES query UI by modifying certain template files that define the display content in the UI.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |