rcc.billing
Automated, data-driven service billing implemented on REDCap Custodian
Science Score: 57.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
○CITATION.cff file
-
✓codemeta.json file
Found codemeta.json file -
✓.zenodo.json file
Found .zenodo.json file -
✓DOI references
Found 1 DOI reference(s) in README -
✓Academic publication links
Links to: zenodo.org -
○Academic email domains
-
✓Institutional organization owner
Organization ctsit has institutional domain (www.ctsi.ufl.edu) -
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (5.4%) to scientific vocabulary
Keywords
Repository
Automated, data-driven service billing implemented on REDCap Custodian
Basic Info
- Host: GitHub
- Owner: ctsit
- License: apache-2.0
- Language: R
- Default Branch: main
- Homepage: https://ctsit.github.io/rcc.billing/
- Size: 11.4 MB
Statistics
- Stars: 0
- Watchers: 2
- Forks: 3
- Open Issues: 19
- Releases: 2
Topics
Metadata Files
README.md
REDCap Automated Billing
REDCap Automated Billing is an automated, data-driven service billing system for a REDCap system. The University of Florida’s CTS-IT designed and wrote this system to charge a modest annual fee for each project and bill for customer support work logged in a REDCap-based service request system. This generates revenue, reduces data privacy risks by incentivizing the deletion of abandoned projects, and improves the quality of research productivity metrics.
Motivation
- Generate revenue to offset costs and improve service.
- Reduce data exposure risk via deletion of unneeded things.
- Improve the quality of metrics by not counting junk projects.
- Reduce support staff workload.
What we learned
- We can make money by charging for REDCap services.
- Charges are a tool to incentivize customer behavior.
- Good people data and project ownership data are required.
- There is no such thing as over-communication.
- Partner with your fiscal team.
- Use an incremental and iterative approach.
- Automate everything.
Novel Concepts
REDCap Automated Billing introduces some concepts outside the normal scope of a REDCap system. These are described in Novel Concepts
Billing for support work
The complexities of billing for REDCap support work are described in Billing for REDCap support work
Business workflows
Cleaning person data
Cleaning ownership data
- cleanupprojectownership_table
- Ban accounts/emails of people who left your institution. See updateinvoicelineitemswithinvoicingdetails
Exempt special people and special projects from billing
Manage abandoned projects
Create & Manage charging records
- createandsendnewinvoicelineitems
- updateinvoicelineitemswithinvoicingdetails
- sequesterunpaidprojects
- cancelinvoiceline_items (Ad hoc)
Manage organizational data
- writeuffiscalorgstoorghierarchies (temporarily disabled)
- writeuffiscalorgstopersonorg (temporarily disabled)
Manage pro bono service request work
Internal reporting
Manage customer communications
When jobs run
Most ETLs and reports are run in a regular basis via Cron. The schedule of those events can be found at When jobs run
Owner
- Name: CTS-IT
- Login: ctsit
- Kind: organization
- Location: 2401 Archer Road Gainesville, FL 32608
- Website: https://www.ctsi.ufl.edu/research/study-design-and-analysis/informatics-consulting/
- Repositories: 160
- Profile: https://github.com/ctsit
Clinical and Translational Science Informatics and Technology, University of Florida
GitHub Events
Total
- Issues event: 26
- Issue comment event: 23
- Push event: 55
- Pull request review comment event: 6
- Pull request review event: 11
- Pull request event: 20
- Create event: 15
Last Year
- Issues event: 26
- Issue comment event: 23
- Push event: 55
- Pull request review comment event: 6
- Pull request review event: 11
- Pull request event: 20
- Create event: 15
Issues and Pull Requests
Last synced: 6 months ago
All Time
- Total issues: 105
- Total pull requests: 89
- Average time to close issues: about 2 months
- Average time to close pull requests: 6 days
- Total issue authors: 5
- Total pull request authors: 5
- Average comments per issue: 1.46
- Average comments per pull request: 0.8
- Merged pull requests: 85
- Bot issues: 0
- Bot pull requests: 0
Past Year
- Issues: 14
- Pull requests: 12
- Average time to close issues: 26 days
- Average time to close pull requests: 10 days
- Issue authors: 2
- Pull request authors: 3
- Average comments per issue: 0.36
- Average comments per pull request: 0.5
- Merged pull requests: 10
- Bot issues: 0
- Bot pull requests: 0
Top Authors
Issue Authors
- pbchase (101)
- ChemiKyle (1)
- ljwoodley (1)
- MichaelChirico (1)
- michael-bentz (1)
Pull Request Authors
- pbchase (46)
- ChemiKyle (17)
- michael-bentz (9)
- saipavan10-git (9)
- ljwoodley (9)
Top Labels
Issue Labels
Pull Request Labels
Dependencies
- JamesIves/github-pages-deploy-action v4.5.0 composite
- actions/checkout v4 composite
- r-lib/actions/setup-pandoc v2 composite
- r-lib/actions/setup-r v2 composite
- r-lib/actions/setup-r-dependencies v2 composite
- actions/checkout v2 composite
- R >= 3.5.0 depends
- DBI * imports
- RMariaDB * imports
- bit64 * imports
- dplyr * imports
- jsonlite * imports
- lubridate * imports
- readr * imports
- rlang * imports
- stringr * imports
- tidyr * imports
- writexl * imports
- DiagrammeR * suggests
- RSQLite * suggests
- digest * suggests
- duckdb * suggests
- fs * suggests
- knitr * suggests
- purrr * suggests
- rmarkdown * suggests
- testthat * suggests
- redcapcustodian latest build