Allow the use of multiple collections for content

[pajtai]

A content type would live in just one collection. The default collection is content.

Collections can have multiple content types (e.g. use case: collection products with seasonal-products and subscription-products).

Nodes can only have content from the same collection. Nested nodes would not have to be the same collection as parent node.

Queries can be targeted at specific collections. The default collection is content. Phase 2 would have a search all collections option.

Can use existing destination field for this.

[travism]

Peter,

Mostly sounds spot on.

For Nodes can only have content from the same collection is there a reason why that is the case? Right now a node can link to multiple content types IE multiple potential collections.

[pajtai]

Was just thinking of use cases and ease of creating the code. I don't really see a use case for multiple collections in a node.

If multiple contenttypes are "related" - as with the seasonal and subscription products example from the description - then they should be put into the same collection.

I kind of view it as a restriction that would force you to structure you data better. It would not disallow multiple contenttypes in the same node, it would disallow multiple contenttypes from multiple collections in the same node.