A resource can only have one parent. You need to look at the Ditto calls as a "pull" mechanism, with different calls pulling data from resources which can have different and overlapping parents, and formatting the data using chunks and placeholders for output on the page containing the Ditto call.
Let’s say you have
Network 1 (id=66)
project n1-1
project n1-2
etc
Network 2 (id=69)
project n2-1
project n2-2
etc
Your Network 1 and Network 2 listing pages (resources 66 and 69) would have a Ditto call including
[!Ditto? &tpl=`format.chunk.for.networkspage` !]
If they are the parents of the project pages, there’s no need to specify
&parents, as the current document is the default
&parents parameter.
The
&tpl parameter names a chunk for formatting the output from each retrieved document. This will include static HTML code and placeholders such as [+longtitle+] for the data that varies from one document to the next.
Your "All Projects" page will be a resource with a Ditto call specifying the network head pages as multiple parents, and a different template chunk, if required, for outputting elements of the retrieved documents:
[!Ditto? &parents=`66,69` &tpl=`format.chunk.for.overviewpage` !]
With no further parameters, the combined list will be displayed in descending order of the project pages’ creation dates. You can use
&orderBy parameter (with multiple settings for sorts within sort) to change that.
KP