New ingredient genarator: users add their own

[ed]

1. Think of a process enabling users to add their own ingredients.
2. Trial a 'add your own ingredients' feature

(might not make phase 5, but let's put some thought into it)

[jim]

2 approaches:

1: allow 'normals' to post ingredient pages... But that means polluting the content and proper moderation to pull out the good ones.

2: uses Webform -- ​http://drupal.org/project/webform -- 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.

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.

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?

[ed]

go for option 2: use a webform with this process:

1. logged in user proposes an ingredient using the webform
2. email is sent to 'ingredient editor' specified email address for assessment
3. email is sent to user confirming the action (copy needs to be editable by ed)
4. ingredient editor reviews proposed ingredient
5. ingredient editor either publishes it as a 'User generated ingredient' or turns it down with a email to the user
6. If the user generated ingredient is published, user gets a 'we have published your ingredient'

NB: we need to differentiate between User Generated Ingredients and Rob Generated Ingredients -

[jim]

Webform and Webform Rules integration added to SVN which will do 95% of this...

[jim]

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.

The full process (based on yours), with ch-ch-changes/comments, will be:

1. Logged in user submits a Ingredient webform
2. Email sent to 'ingredient editor' specified email address for assessment
3. Email is sent to user confirming the action (copy needs to be editable by ed) -- it'll be in rules so editable when you know where to look
4. ingredient editor reviews proposed ingredient as a webform
5. ingredient editor either publishes by copy/pasting it into a new Ingredient page and setting the source as 'User generated ingredient' or turns it down with a manual email to the user
6. If the user generated ingredient is published, user gets a 'we have published your ingredient' email

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).

I'll need to add a new 'Ingredient source' field to the ingredients CT with two options: 'Transition Network' and 'User submitted'

I'll start now, but please do comment ASAP if any of this isn't right.

[jim]

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.

[jim]

Actually, and apols for the brain farts, I don't think my last proposal is sensible either.

The emails saying "we've published your ingredient, thanks" should be manual otherwise we're gonna get our knickers in a twist...

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.

Is this ok, Ed?

[jim]

OK, so the new form is here: ​https://www.transitionnetwork.org/submit-your-ingredient

Please let me know:

1. What editor email addresses will get notifications of the ingredient submission
2. What you want the text for emails to the user confirming they've sent it.
3. If the above process and caveats are ok?

[ed]

right then here i am at last. hmm.

1. ingredienteditor@… gets an alert of the new webform being submitted (with a discrete URL of the specific form added)

"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.

Best wishes,
The Transition Network content team"

3. all points understood - process is:
4. registered logged in user submits form ​https://www.transitionnetwork.org/submit-your-ingredient
5. ingredient editor receives alert with link to stored webform
6. ingredient editor works with rob, reviews all webforms, agrees which are go-ers
7. ingredient editor deletes un-desired ones (and emails users saying sorry)
8. ingredient editor sets up new ingredients, classed as UGIs, with user set as author
9. ingredient editor manually alerts user to their new 'UGI'

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.

[jim]

1. and 2. done, email address and message in place.

3. is all fine.

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?

You can edit ​https://www.transitionnetwork.org/submit-your-ingredient 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.

All done?

[ed]

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?

[jim]

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.

Done bar testing.