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

Multi Selects for Fields #350

Closed
eaquigley opened this issue Jul 9, 2014 · 13 comments
Closed

Multi Selects for Fields #350

eaquigley opened this issue Jul 9, 2014 · 13 comments
Labels
Feature: Metadata Type: Feature a feature request User Role: Depositor Creates datasets, uploads data, etc. UX & UI: Design This issue needs input on the design of the UI and from the product owner

Comments

@eaquigley
Copy link
Contributor


Author Name: Elizabeth Quigley (@eaquigley)
Original Redmine Issue: 3765, https://redmine.hmdc.harvard.edu/issues/3765
Original Date: 2014-03-25
Original Assignee: Gustavo Durand


Try using Multiple Select under Selected and Disabled Support for all multi select fields, which would also allow for auto-populate / auto-complete for any matching terms within the list: http://harvesthq.github.io/chosen/#selected-and-disabled-support

Metadata fields that should use this component:
-Subjects
-Type (Astro Metadata block)
-Language
-Country (Geospatial Metadata block)
All Biomedical terms will be multi-select:
-Design Type
-Factor Type
-Measurement Type
-Organism
-*Cell Type (coming soon... waiting to decide on hierarchical dropdown terms list and/or "type ahead" field for a large list like this one.)

@eaquigley
Copy link
Contributor Author


Original Redmine Comment
Author Name: Elizabeth Quigley (@eaquigley)
Original Date: 2014-04-23T18:59:56Z


For beta, we will try having a scrollable panel that includes all the options with checkboxes next to them so they aren't displayed as a giant list.

@eaquigley
Copy link
Contributor Author


Original Redmine Comment
Author Name: Gustavo Durand (@scolapasta)
Original Date: 2014-04-29T15:46:33Z


Mike, switched to checkboxes. I had to remove the style-class or was limiting it to a ver small space.

Now what we need is to switch it to a small (but not as small) scrollable area.

QA: when does with this ticket please keep it open and in dev (set to May 19?) so we can later examine using the "chosen" type.

@eaquigley
Copy link
Contributor Author


Original Redmine Comment
Author Name: Mike Heppler (@mheppler)
Original Date: 2014-04-29T21:44:55Z


Cleaned up the select-checkbox lists on the dataset page, to be within a contained, scrollable list, and styled them to look like the other form elements on the page.

@eaquigley
Copy link
Contributor Author


Original Redmine Comment
Author Name: Kevin Condon (@kcondon)
Original Date: 2014-04-29T21:49:54Z


Tested on 4/29

All fields have multi select check boxes except cell, which has the multi field control style.

Not sure if that last is by design but passing back to dev per instructions.

@eaquigley
Copy link
Contributor Author


Original Redmine Comment
Author Name: Elizabeth Quigley (@eaquigley)
Original Date: 2014-06-17T18:41:36Z


Bringing this back into play since Gary mentioned doing something like this for at least subject field so it isn't such a large chunk of the page

@eaquigley eaquigley added this to the Dataverse 4.0: In Review milestone Jul 9, 2014
@eaquigley eaquigley modified the milestones: Dataverse 4.0: Beta 4, Dataverse 4.0: In Review Jul 15, 2014
@eaquigley
Copy link
Contributor Author

@mheppler & @scolapasta what is going on with this?

@scolapasta scolapasta modified the milestones: Beta 4 - Dataverse 4.0, In Review - Dataverse 4.0 Aug 19, 2014
@eaquigley eaquigley modified the milestones: Dataverse 4.0: Final, In Review - Dataverse 4.0 Sep 4, 2014
@scolapasta scolapasta modified the milestones: In Review - Dataverse 4.0, Dataverse 4.0: Final Dec 8, 2014
@scolapasta scolapasta modified the milestones: Dataverse 4.0: Final, In Review - Dataverse 4.0 Jan 6, 2015
@scolapasta scolapasta assigned eaquigley and unassigned scolapasta Jan 6, 2015
@scolapasta
Copy link
Contributor

Let's re review this when we get near the end.

@scolapasta scolapasta modified the milestones: Dataverse 4.0: Final, TEMP, In Review - Dataverse 4.0 Jan 23, 2015
@eaquigley eaquigley modified the milestones: In Review - Dataverse 4.0, Beta 14 - Dataverse 4.0 Feb 9, 2015
@eaquigley
Copy link
Contributor Author

Bringing this ticket back up. @scolapasta could we use the component used for searching through usernames for role assignments for this?

@eaquigley eaquigley assigned scolapasta and unassigned eaquigley Apr 29, 2015
@scolapasta scolapasta removed their assignment Jan 27, 2016
@mheppler mheppler added the UX & UI: Design This issue needs input on the design of the UI and from the product owner label Jan 28, 2016
@scolapasta scolapasta removed this from the Not Assigned to a Release milestone Jan 28, 2016
@scolapasta
Copy link
Contributor

@eaquigley can we close this one?

@eaquigley
Copy link
Contributor Author

@scolapasta no, this was never done for multi select fields. I can see this being needed even more with biomedical data. @posixeleni

@djbrooke
Copy link
Contributor

djbrooke commented Aug 2, 2016

@eaquigley gave me an overview of the importance of this, especially in those metadata schemas that have many options. Removing myself for now, will be added in a future release.

@djbrooke djbrooke removed their assignment Aug 2, 2016
@pdurbin pdurbin added User Role: Depositor Creates datasets, uploads data, etc. and removed zTriaged labels Jun 30, 2017
@RightInTwo
Copy link
Contributor

This would be useful in general, also in combination with #4772.

@djbrooke
Copy link
Contributor

Closing in favor of #6030 to evaluate as part of a larger effort.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: Metadata Type: Feature a feature request User Role: Depositor Creates datasets, uploads data, etc. UX & UI: Design This issue needs input on the design of the UI and from the product owner
Projects
None yet
Development

No branches or pull requests

8 participants