Taxonomy & views integration
| Project: | Multireference CCK field |
| Version: | 5.x-1.1 |
| Component: | Miscellaneous |
| Category: | feature request |
| Priority: | normal |
| Assigned: | steve.m |
| Status: | needs review |
Jump to:
Hi Steve.
Well first of all thank you a lot for this module... I think that probably it's the thing that is going to save me :)
I'm creating a website with different custom content types related to eachother.
I am really a beginner to Drupal, so probably there is lot of my fault in this, but I was not able to find a way, using existing modules, to solve my issue.
Being more concrete, I have by example a People content type and an Event content type, and I am using the nodereference to connect people to events. There could be more than one person partecipating to an event, with different roles, and the same person can partecipate to another event with a different role.
So what I needed is a way to reference a node SPECIFYING the type of this reference, like
event ---nodereference: is_a_type ---> people
where type could be performer, presenter, and so on...
So your module seems to be the closest thing to the solution.
Now I'd like to ask you if some things can be done to make this module become even more useful:
- in the widget setting it is possible to specify a list of description terms to be associated to the referenced node/user. Could this list of terms be picked up from a taxonomy vocabulary?
- is it possible, in the views support, to add a filter to filter by description using a match?
Thank you in advance,
GP
#1
#1: is an interesting idea; I'll give it a shot in my next round of revisions (probably later this week).
#2: Do you mean an exact match instead of the wild card match it currently uses?
#2
Thank you for answer!
#1) Yep I think integration with taxonomy could be nice. Easy to define a set of definitions, and it would be nice if then it could be possible that this taxonomy terms acted like a "tag" on the relation.
I don't know if I am able to explain well what I mean, but by example imagining to use the view nodereference inverse filter, I think it could be great to know the tag. Example:
Crazy_Show ----noderefernce: is_a_performer ---> Mark
The inverse nodereference on mark node would give me the crazy_show nid. What if I had also the "is_a_performer" info? I would know what is the role of Mark in the crazy_show.
I don't know if this can be possible in an easy way, but I think it would be great. (I am thinkin with a relational database in mind)
#2) sorry, I've seen later that there is this filter. Do you think it could be possible to have a filter like that, but working on the single node, meaning that I want to filter displaying in the node only the multireference field having a desfription matchin my choice in the filter.
#3) ok last one :) A way to group by description in the display widget
Ok, it's just brainstorming. I hope this gave you good idea! :)
Thank again and I will stay tuned as I'm interested in this module!
GP
#3
#1
Any progress?
#1a
If it was possible to add a second reference to this so that it could be a triplet (the node you are editing, and two other nodes) then it would be the best hierarchy/compositon tool. Lets call the third node an edge; something describing the relationship between this node and the second referenced node, with a lot of extra information.
#1b
If #1a is possible, could it be possible to let the edge node and the second node, be created in situ, ie. using subform or addnode or ajax/ahah, because there might be quite a lot of edge nodes, and it wouldn't be feasible to search them all.
Example:
Lets say you have three content types. Person, Employer and Employment.
The Personnode type can create nodes with info about the employee (for example Name and address).
The Employer node type can create nodes with info about somewhere you can work for pay.
The Employment node type can create nodes with info about with employment details, when you were hired, when you were fired.
When creating an Person, you might want to add info about all the jobs that person has had (as part of a CV). Thus it would be nice to be able to do inline editing for this info.
In a perfect world one could use Automatic Nodetitles to create the Employment node titles, and only show the body and cck-fields available for that node type. Thus just using default settings for the node type when creating it, not allowing any of the settings in "Menu settings", "URL path settings", "Comment settings", "Authoring information" and "Publishing options" to be accessed in this phase.
That could also be an option for the Employer nodes as well.
#4
I am also interested in linking the description to a Taxonomy vocabulary
#5
I have added taxonomy integration to the description fields, so that each can now be a plain textfield, a select field with specified options, or linked to a taxonomy vocabulary. Test out the -dev version of multireference and let me know if there are any problems!
If the other features are still of interest, please file a new feature request for them.