I very much support this request. My sense is that it entails a number of more specific requirements and use cases. Here are the two main ones that brought me here:

1. In building Looker reports, I want to be sure I understand the behavior of derived tables and related filters, dimensions, and measures. In my mind, this requires knowledge of which Clarity fields are being referenced, the LookML object type/derivation method, and the overall table structure of the given Looker model -- as all of these impact how the derived table interacts with the Looker filter context. My hope is that having access to the LookerML or SQL definitions of the derived tables would provide some insight into these factors.

2. Our community has access to the Looker SQL model. I very much appreciate the existing documentation (help article [https://help.bitfocus.com/customer-sql-data-model] and gitlab repository [https://gitlab.com/bitfocus-public/clarity_custom_sql_model]) and would like to see these updated and expanded. For the gitlab repo, specifically, I would like to see an update to reflect the 2024 HMIS Data Standards, a folder that contains SQL definitions for all tables, and more comprehensive documentation on how the tables are related with the consideration of an audience that's likely most familiar with HMIS HUD CSV structure [https://files.hudexchange.info/resources/documents/HMIS-CSV-Format-Specifications-2024.pdf]. Some of the sample queries presented in the gitlab repo already include table definition and have comments that indicate the mapping to HMIS elements, which is helpful!

It would be helpful for the updates to also include what fields have changed and what they have been changed to

Our CoC needs this!

A "Clarity to Looker Data Dictionary" showing all the fields available in all of the Looker models
A diagram of how the tables relate in Looker

We greatly value your feedback. This item may be a long-term update and will remain under review.

I was just looking if this feature existed. This would greatly benefit COHHIO.

Yup,...agreed. That would quickly become part of my go to resources. It would also be a big help for orienting folks new to LOOKER which I've found challenging.

A "Clarity to Looker Data Dictionary" showing all the fields available in all of the Looker models would be pretty handy for sure.

These resources would help King County tremendously in our work.