[
https://issues.apache.org/jira/browse/SOLR-8209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14978773#comment-14978773
]
Gus Heck commented on SOLR-8209:
--------------------------------
bq. "Form a theory / create a collection / add fields via schema tab / add
sample documents to needed to prove the theory / run query via query tab"
Yup we are more or less on the same page there.
bq. Really, the biggest thing needed (and the default option for the UI) should
be a form that allows you to add multiple fields, picking the field name from a
dropdown (can be overridden for dynamic field names) and field values. This
would improve CREATE. Is that what you meant by "data entry form builder"?
Yup, though thinking about this after I made my comment I realized that it's
going to imply a need for some form of persistence. (As would complex
grid/table ui configurations). Any time you let the user configure heavily you
have to let them store it somewhere or it's not useful. We could use browser
storage, since this is not supposed to be a end user facing page, though even
admins/explorers might get irritated at not having the configured form
available from home etc...
> 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]
