CHASERS-Donor
From Chasers_wiki
This page should contain information that is specific to the Donor Database version of CHASERS.
This page is starting from scratch, and we could use help in developing it!
Needed/Wanted Enhancements
Sent Mail Table
This is copied from Comment #12 of DESC Bug 9479, by Nicole Macri, a nice summary of how to proceed.
It seems a Direct Mail table would make the most sense. Could we join this to specific response codes, though, so we'd be able to track rates of response on each mailing sent? Re. the specific fields, here's what I suggest for a Direct Mail table: - response_code: A direct mail effort should match a response_code if applicable. - description: keep - response_coding: keep, or keep this as part of the Resp Code lookup, I'm not sure - total_design_printing_cost - postage_cost For consistency, I'm wondering if we should separate these fields out into: - Design_cost -- should include a portion of a design work used across mulitple mailings (remittance envelopes bought in bulk). - Printing_cost -- same issue as design_costs re. items used in multiple mailings - Postage_cost - Mailing_prep_cost - Staff_time_hours - donors_contacted: keep - date_sent: keep - mail_merge_file: Is this for an excel or csv file with the names/addresses? Do we want to continue to do this? Or, should we change this to "mailing_files_location"? - query: What does this mean -- do we put the SQL directly into this field? - notes: keep The Resp Code table would then only have: - response_code - description - response_coding - direct_mail_code - notes Does this make sense? Can we join these tables to figure out the returns on each mailing (how many give and how much vs. how many we sent and how much it cost? Tangentially related: The "sent_mail" table which tracks who got what mailing on an individual level. Does it make sense to keep that separate as well? If so, perhaps we join the sent_mail to both of these tables as a way to generate a list of who got a specific mailing? I'm not sure....but am open to feedback about all of this -- from both Fund Dev and I/S perspectives. Thanks.
