To Do List

Fixes

• Ensure all translations are picked up from .po files - not just some

Tests

• What happens with the data download at a 'Campaign Action' level if related 'Action Editions' are either (1) different action types or (2) have different data schemas (i.e. extra fields)
• What happens with the data download if different 'Campaign Actions' have different schemas but all share the same data download definition?

Major Changes

• Make the tracking functionality into a separate product
• Generalise & modularise the process (i.e. as a form process) so 'actions' can be added / removed - Ability to save a 'schema' for distribution/adding as a new 'action style'
• Eliminate use of 'portal_factory' as this adds unnecessary server load overhead for higher volume actions
• Develop a centralised 'user profile' system where all action history is stored (separate product)

Usability Improvements

• Simplify set-up process (takes too long right now)
• Make set-up/management process easier to use
• Make context sensitive help/support directly accessible from the management screens
  • Allow creation of required action elements (message, thank you page+email) from the edition via set-up process (vs having to set them up before the action creation process)
  • Add a 'pass along text' content type which contains the copy and paste text provided to supporters to promote the action to others. It is by default used in the thank-you page, thank-you email and when a mass emailing system/follow-up email system is in place it by default uses it in those email as well.
  • Integrate 'content panels' (or similar functionality) on designing the action page
  • WYSIWYG eAction editing (edit sections on action page vs. from folder's view)
  • Selecting the various eAction 'configuration' elements is via drop-down list of only valid types from anywhere on the site (one doesn't have to know where they are or to navigate to them)
  • Have only one 'Action Edition' content type (vs eLetter and ePetition) and enable the 'action style' to be changed to/from ePetition/eLetter, etc.
  • On eAction setup, default ActionTarget?, ActionMessage?, ThankYou? Page, ThankYou? Email content types added and linked
  • /takeaction is default page view
  • Generate a 'content review' page/email with all/links to all the key content for someone to review without taking the action (or download it all in a single rtf/word file that can be distributed for review/signoff/translation). Where conditional content exists, it should also show the content for each condition
  • For targets, make Organisation + LastName? the content 'title (vs just name now)
  • Select/Add organisations for individual targets from individuals interface
  • Option to override (remove) portlets from action edition forms (as per 'Don't Make Me Think' book suggestions)
• Make Action Form less cluttered / more streamlined
  • Field 'Help' (description) text displayed as mouse-over link by default
  • Have field labels and fields on same line (vs one above the other) by default
  • Have a layout option to make all fields horizontal with labels in the fields (which disappear on entering them)
  • Autopopulate form based on stored values in permanent cookie
  • [DONE: 0.1.9]? HTML thank-you emails are possible (with fallback text version)

Data Exchange Improvements

• Ensure data can be stored on an SQL DB if required
• Generate the export file in XML and a zipped csv
• Enable the export to be downloaded via secure FTP with authentication
• Have option to download all data, only new data ((=not downloaded already), data from a particular date & time or from a particular country(s) or language(s)
• Data export auto-generated based on all fields in schema
• Download link at Campaign (vs Action) level to download all ActionData?
• Enable external action data to be merged (origin required, merging user logged). This would usually require at least name, email address, country and opt-in preference

Automation Improvements

• Include Effective & Expiry dates as part of set-up process (and have them trigger when an action goes live and when it ends)
• Enable the set-up of a replacement page/redirect url for when an action expires (and won't expire unless there is a replacement page/redirect url)

Process Improvements

• Enable ActionMessage? can be dynamic/conditional (i.e. ATDataMerge?) with AJAX re-load if relevant to action (change country, postal code)
• Enable ThankYou? Page and ThankYou? Email to have dynamic/conditional content (i.e. ATDataMerge?) - Conditional thank-you page pagelets (address form, etc) based on opt-in and other key fields
• ThankYou? Email content can be configured from multiple parts (template, header, footer, body-parts)
• Include new types: CopyPasteAndEmail? text and CopyPasteIntoEmailSignature? text
• 'Pagelets' for dynamic content based on cookie conditions (i.e. new/return visitor, actionlevel, action taken/not)
• Make form 'portlet' so that a sub-set of the form (name, email, country) is usable in the side panels for promoting the action
• Function to allow people to opt-in via a link after taking an action (Updates Action Record)

Flexibility Improvements

• ActionEditions? can refer to Actions anywhere on the site (don't have to be in subfolder)
• Make all actions 'discussible' using the normal Plone configuration

Data Integrity

• Integrate a robust email validation system (JS + Ajax + Server side)
• Integrate a duplicate checking (and prevention) option - Add feature to toggle the option of preventing someone from taking the same action multiple times (same=same name & email address)

Distributable Action Form Improvements: - Make postRecord so that if messagesubject, message or nexturl are missing/blank it uses the defaults (i.e. Edition URL + /thankyou) for nexturl) for the particular action (so if using URLEncoded? query string it is not too long)

Statistics Improvements

• Action statistics should differentiate between 'actions' and 'supporters' ((supporter=same name & email address)
• Enable approved users to add/upload offsite actions (offline action counts, action counts fro other sites) so that the total public reported figure includes all onsite and offsite actions taken.

Security Improvements

• [Done 0.1.9]? Ensure action-takers names aren't viewable vis the /folder_contents view in Plone 2.1+

Tracking Improvements

• Fix accuracy of 'on-site origin' to be the page a user was referred to the 'Action page' from
• Ensure tracking variables work from all browsers (not just IE, not sure if FireFox? now works)
• Add ability to pick up query string tracking codes from the referrer in cases where a click-through URL is used.
• If no tracking information is picked up (no referrer or query string), ask tracking question on thank-you page
• Add ability to do click-through tracking for use in emails and short URLs? and ensure any query-string variables from tracking codes are carried through
• Add ability to do open-tracking using 'img src' requests with uniquely identifyable url for each user
• Move tracking to its own product

Syndication Improvements

• Create 'rich' feeds of actions and/or action information for syndicating via RSS/Atom/RDF to help promote the actions.
• Syndicate action form (including using XForms?)
• Create 'ping' function to announce new action to a FairSay? server for action aggregation & re-syndication

Campaigning Improvements

• Enable people to look up 'their' politician based on post/zip code (US, UK, Canada) or in other way.
• For targets with forms (inc flash) (vs email addresses) have function to reverse engineer form so messages can be posted without use of target's form but via one's own form instead.

Integration

• Add a 'check for updates' feature to check if the eCampaigning Tool has a new version - and if so what the improvements are and how to get it (and service elements such as ping url, and new extensions like getDataMerge scripts, action configurations, target profiles, how-to tips, documentation updates, etc.)
• Add a 'register action' feature that 'announces' a new action/edition when it is 'launched' with a central registry (url plus other action attributes). The Action Registry will be part of the 'Aggregator/Benchmarking' tool (under development)
• Add a 'share statistics' feature to post statistics to a central 'Benchmarking Tool' (under development)

Other Improvements

• Have a fixed action page url with dynamic page content (vs dynamic urls with factor_portal with fixed page content as it is now)
• Consider a 'testing' mode which sends emails to and from an address specified by the tester. It confirms the success of the test by logging into an email account and looking for the than-you and target emails (as appropriate). It also pre-fills the form with test data so each test is unique. When ending the test mode it deletes all test data ('Action Records')
• Add this to-do list to a issue management system & then classify & prioritise each item plus break it down into more specific technical details
• Add the ability for a 'parent action' to be a URL to a 'parent action' on another Plone site (and this might automate some exchange of statistics or something) or non-Plone site. Useful mainly for coalitions, grassroots activities or decentralised organisations (national, international)