|
4 | 4 | # transaction-coder |
5 | 5 |
|
6 | 6 | ## Summary |
7 | | -An early R package with functions to explore monthly bank transactions data breaking them down by the type of transaction. The type of transaction is defined based upon key words (or patterns) observed in each transaction's description. |
| 7 | +An early R package with functions to explore monthly bank transactions data breaking them down by the type of transaction. The type of transaction is defined based upon key words (or patterns) observed in each transaction's description. See an [example report](https://josephcrispell.github.io/standalone/transaction_coding_report.html) you can generate to give you an idea of what you can generate. |
8 | 8 |
|
9 | 9 | ## Defining transaction types |
10 | 10 |
|
@@ -59,7 +59,23 @@ devtools::install_github("JosephCrispell/transactionCodeR") |
59 | 59 | library(basicPlotteR) |
60 | 60 | ``` |
61 | 61 |
|
62 | | -### Precommit installation (*for development*) |
| 62 | +## Building your report |
| 63 | + |
| 64 | +The [`inst/R/transaction_coding_report.Rmd`](https://github.com/JosephCrispell/transactionCodeR/blob/main/inst/R/transaction_coding_report.Rmd) Rmarkdown script represents a template report you can use to analyse your monthly bank transactions by their type. |
| 65 | + |
| 66 | +The [`inst/R/transaction_coding_report.Rmd`](https://github.com/JosephCrispell/transactionCodeR/blob/main/inst/R/transaction_coding_report.Rmd) is designed to run on dummy transaction data but can easily be modified to run on your own data: |
| 67 | +- Edit the input parameters when knitting the Rmarkdown file providing the file names for your bank transactions data and transactions types files ([more info on knitting with parameters](https://bookdown.org/yihui/rmarkdown/params-knit.html)) |
| 68 | +- Update the following lines with the correct column names and date format: https://github.com/JosephCrispell/transactionCodeR/blob/98d87143cf1f9599fb815d145a71b2785f6b6564/R/transaction_coding_report.Rmd#L26-L31 |
| 69 | + |
| 70 | +The report will automatically call the [`inst/R/process_transactions.R`](https://github.com/JosephCrispell/transactionCodeR/blob/main/inst/R/process_transactions.R) script to process the transactions data provided based upon the parameters set above. |
| 71 | + |
| 72 | +## Generating dummy data |
| 73 | + |
| 74 | +For ease of use, some [dummy bank transactions data](https://github.com/JosephCrispell/transactionCodeR/blob/main/data/dummy_transactions.csv) were generated along with a [transaction type file](dummy_transaction_coding_dictionary.csv). These were generated (and can be readily recreated using the [`inst/R/generate_dummy_data.R`](https://github.com/JosephCrispell/transactionCodeR/blob/main/inst/R/generate_dummy_data.R) script) to provide examples of the input files. |
| 75 | + |
| 76 | +While you are getting comfortable with this R package you can use these dummy data files as input, for example (as noted above) the example Rmarkdown report will by default point to these data files. |
| 77 | + |
| 78 | +## Precommit installation (*for development*) |
63 | 79 | The current repo uses a precommit continuous integration workflow. A precommit workflow triggers a set of task each time you commit any changed files. Here, the tasks mainly help with maintaining a standard coding style and spotting any minor mistakes in the code. |
64 | 80 |
|
65 | 81 | To install the workflow run the following: ([more info here](https://pre-commit.com/)): |
|
0 commit comments