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

Current UX wrongly suggests fields as mandatory #548

Open
avivace opened this issue Jul 5, 2022 · 0 comments
Open

Current UX wrongly suggests fields as mandatory #548

avivace opened this issue Jul 5, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@avivace
Copy link
Member

avivace commented Jul 5, 2022

In some optional (array) fields, a "row" is automatically created when creating a draft, without having to click on "Add one", and the field for these rows are mandatory, suggesting that this data is mandatory.

This happens with:

  • Dates
  • Alternate identifiers
  • Related works

as this is how they appear when you land on the form:

image

without having clicked "Add related work" first. This could be confusing as it seems to suggest they are mandatory, while in reality they are if you decide to add that row at all.

On the other hand, really mandatory fields have no "row" pre-added:
image

@avivace avivace added the bug Something isn't working label Jul 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant