@CCogdill_WMF do we have any flexibility to feedback into header names and formatting of columns? It would be AWESOME if we could use the general import from T88836

Here's the xlsx from the other ticket showing the headers for generic import

@atgo @Ejegg we can almost certainly customize the field names to be
whatever we want them to be. I will confirm with Trilogy, but that is what
I was told when this task was initially created.

Field names and field format, I think. Right @Ejegg @awight?

@atgo I included format in my request to Trilogy as well.

Looks like this is on track. Here are our canonical templates, or the link @Ejegg sent works fine, too.

https://github.com/wikimedia/wikimedia-fundraising-crm/tree/master/sites/all/modules/offline2civicrm/templates

We want the data as a CSV.

They include some additional fields that we don't support directly, let's decide whether we want to use them or not:

• Employer
• Occupation
• Track
• Attribution
• Source alt

It's fine if they can't massage the data into our format, it's a nice to have.

These are the formatting issues I was thinking of, but for the most part their sample looks good.

• Their date format is totally fine
• contribution amounts with no currency symbols or commas are good, but it would be nice to have another column with the ISO currency code
• True/false fields correctly have 1/0 values
• "Contribution Type" and "Payment Instrument" values should correspond to values in the "Contribution Type" and "Paid By" dropdowns in the Civi contributions UI

@awight, any other format-related gotchas I missed?

@awight @Ejegg seems this isn't as easily customizable as I thought; we'll
have to pay a bit extra to change this, so it may be worth just
copy+pasting their data into our own sheet that has the correct field
names, since this will be a manual import. I think we would have the
currency code pre-filled on our template because this will be all USD.

Does the order of the columns matter at all? If not, do you see any issues
with just exporting their data as/is in the sample I gave, and changing the
column names to what Civi will read?

Oh, don't worry about that. We can use their format, we'll just write a file type module to parse it...

We can work with the data as it is, but can they please provide documentation for all the fields? I listed a few we don't support yet.

@awight documentation meaning formatting specifications? This is my first
time setting up an import, apologies for the newb questions :)

Good question. The formatting is pretty uneventful, what I'm more interested in are columns like "Source alt", can they give us some documentation explaining what each column is for?

@awight the Track, Attribution, and Source Alt fields can be ignored.
According to Trilogy, there won't be data in them anyway. I think it will
be up to @CaitVirtue if she wants to ask for Employer and Occupation on her
forms. If not, we can ignore those too.

@awight No, I don't want to ask for those two fields, so i believe they
will be blank.

Caitlin Virtue
Director of Development
Wikimedia Foundation
(415) 839-6885 x6733
cvirtue@wikimedia.org
www.wikimediafoundation.org

*Imagine a world in which every single human being can freely share in the
sum of all knowledge. That's our commitment. Donate.
https://donate.wikimedia.org/*

@CCogdill_WMF I notice the example data file doesn't have actual data in the name, address, or email columns. Would it be possible to get a sample file that has all the expected fields filled out?

Change 237864 had a related patch set uploaded (by XenoRyet):
Set up import for Major Gifts events payment/invitation tool

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

Change 237864 merged by jenkins-bot:
Set up import for Major Gifts events payment/invitation tool

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

@LeanneS - @XenoRyet just deployed the import for the events system. Can you export the data from HUB (the tool Eric gave us a demo on a few weeks ago) and do a test import into Civi? Let us know how it goes!

Thanks all. I tested the import out with the data pulled from HUB, but it resulted in a blank page and it doesn't look like it imported into Civi.

@LeanneS, if you expand the date range on Hub's export, you should see a
$500 donation Lisa/I made which will give you some actual data to import to
Civi. You can also make a few $1 test donations if you want data from the
past 7 days.

@XenoRyet - one thing we did not notice is that Trilogy has a separate
report for refunds. What is the best way to get that data in Civi? Do
refunds on Authorize.net need to be performed in Civi as well?

Sorry, to clarify, I was able to pull the data from Hub, but when I imported the donation from Lisa, the import page resulted in a blank page in Civi.

@LeanneS That's definitely not intended behavior. Can you get me a copy of the file you imported?

@CCogdill_WMF I'll start looking into the best way to handle a refund report. If you could get me a copy of that, it'll help me assess options.

@XenoRyet Thanks! If it's a bunch of extra work to handle a separate
report, I'm sure we could find a way to combine the data from both
reports... I'm guessing there won't be very many refunds for this system.

I'll send you a sample report as well, since @LeanneS is traveling today.

@CCogdill_WMF what's the volume of refunds you're expecting? This might be
a bit hard to predict, but if we have a rough sense for total transactions
maybe that could give us a start? Let's scope the refunds as a separate
task - if it's going to be small numbers, maybe we should do it by hand.
@LeanneS interested in your feedback here, too

@atgo I don't have a good sense of volume - that would be a question for
@CaitVirtue or @LeanneS. My hunch is we're talking about ~20 refunds total
for this event, and that it isn't worth extra work to set up a new import.

I'd be surprised if it was even that many. I was thinking on the order of 1 or 2. I don't think we did any last year.

@atgo @CCogdill_WMF

I agree with scoping the refunds as its own task. I'll be able to estimate it once I see that refunds file. There's a chance it's easy, but manual still may be the best option.

In the mean time I'll work on running down that bug @LeanneS found.

@CCogdill_WMF

The bug should be fixed now, @LeanneS can give it another go whenever she's available, or if you'd like I can try importing the file @LeanneS sent onto production right now.

@XenoRyet if you're confident, let's just wait for @LeanneS to do it, since
she'll be performing the task normally. Thanks!

@CCogdill_WMF, I am confident, we'll wait for @LeanneS

Thanks, @XenoRyet! The file imported successfully for me this time.

We can also proceed with refunding manually given the low volume.

Great, sounds like everything is in order. I'll close the ticket.

@XenoRyet we just have one follow up: We'd like to disable the automated email receipt upon import as they will already be receiving one from the Trilogy site. Can you please remove this feature from the Trilogy import function?

@LeanneS That's fairly straightforward to accomplish. I can do that.

@atgo This is a quick change, but it is in the code, so it'd have to go through review and deploy again. Should I reopen this task or should there be a new one?

Seems like a good @DStrine question - I agree that it should be resolved
ASAP though.

Good call on bringing in @DStrine. It really will be quick. I can get it ready for review before standup tomorrow, just unsure of how we should track it.

That change feels like it is part of the original task. Other team members have pulled things in and out of Done before as they needed.

Cool, I'll handle it that way then.

Change 240146 had a related patch set uploaded (by XenoRyet):
Set no_thank_you for Major Gifts importer

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

Change 240146 merged by Ejegg:
Set no_thank_you for Major Gifts importer

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

@CCogdill_WMF @LeanneS

Requested change has been deployed. Go ahead and take a look, let me know if it looks good to you.

@XenoRyet I just tested using my email and didn't receive any receipt, so we should be all set. Thanks!