[go: up one dir, main page]

Page MenuHomePhabricator

Civi Export: What to do with the MatchingGifts file and mystery fields
Open, Needs TriagePublic

Description

The bundle of files exported to FTP every night includes a “MatchingGifts-*.csv” We don’t have a job set up that runs that file, so I think it’s just been piling up over the years. I just tried to see if I can set up a recurring job for it but I can’t because we don’t have all the columns in that file to map with and I never received a request to create those fields.

I’m also confused because the main DatabaseUpdate-* CSV has most of the MatchingGifts fields in there. Does anyone know how important it is to add the two mystery fields I found in the MatchingGifts file? If not important, can we delete the MatchingGifts file?

Fields we do have in Acoustic (already mapped with DatabaseUpdate-* file to _all_Wikimedia):
employer_id
employer_name
matching_gifts_guide_url
matching_gifts_provider_info_url
matching_gifts_online_form_url

Fields we don’t have in Acoustic at all (mystery fields):
match_policy_last_updated
minimum_gift_matched_usd

Event Timeline

EMartin added a subscriber: NNichols.

@MDemosWMF @NNichols @RKumar_WMF Can any of you chime in here? Are these fields relevant? Should they be imported?

Ok, thanks @Eileenmcnaughton . I just read the documentation and confirming on my side that those last two rows in the chart don't exist in Acoustic. We never received a request to create the columns: minimum_gift_matched_usd, match_policy_last_updated.

Who is the best person to ask if those fields are required for the matching gifts program?

Hi all, just following up. @NNichols and I chat over slack and here is more context from Nora:

"Sorry I am having some login issues with phab. The fields you're talking about for the matching gift stuff were fields that we had at one time brainstormed featuring in the automated email that goes out to donors when the use the employer field while donating. So for example if they enter Microsoft they would receive the email with a link to information about microsoft's program but we could also include information like minimum gift amount. You can see here all the fields we can have been using in the matching gift email here on page two https://docs.google.com/document/d/1042NMnPUA4mdXO5IGkEjIL0KXmzsVJ8tmcsU617Mdbk/edit"

We were able to determine that this is a future use case, and those two fields are not being leveraged right now. With that in mind, I think we should wait to export those two fields to Acoustic until after we have a clear plan in place for using them.

With that being said, this seems to solve everything for now. Since all the rest of the matching_gifts fields are in the main DatabaseUpdate-* export file, I think we are all clear to remove the MatchingGifts-* CSV from the nightly export altogether. If we need to add new matching_gifts fields in the future, we can just add them to the main export.

Is someone in fr-tech available to make that adjustment so we don't have the files piling up anymore? Thanks :)

Thanks @KHaggard ; will add to an upcoming sprint

Thanks @AKanji-WMF ! I feel like I wrote a lot in my last comment so the over-communicator in me wants to just plainly restate for clarity:

  • We only need to stop exporting the MatchingGifts-* CSV to resolve this ticket. No other work is needed at this time. :)

Thanks!

Change #1104750 had a related patch set uploaded (by Eileen; author: Eileen):

[wikimedia/fundraising/tools@master] Remove matching gifts export

https://gerrit.wikimedia.org/r/1104750

Pulled back to triage as this turns out to be a simple delete & getting rid of it is less head hurty - patch posted

Here is an image of the jobs

image.png (498×881 px, 88 KB)