<?xml version="1.0" encoding="UTF-8"?>
<posts type="array">
  <post>
    <body>Hi nax - not yet, but I've been working on some changes this weekend that's leading towards this sort of bulk functionality, so hopefully soon :)

In the meantime, the quickest way might be to archive the garden (this also archives all plantings within the garden). If you don't want to archive the garden as well, I might be able to do a quick database update to unarchive the garden again - have a think about what you'd like to do and let me know.

Good idea on the archive reasons: If anyone has any other thoughts on extra archive reasons that might be useful, let me know and I'll try and factor it into the changes.</body>
    <created-at type="datetime">2009-10-11T18:12:51Z</created-at>
    <delta type="boolean">false</delta>
    <id type="integer">13034</id>
    <photo-id type="integer" nil="true"></photo-id>
    <topic-id type="integer">2758</topic-id>
    <updated-at type="datetime">2009-10-11T18:12:51Z</updated-at>
    <user-id type="integer">1</user-id>
  </post>
  <post>
    <body>On the topic of archiving, it would be really nice if archiving had the same calendar for date selection as starting seeds has.  I had my first frost today and it was irritating to have to manually select date, month, then type in year for every single plant.  Having it default to the day of removal would be nicer, and being able to pick it on a calendar if it were different would be nicer still.</body>
    <created-at type="datetime">2009-10-13T02:54:37Z</created-at>
    <delta type="boolean">false</delta>
    <id type="integer">13047</id>
    <photo-id type="integer" nil="true"></photo-id>
    <topic-id type="integer">2758</topic-id>
    <updated-at type="datetime">2009-10-13T02:54:37Z</updated-at>
    <user-id type="integer">1237</user-id>
  </post>
  <post>
    <body>Little bit of a different take on Archiving reasons.
Now I'm a supporter I notice that with each journal I can add a little comment when selecting what the journal is about, and this shows up with the plant/garden icon at the bottom
On archiving reasons, this same little comment box would be great when archiving because I would be able to add a little reason why it was harvested/died etc. without having to write a fullblown journal before I archive them, which is 2 separate tasks to complete the one action.(this is the way I have been doing it anyway, and may be incorrect)</body>
    <created-at type="datetime">2009-10-13T10:52:46Z</created-at>
    <delta type="boolean">false</delta>
    <id type="integer">13052</id>
    <photo-id type="integer" nil="true"></photo-id>
    <topic-id type="integer">2758</topic-id>
    <updated-at type="datetime">2009-10-13T10:52:46Z</updated-at>
    <user-id type="integer">7750</user-id>
  </post>
  <post>
    <body>what nyaka said.  Being able to select archive as an event with a comment would be great; I often forget to archive plants when I write their final journal then I have another data entry task I have to go back and do later.</body>
    <created-at type="datetime">2009-10-13T10:58:06Z</created-at>
    <delta type="boolean">false</delta>
    <id type="integer">13053</id>
    <photo-id type="integer" nil="true"></photo-id>
    <topic-id type="integer">2758</topic-id>
    <updated-at type="datetime">2009-10-13T10:58:06Z</updated-at>
    <user-id type="integer">1237</user-id>
  </post>
  <post>
    <body>Nice, nyaka.  </body>
    <created-at type="datetime">2009-10-13T19:33:39Z</created-at>
    <delta type="boolean">false</delta>
    <id type="integer">13065</id>
    <photo-id type="integer" nil="true"></photo-id>
    <topic-id type="integer">2758</topic-id>
    <updated-at type="datetime">2009-10-13T19:33:39Z</updated-at>
    <user-id type="integer">3568</user-id>
  </post>
</posts>
