add content_area and topic_tags to dim_course_structure

[jordan-springer]

Description

Bringing in content_area and topic_tags from scripts data to expose in dim_course_structure

• dataops-1054

Additionally, added backup file for course_structure rosetta procedure to deploy in redshift

• dataops-1055

Links

Jira ticket(s): DATAOPS-1054

Testing story

• Does your change include appropriate tests on key columns?
  eg.
  - not_null
  - unique
  - `dbt_utils.unique_combination_of_columns: , ["value","value","value"...]

Note: when submitting a new model for review please make sure the following have been tested:

1. The model compiles (dbt build -m 'your_model')
   or: has the dbt Cloud job succeeded?
2. The model runs (dbt run -m 'your_model')
3. The model produces accessible data in the DW (select 1 from 'your_model')

Privacy

• 1. Does this change involve the collection, use, or sharing of new Personal Data?
• 2. Do these data exist in the appropriate schema(s)?
• 3. Does this change involve a new or changed use or sharing of existing Personal Data?
• 4. Consider: will this data be visible on Tableau? will this data be surfaced in a report exported from Trevor?
• 5. If yes to any of the above, please list the models, columns, and justification below:
  i.
  ii.
  iii.

PR Checklist:

--> Note: if these are not all checked, the PR will be sent back.

• Tests provide adequate coverage
• Privacy and Security impacts have been assessed
• Code adheres to style guide👀 and is DRY
• Code is well-commented (**please do not leave extraneous commentary in model code, if it is for the purpose of documentation, please relocate accordingly)
• Appropriate documentation has been provided (see .yml., did dbt docs generate succeed?)
• New features are translatable or updates will not break up/downstream models
• Relevant documentation has been added or updated (i.e. dbt docs has been updated successfully on Github Pages
• Pull Request is labeled appropriately (eg. chore/, feature/, fix/)
• Follow-up work items (including potential tech debt) are tracked and linked (if applicable)

[nataliazm99]

I haven't finished reviewing but the 'old' code for analysis.rosetta looks very different, looks like a version previous to the existing one, which makes it hard to review and also makes me worry that we might be missing something that has been changed since. Jordan, can you take a look at that?

[nataliazm99]

proposing a change to the student_course_names cte:

student_course_names as (
    select distinct course_name
    from {{ ref('stg_dashboard__scripts') }}
    where participant_audience = 'student'
    and content_area ilike '%curriculum'
),