<?xml version="1.0" encoding="UTF-8"?>
<posts type="array">
  <post>
    <body>I am not certain that I am understanding this correctly.  What if you created a &quot;propagated from&quot; planting, and then added them to the gardens that they are going to?  If I am moving an entire plant, I use the transplanted selection, and then put it in the garden that it is now in, but if you are taking cuttings and moving them, would that not work?</body>
    <created-at type="datetime">2009-09-30T09:52:36-05:00</created-at>
    <delta type="boolean">false</delta>
    <id type="integer">12862</id>
    <photo-id type="integer" nil="true"></photo-id>
    <topic-id type="integer">2726</topic-id>
    <updated-at type="datetime">2009-09-30T09:52:36-05:00</updated-at>
    <user-id type="integer">5779</user-id>
  </post>
  <post>
    <body>That's generally how I do it also. I simply create a &quot;sort of new&quot; planting by propagating one plant off of the mother plant and then I place that one in the new garden.</body>
    <created-at type="datetime">2009-09-30T10:14:38-05:00</created-at>
    <delta type="boolean">false</delta>
    <id type="integer">12863</id>
    <photo-id type="integer" nil="true"></photo-id>
    <topic-id type="integer">2726</topic-id>
    <updated-at type="datetime">2009-09-30T10:14:38-05:00</updated-at>
    <user-id type="integer">1302</user-id>
  </post>
  <post>
    <body>I think that makes the most sense. :)</body>
    <created-at type="datetime">2009-09-30T10:47:49-05:00</created-at>
    <delta type="boolean">false</delta>
    <id type="integer">12864</id>
    <photo-id type="integer" nil="true"></photo-id>
    <topic-id type="integer">2726</topic-id>
    <updated-at type="datetime">2009-09-30T10:47:49-05:00</updated-at>
    <user-id type="integer">5779</user-id>
  </post>
  <post>
    <body>That's good. I just 'found' the child propagation option and that would seem to solve the propagation / division move nicely. I should have used that when I did the first split. I'll go back, redo those and see how it works out.

(update) 
It does work except that to take advantage of the _one journal -&gt; multiple events_ feature requires that the multiple plantings I create can be identified when selecting from the drop down *What's this about?* menu. 
If I'm clear in the process as I'm creating them it does work, but I need to then open and edit each planting, select the garden (so I can select them from the list), reselect the image because it's blank now, adjust the quantity as required, pause, check and save. It's a lot of steps and if you say it quickly it's not much but it's a fiddle and given a choice between selecting an option to *split planting*, which would pre fill these from the existing info, or allotting uninterrupted time to do the above I'll take the *split planting* option. Especially when it becomes more than 3 plantings as in the tomato example below, where the numbers are also real life.
I remember when the multiple journal events feature was introduced and for such a simple feature it made journalling so much easier that you were more inclined to wrap it all up as one rather than spam the grapevine with individual entries. While I don't think split plantings would have the same appeal, they'd certainly make things easier to manage and get your (my) head around
(/update)

I believe for a plain 'transplant' or 'planting out' move such as from seedlings, that Nic's _split planting_ idea is also required. Here's an example...

Very soon I'll start moving my Tomatoes from the glasshouse. I've 20 varieties that I want to split over (say) 3 garden beds. At the moment I can move (transplant) a variety once only before the above _origin &#8594; destination_ confusion kicks in. The only way around it is to create a new planting of that tomato variety. While doing that would work it would become a huge effort for a simple planting. (I'd be creating 40 new plantings in this case).  The new planting (copy planting from the menu) would also be missing all the milestones (except for sown) so for completeness I'd need to duplicate them as well, or link it back to the parent planting somehow.
</body>
    <created-at type="datetime">2009-09-30T18:51:05-05:00</created-at>
    <delta type="boolean">false</delta>
    <id type="integer">12867</id>
    <photo-id type="integer" nil="true"></photo-id>
    <topic-id type="integer">2726</topic-id>
    <updated-at type="datetime">2009-09-30T21:00:48-05:00</updated-at>
    <user-id type="integer">5165</user-id>
  </post>
  <post>
    <body>When splitting things out to beds this last year, I made new plantings, edited them to have the same start date.  Then I looked at my original planting, opened all the existing journals, then added the propagated plantings to the journals.  Not the most efficient solution, but it worked.</body>
    <created-at type="datetime">2009-09-30T20:28:25-05:00</created-at>
    <delta type="boolean">false</delta>
    <id type="integer">12869</id>
    <photo-id type="integer" nil="true"></photo-id>
    <topic-id type="integer">2726</topic-id>
    <updated-at type="datetime">2009-09-30T20:28:25-05:00</updated-at>
    <user-id type="integer">1237</user-id>
  </post>
  <post>
    <body>@cmagnus You have more tenacity than me, or you had a lot of indoor days - hot, wet? Does this also mean you'd encourage Nic to revisit the *split planting* idea. ;-)

I've added an update to my post directly above yours, I could have added it separately but it's in context back there.

It is do-able, but the shortest path sometimes is the least resistance, which means so often, not doing it. As it is I should be in the garden now rather than talking about it, but we've all been there. I'd better go, the tomatoes are calling. 
</body>
    <created-at type="datetime">2009-09-30T21:08:45-05:00</created-at>
    <delta type="boolean">false</delta>
    <id type="integer">12870</id>
    <photo-id type="integer" nil="true"></photo-id>
    <topic-id type="integer">2726</topic-id>
    <updated-at type="datetime">2009-09-30T21:08:45-05:00</updated-at>
    <user-id type="integer">5165</user-id>
  </post>
  <post>
    <body>I'd definitely go for the split planting, but only if it retains the access to all the journals, milestones, photos, etc. that were attributed to the original plant. This became a significant headache for my wintersown plantings.There were usually many seedlings in one container, which could not be anticipated at sowing, and often seedlings were planted out in one or more gardens and/or extras potted up for swapping or gifts or planting later. I ended up using the copy planting option, and putting each new plant where I wanted it while retaining the original planting in the winter-sowing list. Then at the point of planting out, I had to list each garden - the original and the destination - in the journal to ensure all info was retained in both for the transition. If I moved a plant from origin -&gt; destination as graibeard describes, I lost that planting from the winter-sowing list. I wanted to retain the list intact with notes and journals for future WS reference. Once everything was planted out, I archived each WS plant and eventually the entire WS-2009 garden, but it is all still an intact entity to refer back to. I have to say it was a lot of work for 135 winter-sown containers with possible multiple plantings from each, but I felt it was worth it and necessary for me.</body>
    <created-at type="datetime">2009-09-30T21:58:54-05:00</created-at>
    <delta type="boolean">false</delta>
    <id type="integer">12871</id>
    <photo-id type="integer" nil="true"></photo-id>
    <topic-id type="integer">2726</topic-id>
    <updated-at type="datetime">2009-09-30T21:58:54-05:00</updated-at>
    <user-id type="integer">4903</user-id>
  </post>
  <post>
    <body>Hi guys - just an update on this for you all: I've been thinking about how best to implement split plantings over the last couple of months, and haven't yet found a way that I'm happy with yet. I still think it is an important piece of functionality that is needed in the system, but I want to make sure that I implement this one right. Keep the suggestions coming on how you see it working, as it helps visualise this from different perspectives :)</body>
    <created-at type="datetime">2009-10-11T13:15:50-05:00</created-at>
    <delta type="boolean">false</delta>
    <id type="integer">13036</id>
    <photo-id type="integer" nil="true"></photo-id>
    <topic-id type="integer">2726</topic-id>
    <updated-at type="datetime">2009-10-11T13:15:50-05:00</updated-at>
    <user-id type="integer">1</user-id>
  </post>
  <post>
    <body>How about a drop down box like the one in the swaps list with the &quot;add&quot; button beneath it, and beside each planting, a &quot;how many&quot; box?</body>
    <created-at type="datetime">2009-10-11T13:41:47-05:00</created-at>
    <delta type="boolean">false</delta>
    <id type="integer">13037</id>
    <photo-id type="integer" nil="true"></photo-id>
    <topic-id type="integer">2726</topic-id>
    <updated-at type="datetime">2009-10-11T13:41:47-05:00</updated-at>
    <user-id type="integer">5779</user-id>
  </post>
  <post>
    <body>@graibeard: How did you know?  Yes, it rained EVERY SINGLE DAY between June and the beginning of September this year.  I think I'd have less patience doing things manually if I had a summer-like summer.  I totally endorse the splitting option. :)</body>
    <created-at type="datetime">2009-10-12T21:58:21-05:00</created-at>
    <delta type="boolean">false</delta>
    <id type="integer">13048</id>
    <photo-id type="integer" nil="true"></photo-id>
    <topic-id type="integer">2726</topic-id>
    <updated-at type="datetime">2009-10-12T21:58:21-05:00</updated-at>
    <user-id type="integer">1237</user-id>
  </post>
</posts>
