Wrestling the Octopus: Using Pageroute and Nodereference to Manage Complex Node Relationships
http://2008.drupalcamptoronto.org/content/ wrestling-octopus-using-pageroute-and-nodereference-manage-complex-node-relationships

enables complex page / function structure e.g. within each campaign: events > visits > shifts

nodereference - standard part of CCK

• relationships between nodes (dropdown or autocomplete)
• any type of node (not just CCK)

pageroute - chains pages [forms] together http://drupal.org/project/pageroute
uses subform_element

• built-in support for states, workflow_ng
• constructed for use with nodeprofile + nodefamily

routes + path

• overrides edit access to the cotent type
• creates new menu item
• access control by role
• options for navigation buttons, messages, ...

pages

• variety of types: node add, edit, display, management
• for each page, specify type of content, and path, and button
• tab-like submit buttons w/custom labels

[can multiple roles use the same pageroute?]

pageroute_nodereference

• routes based on specific content type
  • e.g. add children to family record (jetsons: george, jane, judy) based on content types (parent, spouse, child)
  • lists children inside parent - showing full node view [but really should be a view of the node]

enhancements

• requires naming conventions to work (but should be based on CCK definitions)
• more options for management + display

demonstration

[code now linked to issue in pageroute]

option:

node relativity http://drupal.org/project/relativity

• complex relationships between nodes that could be multi-level hierarchies
• could also combine with pageroute (to enforce creation of concert before review)
• [this could work for brla / property + family relationships]
• example at kwlug.org | agenda item part of meeting / presented at meeting