yorubaname-website icon indicating copy to clipboard operation
yorubaname-website copied to clipboard

Checkboxes

Open kolatubosun opened this issue 8 years ago • 0 comments

I've figured out all the instances in which a checkbox might make the UX better both for the lexicographer dashboard and the user. Here they are. cc: @dadepo :

For Dashboard/Lexicographer

Homograph: When a name has one spelling but different tone marks (Adéṣọlá/Adésọ́lá, Adémóyè/Adémòye), the lexicographer clicks this check mark and the "meaning field" duplicates for the user to use to demarcate the two meanings.

Shortened form: When a name being defined is in a form generally regarded as a short form (Lanre, Banwo, Deji, etc), the lexicographer clicks this checkbox. The result of this clicking is that on the front end, a small text is displayed by the name, saying "Shortened form". But on the back end, another box is opened for the lexicographer to write all the long versions of the name, as necessary. The box can be duplicatable, in case there are more than one. e.g. Oladeji, Adedeji, etc.

Àmútọ̀runwá (Natural Names): This checkbox will be placed right under the name field, in the back end so that the lexicographer can indicate right from the start that a name is an àmútọ̀runwá. Like the shortened form, a colour-coded notification will also show on the front end to say that the name is an àmútọ̀runwá name, perhaps also with a link that can be clicked so the user can read more about àmútọ̀runwá names. I will write up the essay that the user will see when they click.

Oríkì (Cognomen): Like the last two items above, this works in the same fashion. The oriki checkbox reflects on the front end as a colour-coded notification that this name is an oríkì with a link exploring what orikis are in Yorùbá.

Ìnagijẹ (Nicknames) Same as Oriki above.

Abíkú name (Given typically to children born after many previous deaths). Same as the others above.

For Meaning unknown, the check mark will merely lock up the "Meaning" field for the lexicographer as soon as it is clicked. It saves him/her from having to type anything. But on the front end, it shows "Meaning not yet provided, known, or verified." When hovered over, it says "If you know the meaning of this name, click HERE to suggest it". When clicked, the "improve this entry" suggestion box opens where they can enter their suggestion.

And finally, the Name Verification Needed checkbox. This one will be for entries for which meanings have been provided already but for which none of the lexicographers are absolutely sure, or for which they think there might be better or more meanings out there. When checked, this feature will put a notification under the meaning on the front end saying "Verification Needed" When hovered over, a text says "This meaning needs verification. If you have any suggestion for us as regards its meaning, click to suggest it." And when the user clicks on this phrase, it opens up that suggestion box through which they can put their suggested meaning.

For User

When a name is being suggested from the front end, and the user doesn't know the meaning, he/she doesn't have to type "I don't know the meaning" since the box is a compulsory field. We can merely allow them to check a box that says "I don't know the meaning", to save them the time of completing the form.

kolatubosun avatar Jul 13 '16 23:07 kolatubosun