IQSS / IQSS/dataverse-frontend
Create/Edit Template Page: Avoid Ambiguity with Red Asterisks
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 31
- Forks
- 26
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 4
Description
Currently, when creating or editing a dataset template, two different asterisk (*) indicators are displayed:
- One next to the template name, indicating that the field is required for creating the template.
- Another next to metadata fields, indicating that those fields are required at the collection level, but are not actually required during the template creation process.
Because these two asterisks represent different meanings, @pdurbin , @jp-tosca and I have discussed a few ideas for better distinguishing these scenarios and reducing potential confusion.
- To use a different symbol and color for required by the template vs required by the collection. (Phil has a mock up here)
Also,
- Gray asterisks
- ○ symbol
- A clock symbol/emoji
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Create/Edit Template page and trace how the template-name and metadata required indicators are rendered. Review the proposed visual alternatives and confirm the intended distinction before changing the UI. Done means the two meanings are visibly distinguishable in both create and edit flows without changing which fields are required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- design, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100