Closed ramfox closed 6 years ago
my proposition on sensible metadata field defaults:
~we don't have a mockup of the edit page~ done, mockups in sketch file along with a few options to change I was playing with
~input boxes are too wide~ done sort of, there is now a 'width' option in ValidInput
form inputs design flaws: ~titles are on the bottom and bold, which screws with the hiererarchy~ done, now option for top and bottom in all input fields
distinct lack of the use of dimension of color when an input is focused, the line AND the title now both change color (as we initially intended), so this note is sort of incorporated, but could be more uses of color
~feels bulky~ addressed: added space between inputs, and also now 'hide help' is default (removes a ton of clutter). Could be better but def much better then it was
too dense, too many options at once added space, but haven't yet make certain inputs hidden, that is the next step for metadata editor change for sure
we don’t have read-only metadata display (currently using json component) not addressed
notes on metadata edit screen:
we don't have a mockup of the edit page
there are discrepencies between the form inputs on the sketch file and the in-app stylesheet:
form inputs design flaws
we don’t have read-only metadata display (currently using json component)
The dream:
dynamic input display - only show form fields for existing metadata, users have a method for manipulating the felds that are displayed, have a clear way to pick from available / predefined metadata fields (with descriptions of use), and have a clear method for adding, editing and displaying arbirary metadata, which is visually distinct from predefined metadata values