You could always get the best of both worlds by doing what Zohar suggests re: making each item an individual node, but also providing a single form interfacing for submitting a collection. In this case, on form submission, the individual nodes would be programatically created in the backend. You could even do the magic of creating the 'collection' view at this stage. It could either be dead-simple or prohibitively difficult to set this up, depending on your level of familiarity with PHP and the Forms API.
<br><br>William <br><br><div><span class="gmail_quote">On 9/10/07, <b class="gmail_sendername">Jean Gazis</b> <<a href="mailto:jgazis@gmail.com">jgazis@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I think that probably provides more flexibility in the long run. It's not an e-commerce site. I'm concerned the the client will find entering 12 items separately more cumbersome than just doing one form. <br><span class="sg">
<br>Jean
</span><span class="q"><br><br><div><span class="gmail_quote">On 9/10/07, <b class="gmail_sendername">Zohar Stolar</b> <<a href="mailto:z.stolar@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
z.stolar@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Yes, it's better for you to have a content type for "wine", and then you<br>can do different things with it.<br>Think of a wine as one entity. 12 wines can be an entity if they are<br>bundled in one package, but a single wine should be on its own.
<br><br><br><br>Jean Gazis wrote:<br><br>> I want to have a content type for a monthly list of about a dozen wine<br>> selections. I created the content type, and created fields for one<br>> wine, and I can add new fields or existing fields from a _different_
<br>> content type, but I don't see any way to copy the first set of fields<br>> on the _same_ content type. Is there a reason for this? Do I have to<br>> have Name for wine #1, and then Name2 for wine #2 and so on?
<br>><br>> Would I be better off to have a content type for "wine" and then have<br>> a view that shows the 12 most recent?<br>><br>> --<br>> Jean Gazis<br>> <a href="http://www.jeangazis.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
www.jeangazis.com</a> <<a href="http://www.jeangazis.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.jeangazis.com</a>><br>> <a href="http://www.boxofrain.us" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
www.boxofrain.us</a> <<a href="http://www.boxofrain.us" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.boxofrain.us</a>
><br>><br>> "Believe those who are seeking the truth; doubt those who find it." -<br>> André Gide<br><br>--<br>[ Drupal support list | <a href="http://lists.drupal.org/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://lists.drupal.org/</a> ]
<br></blockquote></div><br><br clear="all"><br>-- <br>Jean Gazis<br><a href="http://www.jeangazis.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">www.jeangazis.com</a><br></span><div><span class="e" id="q_114f04790673525a_3">
<a href="http://www.boxofrain.us" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">www.boxofrain.us</a><br><br>"Believe those who are seeking the truth; doubt those who find it." - André Gide
</span></div><br>--<br>[ Drupal support list | <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://lists.drupal.org/" target="_blank">http://lists.drupal.org/</a> ]<br></blockquote></div><br>