switch to change filter

@JaneSullivan-NOAA I added a switch to change the catch filter from group code to agency code (couldn't remember if you renamed that afsc_code, nmfs_code? so left it as agency_species_code) - let me know if this takes care of the issue for your needs.

afscdata/R/queries.R

Line 9 in 320353f

    
           #' @param use_afsc_code use 3 digit species code to filter instead of species group code (default: FALSE)

stringr::str_replace() is for sure a preferred solution to having a separate query

use_afsc_code should probably be refactored... maybe use_agency_code or use_species_code instead? it's called "agency" because three digit codes are a mix of ADF&G and AKR species codes. there are two "AFSC codes", RACE and NORPAC.

@JaneSullivan-NOAA would appreciate thoughts on going toward dbplyr to keep things more in the R context - which i find easier for using functions/switches etc. this test.R function should do the same task as q_catch though it accounts for the different species inputs (group code or agency code), can add additional columns easily, and covers the other issue of fmp_area/fmp_subarea

@BenWilliams-NOAA just pulled and will test asap.
My initial thoughts: I really like that it simplifies the existing framework and is more flexible and readable. I see the utility in an intermediate step that prints, saves, or allows the user to access the translated SQL code for modification or other use. I'm also curious about speed.
Will follow up soon.

@BenWilliams-NOAA
From email exchange:... "a few bugs with area vector length and the species code data type."

Looks like you already fixed the issue with area vector length here using isTRUE()
The species code data type issue has to do with is.numeric(species)

If you input species as numeric (e.g. species = c(153, 154), you will end up with

FROM (council.comprehensive_blend_ca) "q01"
WHERE
  ("YEAR" <= 2022.0) AND
  ("FMP_SUBAREA" IN ('WG', 'CG', 'WY', 'EY', 'SE')) AND
  ("AGENCY_SPECIES_CODE" IN (153.0, 154.0))

If you input species as a character (e.g. species = c('153', '154'), you end up with

WHERE
  ("YEAR" <= 2022.0) AND
  ("FMP_SUBAREA" IN ('WG', 'CG', 'WY', 'EY', 'SE')) AND
  ("SPECIES_GROUP_CODE" IN ('153', '154'))

adjusted the statement so that it is looking for either 3 digits in the string or not
i think that takes care of this issue (thanks for looking into it!). i put a note in the @ param that the input needs to be either all 3 or all 4 digit codes