Add factor levels to redcap_events col

[rsh52]

Description

This PR seeks to add factor levels and their associated order to the event names and their associated labels when available in the redcap_events column of the supertibble. It does not change how redcap_event appears in the data tibbles of the supertibble, which I think is fine since it should represent the REDCapR output. Users can easily get the level order from the redcap_events column of the supertibble with this branch's setup and it will serve my use case for REDCapExploreR.

Proposed Changes

List changes below in bullet format:

• Add forcats to DESCRIPTION to make use of fct_inorder()
• Update link_arms() to establish and assign factor levels and orders
• Update add_event_mapping() to use link_arms() output and assign factor levels and order
• Update associated tests

Issue Addressed

Closes #210

PR Checklist

Before submitting this PR, please check and verify below that the submission meets the below criteria:

• New/revised functions have associated tests
• New/revised functions that update downstream outputs have associated static testing files (.RDS) updated under inst/testdata/create_test_data.R
• New/revised functions use appropriate naming conventions
• New/revised functions don't repeat code
• Code changes are less than 250 lines total
• Issues linked to the PR using GitHub's list of keywords
• The appropriate reviewer is assigned to the PR
• The appropriate developers are assigned to the PR
• Pre-release package version incremented using usethis::use_version()

Code Review

This section to be used by the reviewer and developers during Code Review after PR submission

Code Review Checklist

• I checked that new files follow naming conventions and are in the right place
• I checked that documentation is complete, clear, and without typos
• I added/edited comments to explain "why" not "how"
• I checked that all new variable and function names follow naming conventions
• I checked that new tests have been written for key business logic and/or bugs that this PR fixes
• I checked that new tests address important edge cases

---

• To see the specific tasks where the Asana app for GitHub is being used, see below:
  • https://app.asana.com/0/0/1208692068485305

[ezraporter]

One tiny suggestion but looks good overall!

[ezraporter]

I would actually not make this ordered. We don't really know if the events in an arbitrary REDCap have meaningful order and using a plain factor will still preserve the order if they are meaningful.

[rsh52]

Well, for my purposes downstream in record_status_dashboard() creation I wanted to capture info on the order that events appear in the display. There's no real assumptions (to my knowledge) I can make otherwise when just accepting the supertibble. I believe the order that events come out resembles how they're ordered in the UI.

[rsh52]

Confirmed this will work using Prodigy as an example.

> db$redcap_events[[1]]
# A tibble: 1 × 5
  redcap_event      event_name        redcap_arm arm_name repeat_type 
  <ord>             <fct>             <chr>      <chr>    <chr>       
1 infusion_sequence Infusion Sequence 1          Arm 1    nonrepeating
> db$redcap_events[[1]]$event_name
[1] Infusion Sequence
23 Levels: Infusion Sequence Screening & Enrollment Manufacturing LD Chemo Pre-Infusion Infusion 1 Day Follow-Up ... Safety/Meds
> db$redcap_events[[1]]$event_name %>% levels()
 [1] "Infusion Sequence"      "Screening & Enrollment" "Manufacturing"          "LD Chemo"               "Pre-Infusion"          
 [6] "Infusion"               "1 Day Follow-Up"        "3 Day Follow-Up"        "7 Day Follow-Up"        "10 Day Follow-Up"      
[11] "14 Day Follow-Up"       "21 Day Follow-Up"       "28 Day Follow-Up"       "2 Month Follow-Up"      "3 Month Follow-Up"     
[16] "4 Month Follow-Up"      "5 Month Follow-Up"      "6 Month Follow-Up"      "9 Month Follow-Up"      "12 Month Follow-Up"    
[21] "Unscheduled"            "End of Study"           "Safety/Meds"