Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Tags] Use simpler "categories/tags" terminology #393

Open
tobyzerner opened this issue Sep 1, 2015 · 27 comments
Open

[Tags] Use simpler "categories/tags" terminology #393

tobyzerner opened this issue Sep 1, 2015 · 27 comments

Comments

@tobyzerner
Copy link

Primary tags → categories
Secondary tags → tags

Consider renaming the whole extension to Taxonomy.

Also consider category "groups"/"headings"

and this: https://discuss.flarum.org/d/1144-should-the-categories-in-the-topic-list-be-right-aligned

@darkspotinthecorner
Copy link

Maybe changing the flarum/tags extension would work best.
Allow the admins to create any number of taxonomies, each with specific attributes (nested vs. flat, single- vs. multi-assigned) and give them a name. That way they could add flavor to their board by labeling the taxonomies according to their theme and you don't have to deal with the headache of limiting flarum to a specific philosophy. 😉

@franzliedke
Copy link

That would be very powerful, but probably also very complicated and hard to understand. Sometimes, too much flexibility can be a pain for the user...

@jenolan
Copy link

jenolan commented Sep 4, 2015

This is a good idea except that it could become confusing (as said above by @franzliedke)
The current method of a two level primary tag, but allowing the admin to name it as they want (ie Category) and then secondary tags could be names 'Tags' ... what should be available is to have the secondary tags appear below the primary ones to allow this differentiation, see screen shot, if the grey ones were 'indented' from the primary ones voila category / tag handling ;-)

screen shot 2015-09-04 at 12 26 28 pm

@tobyzerner
Copy link
Author

That would be very powerful, but probably also very complicated and hard to understand. Sometimes, too much flexibility can be a pain for the user...

The challenge is to implement a system with that kind of power (for users who want to take advantage of it), but with a simple UI so users who just want plain old categories won't get confused. I think I'm up for the challenge ;)

@darkspotinthecorner
Copy link

The challenge is to implement a system with that kind of power (for users who want to take advantage of it), but with a simple UI so users who just want plain old categories won't get confused. I think I'm up for the challenge ;)

Way to go! :)

Maybe a default-UI and the option to switch to an extended-UI.

@darkspotinthecorner
Copy link

Just thought about this. Mainly how to make it easy to understand and still flexible.

I would think this may be good place for a natural language form, something like this.

I made a crude writeup of phrases that could be used. Still needs polish, mind you. ;)

Part 1 (define taxonomy name):
    A term in this new taxonomy will be called ">>label<<", multiple terms will be called ">>labels<<".

Part 2 (define maximum):
    Items may only belong to a single {"label"}.
    - or -
    Items may only belong to a maximum of ">>5<<" {"labels"}.
    - or -
    Items may belong to any number of {"labels"}.

Part 3 (define minimum):
    New items do not need a {"label"}.
    - or -
    New items need to have at least one {"label"}.
    - or -
    New items need to have at least ">>2<<" {"labels"}.

Part 4 (nesting?):
    The {"labels"} cannot be nested.
    - or -
    The {"labels"} may be nested as many times as needed.
    - or -
    The {"labels"} may be nested, up to a maximum depth of ">>3<<" levels.

Part 5 (viewing items):
    When viewing the items inside a {"label"}, only show the directly assigned items.
    - or -
    When viewing the items inside a {"label"}, show all items in sublevels, too.

@SiCoUK
Copy link

SiCoUK commented Sep 13, 2015

Having just installed the beta to test I have to agree that the primary / secondary tag naming is confusing and I would vote for Categories & Tags (or customisable naming). I would of thought that allowing all sorts of customisation may be over kill!

I would also vote to hide secondary tags on the discussion view unless you are in the primary tag. I can see them becoming extremely crowded.

@jordanjay29
Copy link

If I can raise this issue from the dead, I'm not sure where this stands, but I honestly think the term 'categories' is tried and tired in the forumsphere. I like tags, labels, groups (as ambiguous as that is), channels, etc.

@dav-is
Copy link

dav-is commented Feb 18, 2016

There MUST be an option for a regularly styled forum layout. I feel the current way Flarum operates is "chatty". I like it but there needs to be an option for bigger comunities that have many subsections.

It would be cool if you could apply the tags in the subsection without that subsection being the primary tag. There could be global tags and subsection specific tags.

For example:

Main forum =>
Johns Specific Subsection =>
Post 1 (FAQ->Tutorial)
Post 2 (Support->Php)
Post 3 (General)

@jordanjay29
Copy link

There MUST be an option for a regularly styled forum layout.

I feel like the option lies in an extension (which, I'll note, that's all that Tags is).

@luceos
Copy link
Member

luceos commented Feb 18, 2016

I wouldn't be too surprised to see a categories extension come into life any time in the future. If so, it can perfectly exist next to the core tags extension.

Related to terminology, out of experience I've used so far:

  • primary tags
  • sub tags, which are child tags of primary tags
  • secondary tags or classifiers

Related to renaming the extension. I wouldn't do that. But we might redefine the focus of what the goals of this package should be. Nothing in this package is forced. If we'd leave out the tag-index page we would have a perfectly valid and simple tagging system.

@dcsjapan
Copy link

I'm starting to really like Toby's initial suggestion.

For those who haven't seen it yet, you can see a graphic representation of what he's got in mind down at the end of his second reply to flarum/framework#746.

@dcsjapan
Copy link

dcsjapan commented Apr 6, 2016

It just occurred to me that we might want to continue using the term "tags" as the generic name for the things handled by this extension. The reason is this:

tagchange

Rewriting this message to use the "categories/tags" terminology correctly could get too complex. Another approach might be to keep the "tags" term as the generic and use a different term ("keywords", perhaps?) to describe what we're currently calling "secondaries". That gives us:

  • Tags
    • Category tags (a.k.a. "Categories" and "Subcategories")
    • Keyword tags (a.k.a. "Keywords")

EDIT: @luceos refers to secondaries as "Utility tags", which also works quite nicely in my opinion.

That would allow you to leave the post stream message as it is ... and it would also mean you could get away without renaming the extension to Taxonomy.

@dcsjapan
Copy link

As for right-aligning categories in the topic list ... while I agree with that suggestion, I don't much like how the tags fade out when they overflow the space allotted for them:

tags

It looks like a UI malfunction rather than a feature. How about showing only the two most important tags instead, and displaying the rest when the user hovers over them? That would require some means of prioritizing them, such as:

  • Category tags
  • Subcategory tags
  • Secondary tags

And if there's a tie for second place (e.g. a thread has one category tag and two secondary tags) it could show whichever secondary tag was chosen first. This wouldn't be very discoverable, but it would be a bit prettier and help save space for the date in the mobile view

@franzliedke
Copy link

@dcsjapan I agree that making them appear on hover makes sense, but I'm okay with the way it is right now. Did anybody complain on the forums so far?

@franzliedke
Copy link

Oh wait, they already shift to the left on hover. Nice. :)

@dcsjapan
Copy link

I agree that making them appear on hover makes sense, but I'm okay with the way it is right now. Did anybody complain on the forums so far?

No, just me, probably. 😜

The appearing on hover is good, but the half-faded appearance feels wrong somehow.

@dav-is
Copy link

dav-is commented Apr 13, 2016

I agree it looks weird. Perhaps it shows 2 tags then a '...' At the end

@dcsjapan
Copy link

dcsjapan commented Jul 22, 2016

While reworking the Tags extension, would it be possible to add some way for admins to control which tags (or which types of tags) are displayed in the sidebar list? See this forum post for an example of the sort of control that admins might appreciate having.

@tobyzerner
Copy link
Author

@dcsjapan Yes I think that kind of power is probably a good idea.

@sirinath
Copy link

Allow the admins to create any number of taxonomies, each with specific attributes (nested vs. flat, single- vs. multi-assigned) and give them a name. That way they could add flavor to their board by labeling the taxonomies according to their theme and you don't have to deal with the headache of limiting flarum to a specific philosophy.

I think you should do this with pre defined defaults so advance uses can have more flexibility.

@Dremor
Copy link

Dremor commented Feb 21, 2018

I'll add two idea :

  • limit some tags to some groups (admins, etc...). Like that you can use tags to assign a status to a new feature (To Do, Completed, Accepting merge request, etc.), which would only be assigned by a project developer.
  • Give more level (more than the current 2 levels) to the sidebar. In my case, I would like to have a "Main -> Idea -> Accepted" category.

@kwiesmueller
Copy link

On the forum it was suggested to post my message here, so there you go:

I just encountered some questions regarding Tags that should be features for me.
First thing:
Allowing certain Roles/Groups to add Tags (create new ones). I can not find any permission allowing that and it would be really annoying to make everybody admin that should be allowed to add tags.
(I did not find any way to make a group admin or at least some kind of admin as well to let them access some settings).

Aside from this it would look very helpful to me, to allow (some) users to create secondary tasks automatically when creating their new post. This would be some pretty common behavior and would in the end result in better searchability (at least if I got the secondary tags idea right).

@stale

This comment has been minimized.

@askvortsov1
Copy link
Sponsor Member

I feel like this has devolved into a conversation about fundamentally redesigning the tags extension. I don't think this is a bad thing, but I would like to note that the original issue of confusing naming still stands.

I propose that we implement Toby's proposed rename, and then, if relevant, reconsider this conversation (which I think would benefit by being split up over several issues). The conversation can continue regardless of what primary/secondary tags (or categories/tags) are called, but the rename will make end user's lives less complicated, and is trivial to execute.

@luceos
Copy link
Member

luceos commented Feb 24, 2020

I disagree with the original terminology proposed. Categories is absolutely not something that makes this simpler. I would suggest to stick to using the Tag name, but prefix them to make their use and interpretation more straightforward, eg: Primary tags, Sub tags and Helper tags.

Discussion should focus on the terminology here not on changing the actual implementation of the tags extension.

@askvortsov1
Copy link
Sponsor Member

At least from my understanding, there are 2 issues at hand here.

  1. Is potentially rewriting the tags extension to allow for custom taxonomies. Personally, this is something I don't find necessary: I think it adds too much unnecessary complexity to a system that's already complex enough. Id say that allowing more levels should be considered, although even then I'm not sure how I feel about more than 3 levels at max (too many kinda goes against Flarum's philosophy of simplicity).

  2. What each type of tag should be called. The reason I like categories and tags is that's the naming conventionally used to describe the functionality that primary and secondary tags fulfill. People are already familiar with what a category and tag is, and this isn't just for forum software (blogs operate similarly)

@askvortsov1 askvortsov1 transferred this issue from flarum/framework Mar 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests