-
-
Notifications
You must be signed in to change notification settings - Fork 200
Consider further generalizing the placeholder data #587
Copy link
Copy link
Open
Labels
✨ goal: improvementImprovement to an existing featureImprovement to an existing feature💻 aspect: codeConcerns the software code in the repositoryConcerns the software code in the repository🟩 priority: lowLow priority and doesn't need to be rushedLow priority and doesn't need to be rushed🧹 status: ticket work requiredNeeds more details before it can be worked onNeeds more details before it can be worked on
Description
Activity
Metadata
Metadata
Assignees
Labels
✨ goal: improvementImprovement to an existing featureImprovement to an existing feature💻 aspect: codeConcerns the software code in the repositoryConcerns the software code in the repository🟩 priority: lowLow priority and doesn't need to be rushedLow priority and doesn't need to be rushed🧹 status: ticket work requiredNeeds more details before it can be worked onNeeds more details before it can be worked on
Type
Projects
- StatusShow more project fieldsBacklog
Problem
At current the placeholder data does offer an intuitive connection that associates an Attribution Detail input field to its final output spot within a Mark.
However, it might be more clear to further generalize this information to
Authorinstead ofJane Doe.Or even '[Author]'.
Description
This might provide a backwards flow of UX connection inference between the Mark and the fields, but it also might reduce clarity of how a final Mark would look.
Alternatives
Create a "sample" area in the Marking section that includes these super generic "tokens", but leave the current less generalized placeholders for the rest of the specific Marks.
If don't right this alternative might provide gains in both directions of inference from Field to Mark, and from Mark to Field; and help with passive inference and license education.
Additional context
Implementation