<?xml version="1.0"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>Transition Technology: Ticket #322: New ingredient genarator: users add their own</title>
    <link>http://localhost:8080/trac/ticket/322</link>
    <description>&lt;ol&gt;&lt;li&gt;Think of a process enabling users to add their own ingredients.
&lt;/li&gt;&lt;li&gt;Trial a 'add your own ingredients' feature
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
(might not make phase 5, but let's put some thought into it)
&lt;/p&gt;
</description>
    <language>en-us</language>
    <image>
      <title>Transition Technology</title>
      <url>/trac/chrome/site/TransitionNetwork-Logo-Web-Small.jpg</url>
      <link>http://localhost:8080/trac/ticket/322</link>
    </image>
    <generator>Trac 0.12.5</generator>
    <item>
      
        <dc:creator>jim</dc:creator>

      <pubDate>Thu, 22 Sep 2011 18:20:34 GMT</pubDate>
      <title>hours, totalhours changed</title>
      <link>http://localhost:8080/trac/ticket/322#comment:1</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/322#comment:1</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;hours&lt;/strong&gt;
                changed from &lt;em&gt;0.0&lt;/em&gt; to &lt;em&gt;0.1&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;totalhours&lt;/strong&gt;
                changed from &lt;em&gt;0.0&lt;/em&gt; to &lt;em&gt;0.1&lt;/em&gt;
            &lt;/li&gt;
          &lt;/ul&gt;
        &lt;p&gt;
2 approaches:
&lt;/p&gt;
&lt;p&gt;
1: allow 'normals' to post ingredient pages... But that means polluting the content and proper moderation to pull out the good ones.
&lt;/p&gt;
&lt;p&gt;
2: uses Webform -- &lt;a class="ext-link" href="http://drupal.org/project/webform"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://drupal.org/project/webform&lt;/a&gt; -- which allows any form to be created and stored. Its advantages are the node you make IS the form, and people's submissions are entities that live against it.
&lt;/p&gt;
&lt;p&gt;
In our case, a simple webform would be made that's submittable by logged in people (or anyone?) that when submitted sends an email to the appropriate person. They then check it and post it live by converting it to to a new ingredient which then can be edited as needed.
&lt;/p&gt;
&lt;p&gt;
Fundamentally the issue is: Do you want people to be able to see the posted ingredients too? How precious are we about the ingredient data that might be posted -- I imagine it'll all need editing/curating anyway?
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>ed</dc:creator>

      <pubDate>Wed, 28 Sep 2011 10:46:05 GMT</pubDate>
      <title></title>
      <link>http://localhost:8080/trac/ticket/322#comment:2</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/322#comment:2</guid>
      <description>
        &lt;p&gt;
go for option 2: use a webform with this process:
&lt;/p&gt;
&lt;ol&gt;&lt;li&gt;logged in user proposes an ingredient using the webform
&lt;/li&gt;&lt;li&gt;email is sent to 'ingredient editor' specified email address for assessment
&lt;/li&gt;&lt;li&gt;email is sent to user confirming the action (copy needs to be editable by ed)
&lt;/li&gt;&lt;li&gt;ingredient editor reviews proposed ingredient
&lt;/li&gt;&lt;li&gt;ingredient editor either publishes it as a 'User generated ingredient' or turns it down with a email to the user
&lt;/li&gt;&lt;li&gt;If the user generated ingredient is published, user gets a 'we have published your ingredient'
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
NB: we need to differentiate between User Generated Ingredients and Rob Generated Ingredients -
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>jim</dc:creator>

      <pubDate>Wed, 28 Sep 2011 17:28:07 GMT</pubDate>
      <title>hours, totalhours changed</title>
      <link>http://localhost:8080/trac/ticket/322#comment:3</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/322#comment:3</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;hours&lt;/strong&gt;
                changed from &lt;em&gt;0.0&lt;/em&gt; to &lt;em&gt;0.05&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;totalhours&lt;/strong&gt;
                changed from &lt;em&gt;0.1&lt;/em&gt; to &lt;em&gt;0.15&lt;/em&gt;
            &lt;/li&gt;
          &lt;/ul&gt;
        &lt;p&gt;
Webform and Webform Rules integration added to SVN which will do 95% of this...
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>ed</dc:creator>

      <pubDate>Thu, 13 Oct 2011 13:53:22 GMT</pubDate>
      <title>priority changed</title>
      <link>http://localhost:8080/trac/ticket/322#comment:4</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/322#comment:4</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;priority&lt;/strong&gt;
                changed from &lt;em&gt;major&lt;/em&gt; to &lt;em&gt;critical&lt;/em&gt;
            &lt;/li&gt;
          &lt;/ul&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>jim</dc:creator>

      <pubDate>Thu, 13 Oct 2011 15:56:05 GMT</pubDate>
      <title>hours, status, totalhours changed</title>
      <link>http://localhost:8080/trac/ticket/322#comment:5</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/322#comment:5</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;hours&lt;/strong&gt;
                changed from &lt;em&gt;0.0&lt;/em&gt; to &lt;em&gt;0.1&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;
                changed from &lt;em&gt;new&lt;/em&gt; to &lt;em&gt;accepted&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;totalhours&lt;/strong&gt;
                changed from &lt;em&gt;0.15&lt;/em&gt; to &lt;em&gt;0.25&lt;/em&gt;
            &lt;/li&gt;
          &lt;/ul&gt;
        &lt;p&gt;
OK, all the bits are on the site waiting to go... I'm going to make a webform and do some rules work to spew emails around too.
&lt;/p&gt;
&lt;p&gt;
The full process (based on yours), with &lt;strong&gt;ch-ch-changes/comments&lt;/strong&gt;, will be:
&lt;/p&gt;
&lt;ol&gt;&lt;li&gt;Logged in user submits a Ingredient webform
&lt;/li&gt;&lt;li&gt;Email sent to 'ingredient editor' specified email address for assessment
&lt;/li&gt;&lt;li&gt;Email is sent to user confirming the action (copy needs to be editable by ed) -- &lt;strong&gt;it'll be in rules so editable when you know where to look&lt;/strong&gt;
&lt;/li&gt;&lt;li&gt;ingredient editor reviews proposed ingredient &lt;strong&gt;as a webform&lt;/strong&gt;
&lt;/li&gt;&lt;li&gt;ingredient editor either publishes &lt;strong&gt;by copy/pasting it into a new Ingredient page and setting the source as&lt;/strong&gt; 'User generated ingredient' or turns it down with a &lt;strong&gt;manual&lt;/strong&gt; email to the user
&lt;/li&gt;&lt;li&gt;If the user generated ingredient is published, user gets a 'we have published your ingredient' email
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
The key thing is: Webform submissions are NOT like nodes, so there is an editorial process to convert from the webform to the ingredient (step 5).
&lt;/p&gt;
&lt;p&gt;
I'll need to add a new 'Ingredient source' field to the ingredients CT with two options: 'Transition Network' and 'User submitted'
&lt;/p&gt;
&lt;p&gt;
I'll start now, but please do comment ASAP if any of this isn't right.
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>jim</dc:creator>

      <pubDate>Thu, 13 Oct 2011 16:02:44 GMT</pubDate>
      <title>hours, totalhours changed</title>
      <link>http://localhost:8080/trac/ticket/322#comment:6</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/322#comment:6</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;hours&lt;/strong&gt;
                changed from &lt;em&gt;0.0&lt;/em&gt; to &lt;em&gt;0.05&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;totalhours&lt;/strong&gt;
                changed from &lt;em&gt;0.25&lt;/em&gt; to &lt;em&gt;0.3&lt;/em&gt;
            &lt;/li&gt;
          &lt;/ul&gt;
        &lt;p&gt;
Hmm... thinking about it, part 6 is a pain too... Will the editor change the author from them to the user? If not, they'll need to manually email the person if it goes public, if so then we can set up a rule to send the email.
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>jim</dc:creator>

      <pubDate>Thu, 13 Oct 2011 16:14:02 GMT</pubDate>
      <title>hours, totalhours changed</title>
      <link>http://localhost:8080/trac/ticket/322#comment:7</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/322#comment:7</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;hours&lt;/strong&gt;
                changed from &lt;em&gt;0.0&lt;/em&gt; to &lt;em&gt;0.05&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;totalhours&lt;/strong&gt;
                changed from &lt;em&gt;0.3&lt;/em&gt; to &lt;em&gt;0.35&lt;/em&gt;
            &lt;/li&gt;
          &lt;/ul&gt;
        &lt;p&gt;
Actually, and apols for the brain farts, I don't think my last proposal is sensible either.
&lt;/p&gt;
&lt;p&gt;
The emails saying "we've published your ingredient, thanks" should be manual otherwise we're gonna get our knickers in a twist...
&lt;/p&gt;
&lt;p&gt;
It's nothing that can't be put as a template in a PDF for editors they can cut/paste into the users' contact form.
&lt;/p&gt;
&lt;p&gt;
Is this ok, Ed?
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>jim</dc:creator>

      <pubDate>Thu, 13 Oct 2011 16:27:09 GMT</pubDate>
      <title>hours, totalhours changed</title>
      <link>http://localhost:8080/trac/ticket/322#comment:8</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/322#comment:8</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;hours&lt;/strong&gt;
                changed from &lt;em&gt;0.0&lt;/em&gt; to &lt;em&gt;0.2&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;totalhours&lt;/strong&gt;
                changed from &lt;em&gt;0.35&lt;/em&gt; to &lt;em&gt;0.55&lt;/em&gt;
            &lt;/li&gt;
          &lt;/ul&gt;
        &lt;p&gt;
OK, so the new form is here: &lt;a class="ext-link" href="https://www.transitionnetwork.org/submit-your-ingredient"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/submit-your-ingredient&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Please let me know:
&lt;/p&gt;
&lt;ol&gt;&lt;li&gt;What editor email addresses will get notifications of the ingredient submission
&lt;/li&gt;&lt;li&gt;What you want the text for emails to the user confirming they've sent it.
&lt;/li&gt;&lt;li&gt;If the above process and caveats are ok?
&lt;/li&gt;&lt;/ol&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>ed</dc:creator>

      <pubDate>Tue, 18 Oct 2011 14:30:01 GMT</pubDate>
      <title></title>
      <link>http://localhost:8080/trac/ticket/322#comment:9</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/322#comment:9</guid>
      <description>
        &lt;p&gt;
right then here i am at last. hmm.
&lt;/p&gt;
&lt;ol&gt;&lt;li&gt;ingredienteditor@… gets an alert of the new webform being submitted (with a discrete URL of the specific form added)
&lt;/li&gt;&lt;/ol&gt;&lt;ol start="2"&gt;&lt;li&gt;
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
"Thank you for submitting your ingredient. We are collecting recommendations and will review them as a group in due course. We will contact you when we have done the review and let you know if we will publish it or not.
&lt;/p&gt;
&lt;p&gt;
Best wishes,
The Transition Network content team"
&lt;/p&gt;
&lt;ol start="3"&gt;&lt;li&gt;all points understood - process is:
&lt;/li&gt;&lt;li&gt;registered logged in user submits form &lt;a class="ext-link" href="https://www.transitionnetwork.org/submit-your-ingredient"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/submit-your-ingredient&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;ingredient editor receives alert with link to stored webform
&lt;/li&gt;&lt;li&gt;ingredient editor works with rob, reviews all webforms, agrees which are go-ers
&lt;/li&gt;&lt;li&gt;ingredient editor deletes un-desired ones (and emails users saying sorry)
&lt;/li&gt;&lt;li&gt;ingredient editor sets up new ingredients, classed as UGIs, with user set as author
&lt;/li&gt;&lt;li&gt;ingredient editor manually alerts user to their new 'UGI'
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
NB: pls confirm - can an ingredient editor set up an ingredient with a registered user as the author? then the author could edit it and make it nicer if they wanted.
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>jim</dc:creator>

      <pubDate>Tue, 18 Oct 2011 15:33:58 GMT</pubDate>
      <title></title>
      <link>http://localhost:8080/trac/ticket/322#comment:10</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/322#comment:10</guid>
      <description>
        &lt;ol&gt;&lt;li&gt;and 2. done, email address and message in place.
&lt;/li&gt;&lt;/ol&gt;&lt;ol start="3"&gt;&lt;li&gt;is all fine.
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
NB: confirmed, you can if you want to... Presently users don't have permission to edit their own ingredients -- I've enabled this though - ok?
&lt;/p&gt;
&lt;p&gt;
You can edit &lt;a class="ext-link" href="https://www.transitionnetwork.org/submit-your-ingredient"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/submit-your-ingredient&lt;/a&gt; as with any other node to change the blurb... Worth clicking around the 'Webform' tab on that page and getting a feel for it, too.
&lt;/p&gt;
&lt;p&gt;
All done?
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>ed</dc:creator>

      <pubDate>Wed, 19 Oct 2011 15:15:05 GMT</pubDate>
      <title></title>
      <link>http://localhost:8080/trac/ticket/322#comment:11</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/322#comment:11</guid>
      <description>
        &lt;p&gt;
What happens to 'UGI's once they're in? How can we display them? Is this something Laura can do as vebmaster or do we need a plan while we've got ttech cash?
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>jim</dc:creator>

      <pubDate>Thu, 20 Oct 2011 11:39:09 GMT</pubDate>
      <title>status changed; resolution set</title>
      <link>http://localhost:8080/trac/ticket/322#comment:12</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/322#comment:12</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;
                changed from &lt;em&gt;accepted&lt;/em&gt; to &lt;em&gt;closed&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;resolution&lt;/strong&gt;
                set to &lt;em&gt;needs testing&lt;/em&gt;
            &lt;/li&gt;
          &lt;/ul&gt;
        &lt;p&gt;
As discussed... The UGIs will appear with the others so no filtering is in place. However the 'Ingredient source' field allows such filtering, so when UGIs are ready to be added the views and panels can be tweaked once Rob and co have decided how/where they want them to sit.
&lt;/p&gt;
&lt;p&gt;
Done bar testing.
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item>
 </channel>
</rss>