Smartqueue for CCK node reference - a subqueue for each value

You know, I don't have any idea. I actually believe that a smartqueue *could* be used to do this; the association would be to the nid and the queue itself would be tied to a particular field. I'm not familiar enough with CCK to understand how the integration on that side would work, but this is possible.

I hope someone picks up this project.

This actually exists with CCK for Drupal 6. You can have a nodereference field with multiple values, and re-order the list of values on the fly.

Automatically closed -- issue fixed for two weeks with no activity.

restating what I think the OP meant (and what I think should be built).

@Moshe, could you elaborate here? I'm not sure what the feature requested is here.

Assume that the Story content type has a node reference field called Issue where each piece of content gets associated with an Issue node. Think magazines, for example. I would love a smartqueue for each issue so that admins could reorder the nodes within an issue. Make sense?

Ah, so then you could arrange all nodes who reference (are part of) a particular issue?

yes - exactly.

That sounds great. What's the main benefit of having both a nodereference and a smartqueue for a particular issue? Is it the more extensive Views support that could apply to the issue node?

We've run into a use case for galleries in which this feature would be useful. The preferred workflow is to assign each Gallery Image node a Gallery via node reference then use Nodequeue to order images within each gallery. Using a multiple nodereference field as part of the Gallery content type to associate and order Gallery Images is not an acceptable workflow in this case (unintuitive flow, too many images to select from once galleries get large enough, etc.).

Would love to see this kind of functionality.
Subscribe.

This would be helpful. My current implementation consists of a node (region page) with a taxonomy term (region page type). I also have a nodequeue for each region consisting of region pages.

When I display the Region Page node, I look up its term id. I feed that term ID to my 'get_nodequeue_mapping' function that gives me back a nodequeue id (its a manual mapping). Now that I have the nodequeue ID, that is an arg to a embedded view.

In my case, it would be nice to just have a drop down on the node that specified which nodequeue to use. I hate having to do manual mappings of termID's to <insert other drupal feature>. ;)

Anyone make any progress on this functionality?

One implimentation hurdle seems to be that there is some major overlap in functionality between nodereference and nodequeue. If you are already using nodereference to store the relationship information, it would be redundant to install nodequeue and replicate the same queue membership data again.

Instead of building upon nodequeue, it almost seems better to use a stripped down module just to handle the order functionality, and not duplicate relationship data and node type restrictions. Perhaps just add a single additional column to the content_type_xxx tables alongside the nodereference field data to store a numerical order value. The only downside seems to be that you would have to duplicate the views integration and the admin interface to reorder nodes.

Attached is a simple module based on smartqueue taxonomy, with essentially the same kind of functioning.