I've started working on providing a userfriendly way for filling out the nodes of a profile in a through steps. I started with providing a unique url for each content-type which restricts its number of creatable nodes per user to 1 - as it happens for a nodeprofile content type.
By doing the nodefamily views integration I ended in writing the module views_fusion.
Views Fusion allows one to fuse multiple views into one. So you can build fusioned views that display information that is stored in multiple nodes - useful for tabular views. It uses node relations for joining the appropriate nodes together.
In the last days I was working on the views integration for the nodefamily module. Unfortunately it turned out to be more complex than I thought originally. What I wanted to do, was that views is able to automatically join the node tables of different nodes together, so that one is able to list information of both nodes. But I noticed that this approach has some downsides. They are:
I have done the views integration for the usernode module. With it's possible to create user listings using views. The next step I've planned is to add views integration to the nodefamily module in that way, that it would be possible to display profile fields like "Surname", "Address", .. in the userlist.
at http://drupal.org/node/73245#comment-115470 the suggestion came up to reuse the author field of the node table for linking users with usernodes.
i've started development of the node relations module, i called it nodefamily module. As the module might be useful not only for profile nodes, I've written it generally, so that it may be used without nodeprofiles at all.
i started with the development of the usernode module, which cares for creating/deleting a node, whenever users are added/deleted - so other modules can rely on that a node exists for each user. it already does its job, however the views integration is still missing.
As i noted in the proposal I need a node relationship, which offers views integration. The views integration I 've in mind is that it's not only possible to display a link to a related node in a view, like it is with CCK node relations, instead it should be possible to list concrete data (e.g. CCK fields) of the related node.
I noted that I've not published a project schedule yet, so here it is: