#searchfilter
#medlibs we added a paper by Morgan-Daniel J et al about the Development and Validation of a #SearchFilter to Identify #Research on #Bisexuality sites.google.com/a/york.ac.uk...
June 2, 2026 at 11:03 AM
There is a new #searchfilter in the latest issue of the JMLA @medlibassn.bsky.social "Mueller M, Askin N. Acute mental health concerns in emergency settings: development and validation of an Ovid #MEDLINE search filter" jmla.mlanet.org/ojs/jmla/art...

Shortly on the ISSG website as well :-)
https://jmla.mlanet.org/ojs/jmla/article/view/2081‬
August 4, 2025 at 2:07 PM
#medlibs we added an updated performance review (Muente et al) of a #geographic #searchfilter to focus on studies about #Germany sites.google.com/a/york.ac.uk...
January 22, 2025 at 5:00 PM
#medlibs we added a paper by Premji Z & Kraus H which brings a translation of a #PsycInfo #RCT #searchfilter from the Ovid interface to EBSCOhost sites.google.com/a/york.ac.uk...
ISSG Search Filters Resource - RCTs
Inclusion of a search filter on this site is not an endorsement of its validity or a recommendation for its use by the editors of this site, by the InterTASC Information Specialists SubGroup or by the...
sites.google.com
May 21, 2025 at 2:06 PM
It was a pleasure to work with @soyuka.me on improving the filters.

Let's go now to finish the SearchFilter redesign 👨‍💻💪

Otherwise looking forward to using all these 4.1 features in customer projects!
API Platform 4.1 est disponible ! Découvrez avec @soyuka.me les différentes évolutions qu'apporte cette release. Au programme :


🔧 Améliorations d'OpenAPI
🔦 Évolution des paramètres de filtrage et de requête
🔎 Hydra
🏎️ Laravel 12


les-tilleuls.coop/blog/sortie-...
Sortie d'API Platform 4.1 : la documentation au cœur de la découvrabilité des API | Les-Tilleuls.coop
La version 4.1 du framework API Platform est sortie : découvrons ensemble les nouveautés de cette dernière release.
les-tilleuls.coop
March 4, 2025 at 3:16 PM
it is a subject, not a study design #searchfilter, hence it does not qualify for inclusion on the website
August 19, 2025 at 1:25 PM
いつの(ゴールドスタンダードセット特定のための)検索結果から開発されたのだろう
#searchfilter
#memo
Yin, D., Engracia, M.V., Edema, M.K. et al. A PubMed search filter for efficiently retrieving exercise training studies. BMC Med Res Methodol 24, 302 (2024). doi.org/10.1186/s128...
A PubMed search filter for efficiently retrieving exercise training studies - BMC Medical Research Methodology
Background A barrier to evidence-informed exercise programming is locating studies of exercise training programs. The purpose of this study was to create a search filter for studies of exercise traini...
doi.org
December 23, 2024 at 9:58 PM
Working on translating a #SearchFilter from a database on one interface to the same database on a different interface - wow have I learned alot! Strangely, I've used both options before, & yet there was a lot I did not know that I now know. #SRLibrarianProblems #SystematicReview #ExpertSearching
July 21, 2023 at 9:38 PM
InputBox parameters and form submission
**_Fremantle_ 2025 July 4 (Friday), 1:34PM** · Wikimedia · MediaWiki · searching · InputBox · Thanks to a recent wish I've been poking a bit at the InputBox extension lately, to make it work better with MediaSearch and CirrusSearch. This involves making it honour the user preference for Special:Search or Special:MediaSearch (if the extension for the latter is installed), and fixing up the way in which it passes its `searchfilter` parameter to the search page. The fix for the first issue was to set the initial form action (which ends up in the parser cache and so can't be user-specific) to the site's default, and then have a front-end switch that dynamically changes it to whatever the current user has as their preference. Slightly clunkily, this involves sending both possible URLs to the front end and then choosing between them, because otherwise they wouldn't be localised. The second issue came about because InputBox submits `search` and `searchfilter` values as separate GET parameters, and then on loading the special page it would changes the internal request object to have a unified value (i.e. these two values concatenated with a space between them). The trouble with that was that you'd end up at a URL like `Special:Search?search=foo&searchfilter=insource:Bar` and so anything that was accessing the `search` value directly would get it wrong. So the fix was to unify the values and then redirect to a new URL without `searchfilter`, and also to skip that redirect by doing the same sort of replacement in the front-end. So most people will not get the redirect, but we always aim to have a no-JS fallback. I did wonder about switching the input names around so that there's no visible change to the text input, which might be confusing to people who see it change but only after they've clicked submit and so there's no time to notice what it's doing. I think there are similar improvements that could be made to other parts of InputBox, such as `type=move` with a `prefix`, but no one's complained about that not working so I don't think I'll bother digging any further for now. ← PreviousNext → **Reply, comment, contact, follow, etc.** My main RSS news feed: https://samwilson.id.au/news.rss (or Wikimedia.rss, Fremantle.rss, OpenStreetMap.rss, etc. for topic feeds). Email me at `sam samwilson.id.au` or leave a comment below… _No comments yet_ + Add a comment
samwilson.id.au
July 8, 2025 at 5:10 PM
InputBox parameters and form submission
**_Fremantle_ 2025 July 4 (Friday), 1:34PM** · Wikimedia · MediaWiki · searching · InputBox · Thanks to a recent wish I've been poking a bit at the InputBox extension lately, to make it work better with MediaSearch and CirrusSearch. This involves making it honour the user preference for Special:Search or Special:MediaSearch (if the extension for the latter is installed), and fixing up the way in which it passes its `searchfilter` parameter to the search page. The fix for the first issue was to set the initial form action (which ends up in the parser cache and so can't be user-specific) to the site's default, and then have a front-end switch that dynamically changes it to whatever the current user has as their preference. Slightly clunkily, this involves sending both possible URLs to the front end and then choosing between them, because otherwise they wouldn't be localised. The second issue came about because InputBox submits `search` and `searchfilter` values as separate GET parameters, and then on loading the special page it would changes the internal request object to have a unified value (i.e. these two values concatenated with a space between them). The trouble with that was that you'd end up at a URL like `Special:Search?search=foo&searchfilter=insource:Bar` and so anything that was accessing the `search` value directly would get it wrong. So the fix was to unify the values and then redirect to a new URL without `searchfilter`, and also to skip that redirect by doing the same sort of replacement in the front-end. So most people will not get the redirect, but we always aim to have a no-JS fallback. I did wonder about switching the input names around so that there's no visible change to the text input, which might be confusing to people who see it change but only after they've clicked submit and so there's no time to notice what it's doing. I think there are similar improvements that could be made to other parts of InputBox, such as `type=move` with a `prefix`, but no one's complained about that not working so I don't think I'll bother digging any further for now. ← PreviousNext → **Reply, comment, contact, follow, etc.** My main RSS news feed: https://samwilson.id.au/news.rss (or Wikimedia.rss, Fremantle.rss, OpenStreetMap.rss, etc. for topic feeds). Email me at `sam samwilson.id.au` or leave a comment below… _No comments yet_ + Add a comment
samwilson.id.au
July 4, 2025 at 5:43 PM
📦 cakedc/search-filter 2.0.9

SearchFilter plugin for CakePHP

🔗 https://github.com/CakeDC/search-filter
July 26, 2025 at 4:11 PM
Google introduces a new search filter called "Web" to streamline results, displaying text-based links exclusively. Enhance your browsing experience with focused search outcomes! #Google #SearchFilter #WebResults #BrowsingExperience r/martechnewser
May 15, 2024 at 1:03 AM