Closed pjsier closed 7 years ago
@cecilia-donnelly I fixed the stage
attribute for the export, and as for the first column being wide I think we could potentially split that header into two columns. Maybe something like Exported on: 2017-11-08,Search terms: search_for = participant
. It'll still be a bit wide, but not quite as bad. Does that work?
Thanks! And yes, can we try that? It sounds like it would be an improvement.
@cecilia-donnelly Just updated! Let me know if that works
Fixes #331
Adding ID is straightforward, but the query for leadership stage is now updated to use the through model
LeadershipGrowth
because it tracks the time. This is assuming that the export will pull the latest leadership stage, and not necessarily the one that was most recent for the last date of the query. Converting the prefetched queryset to a list, because sorting it directly will trigger another DB call for each rowI realized I'm not entirely sure from the issue whether DATE is the date of the export or something passed in the query, but I can update it if this doesn't work. Also, this should be merged before #325 now that the CSV import is going to be partially based off of exports