1_Bulletin
This section tracks updates and notes documenting decision making on UMI metrics and the metric update process. This is a living document - Metric Leads should check-in on this page for the latest on UMI data management decisions.
12/20/24: There is now a template for Metric Update pull requests that prompt metric leads on what detail to include in their PRs. You will see an option to select this template when create a PR. When submitting a metric update please select this template and fill in the prompted details.
12/19/24: For metric leads that have crosswalks specific to their metric, please save it in your metric folder and include it in your pull request. We want these files to be accesible to reviewers and future metric leads.
12/18/24: The instructions for saving and filling out the final file evaluation forms has been updated on the Wiki to add clarity. We encourage metric leads to read through the updated version.
12/9/24: Milestones for metric leads and the dates associated with those milestones have been added to the front page of the Wiki. Metric leads should evaluate their progress relative to key milestones listed and reach out to the data admin team if they feel that they will not be able to reach each milestone by the date-range provided.
11/11/24: We have amended our requirements on the final file evaluation forms and tests in several ways.
-
We are not requiring metric leads to fill out the "final_data_evaluation_form.csv" anymore. Instead, a member of the data leadership team will fill out this form for each metric and the information in the form will be confirmed with metrics leads during check-ins with the maintainer.
-
In previous documentation we required metric leads to run a successful test of their final files with the "evaluate_final_data.R". function prior to writing out any final data files. We are now recommending completing code and writing out a final file first and then returning to run the evaluation function after an initial draft PR is submitted. The function must still be included and passed for all final data files prior to finalizing metric updates.
10/30/24: We decided that for Connecticut, for county-level calculations, we will stick to the 8 counties from 2014-2021, and then starting in 2022, we will drop the 8 counties and add in the 9 planning regions. Details around our decision is specified HERE. Note that our PUMA- and tract-level crosswalk files have this embedded, so it will generate these outcomes. For those using other crosswalks, such as school district or county-level, you may or may not be able to map to these planning regions. Please make an effort, and discuss in your standup meetings and/or raise in the team slack. We also saw that some 2022 population estimates are not accurate for certain localities, and they are on a case-by-case basis getting adjusted. We decided not to account for these adjustments (at least not yet) because this can continue to change, and there's a program for communities to contest population estimates that is still open.