Release Notes
      Back to home
      1. Clarity Human Services Help Center
      2. Data Analysis
      3. Release Notes

      Data Analysis Release Notes 8/21/2023

      Release Notes Summary

      General Notes:

      The changes outlined here will be released to Looker training instances on 8/7/23 and production and migration instances on 8/21/23. There may be changes to this article until the release date. 

      We will be upgrading Looker to version 23.12 during the maintenance window on  08/13/2023. Review Looker’s changelog for details.

      2024 HUD Data Standards

      As we are working to make the updates needed in Looker for the 2024 Data Standards we are aware that there are many changes that will affect existing looks and dashboards and cause breakage. We are working to put together information that will help identify content that will break and provide guidance around making updates. We plan to send out this information early in September.

      We are also working to identify where we are able to make automatic updates and there will be more information on this to come. Updates to content cannot be made until after the changes go live on 10/1.

      LookML Dashboards:

      • Removed the following retired dashboards: Clarity Usage and System Stats, Recidivism - Returns to Homelessness, Data Quality Dashboard - (Data Quality Summary Dashboard)

      Coordinated Entry Model:

      • An update was made in the Coordinated Entry model to remove obsolete code. No functionality visible to users was affected. 

      Client Model:

      •  Label changes for “Programs:Availability Start Date” and “Programs: Availability End Date”. 
      • An update was made in the Client model to remove obsolete code. No functionality visible to users was affected. 

      HMIS Performance Model:

      •  Label changes for “Programs:Availability Start Date” and “Programs: Availability End Date”. 
      • An update was made in the HMIS Performance model to remove obsolete code. No functionality visible to users was affected. 

      Services Model:

      • An update was made in the Services model to remove obsolete code. No functionality visible to users was affected. 

      Project Descriptor Model:

      •  Label changes for “Programs:Availability Start Date” and “Programs: Availability End Date”. 

      Data Quality Model:

      •  Label changes for “Programs:Availability Start Date” and “Programs: Availability End Date”. 

      Reservations Model: 

      •  Label changes for “Programs:Availability Start Date” and “Programs: Availability End Date”. 

      Inventory Model:

      • Added One new field, “Is Current Unit Status”.

      Outreach Model:

      • Added four new Client Demographics fields.
      • Added Geolocation Information Date field to the Geolocations View.
      • Added "Is Latest Geolocation (Per Client)"  Field to the Geolocations View. 
      • A new dimension labeled "Geolocation Individual/Encampment" has been added to the "Outreach" model under the section "Geolocations". 

      Detailed Notes: 

      LookML Dashboards:

      • Removed the following retired dashboards:
        • Clarity Usage and System Stats,
        • Recidivism - Returns to Homelessness,
        • Data Quality Dashboard - (Data Quality Summary Dashboard). 

      Coordinated Entry Model: 

      • An update was made in the Coordinated Entry model to remove obsolete code. No functionality visible to users was affected. 

      Client Model:

      The labels for the fields “Availability Start Date” (programs.availability_start_date) and “Availability End Date” (programs.availability_end_date) have been changed to “Operating Start Date” (programs.availability_start_date) and “Operating End Date” (programs.availability_end_date) to better align with the HUD Data Dictionary. 

      • An update was made in the Client model to remove obsolete code. No functionality visible to users was affected. 

      Changed Fields 

      • “Programs:Availability Start Date” -> “Programs:Operating Start Date” (programs.availability_start_date)
      • “Programs:Availability End Date” -> “Programs:Operating End Date” (programs.availability_end_date)

      Required Actions: 

       Update any downstream uses of content that rely on the labels “Availability Start Date” and “Availability End Date”. 

      HMIS Performance Model:

      The labels for the fields “Availability Start Date” (programs.availability_start_date) and “Availability End Date” (programs.availability_end_date) have been changed to “Operating Start Date” (programs.availability_start_date) and “Operating End Date” (programs.availability_end_date) to better align with the HUD Data Dictionary. 

      An update was made in the Client model to remove obsolete code. No functionality visible to users was affected. 

      Changed Fields

      • “Programs:Availability Start Date” -> “Programs:Operating Start Date” (programs.availability_start_date)
      • “Programs:Availability End Date” -> “Programs:Operating End Date" (programs.availability_end_date)

      Required Actions: 

       Update any downstream uses of content that rely on the labels “Availability Start Date” and “Availability End Date”. 

      Services Model: 

      • An update was made in the Services model to remove obsolete code. No functionality visible to users was affected. 

      Project Descriptor Model:

      The labels for the fields “Availability Start Date” (programs.availability_start_date) and “Availability End Date” (programs.availability_end_date) have been changed to “Operating Start Date” (programs.availability_start_date) and “Operating End Date” (programs.availability_end_date) to better align with the HUD Data Dictionary. 

      Changed 

      • “Programs:Availability Start Date” -> “Programs:Operating Start Date” (programs.availability_start_date)
      • “Programs:Availability End Date” -> “Programs: Operating End Date” (programs.availability_end_date)

      Required Actions: 

       Update any downstream uses of content that rely on the labels “Availability Start Date” and “Availability End Date”. 

      Data Quality Model:

      The labels for the fields “Availability Start Date” (programs.availability_start_date) and “Availability End Date” (programs.availability_end_date) have been changed to “Operating Start Date” (programs.availability_start_date) and “Operating End Date” (programs.availability_end_date) to better align with the HUD Data Dictionary. 

      Changed Fields

      • “Programs:Availability Start Date” -> “Programs:Operating Start Date” (programs.availability_start_date)
      • “Programs:Availability End Date” -> “Programs:Operating End Date” (programs.availability_end_date)

      Required Actions: 

       Update any downstream uses of content that rely on the labels “Availability Start Date” and “Availability End Date”. 

      Reservations Model:

      The labels for the fields “Availability Start Date” (programs.availability_start_date) and “Availability End Date” (programs.availability_end_date) have been changed to “Operating Start Date” (programs.availability_start_date) and “Operating End Date” (programs.availability_end_date) to better align with the HUD Data Dictionary. 

      Changed Fields

      • “Programs:Availability Start Date” -> “Programs:Operating Start Date” (programs.availability_start_date)
      • “Programs:Availability End Date” -> “Programs:Availability End Date” (programs.availability_end_date)

      Required Actions: 

       Update any downstream uses of content that rely on the labels “Availability Start Date” and “Availability End Date”. 

      Inventory Model:

      Added the 'Is Current Unit Status' field to the “Unit Status” View of the Inventory model. This field returns “Yes” if the end date of a unit status is in the future, is the same as the date the report is run, or is null. The field returns “No” if a unit status has an end date that is earlier than the current date. 

      New Field

      • Field name: unit_status.current_unit_status, Location: “Unit Status:Is Current Unit Status” 

      Required Actions: 

      None

      Outreach Model:

      Four new demographic fields are available in the Outreach model.  “Race”, “Ethnicity, “Veteran Status”, and “Gender” are now exposed in the “Clients” view.

      A new datetime field “Information Date” has been added to the “Geolocations” view in the “Outreach” model, indicating the information date. The Information Date may be different from the Added Date.

       A new yes/no field "Is Latest Per Client" has been added to the Geolocations view. This field will return yes if a geolocation is a client's most recent recorded geolocation in the system.

      A new dimension labeled "Geolocation Individual/Encampment" has been added to the "Outreach" model under the section "Geolocations". This dimension shows "Individual" when the client geo-location is not linked with an active Encampment, or shows "Encampment" when the client geolocation is linked with an active Encampment.

      New Fields:

      • Field Name: “Clients:Race” (client_demographics.race_text)
      • Field Name: “Clients:Ethnicity” (client_demographics.ethnicity_text)
      • Field Name: “Clients:Veteran Information:Veteran Status” (client_demographics.veteran_text) 
      • Field Name: “Clients:Gender” (client_demographics.gender_text)
      • Field Name: "Geolocations:Information Date" (geolocation_actuality_dates.actual_on_datetime_date)
      • Field Name: "Geolocations:Information Date:Month" (geolocation_actuality_dates.actual_on_datetime_month)
      • Field Name: "Geolocations:Information Date:Quarter" (geolocation_actuality_dates.actual_on_datetime_quarter)
      • Field Name: "Geolocations:Information Date:Year"
        (geolocation_actuality_dates.actual_on_datetime_year)
      • Field Name: "Geolocations:Information Date:Time" (geolocation_actuality_dates.actual_on_datetime_time)
      • Field Name: "Geolocations:Is Latest Geolocation: Per Client" (client_last_geolocation.is_latest_geolocation)

      Required Actions:

      None

      Upcoming Changes:

      In preparation for fields that will be retired as part of the 2024 Data Standards changes, we are deprecating some of the previously retired HUD fields. The following fields will no longer be available in Looker in our next release (not a part of the 8/21 release)

      ( Note: SOAR fields are included in "Entry Screen", "Status Update Screen", "Followup Screen" and "Update/Exit Screen" Views. To keep the notes concise, we have written the SOAR Field labels and field names, but excluded the view label names and LookML field view names from our list of fields. For example "SOAR:Decision Received" (soar_decision_received) can be found on the Entry Screen View as "Entry Screen:SOAR:Decision Received" (entry_screen.decision_received), the Status Update Screen View as "Status Update Screen:SOAR:Decision Received" (status_update_screen.decision_received), and similarly for Followup Screen and Update/Exit Screen.  ) 

      • “Hidden:BCP Status Determined” (entry_screen.rhy_bcp_is, screen_master.rhy_bcp_is)
      • "SOAR:Decision Received" (soar_decision_received)
      • "SOAR:Initial Decision" (soar_initial_decision)
      • "SOAR:Pending Status" (soar_pending_status)
      • "SOAR:Reconsideration Date" (soar_reconsideration_date)
      • "SOAR:Region" (soar_region)
      • "SOAR:Applicant had an attorney" (soar_alj_attorney)
      • "SOAR:Expedited Hearing Requested" (soar_alj-expedited_hearing)
      • "SOAR:SSA 1696 Appointment of Representative form on file" (soar_ssa_form)
      • "SOAR:Date of ALJ Hearing" (soar_alj_hearing_date)
      • "SOAR:Outcome of ALJ Review" (soar_alj_outcome)
      • "SOAR:Review on Record Requested" (soar_alj_review_req)
      • "SOAR:Appeal Filed" (soar_appeal_filed)
      • "SOAR:Protective Filing Date (consent form faxed to SSA)" (soar_consent_faxed)
      • "SOAR:Initial Decision Outcome" (soar_initial_outcome)
      • "SOAR:Medical Summary Report Submitted" (soar_med_summary)
      • "SOAR:Application NOT Submitted" (soar_not_submitted)
      • "SOAR:Reason Application was NOT Submitted" (soar_not_submitted_reason)
      • "SOAR:Outcome of Reconsideration" (soar_reconsideration_outcome)
      • "SOAR:State Disability" (soar_ssa)
      • "SOAR:SOAR Staff Initiated Appeal" (soar_staff_initiated)
      • "SOAR:SOAR Staff Initiated SSA 1696 Form" (soar_staff_ssa)
      • "SOAR:Approved for SSDI" (soar_ssdi_approved)
      • "SOAR:Appeal Filed" (soar_appeal_level)
      • "SOAR:Consultative Exam" (soar_consult_exam)
      • "SOAR:Reason Decision Not Received" (soar_decision_not_reason)
      • "SOAR:Denial Reason" (soar_denial_reason)
      • "SOAR:General-Public Assistance Reimbursement" (soar_ga_reimbursement)
      • "SOAR:Hours to Complete Claim" (soar_hours)
      • "SOAR:Medicaid Reimbursement Amount" (soar_medicaid_reimbursement)
      • "SOAR:Medical Summary Report Submitted" (soar_medicare_reimbursement)
      • "SOAR:Approved for SSI" (soar_ssi_approved)
      • "SOAR:Medical Report Cosigned" (soar_med_cosign)
      • "SOAR:Medical Records Submitted" (soar_med_records)
      • "SOAR:Quality Review Completed" (soar_quality_review)
      • "SOAR:Name of Person(s) Assisting Applicant" (soar_staff)
      • "SOAR:SOAR Trainer Status" (soar_trained)
      • "SOAR:SOAR County" (soar_county)
      • "SOAR:Date SSI Application was Submitted" (soar_ssi_app)
      • "SOAR:Date Applicant was Housed" (soar_housed)
      • “Hidden:Developmental Services” (screen_master.health_dev_disability_services)

      Required Actions: Update any content that uses the above fields. 

      Updated:  8/2/23