Skip to main content
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    360 Search: Search Fields

    • Product: 360 Search

    How are the search fields in 360 Search mapped?

    The way we map 360 Search search fields will vary according to the native database's configuration:
    In most cases, the Title field in 360 Search is mapped to the primary title field of the native database that contains the primary name of the entity being described in the database entry (the title of a book or article, the name of a person in a biography database, the name of a company in a company profile database, etc.). There are some exceptions to this; in some cases, the databases we are submitting queries to are configured to search more than the primary title field when doing a title search. For example, they may also search alternate titles (e.g., titles displayed in a different language), subtitles, and, in some cases, titles of chapters in a book.
    360 Search's "Keyword" searches are mapped to the keyword field in the native interface of the database being searched (if there is one). Precisely which metadata fields this search field corresponds to depends on how the native interface is configured. As an example, in OCLC s ABI-INFORM database, a Keyword search is mapped to the fields for title, author, abstract, subject, and publication name, but not the full text; whereas for most (but not necessarily all) ProQuest databases, a Keyword search looks at author, title, publisher, abstract, publication title and information, and also the full text, including footnotes. So, a broader net is cast when issuing a Keyword search to most ProQuest databases than OCLC's ABI-INFORM, and with increased retrieval comes decreased relevancy. This is why, in general, we encourage clients to use Title keyword as their default search type, which brings fewer but more relevant results. The default search type you want to use, of course, if up to you.
    This field is mapped to the native database's 'Subject' field, if it has one. If the native database has no Subject field, results will vary depending upon the configuration of the native database. For some databases that don't have Subject searching enabled in their native interface, a term entered in the 360 Search Subject field will be re-mapped as a Keyword or Title Keyword search instead. Other databases will simply not return any results if they don't support Subject searching.
    'Full Text'
    "Full Text" searches are mapped to the entire text of the record, but only if the native database supports full text searches. If the native database does not support full-text searches, no results will be returned.
    "Any" searches will be mapped to the native database's field designated "any" or "all," if they support that. In many cases, however, "any" is treated by providers the same as "keyword." Libraries will need to experiment to see which databases support "Any" and which re-map the search to "keyword."

    • Date Created: 9-Feb-2014
    • Last Edited Date: 21-Feb-2014
    • Old Article Number: 7473