[
https://issues.apache.org/jira/browse/SOLR-13133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gus Heck updated SOLR-13133:
----------------------------
Description:
In a recent discussion I was yearning for a better overview of the fields,
dynamic fields and types available. To that end and with probably little or no
will/ability to actually implement it in the Admin UI I did however spend a few
minutes drawing out what I think might be better than what we have now. This
issue is to record the idea and maybe inspire someone. There is a small chance
I'll decide I want to learn more about Angular and give a crack at it, but
anyone who likes it or thinks they have something even better is free to run
with it.
!schemabrowse.png!
The basic idea is that our current UI hides the fields/types in a dropdown
where they are impossible to see, and leaves acres of wasted space below. This
design endeavors to make use of that space. Also a couple details are repeated
such as the field type. The above image shows just 2 fields (_text_ and id)
with _text_ selected. Obviously the list would be much longer and also have a
section for types (hopefully with a nice pretty divider). The other key feature
here is an "at a glance" flag specifier (intended to represent the schema
values only, details of schema/props/index would be in the detail view to the
right as they are now) Flags that are capitalized are on and flags that are
lowercase are off. The sections correspond to the sections in the create field
dialog in the UI, with an additional -t- between the first two to represent
Tokenized or not.
was:
In a recent discussion I was yearning for a better overview of the fields,
dynamic fields and types available. To that end and with probably little or no
will/ability to actually implement it in the Admin UI I did however spend a few
minutes drawing out what I think might be better than what we have now. This
issue is to record the idea and maybe inspire someone. There is a small chance
I'll decide I want to learn more about Angular and give a crack at it, but
anyone who likes it or thinks they have something even better is free to run
with it.
!schemabrowse.png!
The basic idea is that our current UI hides the fields/types in a dropdown
where they are impossible to see, and leaves acres of wasted space below. Also
a couple details are repeated such as the field type. The above image shows
just 2 fields (_text_ and id) with _text_ selected. Obviously the list would be
much longer and also have a section for types (hopefully with a nice pretty
divider). The other key feature here is an "at a glance" flag specifier
(intended to represent the schema values only, details of schema/props/index
would be in the detail view to the right as they are now) Flags that are
capitalized are on and flags that are lowercase are off. The sections
correspond to the sections in the create field dialog in the UI, with an
additional -t- between the first two to represent Tokenized or not.
> Schema Browser could be better
> ------------------------------
>
> Key: SOLR-13133
> URL: https://issues.apache.org/jira/browse/SOLR-13133
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Admin UI
> Affects Versions: master (9.0)
> Reporter: Gus Heck
> Priority: Minor
> Attachments: schemabrowse.png
>
>
> In a recent discussion I was yearning for a better overview of the fields,
> dynamic fields and types available. To that end and with probably little or
> no will/ability to actually implement it in the Admin UI I did however spend
> a few minutes drawing out what I think might be better than what we have now.
> This issue is to record the idea and maybe inspire someone. There is a small
> chance I'll decide I want to learn more about Angular and give a crack at it,
> but anyone who likes it or thinks they have something even better is free to
> run with it.
> !schemabrowse.png!
> The basic idea is that our current UI hides the fields/types in a dropdown
> where they are impossible to see, and leaves acres of wasted space below.
> This design endeavors to make use of that space. Also a couple details are
> repeated such as the field type. The above image shows just 2 fields (_text_
> and id) with _text_ selected. Obviously the list would be much longer and
> also have a section for types (hopefully with a nice pretty divider). The
> other key feature here is an "at a glance" flag specifier (intended to
> represent the schema values only, details of schema/props/index would be in
> the detail view to the right as they are now) Flags that are capitalized are
> on and flags that are lowercase are off. The sections correspond to the
> sections in the create field dialog in the UI, with an additional -t- between
> the first two to represent Tokenized or not.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
