Jump to:
| Project: | Drupal core |
| Version: | 8.x-dev |
| Component: | node system |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (won't fix) |
Issue Summary
I am interested in having the taxonomy be resposible for more of the properties of nodes. For example, at the moment it seems that nodes have some specialized meta-data, like "type", "comment", "promote". The various types could instead be terms in a "type" vocabulary, e.g. "story", "forum topic", etc. And things like "comment" and "promote" could be terms in a "properties" vocabulary.
This way, it seems like certain aspects of the display and handling of nodes becomes more standardized. For example, the front page could just be a general instance of a taxonomy filter, where its criteria is simply, "does this node have the 'promote' term from the 'properties' vocabulary?" And a forum page likewise can filter based on the "forum" term in the "type" vocabulary.
However, I think a more interesting area this could effect is moderation. One could generalize moderation to be about, "do we allow this new node to be term x?" Terms could include a property to only allow a node to be classified under it given certain access rights, and one of those access rights could be "moderated". Therefore, the Queue module could instead look for all nodes that are waiting to get into terms, and let people assign points based on whether or not it should be allowed in. This includes the current "promoting" concept of the Queue module, because that would just be "do we allow this new node to be term 'promoted'?"
This would allow, for example, one to be able to put Events into the queue, and let people moderate on whether it should actually go onto the calendar (i.e. should this node be allowed to be type "event"?). Or, one could use the Subscribe module to allow people to subscribe to the front page, since it is just a term that can be notified about. Or one could subscribe to all Events, since that too is just a term.
I hope this sounds useful.
Comments
#1
Sorry... I don't know why "Version 4.2.0" was selected, as I selected "none", given I'm not sure the timeframe it was take to implement this... apparently I can't select "none" so I'll just select "cvs"...
#2
Oh no, not again... I'm sorry, the project should be "Drupal" not "Feature"... I got confused... :(
I hope my idea is still considered even though I'm incompetent in using this feature submission system...
#3
#4
#5
Since then Drupal has evolved, and is now using fields, entities, etc. node or taxonomy access control belong to contrib modules, not Drupal core.