View by category

Search Tips: What makes a Scopus search complex?

Last updated on October 20, 2025

Boolean-type search is a powerful and precise tool that allows you to tailor your search criteria to obtain specific results. You can use Boolean search through both Basic Document Search and Advanced Search.

Previously, the legacy Scopus's query interpreter was more lenient with complex string combinations, deeply nested proximity operators, extensive use of filters, incorrect usage of special characters and search fields, and intricate Boolean logic. With the recent system optimizations (Summer 2025) for more robust and efficient parsing, these complex query structures may on occasion be identified as syntactically incorrect or too ambiguous for effective processing if they trigger alerts that might harm our system , meaning we cannot guarantee they will run reliably on Scopus.

Please Note: Scopus has NO EXPLICIT limit on the length of queries or the number of boolean operators. However, when using the Exclude or Limit to function (please use them responsibly)

To ensure your queries function correctly and efficiently, you may encounter some that must now be restructured and optimised to align with these enhanced parsing capabilities. Our team is available to assist you in Optimize your queries to meet current system requirements.

Below are a few tips to help you get started:

When you search in Scopus, it's important to understand how different types of documents are indexed and searched. This can explain why your search results might vary depending on the fields you use.

Core Documents: These are documents fully indexed in Scopus. For these, Scopus has complete information (titles, abstracts, authors, keywords, full reference lists, etc.), and all this data is thoroughly searchable across various fields.

Secondary Documents (References to Non-Indexed Items): These are documents cited in a Core Document, but which themselves are not fully indexed in Scopus. Scopus only knows about them because they were referenced. Think of them as citations to external works rather than fully cataloged items within Scopus.

Why Search Results Can Differ Depending on the field used to search:

Incomplete Data for Secondary Documents:
- Since Secondary Documents are not fully indexed, Scopus may have only partial or inconsistent information about them (e.g., missing abstracts, keywords, or even slight variations in titles).
- Impact: If you search for a term that should be in a Secondary Document's abstract, but Scopus doesn't have that abstract, the document won't appear in your results. What you see as the title of a reference might not be what Scopus searches in its index.
"REF" Field Specifics (Searching References):
- The REF field (References) searches information within the cited references of a Core Document.
- Scoped Search: The REF field is "scoped." This means that all your search terms must be found together within the same individual reference (citation) for a match to occur. It will not find results if your terms are spread across different references within the same parent document.
  Example: If you search REF ( "term A" AND "term B" ), it will only return documents where "term A" and "term B" are both present in a single citation. If "term A" is in citation #1 and "term B" is in citation #2 of the same document, that document will not be a result for this specific REF field search.
ALL" Field vs. Specific Fields:
- The ALL field searches across a very broad range of fields (e.g., Abstract, Title, Keywords, Authors, References). o When you search specific fields individually (e.g., ABS for Abstract, TITLE for Title, REF for References), you are narrowing the scope.
- Impact: An ALL field search will often yield more results than searching individual fields separately, because it covers a wider array of indexed content, including the primary content of core documents which is more comprehensively indexed.

Key Takeaway: When performing searches, especially using the REF field, be aware that the information displayed for a reference might not be fully indexed or might be indexed differently. For comprehensive searches, using the ALL field is generally recommended, or carefully structuring your REF field searches to account for its scoped nature.

Some searches can take longer than usual and use a lot of processing time and capacity. A search that contains common terms and many OR groups, together with many wildcards and proximity operators, is complex and can require a lot of processing. Scopus searches may even time out, especially if the server is very busy with other searches.

Searches like this can even cause simpler queries to be slow because they use up so much processing capacity. For this reason, Scopus now tries to identify them in advance and processes them in an area which interferes less with other searches.

Please consider the following common Don'ts when constructing your queries:

Don'ts	Examples
Don’t run dot/slash/hyphen queries with wildcards. The dot/slash/hyphen will be stripped, and the query will fail.	TITLE-ABS-KEY *(5.0)** (5.0) will be translated into (5 0) and 0* is not allowed (since it’s a single character wildcard). FUND-ALL *(izp-2021/1)** (izp-2021/1) will be translated into (izp-2021 1) and 1* is not allowed (since it’s a single character wildcard). TITLE-ABS-KEY *(fire-)** (fire-) will be translated into (fire ) and * (standalone wildcard) is not allowed
Don’t use a minus in front of a term as (-) is a reserved character. A hyphen between terms is OKAY	TITLE (-french) Query will fail or return no results.
Don’t use proximity operator with exact phrase on one side of the operator (instead you can use keyword or loose phrase)	TITLE-ABS-KEY ({nitrous oxide} W/2 *emission)** Query will fail or return no results, or results will be ambiguous
Don’t use wildcards with exact search unless you want to be searching for the exact character.	TITLE-ABS-KEY *({nitrous oxi}** will find ONLHY nitrous oxi*
Don’t use double truncations as it’s not allowed	TITLE-ABS-KEY *(daylight)* Query will fail or return no results
Don’t use quotes around single terms, especially not if you’re also using a wildcard. P.S. # is not a wildcard	TITLE *(“mou”) Don’t use it!! TITLE (“mou#”)** Query will fail or return no results
Don’t use single quotes as they don’t do anything, if you want to do a phrase search, use double quotes	TITLE-ABS-KEY (‘daylight saving’) Doesn’t do anything. Use loose phrase search instead, TITLE-ABS-KEY (“daylight saving”)
Don’t use two single quotes to make a double quote, or faux quotes - those are different characters.	TITLE-ABS-KEY (‘ ‘daylight saving'') Doesn’t do anything, and will give unexpected results.

Here are some of the factors that require the search engine to do extra processing and calculation, and reducing the number of these in any query may speed things up.

Broad searches - If the search contains only a lot of terms joined with "OR", the search engine must find all the documents that contain ANY of these things. If this is not limited by AND or other definitions ( like date range), then the number of documents to be considered becomes very large.
Common terms - Another factor that makes searches very broad is the use of common terms that occur in very many documents.
Wildcards - Wildcards, especially the multi-character wildcard *, mean that the search engine must match any words that fit the pattern. Although it is less of a problem at the end of a word, it still requires calculation of all possibilities. Remember, you do not need a wildcard for singular/plural forms. Scopus uses lemmatization in the search (unless you are using exact phrase) for English words and most scientific terms. Wildcards at the start of a word exponentially increase the possibilities (see examples below).

Examples

contrast finds contrast, contrasts, and vice versa (about 69,000 results in Article titles).
contrast* finds both these, but also finds (about 84,000 results in article titles) contrasting, contrasted, contrastain, contrastive, contrasteric, Contrastivism, contraste, ContrastRank, contrastivity, contrastable, contrastivist, contrastion, and various non-English terms.
con* finds about 43,000,000 results.

Note: The hyphen is treated as punctuation and therefore ignored if it is not in an exact phrase. Wildcards must be used with words because they cannot be standalone. When an hyphen is placed between a wildcard and a word, the wildcard will be dropped.

Examples

title-abs-key (*-art) will be searched as title-abs-key(art)
abs(iwv-*) will be searched as abs(iwv)

Proximity operators - Using "within" and "preceding' (W/n, Pre/n) means "AND but within the specified distance". So the search engine must calculate the distance between the terms in all the documents that contained them. The longer the distance, the larger this calculation can be.
You do not need a wildcard for singular/plural forms. Scopus uses lemmatization in the search (unless you are using exact phrase) for English words and most scientific terms.

Search Tips: What makes a Scopus search complex?

Did we answer your question?

Related answers

Recently viewed answers

Also available in

For further assistance: