Currently, we have a facet control to find records with or without dbgap_study_id but not to see or choose from available values. Change this to offer the raw values instead, so we can evaluate the UX.
A possible enhancement out of scope for this round would be to introduce a dbgap_study_id quasi-vocabulary where we could treat this column much like other controlled vocabulary term IDs and link to more information such as a study name or description.
This is in preview in the app-dev catalog 1, but the code is in the same branch where we will do the dbgap_study_id access rights summary UX (also in progress), so has not been merged yet.
Currently, we have a facet control to find records with or without dbgap_study_id but not to see or choose from available values. Change this to offer the raw values instead, so we can evaluate the UX.
A possible enhancement out of scope for this round would be to introduce a dbgap_study_id quasi-vocabulary where we could treat this column much like other controlled vocabulary term IDs and link to more information such as a study name or description.