[
https://issues.apache.org/jira/browse/SOLR-8209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14978689#comment-14978689
]
Erik Hatcher commented on SOLR-8209:
------------------------------------
bq. /browse already has a search UI (... try pointing it at an index that
doesn't have the "cat" field)
Try the Solr 5 data driven /browse. techproducts kitchen sink is the issue on
that. The data driven one is entirely field/data agnostic. Facets appear if
you've configured them, otherwise do not.
/browse really ought to be considered to be one of the ways this "documents"
view thing should work. For one thing, it's highly customizable by the end
user so any debate about how things should render can be made pluggable
straightforwardly. Mmm cookies _and_ milk!!
As someone who has written and been involved in a boatload of "general purpose"
browse/documents/search UI efforts - there's no one right answer and you end up
building a general purpose thing that has a zillion switches and options. Fun
times indeed.
VelocityResponseWriter has more power and flexibility than folks give it credit
for, and it's my fault for not educating and demonstrating it well enough (I've
got a blog draft on it that is overdue to publish, consider me nagged to get
that done ASAP). It'd be a shame (and disservice/injustice :) for it not to be
factored in. It can be used to generate a grid, or a list view, toggleable by a
switch... straightforwardly (and fairly cleanly I'd even assert, relative to
any other technique that would be used here).
> Admin UI documents tab improvements
> -----------------------------------
>
> Key: SOLR-8209
> URL: https://issues.apache.org/jira/browse/SOLR-8209
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 5.3
> Reporter: Upayavira
> Assignee: Upayavira
>
> A newbie, when clicking on the 'documents' tab might expect to, well, see
> documents. Instead, they see a UI that very low level allows them to post
> JSON/XML to add documents, etc. This presumes knowledge of Solr APIs in order
> to make good use of it, which goes against the intention of the UI - to make
> it easier for people.
> In its place, I propose to show a data-grid. This grid will contain maybe the
> first 100 documents in the index. It could have infinite scroll (to a certain
> point) to show further documents. It will have "filter" options alongside the
> field headings, allowing the filtering of fields (exact term match filtering,
> or wildcarded).
> The left-most column will contain pencils. Clicking on this will bring up a
> form that allows a user to edit the document (We could be clever hear - if
> the index contains indexed fields that have content, we could warn people
> that content from those fields would be lost if documents containing those
> fields is re-indexed).
> At the top is a button which, when clicked, brings up a form that allows us
> to insert a new document. This will be a tabular view - the left column is
> field names (a dropdown) and the right a free text box for content.
> We could add an advanced button that brings up a q= box, allowing you to
> enter arbitrary queries. In time, this could expand to include a query
> builder - a bit like the query tab.
> We could add delete by query functionality here, too.
> We should probably have two buttons at the top - one that brings up a modal
> allowing the user to enter arbitrary JSON or XML for posting to Solr, and the
> other that brings up a modal allowing the user to upload a file from their
> filesystem - this means we retain the essential functionality that is
> currently present in the documents tab.
> Basically, we give a very straightforward view of the content of an index,
> much like one would in a relational database tool.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
