Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing Search API search engine Documentation #862

Open
serkef opened this issue Oct 27, 2023 · 1 comment
Open

Missing Search API search engine Documentation #862

serkef opened this issue Oct 27, 2023 · 1 comment
Labels
curbside_appeal Make it easier for folks to get into Quepid and trust it. documentation Improvements or additions to documentation help wanted Extra attention is needed

Comments

@serkef
Copy link

serkef commented Oct 27, 2023

Is your feature request related to a problem? Please describe.
One of the options when setting up a search engine is a custom Search API (see pic below). Unfortunately, there is no documentation on how to use it. Especially it is not defined how the mapping should work. It says:

This Javascript is run in the browser to map custom search api responses to what Quepid understands.

But I found nowhere in the documentation an explanation. Is it a mapping to Solr responses? Or Open search? Or Elastic? A clear schema definition would massively help.
image
image

Describe the solution you'd like
A description and an example of what the javascript mapping should return would be very helpful.

Describe alternatives you've considered
I've searched and found a blog post and a couple of related PRs [1,2], but none of them addresses the problem.

Additional context
Only 2 of the 6 Search Engine options are documented. Maybe it's something that is obvious and I'm missing.

@epugh
Copy link
Member

epugh commented Oct 30, 2023

I really appreciate your calling this out! It's exciting that the fact that you noticed that docs are missing means folks are interested!

So yeah..... In true open source pattern, we moved faster on writing the code then we did on writing the docs/tutorials to support the code.

So, we have two things to get better docs, we need some folks to volunteer to do the docs, and then the repo that hosts the docs, quepid-web which is currently a private repo needs to be made public so folks can contribute.. And then, with that, we need to rewrite the https://quepid.com/tutorials/#quepid-for-human-raters section to reflect the use of books!

@epugh epugh added documentation Improvements or additions to documentation help wanted Extra attention is needed curbside_appeal Make it easier for folks to get into Quepid and trust it. labels Nov 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
curbside_appeal Make it easier for folks to get into Quepid and trust it. documentation Improvements or additions to documentation help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants