This just requires co-ordination with Katie to update the field mapping
Description
Description
Details
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Stop exporting voter_party | wikimedia/fundraising/tools | master | +2 -19 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Restricted Task | |||||
| Resolved | Ejegg | T304357 Remove voter party field from acoustic export |
Event Timeline
Comment Actions
Change 772459 had a related patch set uploaded (by Ejegg; author: Ejegg):
[wikimedia/fundraising/tools@master] Stop exporting voter_party
Comment Actions
@Ejegg @KHaggard it looks like the voter party field is the very last field in the csv so won't require any change in the order of fields that are uploaded - perhaps @KHaggard can just go ahead & unmap the field before we even stop sending it? Otherwise it is merged & just deployment needs to be co-ordinated
Comment Actions
Change 772459 merged by jenkins-bot:
[wikimedia/fundraising/tools@master] Stop exporting voter_party
Comment Actions
Thanks @Eileenmcnaughton - I still rely on the nightly imports to "unmap" a field, but it's true that I can just pause the next scheduled import job and run it manually after mapping and choosing to ignore the voter party field. I can give that a try tomorrow morning.
Comment Actions
Whoops @Eileenmcnaughton I overlooked that we have sends going out tomorrow - I can remap w/ignoring voter party starting on my Wednesday morning instead.
Comment Actions
Sorry, one last update here @Eileenmcnaughton (@TSkaff for visibility). I see we added another Planned Giving email send to the calendar on Wednesday, so the soonest I will be able to initiate a remapping is Friday the 25th when we have no emails scheduled to send. Hope that's ok for the timeline here.
Comment Actions
Ok @Eileenmcnaughton I've remapped the files today and ignored the voter_party field. Things should be working fine over the weekend but I'll update again on Monday to make sure the imports are processing successfully. Have a great weekend!
Comment Actions
Hello @Eileenmcnaughton ! Updating here that the imports ran successfully over the weekend. Acoustic now ignores the voter_party field sent from Civi. I'm working with Trilogy on deleting the field from Acoustic, but it no longer has any data and it is not tied with Civi anymore.
Comment Actions
Hello @Eileenmcnaughton ! Updating here that the imports ran successfully over the weekend. Acoustic now ignores the voter_party field sent from Civi. I'm working with Trilogy on deleting the field from Acoustic, but it no longer has any data and it is not tied with Civi anymore.
Comment Actions
Hi @Eileenmcnaughton !
@Ejegg and I learned today that ignoring a field in Acoustic remapping will not stick if the export stops sending a field. Noted this for next time! Guess we'll always have to "push go" at the same time going forward for these tasks. Resolving this task since we've properly remapped and all is well. Thanks!
Comment Actions
AH well - I wouldn't have even tried if it hadn't been the very last field
in the mapping...
Comment Actions
Looks like it's mapped as TS_voter_party which is sorted before email
because T is a lower ASCII codepoint than e