hey @MDemosWMF has @NNichols been looped into this regarding the new fields & creating them?

Can we re-use any of the target smart ones & add new options - or do we need whole new fields?

No not yet! @NNichols since you are overseeing the civi field cleanup and streamline this may feed into your work. The new fields are listed out in the doc linked in the description above.

I'll add here what I mentioned on the re-import phab: "As far as the existing Targetsmart fields I believe when we talked earlier we realized we couldn't reuse these because the Data Axle coding was different. For example the Net Worth ranges are different but use the same letter coding. There was caution of overwriting that old data as well but perhaps archiving it somewhere?
Would it cause any issues to create all new fields? I think there was interest in creating a new tab for this data on the records for ease of viewing, but let us know your thoughts on that."

Perhaps we can all meet with Erica next week to talk it through. I'll put something on the calendar.

@Dwisehaupt did I misfile this in ops? @Eileenmcnaughton @MDemosWMF flagged that this task should be completed before T341902: Data Axle Project - Re-import to Civi

@AKanji-WMF Yes this is misfiled. As far as I can tell, this isn't something we would be leading.

Thanks! Moving back to triage so we can talk about it today.

@MDemosWMF I'm just looking to start creating these fields - it seems we have 2 'types' of fields

1. Data Axel specific - these have no existing paralel in our database
   • Degree of interest in donation (0-9)
   • Is Grandparent (yes,no)
   • is parent
   • likelihood of holding significant securities (0-9)
   • likelihood of holding significant stock (0-9)
   • number of co-habitant children
   • is single
   • is home owner
   • expendable income rank (A-O)

2. fields for which we already have data
   • net worth

So the only field which really has overlap is net worth.

There are 2 decisions to make

1. Should the DataAxle fields be added to Prospect or it's own group /tab
2. Should we create a new net_worth field or add the options to the existing field (we can create new options like 'data-axle-A' to disambiguate from our existing & make the label reflect it (e.g " B-98-99 Percentile - Net Worth Range: $8,693,520 - $13,693,439" per Data Axle) so it would only be overwritten for people with additional incoming data. -

If we are adding new fields to the prospect group it may need to happen during the maintenance week (adding fields to existing large tables can require an outage) - but ideally we are gonna add them next week either way

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

[wikimedia/fundraising/crm@master] Add new DataAxle fields

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

Hi @Eileenmcnaughton - thanks for the questions! I reviewed some of our previous notes based on past discussions and I think we had settled on the below:

1. Mark all the old TargetSmart fields with 'TS' in the name, new fields will have DA in the name to make clear DA vs TS
2. I think we should create a new DA Net worth field to go along with the rest of the new Data Axle fields - may help to keep things clear for users and make all of our updates uniform
3. Yes, I think we had landed on adding all of the new fields to the Prospect tab, thanks for coordinating this with the maintenance week!

@ERoden-WMF Please review the above and confirm if this is correct. Thanks!

@MDemosWMF I have added the (TS) to the existing fields that I believe to be targetsmart

Thanks @MDemosWMF all that sounds correct to me.

@MDemosWMF These fields are not on Staging - are you able to take a look & let me know if anything needs adjusting before we add to live - https://civicrm.frdev.wikimedia.org/civicrm/admin/custom/group/fields#/?gid=5

@Eileenmcnaughton New DA fields look good! I see the TS 401K/IRA decile is labeled, but I think we want to label the other TS fields as well. I have this list:

Income Range
Charitable Contribution Decile
Discretionary Income Range
Net worth
Occupation
Family Composition Code
IRA and 401K Decile

@mdemos - can you check which ones I labeled {TS) on live cos I didn't really label them on staging but I went through all on live

The only two I'm not sure of are:
(TS) Capacity Range
(TS) Estimated Capacity

I don't see them in the historical TargetSmart docs. The rest look good!

Change 966942 merged by jenkins-bot:

[wikimedia/fundraising/crm@master] Add new DataAxle fields

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

@MDemosWMF i took the ts back out of those 2 fields (it's just a label on live, which can be edited)

we've added the fields, now need to import https://phabricator.wikimedia.org/T341902