Open gordonje opened 6 years ago
Added this to https://github.com/opencivicdata/docs.opencivicdata.org/pull/104 - added an optional is_rejected boolean to the amount field, and explained in the description not to use that field if you're setting transaction values to negative for returned contribs, etc.
California campaign finance committees are required to itemize returned contributions on the same schedule that includes received contributions. The real world situation would be something like:
In our source data, we have a line item for the original contribution and another with a negative amount for the returned contribution:
In mapping these records to the
Transaction
model, my initial thought was to flip the sender and receiver and take the absolute value of the amount. So the above source records would become:However, @palewire and I discussed further and decided against this approach. We're worried about the potential for inaccuracies when summing the amount field. Instead, we're planning to leave the source values more or less unchanged in loading the
Transaction
model:Have others seen similar use cases in other jurisdictions and, if so, does our approach for fitting it into our shared models make sense?
If we agree this is proper use, then we might expand the description on
Transaction.amount
to say that negative numbers are allowed and why.