Posted by no2e on April 11, 2009 at 9:08pm
Jump to:
| Project: | Relationship |
| Version: | master |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
From the module homepage
The CVS repository has been cleared pending a rewrite for D6, proposed by atipton.
This module is to be considered inactive until that's ready.
When might this happen? Or won't this happen anymore?
Comments
#1
Do we have a status on this? I am willing to help with getting this ready for drupal 6/7, and adding to it so it supports nested subsets (ala the ruby/rails awesome nested subsets code). I am looking for a relations module to underlie a new version of OG sub-groups that will support multiple nested hierarchies, so a given node of type group having relations of different types to different groups (a garden club group being related to the neighborhood it is located in for a geography hierarchy and to the region in the city gardening network for the garden club hierarchy, for example).
I'm trying to find a node relation module that can underlie this, but that can also be used for many more types of connections, so eventually I can build software to map networks in drupal systems that only has to know about one (or two - CCK's node relations) standard ways of relating nodes. Is anyone working on this? And has anyone tried to figure out how hard it would be to essentially take this relationship module and build its functionality out using the CCK node relation code?
#2
Adding a few more design notes, for me as much as for anyone else (since I suspect no one is going to see this... =) ).
- needs to be able to deal with multiple entity types (nodes, users, perhaps taxonomies and taxonomy values). Some of this can be accomplished by making node-types to accompany some of these entities (a person node type, for example, so people can be in the system regardless of whether they have a user, but also so users can tie themselves to the people who correspond to them).
- needs to be able to have a relation type, so a given node can have a number of different types of relations with another node.
- should be able to have relation strength.
- should also be able to have multiple properties associated with a given relation, perhaps speced by its relation type.
- elements of different types should be able to be related. This implies that there will probably have to be a separate set of relations tables even if you integrate with nodereference in CCK. It would be good to take advantage of nodereference when relations are between nodes, but you should be able to mix entities, and to do that, I think you have to have a separate master table of related things, regardless of type.
These features support using a well-thought-out-and-implemented relation module to be the basis of a hierarchy module that could then underlie a better implementation of OG sub-groups. This is one end goal, but to do this, need the relations to be built well first.
Is anyone actively maintaining relationship at the moment?