| { |
| "paper_id": "X96-1015", |
| "header": { |
| "generated_with": "S2ORC 1.0.0", |
| "date_generated": "2023-01-19T15:05:21.857967Z" |
| }, |
| "title": "SPOT: TRW'S MULTI-LINGUAl, TEXT SEARCH TOOL", |
| "authors": [ |
| { |
| "first": "Peggy", |
| "middle": [], |
| "last": "Otsubo", |
| "suffix": "", |
| "affiliation": { |
| "laboratory": "TRW Systems Development Division R2", |
| "institution": "", |
| "location": { |
| "addrLine": "2162 One Space Park", |
| "postCode": "90278", |
| "settlement": "Redondo Beach", |
| "region": "CA" |
| } |
| }, |
| "email": "peggy@wilbur.coyote.trw.com" |
| } |
| ], |
| "year": "", |
| "venue": null, |
| "identifiers": {}, |
| "abstract": "TRW has developed a text search tool that allows users to enter a query in foreign languages and retrieve documents that match the query. A single query can contain words and phrases in a mix of different languages, with the foreign-language terms entered using the native script. The browser also displays the original document in its native script. Key terms in the browser display are highlighted. The interface is targeted for the non-native speaker and includes a variety of tools to help formulate foreign-language queries. Spot has been designed to interface to multiple search engines through an object-oriented search engine abstraction layer. It currently supports Paracers Fast Data Finder search engine, with support for Excalibur's RetrievalWare currently being developed.", |
| "pdf_parse": { |
| "paper_id": "X96-1015", |
| "_pdf_hash": "", |
| "abstract": [ |
| { |
| "text": "TRW has developed a text search tool that allows users to enter a query in foreign languages and retrieve documents that match the query. A single query can contain words and phrases in a mix of different languages, with the foreign-language terms entered using the native script. The browser also displays the original document in its native script. Key terms in the browser display are highlighted. The interface is targeted for the non-native speaker and includes a variety of tools to help formulate foreign-language queries. Spot has been designed to interface to multiple search engines through an object-oriented search engine abstraction layer. It currently supports Paracers Fast Data Finder search engine, with support for Excalibur's RetrievalWare currently being developed.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Abstract", |
| "sec_num": null |
| } |
| ], |
| "body_text": [ |
| { |
| "text": "1.0. INTRODUCTION", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| }, |
| { |
| "text": "TRW has developed a text search tool that allows users to enter a query in a number of languages and retrieve documents that match the query. This text search tool is called Spot. The following subsections describe the design objectives and goals of Spot.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Design Objectives", |
| "sec_num": "1.1." |
| }, |
| { |
| "text": "Our government users currently use a variety of tools for different purposes. For example, an archival database is only available through a legacy text search system that performs its searches very quickly, but lacks a great deal in search functionality. Other users use Paracel's Fast Data Finder search engine due to its power-ful search capabilities and are only able to access its power through the FDF search tool user interface.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Support multiple search engines", |
| "sec_num": "1.1.1." |
| }, |
| { |
| "text": "One of our design objectives was to handle multiple search engines within the same user interface tool. This provides users with a single user interface tool to learn, while providing them with a choice of search engines. Users might choose to perform a natural language query using the Excalibur/ConQuest search engine's concept query and switch to the Fast Data Finder to search Chinese text.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Support multiple search engines", |
| "sec_num": "1.1.1." |
| }, |
| { |
| "text": "We also nimed to provide the users with the full functionality of each of the search engines. This approach necessitates a more generic approach to many functions to ensure that the same user interface can be tailored to differing search engine technologies.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Support multiple search engines", |
| "sec_num": "1.1.1." |
| }, |
| { |
| "text": "Internationalized support is fairly easy to obtain commercially for a number of commonly-supported languages. The commercial products for internationalization are designed to support the marketing of a tool in a specific set of foreign countries, where the menus, buttons, error messages, and text all need to be displayed in the appropriate foreign language. For example, if a specific product needs to be marketed to the Japanese, it might be running under Sun's Japanese Language Environment, with JLE providing support for entering and displaying Japanese text.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Support multi-lingual data", |
| "sec_num": "1.1.2." |
| }, |
| { |
| "text": "Multi-lingual support, however, is very difficult to obtain commercially. Our user community consists of native-English speakers, who want the menus and buttons to appear in English, but require support for viewing foreign-language documents in their native scripts, as well as entering foreign-language query terms in their native scripts. For this functionality, internationalized support is inadequate.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Support multi-lingual data", |
| "sec_num": "1.1.2." |
| }, |
| { |
| "text": "Users who are not native speakers of the foreign language in which they are submitting a query would like tools to assist in building queries. For example, we located a large Japanese-to-English thesaurus that was available in electronic for~L It would be very useful for native-English speakers to look up relevant words in the Japanese thesaurus for assistance in building their queries.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Support query generation tools", |
| "sec_num": "1.1.3." |
| }, |
| { |
| "text": "In addition, words that are of a foreign origin are often transliterated in a number of different ways. For example, the name \"Kadafi\" is often spelled \"Khadafi\" or \"Gadam'. Query generation tools that allow users to enter \"Kadafi\" and find the other possible spellings are designed into Spot.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Support query generation tools", |
| "sec_num": "1.1.3." |
| }, |
| { |
| "text": "Spot was designed to be the user interface for a large archival database of hundreds of gigabytes of data. It needs to provide hundreds of users with access to this database.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Maximize performance", |
| "sec_num": "1.2." |
| }, |
| { |
| "text": "An archival database using the Fast Data Finder was implemented using Paracers Batch Search Server (BSS) product. Spot currently interfaces to this FDF archival database. Development is currently proceeding to interface Spot to an Excalibur/ConQuest archival database.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Maximize performance", |
| "sec_num": "1.2." |
| }, |
| { |
| "text": "Our objective in developing functionality, including multi-lingual query generation tools and query functionality, has emphasized solutions that work very quickly, usually by exploiting the features of a specific search engine.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Maximize performance", |
| "sec_num": "1.2." |
| }, |
| { |
| "text": "Speed and throughput of searches through the FDF hardware search engine was measured using a commercial FDF-3 system.A single FDF-3 produced a search rate of around 3.5 MB/s, which could be obtained while searching 20 to 40 average queries simultaneously. A system of multiple FDFs can linearly expand the search rate.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Maximize performance", |
| "sec_num": "1.2." |
| }, |
| { |
| "text": "Some of the highlights of our current user interface system include the following:", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "User Interface Highlights", |
| "sec_num": "1.3." |
| }, |
| { |
| "text": "\u2022 Multi-lingual query entry ", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "User Interface Highlights", |
| "sec_num": "1.3." |
| }, |
| { |
| "text": "We have developed a multi-lingual text search tool that is being enthusiastically embraced by users. Some of our key innovations include:", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "KEY INNOVATIONS", |
| "sec_num": "2.0." |
| }, |
| { |
| "text": "\u2022 Search and retrieval of multi-lingual data, using queries specifying search terms in different languages and encoding sets.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "KEY INNOVATIONS", |
| "sec_num": "2.0." |
| }, |
| { |
| "text": "\u2022 Display of search results in native scripts including Japanese, Chinese, Korean, Arabic, Cyrillic, ThAi, and Vietnamese.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "KEY INNOVATIONS", |
| "sec_num": "2.0." |
| }, |
| { |
| "text": "\u2022 Multi-lingual query entry using NMSU's multi-lingual text widget (MUTT).", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "KEY INNOVATIONS", |
| "sec_num": "2.0." |
| }, |
| { |
| "text": "\u2022 Multiple languages in a single query.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "KEY INNOVATIONS", |
| "sec_num": "2.0." |
| }, |
| { |
| "text": "\u2022 Multiple encoding sets in a single query.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "KEY INNOVATIONS", |
| "sec_num": "2.0." |
| }, |
| { |
| "text": "\u2022 Query generation tools to help non-native speakers build queries in different languages.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "KEY INNOVATIONS", |
| "sec_num": "2.0." |
| }, |
| { |
| "text": "\u2022 Allow users to perform external processes on portions of browsed text.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "KEY INNOVATIONS", |
| "sec_num": "2.0." |
| }, |
| { |
| "text": "\u2022 Fill-in-the-box, customizable query entry forms.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "KEY INNOVATIONS", |
| "sec_num": "2.0." |
| }, |
| { |
| "text": "\u2022 Easy-to-use date-oriented database selection screen.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "KEY INNOVATIONS", |
| "sec_num": "2.0." |
| }, |
| { |
| "text": "\u2022 Allow users to select their desired search engine.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "KEY INNOVATIONS", |
| "sec_num": "2.0." |
| } |
| ], |
| "back_matter": [], |
| "bib_entries": {}, |
| "ref_entries": {} |
| } |
| } |
