Background
Following the outcome of T416948: CiviCRM should export a CSV that can be used in a MediaWiki maintenance script and T416949: Implement the first pass of a maintenance script that supports preference updates for consenting donors we'll need to work with SRE to connect the two by finding a machine that CivicCRM can scp a CSV file to, and how a MediaWiki maintenance script can process the results for updates in the MediaWiki preferences database.
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
- We understand where the solution will live and how CiviCRM will export to it
- We have decided what level of encryption is needed for the transfer (if any)
- We have sent a dry run test (using test data with our own email addresses/donation records) that proves the solution works end to end.
BDD
- For QA engineer to fill out
Test Steps
- For QA engineer to fill out
Design
- Add mockups and design requirements
Acceptance criteria
- Add acceptance criteria
Communication criteria - does this need an announcement or discussion?
- Add communication criteria
Rollback plan
- What is the rollback plan in production for this task if something goes wrong?
This task was created by Version 1.2.0 of the Web team task template using phabulous