[ 
https://issues.apache.org/jira/browse/SOLR-10081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15866180#comment-15866180
 ] 

Christine Poerschke commented on SOLR-10081:
--------------------------------------------

Hello [~qfdk],

Thank you for your interest in the Apache Solr Learning-to-Rank (LTR) plugin 
and thanks for opening this ticket.

My initial thoughts would be that your GenTrainingDataSolr web UI is 
conceptually independent of any particular search engine and that as such the 
web UI would best be maintained and shared independently e.g. via a repo such 
as your [GenTrainingDataSolr|https://github.com/qfdk/GenTrainingDataSolr] repo.

In your repo seeing the _Apache Solr_ vs. _Apache Solr with LTR_ comparison in 
your [second 
screenshot|https://github.com/qfdk/GenTrainingDataSolr/blob/master/imgs/2.png] 
reminded me of the [Quepid|http://quepid.com/] tool. If you haven't come across 
Quepid before then [this blog 
post|http://www.flax.co.uk/blog/2016/07/08/setting-first-quepid-test-case/] is 
great to get started.

Regards,

Christine

----

PS: [~upayavira] and [~romseygeek] - would you have any thoughts to share here 
perhaps e.g. based on your work with the Solr Admin UI and/or your experience 
with Quepid?


> Web UI (Generate Training Data ) for LTR plugin
> -----------------------------------------------
>
>                 Key: SOLR-10081
>                 URL: https://issues.apache.org/jira/browse/SOLR-10081
>             Project: Solr
>          Issue Type: New Feature
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: qfdk
>
> This is a New Feature for LTR plugin. It will help you to generate the 
> training data (HUMAN_JUDGEMENT) by using score between 0-4. Live demo 
> http://ltr.qfdk.me



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to