You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Keywords: Python, search query, literature search, literature review, meta-analysis.
51
53
52
-
<!--
54
+
<!--
53
55
- entry: enter queries from cli/programmatically
54
56
- manipulation: change query elements programmatically
55
57
- parsing: parse query (tree) object from different input formats
56
58
- formatting (translation): generate query strings in different syntax from query object
57
59
- analysis: retrieval size per sub-tree (Theis), syntactic analysis of contradiction
58
60
- simplification:
59
61
- Stemming and Lemmatization: Reduce words to their root forms to capture all variants (e.g., "running" to "run")., Wildcards: Use symbols (e.g., ?, #) within words to replace a single character (e.g., "wom?n" retrieves "woman" and "women"), Truncation: Use a symbol (usually ) to replace one or more characters at the end of a word (e.g., "comput" retrieves "computer," "computing").
60
-
- Combining terms: combining terms in queries like "run AND running" (absorption law), using wildcards to combine terms (if they have the same search-fields).
62
+
- Combining terms: combining terms in queries like "run AND running" (absorption law), using wildcards to combine terms (if they have the same search-fields).
61
63
- Redundant Nesting: Remove unnecessary parentheses to simplify the query structure (associative property), remove unnecessary parentheses
62
64
-refinement (TBD): expansion based on synonyms and thesaurus terms
63
65
- Synonym Expansion: Use a thesaurus or controlled vocabulary (like MeSH for medical terms) to expand queries with synonyms or related terms (see synonym-expansion-mesh.py)
@@ -294,7 +296,7 @@ instead, guidance can be found in the [online documentation](https://colrev-envi
294
296
295
297
# Related software packages
296
298
297
-
<!--
299
+
<!--
298
300
Tools for academic (Boolean) literature search queries:
299
301
300
302
- *Yale MeSH Analyzer*: Organizes MeSH terms (keywords) for selected papers in a table for manual search query construction, [link](https://mesh.med.yale.edu/) [@GrossettaNardiniWang2023]
@@ -311,7 +313,7 @@ Tools for academic (Boolean) literature search queries:
@@ -329,7 +331,7 @@ Table: Overview of related tools
329
331
-->
330
332
331
333
Table 1 provides an overview of related software packages and a comparison with *search-query*.
332
-
The leading query translators, *Polyglot search* and *Litsonar*, are proprietary and delivered through websites, i.e., without integration capabilities.
334
+
The leading query translators, *Polyglot search* and *Litsonar*, are proprietary and delivered through websites, i.e., without integration capabilities.
333
335
<!-- Litsonar: no parser -->
334
336
*Polyglot search* supports a more comprehensive selection of databases (15) and initial validation hints [@ClarkGlasziouDelMarEtAl2020a].
335
337
*Litsonar* supports seven databases, but does not offer parsers [@SturmSunyaev2019].
@@ -342,12 +344,12 @@ and *litsearchr* [@Grames2020] is an R library that supports semi-automated gene
342
344
\centering
343
345
\begin{tabular}{lllccccccc}
344
346
Software package
345
-
& Setup
346
-
& License
347
-
& \rotatebox{80}{Load}
347
+
& Setup
348
+
& License
349
+
& \rotatebox{80}{Load}
348
350
& \rotatebox{80}{Save}
349
-
& \rotatebox{80}{Lint}
350
-
& \rotatebox{80}{Translate}
351
+
& \rotatebox{80}{Lint}
352
+
& \rotatebox{80}{Translate}
351
353
& \rotatebox{80}{Improve}
352
354
& \rotatebox{80}{Automate}
353
355
\\
@@ -375,7 +377,7 @@ It is extensible and currently supports three databases (*Web of Science*, *PubM
375
377
The query parsers were tested with a comprehensive selection of peer-reviewed queries from *[searchRxiv](https://www.cabidigitallibrary.org/journal/searchrxiv)*[@White2024].
376
378
Testing showed that a significant number of queries still contained errors after passing the peer-review process, further highlighting the need for linters like *search-query*.
377
379
378
-
<!--
380
+
<!--
379
381
Given that *search-query* is designed for programmatic access, it can serve as a basis for query improvement and can be integrated into existing tool pipelines [@BellerClarkTsafnatEtAl2018].
380
382
381
383
There is no tool supporting programmatic access (integration with other tools).
0 commit comments