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

Auto-completed #29

Closed
AmberSJones opened this issue Mar 6, 2014 · 4 comments
Closed

Auto-completed #29

AmberSJones opened this issue Mar 6, 2014 · 4 comments
Assignees
Labels

Comments

@AmberSJones
Copy link

The default entries from fields with selection appear in the metadata tabs even when those entries are optional and the user may not have changed them at all. (In the below example, the update frequency was not edited, but it defaulted to "Daily".) They should either not be assigned or else the fields should default to a null.

image

@horsburgh
Copy link
Member

Agreed - this is a bug.

@pkdash
Copy link
Contributor

pkdash commented Mar 9, 2014

All optional fields where we are providing user to select a value from a dropdown list, there should not be any default selection. This can be easily implemented.

@pkdash
Copy link
Contributor

pkdash commented Mar 12, 2014

Have posted a fix for this. In order to show the dropdown list box without any value, I had to include an option "Select a value". If the user selects "Select a value" no value will be saved against the corresponding metadata field. As I was implementing this I noticed the 'research_focus" metadata element was missing from the dataset schema. Now I have included this element. Due to this new element in the dataset schema all previously created dataset will generate server error if viewed or edited.

@AmberSJones
Copy link
Author

This seems to be working well.

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

3 participants