write an exploratory document on what transactions constitute a transfer and in what domains (discounts, travel model, etc)

[ytse17]

the lag method used here works for a specific desired outcome but it might be helpful to compare it against results from the transfer operator column tag.

https://github.com/BayAreaMetro/clpr/blob/master/R/transfers.R#L36-L46

one helpful thing to do would be to get better documentation on how the transfer_operator column works (how its assigned, rules about what constitutes a transfer, etc.)

[tbdv]

@ytse17 a good exploratory document about whether a transaction is a transfer could help us determine rules for something like #15

[tbdv]

here's a set of rules from the history of this project:

https://github.com/BayAreaMetro/clpr/blob/169fe072c9dce76371b85d20884b9c040492f10f/Transfers/transfer_rules_database.csv

[tbdv]

@ytse17 and here's where that rule book was applied: https://github.com/BayAreaMetro/clpr/blob/master/R/transfers.R#L141

[ytse17]

method using the transferoperator column:

https://github.com/ytse17/clpr/blob/transfer-operator/R/bart_transfer_operator.R