Using together with Node Queue

HansBKK - November 20, 2008 - 08:23
Project:RelatedContent
Version:5.x-1.x-dev
Component:Miscellaneous
Category:support request
Priority:normal
Assigned:Unassigned
Status:active
Description

This isn't so much a question as a proposed usage scenario, but I am looking for feedback on 1 whether this would work from a technical/compatibility POV, 2 if it seems like an appropriate use of RC and 3 would there be a simpler way to accomplish the same thing?

Rather than issues with distinct content, my "issues" are released versions of a document assembled from a series of nodes, many/most of which will be the same nodes from one issue to the next. New nodes will get inserted and some old ones deleted, and some existing nodes will get updated between issues.

I'm trying to visualize the workflow for my use case, and it seems I could use both these modules together building the "eligible for RC selection" Views on a Node Queue. This would combine RC's ability to group and NQ's arbitrary sort ordering and the ability to add a node to a queue directly from a node during normal day-to-day viewing.

The queue is a staging area for pre-processing, while RC creates the periodical "publishing snapshot". As the "editor" is reading through new/updated nodes between issues, using whatever views/navigation, she adds nodes to the different topic queues, letting them collect there.

Then when it's time to assemble the next revision of that topic doc, she first goes to the queue(s), puts the new nodes sorted in the right order, perhaps creates some new connecting nodes with editorial transition text, perhaps removing now irrelevant content, etc.

Note there may be more than one View of a given Node queue, perhaps filtering by content type, or anything else Views can filter on. From RC the final set is selected/deselected - some nodes may be pending but not yet ready to be published and left in the queue but not let include in the RC node. When everything is ready the editor clicks Update and that revision's done.

This use case is a bit different in that the previous issues will not be preserved, but if needed one could perhaps print to PDF or something to create archives. Side question - how to get prettyprint like Book?

Thanks in advance.

 
 

Drupal is a registered trademark of Dries Buytaert.