[ 
https://issues.apache.org/jira/browse/SOLR-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Upayavira updated SOLR-4157:
----------------------------

       Priority: Minor  (was: Major)
    Description: 
The admin UI has a 'query' pane which allows searching the index. However, this 
is currently an 'expert' level feature, as you must specify exact request 
parameters and interpret output XML or JSON. 

I suggest we add simple versions of each. A simple query pane would give a more 
conventional search interface for running queries. A simple results pane would 
give HTML formatted results with features to nicely display hightlighting, 
explains, etc.

To give an idea of what this might look like, I've attached a rudimentary patch 
that gives an HTML option for wt which formats the query results as (somewhat 
minimal) HTML.

The challenge will be in producing a search interface that is schema agnostic, 
as to be really useful, it should work with any index, and not just with the 
fields in the default schema (perhaps Erik Hatcher is right, this should be 
backed by the velocityResponseWriter).

Thoughts welcome.

  was:
The /browse interface is looking old. It also gives the impression that using 
the VelocityResponseWriter to create HTML is actually a good idea.

At the same time, /browse is actually quite useful - it provides easy access to 
some features such as explains, raw queries, etc, in an easy and usable way.

We also have a lovely new admin UI.

So, after some thought, it occurred to me that we should migrate the 
functionality of /browse to the admin UI.

At present, in the query pane, we have an 'advanced' query pane (you just enter 
request parameters) and an advanced results pane (we just show raw XML or JSON, 
etc). 

I suggest we add simple versions of each. A simple query pane would give a more 
conventional search interface for running queries. A simple results pane would 
give HTML formatted results with features to nicely display hightlighting, 
explains, etc.

To give an idea of what this might look like, I've attached a rudimentary patch 
that gives an HTML option for wt which formats the query results as (somewhat 
minimal) HTML.

Thoughts welcome.

        Summary: Add more conventional search functionality to the Admin UI  
(was: Migrate Browse functionality to the Admin UI)
    
> Add more conventional search functionality to the Admin UI
> ----------------------------------------------------------
>
>                 Key: SOLR-4157
>                 URL: https://issues.apache.org/jira/browse/SOLR-4157
>             Project: Solr
>          Issue Type: Improvement
>          Components: web gui
>            Reporter: Upayavira
>            Priority: Minor
>         Attachments: SOLR-4157.patch
>
>
> The admin UI has a 'query' pane which allows searching the index. However, 
> this is currently an 'expert' level feature, as you must specify exact 
> request parameters and interpret output XML or JSON. 
> I suggest we add simple versions of each. A simple query pane would give a 
> more conventional search interface for running queries. A simple results pane 
> would give HTML formatted results with features to nicely display 
> hightlighting, explains, etc.
> To give an idea of what this might look like, I've attached a rudimentary 
> patch that gives an HTML option for wt which formats the query results as 
> (somewhat minimal) HTML.
> The challenge will be in producing a search interface that is schema 
> agnostic, as to be really useful, it should work with any index, and not just 
> with the fields in the default schema (perhaps Erik Hatcher is right, this 
> should be backed by the velocityResponseWriter).
> Thoughts welcome.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to