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.

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.

I started a quick, light review of this module. My impression is that it's working generally well and needs a few fixes.

Setup:
- Click "add new node reference queue"
- The queue edit form displays the error "Invalid argument supplied for foreach() in form.inc on line 1423." There are no node reference fields in my test install.
- Created a nodereference field, field_issue, that refers to issue nodes.
- Once again tried to add the first node reference queue, the error does not display
- Submitted a page node, did not populate field_issue, got a white screen of death and undefined function error for "return arary();" ;) -- I changed this to array(), resolving the WSOD
- As expected nodes were eleigible for an issue subqueue only when their field_issue was populated
- unpopulating an issue field leaves the node in the subqueue but removes the links to remove the node from a subqueue, and it doesn't show up on the nodequeue tab. My sense is that we should probably remove the node from the subqueue if it loose it's field_issue contents.

Great work, and I look forward to seeing this as part of the Nodequeue package!

I've trying to make it simpler. Here is my draft module, it's pretending to replace nodereference module with similar functions but on nodequeues steroids.

It's not fully functional and it's not all clear for me with Smartqueue API.

Essentially it creates a nodequeue for each node of selected content type. Referable types of nodes to enqueue are choosed as usual for nodequeue. What you can do with it is multilevel one-to-many node relationship with all UX and integrations.

* Update: Shame on me for this attachment! Don't test it! It was at early morning after sleepless night :)
** Update: See my project.

I'm not really if http://drupal.org/project/smartqueue_nodetypes referenced in #16 really does what is being asked for in this ticket, which if understand it correctly, is to provide a means or ordering a node reference field, by tying it in with nodequeue.

Subscribing.

I second #17 - I don't think the smartqueue_nodetypes is the solution.

I think #13 is on to something, why use nodequeue at all, when the only thing needed is a way to order node references? Or go the other way and skip the node references and only have one reference to an existing nodequeue.

Actually, you CAN order the node reference fields using nodereference and views alone.

1) Set the nodereference field to use the autocomplete widget - with this selected, you can do drag drop ordering on the values. This applies a 'delta' value to each reference.
2) in views, sort by 'Content [fieldname] : delta)

Ah, nice, thanks!

This would be great functionality to have. I have been in a situation where I have a similar need to what Moshe (#6) and ethanw(#10) were describing above. The nodereference field needs to be on the child node, and this means that I can not use the drag and drop reordering functionality built into nodereference. I have usually ended up use the NAT module combined with a taxonomy smartqueue to get the results that I want, but I still feel that this is less than ideal. For one thing ... when creating a view that lists the child nodes, I do not know how to create a relationship back to the parent nodes because the argument that is used is the nat term id instead of the node id as would be the case if I were using nodereference.

This issue is rather old now, so I am wondering if there is a better method for solving this problem now or if there is any more interest in creating this type of additional smartqueue functionality.

I agree with #21: I'm still looking for a solution to this since, in my mind, the proper architecture is to have the reference on the child node, not the parent (ie. in a photo gallery the photos are referencing the gallery, not the other way around).

I'm going to attempt to do this through smartqueue and taxonomy (adding a taxonomy which isn't really necessary to photo nodes just to be able to use smartqueue taxonomy). Any other solutions or directions at this point would be helpful.

All - I'm looking for a CCK queue. Found this discussion, but it has moved away from the original question. Is there a way to create a queue for contents of CCK fields and not just nodes?
For example, I would like to add CCK audio to a queue as a way of making a set list, without having to create a node for each audio file.
Does anyone know if this is possible?
Thanks, Mick

@#23

That just sounds like you want a multiple-value filefield on your "setlist" node, which already allows you to order the files, IIRC.