Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Separate unit-type and unit into two dropdowns #191

Closed
SRGDamia1 opened this issue Mar 1, 2018 · 7 comments
Closed

Separate unit-type and unit into two dropdowns #191

SRGDamia1 opened this issue Mar 1, 2018 · 7 comments

Comments

@SRGDamia1
Copy link
Member

The unit should only be select-able based on the unit type.

@aufdenkampe
Copy link
Member

Let's think about how to best do this. Sometimes the term for the relevant Unit type is a bit obscure, and in my recent work with @roelofversteeg, I have found that first sorting my unit type is actually quite hard to do, even for me with all my previous work on Units. I found that it is much easier to search by unit name, especially if there is free-text filtering in the dropdown.

@aufdenkampe
Copy link
Member

@jcaraballo17 and @Maurier, we probably should have discussed this today, for the reasons I discussed above. Ideally we would have free-text filtering of all the fields associated with a unit, similar to what is implemented on the front-end for sensors, variables, sites, etc.

Also, because UnitTypes are often obscure, I do not believe that it is a good idea to require that a user first select a UnitType before selecting a Unit. This would make things very hard and frustrating for the end user. Please discuss your ideas with the group before going very far down into delivering a solution on this one.

@horsburgh
Copy link
Member

@aufdenkampe - @jcaraballo17 and @Maurier need some clarity. @SRGDamia1 suggests that the unit should only be selectable by unit type, but Anthony, your last comment suggests that we don't want to do this. It would be great if you and Sara can get together and decide what you want here. Juan and Mauriel can do whatever, but we need to tell them how this should work.

@SRGDamia1
Copy link
Member Author

When I'd created this issue, I was only thinking of having this apply on the admin panel when adding an instrument output variable.

@horsburgh
Copy link
Member

If it's just in the Admin panel, it should be pretty straightforward.

jcaraballo17 added a commit that referenced this issue Dec 20, 2018
…ree-text searching and better usability of the admin.
@jcaraballo17
Copy link
Member

Adding a new dropdown that is not directly a field of the model and then filtering through it is a little bit complicated.
I added the free-text searching to each dropdown in the admin instead. It's a lot simpler and easier to just filter the units selection through that.

@SRGDamia1
Copy link
Member Author

The search seems to be working on staging. I'd still prefer the split, but I guess that problem is an ODM2 structural one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants