Sharing Engine/workflows

From TransitionWiki
< Sharing Engine
Revision as of 10:02, 30 October 2012 by Edmitchell (Talk | contribs) (Moderation of Project Submission item)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Webmaster generates widget for own site

  • webmaster follows a link to add widget to their site
  • webmaster arrives on 'add a widget page/section'
  • IF webmaster is registered:
  •   webmaster login (stay on page if possible, come back to page if not)
  • IF webmaster is not registered:
  •   webmaster register
  •   webmaster authenticates
  •  IF initiative is not registered:
  •     webmaster adds initiative to directory
  • webmaster is back on 'add a widget page/section'
  • webmaster selects Transition Initiative (TI) from list of registered initiatives
  • webmaster selects widget type (from options of widget types in widget hierarchy)
  • system generates widget code incl. unique TI reference
  • webmaster copies code
  • webmaster logs out (or doesn't, or can just close browser window)
  • webmaster pastes code into own site's widget

Submitter submits 'Project Submission' item

  • submitter browses projects on TI site with widget
  • submitter clicks on 'add a project'
  • in TI site overlay, submitter adds data in two stages (with explano-text)
  • On step 1:
  •   IF submitter is registered user
  •    submitter logs in with TN account
  •   IF submitter is not registered user
  •    submitter is presented with form for (1) email address and (2) First and Last names (3) captcha
  • On step 2:
  •   submitter submits project submission: as per the Information Architecture description
  • On step 3:
  •   submitter gets thank you message and closes the widget window
  • project submission item is held by TN system as 'status: pending'
  • submitter receives thank you email with information about what next (TI webmaster moderates)

Moderation of Project Submission item

  • Webmaster receives email alert with project submission details and URL and 'please moderate' request
  • Webmaster follows link from email, logs into TN.org, looks in list of projects in PSE Moderation tab
  • IF webmaster approves project submission
  •    TN system deletes original project submission item and creates formal project profile node with user account set to author in TN projects directory and related widget
  •   new project profile appears in list of 'approved' projects in webmasters 'PSE moderation' list
  •    Submitter receives email alert with project node details and instructions on editing their project profile
  •    Submitter can click on links and edit project profile node
  •    Submitter receives email alert with any project node updates
  •    Project Profile node link appears in submitter's 'my content' section
  • IF webmaster rejects project submission
  •    Project submission status is set to 'rejected' and is deleted
  •    Submitter is informed by email that the project has not been approved with link to webproject email
  • IF webmaster does not check project item (TBC)
  •    project item remains unconfirmed in various views
  •    after period of time (x), webmaster receives reminder to check project item
  •    after period of time (x)x2, admin receives alert about webmaster not responding

User edits own Project item

  • User sees project item (on widget or tn.org) and wants to update it
  • User logs in from link in project item on TN.org
  • User sees 'edit' function
  • User clicks on 'edit' function
  • User can add extra information or edit existing information
  • User logs out or just moves on
  • information stored in main projects directory
  • new information presented through project item when various views updated
  • TN.org admin receives email alert 'user: [user name] has edited their Transition Project [project item title and link]'