Key Features

Last modified: October 11, 2008 - 05:55
Preset driven relationship definitions
I really like the Imagecahe and User Relationship module use of presets. I believe we could do the same for this module
Taxonomy-like API
After reviewing much of the taxonomy engine in Drupal, I've come to the conclusion, relationships between nodes should have the same power and flexibility that are given to categories. The various contributed projects provide in some fashion an interpretation of the taxonomy functions, yet the flexibility of easily defining these relationships lacks in most implementations. This will be closely tied to Preset driven relationship definitions.
Improved VIEWS integration
I believe we can provide better filtering and sorting criteria for the module. I propose that each relationship preset have a multi-select option permitting the administrator to select which fields from the parent's node will be exposed to VIEWS.
Improved CCK integration
Much like the node_reference CCK type, this module should not only expose node operations to the viewer of the node relationship, but also to the editor. Thereby increasing the flexibility and power of the module. Attaching and detaching relationships between nodes should be simple and painless. Also, providing easy filtering of node lists for parent/child selection should be flexible enough to be done from within the node edit form.
More robust pathing/menu handling routines
I've come across some pretty horrible URL based path issues that can quickly expose Node Relativity to abuse. These holes need to be plugged and naming conventions need to be easily modified by the admin (think PathAuto and Token modules)
Better Breadcrumbs
Given the number of times we've seen this issue come up, it is paramount this module provide a mechanism to expose breadcrumb options, easily and simply to the administrator of a relationship preset.
Refined Access Controls
I've noticed a serious lack of permission granularity in the module, thus exposing a greater set access controls to roles would be nice.
More theme function flexibility
In the previous versions, theme functions were very heavy and required a high degree of PHP understanding to get the module to do what should be simple. By simplifying the theme functions, exposing API calls and increasing the Administrative Front End display features, we could greatly enhance the theme flexibility of the module.
 
 

Drupal is a registered trademark of Dries Buytaert.