Discussion Request: Modify our Schema naming strategy

[brendagutman]

Is your feature request related to a problem? Please describe

I want to discuss this topic prior to making any changes to an ADR.

I would like us to confirm that devs will make use of the qa environment as well. I am assuming that validation of the cross-project access model data will be up to the devs. If our dev environment schema are created on a developer level(example 1) we will not be able to cross check our harmonizations with other studies.

If we don't want the devs to use the qa environment to test study integration. We could change the schema naming convention for the cross-project schema using the generate_schema_name macro to enable this. We would want to make sure the harmonizers are not working on the cross-project models at the same time, but I don't see that being a huge problem.

- bg_dev_inc_brainpower_src
- aw_dev_kf_chr_18_src
...
- bg_dev_combined
- aw_dev_combined
....
- bg_dev_access
- aw_dev_access
...
- bg_dev_fhir_export
- bg_dev_fhir_export

VS

- bg_dev_inc_brainpower_src
- aw_dev_kf_chr_18_src
...
- dev_combined
- dev_access
- dev_fhir_export

Describe the solution you'd like

I would like devs(harmonizers) to validate their work with cross-project data within the dev environment.

I would like a non-dev to validate the data in the qa environment.

Describe alternatives you've considered

No response

Additional Context

No response