Posted by xjm

There are a number of existing issues on ways to improve the D8 taxonomy UI/UX, many of which are related, overlapping, or contradictory. Here's a list:

Term properties and fields

Vocabulary properties

...Okay, wow, that was more than I thought.

I think we should probably get some general direction on this: decide which of the above should be won't fix, which can have a shared solution, etc.

CommentFileSizeAuthor
#10 sample-terms.xls155.5 KBjenlampton

Comments

xjm’s picture

I'll try grouping/sorting this list a little after I've had some coffee...

xjm’s picture

Issue tags: +Usability

Tagging.

xjm’s picture

Issue summary: View changes

(xjm)

xjm’s picture

Component: documentation » taxonomy.module

Um. Right. Dunno how/why I did that.

xjm’s picture

Issue summary: View changes

Updated issue summary.

xjm’s picture

Title: [META] Taxonomy admin UI Improvements » [META] Taxonomy admin usability Improvements
xjm’s picture

Issue summary: View changes

Updated issue summary.

yoroy’s picture

Thanks for collecting these.

yoroy’s picture

Issue summary: View changes

Updated issue summary.

joachim’s picture

yoroy’s picture

Issue summary: View changes

Removed 1160292 which I marked duplicate of 263301

xjm’s picture

Issue summary: View changes

Updated issue summary.

xjm’s picture

Related: #211494: Usability: Unify select option formatting. While it's not exclusively about taxonomy nor a part of the admin UI, it is a persistent taxonomy usability issue.

Bojhan’s picture

Is this still major, we really need a meta category.

xjm’s picture

Priority: Major » Normal

Agreed, it's not major.

giorgio79’s picture

Not sure if this is the right place to mention this, but when I look at node/add/mycontenttype and taxonomy/term/add the only difference is the "relation field" on the taxonomy/term/add. Why not finish up the decoupling and converting taxonomy term into a relation field, that has an optional title (just like Link field)? This whole taxonomy seems like a duplication of effort when it could be made a full blown field. Or just push for replacing it with http://drupal.org/project/entityreference with the Tree http://drupal.org/project/tree or http://drupal.org/project/relation

PS Seems like it's already happening #1847596: Remove Taxonomy term reference field in favor of Entity reference

jenlampton’s picture

StatusFileSize
new155.5 KB

Unfortunately, taxonomy administration has a lot more problems than are mentioned here. I'm going to add a few more items to the meta issue that we really need to resolve.

I've been forced to add taxonomy/terms for my clients on many occasions since the admin experience is so bad they either can't figure it out or get really frustrated with the experience, especially around the ordering. :(

I'm attaching a list of terms here, to be entered for QA purposes. I suspect most of the developers who have been working on the UI for taxonomy have never actually tried to use it in a real-world scenario. Well here's your chance :) Most of the time when taxonomy is needed, users have a list like the attached - already sorted the way they want it - hierarchy included. Le's make it so that this list can be entered in Drupal 8 painlessly!

jenlampton’s picture

Issue summary: View changes

Updated issue summary.

jenlampton’s picture

Issue summary: View changes

add 3 more issues :)

xjm’s picture

Box of 'relation' terms on add from is too short to be usable - needs issue?

Yes! This drives me nuts. It's also way too far down on the page. Usually that's the first thing I want to enter after the term name.

tim.plunkett’s picture

#843162: Creating vocabularies with machine-names "List" or "Add" breaks links in taxonomy overview admin area. codified the limitation of the current path structure. I'm going to double check again that there is no existing issue, but moving this to admin/structure/taxonomy/manage like everyone else would be good to do.

tim.plunkett’s picture

Issue summary: View changes

unconfuse

xjm’s picture

Issue summary: View changes

Removing myself from the author field so I can unfollow. --xjm

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

jukka792’s picture

Issue summary: View changes

If Twitter would work similarly, when adding a hashtag for example #hashtag it would instead give #hashtag(4).
So my suggestion is, when adding a taxonomy terms using the autocompolete tags style form, it would not show that "(4)" machine name?
This (4) could be hidden using permissions or something else. It is absolutely useless information and missleading and confusing when a content creator adds tags to her content, and there is this machine name number after the tag. It is a very small but critical user interface issue. Or if it is possible to hide with theme templates, please let me know how to do it.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

Issue summary: View changes

Just removing closed issues from the issue summary.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.