node term node relationship.
I've been looking through the node relationship modules, but I don't find exactly what I'm looking for, which probably means I skipped over something or just didn't get the full feature set of something. So I'm going to ask the brilliant world out there for some guidance.
What I have is two kinds of nodes, Entities (people, companies, groups) and Projects (theater production, concert, CD, Video).
Now any Entity is likely to be linked to multiple Projects, and Projects are linked to Multiple Entities.
So I'm looking for a many to many sibling relationship. (though Parent to multiple child is OK too, just fast lookup one way, slow lookup the other I'm guessing)
But here's the extra wrinkle: the relationship type of each Entity-Project can be different, so I imagined using a taxonomy, which has many features that I want to include in the relationship (such as synonym, and a hierarchy of relationship types)
So I imagine that what I'm looking for is Node - Term - Node relationship, though if someone even has a better moniker for this that might just help me search my way to something close to what I'm looking for.
I also start to feel that this really sounds like something that ought to be deeper in the Database design, and perhaps that is the case and the Drupal framework is too wrench shape for my nail. In which case does anyone know of a Node - Term - Node shaped hammer?
thanks
How many relationship types
How many relationship types are you thinking of? If it's fairly small, you could create separate nodereference fields for each type and simply allow some fields to be blank for any given Project. This way you embed the relationship type in the database tables themselves, rather than as a separate column somewhere.
Another alternative is to create intermediate content types. For instance, create a Manager content type and have it reference an Entity and a Project as a way of connecting those two.
If you're trying to deal with a very large number of relationship types, though, all I can say is that I hope someone else has better advice than I do.
Also, though I don't know anything about your project beyond what you've said above, do you really want to lump people, companies, and groups into a single Entities category? If individuals and groups stand in different relations to Projects (which I imagine they might), would it be more helpful to create a Person content type and a Company content type?
Massive number of relationship types.
On the one hand I can think of a lot of relationship types.
Producers provide money
Presenters provide space
Dancers Perform
Choreographers Choreograph
Designers Paint, light, costume ...
Not only that but I liked the idea of unitizing Terms because you can add more terms, and utilize the synonyms for a term (Producer=Funder=Investor) which will keep search working well, and make users happy.
Also there are a variable number of connections per Project / Entity.
Entity A may work on 10 projects and Entity B only on 1 or two.
Likewise Project ONE may only have one person working on it.
But Project TWO has 200 entities.
Yes a person and a group are different, and maybe people should be linked into groups, but both can slot into the same relationship. Project ONE's 'producer' is a person, but Project TWO has 4 Producers, two are people, and two are Groups (one company, one foundation)
RDF?
I see. That is too hard to do with nodereferences.
Have you looked into Drupal's emerging RDF capabilities?
It sounds like you really do need ternary relationships in which you can name both the relation and the relata. RDF handles that quite well. I don't know the details about how you would do it, but it may be your best solution.
Another is create two content types Entities and projects & use
Another is create two content types Entities and projects & use parent child relationship using node relativity module.
E.g. create content type entities and projects, and then from configuration of node relativity you can set the parent and child content type. then after creating each entity(parent in ur case) you can create multiple nodes of projects under related entity.
thx
Bi-directional, and labled relationships.
I'll give it a test along with everything else but I'm expecting it to fall down in two areas. entities and projects are not exactly a parent child relationship, but they are a many to many relationship which would be OK to represent in parent child as long as I can look up parents on a child page to provide a link.
The other little sticky bit is I really want to "name" the relationship, not all relations of entities to projects are the same, and not consistent across projects. In project ONE: Entity A is a Producer (who just provides money), Entity B is Designer (who really works on the project), Entity C is a Dancer (who works on/performs in a project).
But in project TWO: Entity B is a Dancer, and the Producer.
I think I search for a
I think I search for a similar solution. I created a support request to RDF CCK, because I hope, it fits into this module:
http://drupal.org/node/424654