Background
As part of the donor identification project we will need to prepare a script that exports e-mail addresses and their corresponding CiviCRM
User story
As a user who has consent donor identification I want MediaWiki have awareness of how recently I last donated so that it can tailor my experience accordingly.
Requirements
- The export should not contain any duplicate rows. I defer to you on how to handle duplicates (e.g. consolidate them or discard rows based on segment priority)
- The export only transfers records that have changed since the last run
- The export can be transferred securely to a TBC machine for processing in MediaWiki
- We have finalized the expected structure of the export and its columns. It should be a CSV that is formatted such that it can consistently parsed by another script (e.g. we can ensure column 1 always corresponds to an email address and won't change 3 weeks later)
- The export should include only the donor segment number
- A decision should be made about whether to include the donors "do not solicit" field in case a future version wants to make use of this (either as a donor segment or a distinct field)
- The exported file doesn't impede us transferring information in the opposite direction in future
Out of scope
- We can assume that encryption will be handled at a later date.
- We currently do know where the file will be exported to. This will be worked out later.
- We do not need to make decisions around how the export will be used
- Optimizations - we will evaluate these later once we understand the volume and cadence we are dealing with.
BDD
- For QA engineer to fill out
Test Steps
- For QA engineer to fill out
Communication criteria - does this need an announcement or discussion?
- Add communication criteria
This task was created by Version 1.2.0 of the Web team task template using phabulous