Hmm, I'll take a swing at this but you should probably kick off a thread on https://groups.google.com/g/dataverse-community where you might get a reply by Jim Myers, who implemented Configurable Search Services in #11281.
Nobody is using this feature in production as far as I know.
At the 2025 community meeting, we demo'ed this functionality with an AI search service. I'm pretty sure the code is here: https://github.com/siacus/searchdv
Stefano mentioned in his slides:
![]()
As you can see from the screenshot above, yes, users select which search engine they want to use.
We used to have a demo up, for the 2025 community meeting, but it doesn't seem to be up anymore.
Thank you, Phil! I rember I saw a demo about it but didnβt rember where. Anyway, I will try how it works.
Sure, as you may have noticed in the docs, there are a couple goofy examples to play with: GoldenOldiesSearchServiceBean and GoldenOldiesSearchServiceBean.
Jim and Stefano also gave a talk that was a much deeper dive: https://osf.io/j4r2e/files/27ykf
Maybe we should link to those slides from the docs.
Hmm, https://qa.dataverse.org/api/search/services still shows both search services:
{
"status": "OK",
"data": {
"services": [
{
"name": "postExternalSearch",
"displayName": "Natural Language Search"
},
{
"name": "solr",
"displayName": "Dataverse Standard Search"
}
],
"defaultService": "solr"
}
}
Oh! I forgot we renamed "spa" to "modern"! You can see it at https://qa.dataverse.org/modern/
![]()
D'oh!
"ErrorΒ -Β There was an error when reading the resource. Reason was: [500] Internal server error. More details available at the server logs."
Well, you can see what the UI looks like, at least! :sweat_smile:
Last updated: May 30 2026 at 06:18 UTC