Create get_project_details_for_billing()

[pbchase]

Create a function, get_project_details_for_billing(). Given a redcap DB connection object and a vector of project IDs, it should return all these facts needed in a billing record:

• project_id
• app_title
• billable
• sequestered
• creation_time
• pi_last_name = coalesce(user_lastname, project_pi_lastname, lastname),
• pi_first_name = coalesce(user_firstname, project_pi_firstname, firstname),
• pi_email
• ctsi_study_id (or should something else fetch this? it is available in the REDCap DB because invoice_line_item is synch'd by update_invoice_line_items_with_invoicing_details.R)

Steal code from create_and_send_new_redcap_prod_per_project_line_items.R, line 74-119, but edit out all of the filters.

To do this, the code will need data from these tables:

• redcap.redcap_projects
• redcap.redcap_entity_project_ownership
• redcap.redcap_user_information
• redcap.invoice_line_item

[ljwoodley]

In adding ctsi_study_id I'm wondering when it was used in the anti_join instead of service_identifier? Isn't service_identifier the project_id?

https://github.com/ctsit/rcc.billing/blob/5c8c4ea781d77bbf9eefcbbe583633f01c32f8c4/etl/create_and_send_new_redcap_prod_per_project_line_items.R#L105

This anti_join will not be included in this function but I'm pointing it out on the off chance that it's a bug.

[pbchase]

Yes, that's got to be a bug. That Anti join wouldn't do anything. It doesn't harm, but it doesn't help

[ChemiKyle]

Addressed by #209