Use checkbox and radio instead of Select, Provide better user experience

Created on 23 September 2022, almost 2 years ago
Updated 20 April 2024, 2 months ago

Problem/Motivation

Users have difficulty finding taxonomy in "Terms to merge" and "Existing term" fields. They also want to see the details of taxonomy for final control.

Proposed resolution

1. Let's make the "Terms to merge" field checkbox and the "Existing term" field radio.
2. Let's sort both by label.
3. Let's give label a taxonomy link in parentheses.

✨ Feature request
Status

Needs review

Version

2.0

Component

Code

Created by

πŸ‡ΉπŸ‡·Turkey seyfettinkahveci

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • First commit to issue fork.
  • I like the improved user experience. I have a suggestion to make it a little better - make the text for the link to the taxonomy term the term ID, rather then the term label.

    Instead of displaying a term like this:

    [ ] Cheese and wine (Cheese and wine)

    it display it like this:

    [ ] Cheese and wine (7728)

    Motivation: The term label is already displayed - there is no benefit to displaying it again as the link text. But it can be helpful in some situations to know the ID of the term. For example, if you have two terms which are identical, or differ only in small ways (such as a having a space at the start). In this case, it can be hard to know which term to choose. Other parts of the Drupal UI typically display a taxonomy term label followed by its ID in parenthesis. This change follows the same style.

    I've added a commit to the issue fork with this minor modification.

  • This issue is a superset of issue ✨ Sort terms and provide a better UI Needs review

  • Issue was unassigned.
  • Status changed to Needs review about 1 year ago
  • πŸ‡ΊπŸ‡ΈUnited States DamienMcKenna NH, USA

    As a reminder - please set the "Assigned" field back to "Unassigned" once you are finished with your changes so others can know you're finished.

    Also, the correct status for when there's a patch or merge request to review is "Needs review"; "Patch (to be ported)" is for when a patch/MR is committed to one branch and it needs to be ported to another branch.

  • Status changed to Needs work about 1 year ago
  • πŸ‡ΊπŸ‡ΈUnited States DamienMcKenna NH, USA

    Ah, the issue needs some further work per #7.

  • Pipeline finished with Skipped
    9 months ago
    #28677
  • Pipeline finished with Skipped
    9 months ago
    #28678
  • Status changed to Needs review 9 months ago
  • Apologies for the earlier confusion. The work I described in #7 was committed in #6. So it now needs to be reviewed.

    My changes can be obtained either from the issue fork repo (branch 3311345-use-checkbox-and) , or by applying the patch: https://git.drupalcode.org/project/term_merge/-/merge_requests/7.diff (apply this instead of patch #4, not in addition to it).

  • First commit to issue fork.
  • πŸ‡«πŸ‡·France tostinni

    Thanks for the improvements, I added a natural sort using natcasesort() so terms with lowercase/uppercase get grouped together.

    Regarding the checkbox, yes that's an improvement, but I was wondering about providing an empty radio for the target list of terms because contrary to select list, once you checked a radio you can't uncheck it. I haven't implemented this yet.

  • I have tested the patch https://git.drupalcode.org/project/term_merge/-/merge_requests/7.diff and it's look good for me. Beside the term name term id's are added with a link reference to that particular term which will surely provide better user experience to select term from the checkbox if those terms has similar kind of name.

  • Status changed to RTBC 3 months ago
  • Status changed to Needs review 2 months ago
  • πŸ‡«πŸ‡·France tostinni

    We had a website with 10k terms which created 2 problems:

    • huge and slow term merge page
    • need to search for a specific term

    We decided to adress this by limitating the display of terms to 20 and add a "Display all terms" checkbox to load the whole list (we could have added a load more, but with the search feature, this doesn't seem that useful).

    We also added an ajax search input that will search for terms matching the characters in it.

    I put this as a patch to avoid highjacking the MR, but if there is some interest I can create a new MR.
    The code could use some work to polish what is done but is functional.

  • πŸ‡«πŸ‡·France tostinni

    Parts of other patches were included in #16, updating with patch working against beta6.

Production build 0.69.0 2024