Review Notes

These notes are based on my (Dave Greenberg) review of the mockups and partial ERD attached to this document - as of 4/16/2008.

Notes on the Mockups

What are the downstream results of picking a method (e.g. "Raise money by ... Sports") and a related sub-method (e.g. "Marathon")? Is the idea that this would somehow automatically provide content for the resulting fund-raising page? Might consider dropping this part of the configuration process and just have free-form description of the activity by the fund-raiser (more flexible and much simpler to present the interface w/o all the structured and conditional options). A fixed set of other properties (fundraising start, duration, end dates) - rather than properties that change cased on "method" would also simplify things.

Not clear on the flow from "Raise money through an event.." and then pick an existing FPWR event. Wouldn't it make more sense to show me existing events first - then ask what type of event I want if I decide NOT to hook up w/ an existing event (i.e. decide to create a new event).

When do they set the properties shown on "Edit your fundraising page" during the "create fundraising page" flow? (e.g. Personal Message, Image(s), Supporter Display, etc.)

Intro message for user (from the NPO) - e.g. "Thank you for supporting FPWR by raising
money on our behalf..."

Options / text for "How do you want to raise money..." page. Are these fund-raising "methods" fixed / hard-coded?

Step 3 - Form for "Raise money through...". Does each of the fund-raising "methods" have a fixed / hard-coded set of properties (form fields)? Example, "sports" method has sport_type ("Marathon", "Walk-run", etc.) and event_date.

Why are "Sponsor Me Now" buttons on this page? Also, "Give me a page like this" seems odd (since this screen is for the fundraiser who has a / this page."

Why is "add images" on the "summary" page (p 10 in mockups) rather than "Edit your fundraising page" ? Where will images go?

Does "Sponsor me now" link to a "regular" CiviContribute Online Contribution Page - and pass in a parameter which specifies the referring personal contrib page? A data property linking the actual contribution record back to the personal fundraising page will be needed.

Assuming above is the proposed flow, will the fund-raiser pick from a selection of existing contribution pages to link to? Or will the CiviCRM admin create and designate a particular online contribution page for all personal fundraising pages? Or will the link to "Get your own personal fundraising page" be encoded w/ the "parent" contribution page (this seems like a decent and flexible approach).

It seems like this is an optional property of these pages?? The main "connection points" I see is that the event sets the "Event Name" and "Start Date" properties on the fundraising page. AND, given that the linked event_id is stored with the personal page record - it will be possible to aggregate contributions raised by personal fundraisers for a given event.

Are there other "connection points"? Does the fund-raiser need to be a registered participant in the linked event? What's the intended usage for the fpwr_event_template table?

I don't see where many of the personal contribution page properties are stored in the ERD:
- fundraising dates: start_date, duration, end_date ...
- several properties set in "Edit your fundraising page" form - Personal Message, Donation Confirmation text, Image(s) for page
- selected fund-raising method (e.g. 'Sports', 'Celebration', ...)
- selected sub_method or description (these seem like they might be option value ID's e.g. 'Trek', 'Cycling' etc for 'Sports'; or just text e.g. challenge description for 'Personal Challenge')

Contributions resulting from a given fundraising page need to be "marked" for page-level listings and aggregation, search, etc. One option is to add fundraising_page_id to civicrm_contribution table? Or given the potential usefulness of a more structured "source" property for contributions - we could add source_entity_table (civicrm_fundraising_page) and source_entity_id (fundraising_page_id).

Depending on how much of the "configure your fundraising page" wizard flow is configurable - we may need data stores for these (e.g. fundraising methods, sub-method options, etc.). Some aspects (like all the text on these pages) may best be handled by a set of default templates which can be customized by the organization. Some things ( could potentially be handled by a custom field group(s) "used for" personal fundraising pages. ??

Suggested table name: civicrm_fundraising_page instead of fpwr_contribution_pages
CiviCRM column naming convention uses is_xxxx for booleans (e.g. is_show_contributor_name)
offline_contribution_amount - intended usage ??
fpwr_event_template table - intended usage??