Content deleted Content added
Break up what formerly was one very long sentence into multiple sentences that define each term separately. |
TokenByToken (talk | contribs) revise for clarity Tags: Visual edit Disambiguation links added |
||
(29 intermediate revisions by 16 users not shown) | |||
Line 1:
{{short description|Classical information retrieval model}}
{{technical|date=June 2018}}The (standard) '''Boolean model
==Definitions==
In the Boolean model, documents and queries are represented using concepts from [[set theory]]. A document is seen as a simple collection (a set) of terms, and a query is a formal statement (a Boolean expression) that specifies which terms must or must not be present in a retrieved document.
* An '''index term'''
* A '''document''' is represented as a [[set]] of index terms. This is a [[bag-of-words model]], meaning the order and frequency of terms in the original document are ignored. For example, a document about Bayes' theorem might be represented simply as the set <math>\{\text{Bayes' theorem, probability, decision-making}\}</math>.
* A '''query''' is a formal expression of the user's information need, written using index terms and Boolean operators (AND, OR, NOT). The model retrieves every document that is considered a "match" for this logical expression.
===Formal representation===
The model can be defined formally as follows:
* Let <math>T = \{t_1, t_2, \ldots, t_k\}</math> be a set of all index terms.
* A document <math>D_j</math> is any subset of <math>T</math>.
* A query <math>Q</math> is a Boolean expression, typically in [[conjunctive normal form]]:<math display="block">Q = (t_a \lor t_b) \land (\lnot t_c \lor t_d) \land \dots</math>where <math>t_a, t_b, \dots \in T</math>.
Retrieval is the process of identifying the set of all documents <math>\{D_j\}</math> that satisfy the query <math>Q</math>. For example, for the simple query <math>Q = t_a \land t_b</math>, the system would retrieve all documents whose set of terms contains both <math>t_a</math> and <math>t_b</math>.
==Example==
Line 18 ⟶ 20:
Let the set of original (real) documents be, for example
: <math>
where
<math display="inline">
<math display="inline">
<math display="inline">
Let the set <math display="inline">T</math> of terms be:<math display="block">T = \{t_1=\text{Bayes' principle}, t_2=\text{probability}, t_3=\text{decision-making}, t_4=\text{Bayesian epistemology}\}</math>Then, the set <math display="inline">D</math> of documents is as follows:<math display="block">D = \{D_1,\ D_2,\ D_3\}</math>where <math display="block">\begin{align}
▲D_1 &= \{\text{probability},\ \text{Bayes' Principle}\} \\
D_2 &= \{\text{probability},\ \text{decision-making}\} \\
D_3 &= \{\text{probability},\ \text{Bayesian
\end{align}</math>Let the query <math display="inline">Q</math> be ("probability" AND "decision-making"):<math display="block">Q = \text{probability} \and \text{decision-making}</math>Then to retrieve the relevant documents:▼
▲<math display="block">Q = \text{probability} \and \text{decision-making}</math>Then to retrieve the relevant documents:
# Firstly, the following sets <math display="inline">S_1</math> and <math display="inline">S_2</math> of documents <math display="inline">D_i</math> are obtained (retrieved):<math display="block">\begin{align}
S_1 &= \{D_1,\ D_2,\ D_3\} \\
S_2 &= \{D_2\}
\end{align}</math>Where <math>S_1</math> corresponds to the documents which contain the term "probability" and <math>S_2</math> contain the term "decision-making".
# Finally, the following documents <math display="inline">D_i</math> are retrieved in response to <math display="inline">Q</math>: <math display="block">Q: \{D_1,\ D_2,\ D_3\}\ \cap\ \{D_2\}\ =\ \{D_2\}</math>Where the query looks for documents that are contained in both sets <math>S</math> using the intersection operator.
This means that the original document <math
== Advantages ==
Line 59 ⟶ 49:
* Easy to implement
* Intuitive concept
* If the resulting document set is either too small or too big, it is directly clear which operators will produce respectively a bigger or smaller set.
*It gives (expert) users a sense of control over the system. It is immediately clear why a document has been retrieved given a query.
== Disadvantages ==
Line 64 ⟶ 56:
* [[String search algorithm|Exact matching]] may retrieve too few or too many documents
* Hard to translate a query into a Boolean expression
* Ineffective for Search-Resistant Concepts<ref>{{cite journal |last1=Shokraneh |first1=Farhad |title=Stop searching and you will find it: Search-Resistant Concepts in systematic review searches |journal=BMJ Evidence-Based Medicine |date=6 August 2024 |pages=bmjebm–2023–112798 |doi=10.1136/bmjebm-2023-112798}}</ref>
* All terms are equally weighted
* More like ''[[data retrieval]]'' than ''information retrieval''
* Retrieval based on binary decision criteria with no notion of partial matching
* No ranking of the documents is provided (absence of a grading scale)
* Information need has to be translated into a Boolean expression, which most users find awkward
* The Boolean queries formulated by the users are most often too simplistic
* The model frequently returns either too few or too many documents in response to a user query
== Data structures and algorithms ==
From a pure formal mathematical point of view, the BIR is straightforward. From a practical point of view, however, several further problems should be solved that relate to algorithms and data structures, such as, for example, the choice of terms (manual or automatic selection or both), [[stemming]], [[hash table]]s, [[Inverted index|inverted file]] structure, and so on.<ref name="wartik">{{cite book | last = Wartik | first = Steven | title = Information Retrieval Data Structures & Algorithms | chapter = Boolean operations | publisher = Prentice-Hall, Inc. | year = 1992 | isbn = 0-13-463837-9 | url = https://www.scribd.com/doc/13742235/Information-Retrieval-Data-Structures-Algorithms-William-B-Frakes |
=== Hash sets ===
{{ main | feature hashing }}
Another possibility is to use [[Set (abstract data type)|hash
=== Signature file ===
Each document can be summarized by [[Bloom filter]] representing the set of words in that document, stored in a fixed-length bitstring, called a signature. The signature file contains one such [[superimposed code]] bitstring for every document in the collection. Each query can also be summarized by a [[Bloom filter]] representing the set of words in the query, stored in a bitstring of the same fixed length. The query bitstring is tested against each signature.<ref name="zobel" >
Justin Zobel; Alistair Moffat; and Kotagiri Ramamohanarao.
[https://people.eng.unimelb.edu.au/jzobel/fulltext/acmtods98.pdf "Inverted Files Versus Signature Files for Text Indexing"].
</ref><ref name="goodwin" >
Bob Goodwin; et al.
[https://safari.ethz.ch/architecture/fall2018/lib/exe/fetch.php?media=p605-goodwin.pdf "BitFunnel: Revisiting Signatures for Search"].
2017.
</ref><ref>
Richard Startin.
[https://richardstartin.github.io/posts/bit-sliced-signatures-and-bloom-filters "Bit-Sliced Signatures and Bloom Filters"].
</ref>
The signature file approached is used in [[BitFunnel]].
=== Inverted file ===
▲Another possibility is to use [[hash set]]s. Each document is represented by a hash table which contains every single term of that document. Since hash table size increases and decreases in real time with the addition and removal of terms, each document will occupy much less space in memory. However, it will have a slowdown in performance because the operations are more complex than with [[bit vector]]s. On the worst-case performance can degrade from O(n) to O(n<sup>2</sup>). On the average case, the performance slowdown will not be that much worse than bit vectors and the space usage is much more efficient.
{{ main | inverted index }}
An inverted index file contains two parts:
a vocabulary containing all the terms used in the collection,
and for each distinct term an inverted index that lists every document that mentions that term.<ref name="zobel" /><ref name="goodwin" />
== References ==
{{reflist}}
* {{ citation | last1= Lashkari | first1=A.H. | last2=Mahdavi | first2= F.| last3=Ghomi | first3= V. | title=2009 International Conference on Information Management and Engineering | doi= 10.1109/ICIME.2009.101 |
[[Category:Mathematical modeling]]
|