Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can Transaction.date be optional? #102

Open
gordonje opened this issue Nov 17, 2017 · 1 comment
Open

Can Transaction.date be optional? #102

gordonje opened this issue Nov 17, 2017 · 1 comment

Comments

@gordonje
Copy link
Contributor

In California, campaign expenditures are reported on Schedule E of Form 460 which does not provide an obvious place for filers to report the date of a payment made. Thus, about 40% of Form 460 Schedule E Items are missing an expense date.

In the current version of the draft spec Transaction.date isn't labeled as optional, but maybe it should be?

In the draft implementation in python-opencivicdata, I'm going to allow NULLs in this field, for now.

This sort of overlaps with #98 in terms of how these decisions facilitate longitudinal analysis of transaction data.

@aepton
Copy link
Contributor

aepton commented Dec 16, 2017

Added to #104

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants