Usability: on taxonomy vocabulary page, document new way of applying to content types

@D7csmtl

I have made a little patch for this function. But it has typos.

@D7csmtl

And here's a better patch that will actually work!

reroll

#5: taxonomy-719424-5.patch queued for re-testing.

> I second that, because coming from Drupal 6, I was expecting to be able to add taxonomies to content types via the taxonomy vocabulary page.

There's a case to be made for this being a UI regression, and that we should keep that UI in.

Patch works fine for me using alpha6.

I thought I'd forgotten or broken something when I couldn't work out where to apply vocabularies to content types. After figuring it out I actually prefer D7's way a lot more so wouldn't call it a UI regression, just minor confusion :) Would it be worthwhile indicating on the content type creation form where you would set up the vocabularies to apply to the content type?

+++ modules/taxonomy/taxonomy.admin.inc	2010-02-19 10:50:24.000000000 -0500
@@ -110,6 +110,10 @@ function taxonomy_form_vocabulary($form,
+    '#markup' => t('Edit your taxonomy here, and apply it to !link in the manage fields tab', array ('!link' => l(t('content types'), 'admin/structure/types'), ) ),

- admin/structure/types has no 'Manage fields' tab. It's a list of node types, each one having a 'Manage fields' link.

- All entities can use taxo fields : comments, users, contrib entities... - not just nodes.
'Taxo field on nodes' is the most common use case, and is likely to be the 1st one people coming from the D6 way will be looking for, but we should not have a hardcoded UI text that makes it seem restricted to nodes, because people adding taxo fields to non-nodes will get the feeling they're doing something 'wrong'.

+ patch has spaces in an empty line

Powered by Dreditor.

I just tested this on a local drupal 7 instance. Here is one last adjustment to the wording - changed tab for link.

um, this requires UX team review. And be aware that the UX team needs screenshots...

This should be added using hook_help(), not set in the form, surely.

Also, I've tried the patch, and the new text seems to be at admin/structure/taxonomy/add. Why here, and not the main taxonomy page? This already says:

> Taxonomy is for categorizing content. Terms are grouped into vocabularies. For example, a vocabulary called "Fruit" would contain the terms "Apple" and "Banana".

It seems to me the "Taxonomy is for categorizing content" statement could be expanded on here. There is in fact an explanation of how to apply taxonomy vocabs to other entities at admin/help/taxonomy -- we should briefly say what's possible and link to that page.

Patch also produces text that looks wrong at admin/structure/taxonomy/forums/edit.

Any updates since the official release? FWIW, I agree with joachim.

Description

Currently there is no text to indicate what happens with newly created vocabularies. No instruction or simple explanation on how they get assigned to a content type for use. In D6 it was part of creating the vocabulary. This is very confusing, and I believe the thought will be that once it is created it will just show up for selection when creating content. That it then needs to be added to the content type after you create the vocabulary in a completely different area isn't indicated anywhere, this is not intuitive to a user.

I would suggest two changes.
1. On the Taxonomy landing page (I think that's what you call it) where it says currently:
Taxonomy is for categorizing content. Terms are grouped into vocabularies. For example, a vocabulary called "Fruit" would contain the terms "Apple" and "Banana".
Should include:
Add a term reference field to any content type you want your created vocabularies to include.

2. On the Structure page where it says:
Manage content types, including default status, front page promotion, comment settings, etc.
Should be changed to:
Manage content types, including default status, front page promotion, comment settings, assigned vocabularies, etc.

You may also want to add a note to the admin/structure/taxonomy/add page
After creating your vocabulary add a term reference field to all the content types you would like to include this new vocabulary.

no screenshots

I created a new patch that addresses only the scope of the original issue.

It adds the following text to admin/structure/taxonomy:
A vocabulary is assigned to content types, users, or other entities on the manage fields tab by adding a Term reference field.

I've observed that Term reference is a confusing label for some new users who just created a vocabulary and want to add the vocabulary to a content type, but I think renaming fields requires more consideration and getting help text on the taxonomy page is valuable.

Thank you so much for posting this. I was fighting with this all morning. :)

Sounds fine!

Still a good idea. Lets try and make it a bit shorter though.

Thank you for sharing your idea for improving Drupal.

We are working to decide if this proposal meets the Criteria for evaluating proposed changes. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or there is no community support. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

If this is still desired can the summary be updated with screenshots.