Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Bold views are final views
Italic views are cached

  • Box

  • Denodo VDP

    • student_lifecycle

      • 01-base_layer

        • 01-connections

          • slate

            • ds_slate_tuf_application

            • ds_slate_tuf_person

            • ds_slate_tuh_application

            • ds_slate_tuh_person

            • ds_slate_tup_application

            • ds_slate_tup_person

            • ds_slate_tuv_application

            • ds_slate_tuv_person

            • ds_box_slate_race_release_dates

        • 02-base_views

          • slate

            • bv_slate_tuf_application

            • bv_slate_tuf_person

            • bv_slate_tuh_application

            • bv_slate_tuh_person

            • bv_slate_tup_application

            • bv_slate_tup_person

            • bv_slate_tuv_application

            • bv_slate_tuv_person

            • bv_box_slate_race_release_dates

      • 02-transformation

        • slate

          • agg_slate_person_max_race_release_date

          • p_slate_person

          • p_slate_application

      • 03-integration

        • slate

          • u_slate_person

          • u_slate_application

      • 04-interface_fulfillment

        • slate

          • slate_person

          • slate_application

  • Denodo Scheduler

    • slate-union-views-cache (runs daily at 2AM)

...

Deans should not be able to see race data for a current or future application cycle in order to prevent intervention in applications based on raced. To prevent this, a race release date (term start date) is associated with each application based on the school and application term. These dates are currently defined in the race-release-dates sheet in the Box spreadsheet linked above. The max race release date is calculated for each person based on their applications and if this date is in the future, their race data values are set to null.

...