From c06aef348d39c2ec59198aecba3f80fda54470dd Mon Sep 17 00:00:00 2001 From: John DeAngelis Date: Thu, 16 Jan 2025 13:58:00 -0500 Subject: [PATCH 1/6] feat: updates to portfolios and divisions Signed-off-by: John DeAngelis --- backend/data_tools/data/portfolio_data.json5 | 97 ++++++++++++++------ backend/data_tools/data/user_data.json5 | 10 ++ 2 files changed, 77 insertions(+), 30 deletions(-) diff --git a/backend/data_tools/data/portfolio_data.json5 b/backend/data_tools/data/portfolio_data.json5 index a85d60e159..3d80cf0f04 100644 --- a/backend/data_tools/data/portfolio_data.json5 +++ b/backend/data_tools/data/portfolio_data.json5 @@ -244,44 +244,49 @@ to MIECHV and home visiting.\ ", }, +// { // 8 +// name: "Program Support", +// abbreviation: "PS", +// division_id: 6, +// status: "IN_PROCESS", +// team_leaders: [ +// { +// "tablename": "ops_user", +// id: 507 +// }, +// { +// "tablename": "ops_user", +// id: 508 +// }, +// { +// "tablename": "ops_user", +// id: 520 +// } +// ], +// description: "\ +// Evidence capacity” refers to the knowledge, skills, behaviors, and resources that enable an organization\ +// to build and use evidence in its work. OPRE’s Evidence Capacity Framework outlines five key dimensions of\ +// capacity: Evidence Culture, Evidence Infrastructure, Engagement, Human Capital, and Leadership. Examples\ +// of evidence capacity-building activities include learning agenda development; performance measurement\ +// design or improvement; analyzing administrative data and conducting targeted collection of data to answer\ +// operational questions; and providing training and technical assistance on evidence-related topics such as\ +// rapid cycle evaluation and continuous quality improvement.\n\nMany OPRE projects support the development\ +// of evidence capacity within ACF and among its grant recipients. For the purpose of OPS, this portfolio\ +// covers projects that advance ACF’s operational data and evidence capacity. This portfolio is led by the\ +// OPRE Division of Data and Improvement.\ +// ", +// }, { // 8 - name: "Program Support", - abbreviation: "PS", + name: "Data Governance", + abbreviation: "DG", division_id: 6, status: "IN_PROCESS", team_leaders: [ { "tablename": "ops_user", - id: 507 + id: 68 }, - { - "tablename": "ops_user", - id: 508 - }, - { - "tablename": "ops_user", - id: 520 - } ], - description: "\ - Evidence capacity” refers to the knowledge, skills, behaviors, and resources that enable an organization\ - to build and use evidence in its work. OPRE’s Evidence Capacity Framework outlines five key dimensions of\ - capacity: Evidence Culture, Evidence Infrastructure, Engagement, Human Capital, and Leadership. Examples\ - of evidence capacity-building activities include learning agenda development; performance measurement\ - design or improvement; analyzing administrative data and conducting targeted collection of data to answer\ - operational questions; and providing training and technical assistance on evidence-related topics such as\ - rapid cycle evaluation and continuous quality improvement.\n\nMany OPRE projects support the development\ - of evidence capacity within ACF and among its grant recipients. For the purpose of OPS, this portfolio\ - covers projects that advance ACF’s operational data and evidence capacity. This portfolio is led by the\ - OPRE Division of Data and Improvement.\ - ", - }, - { // 9 - name: "Data Governance", - abbreviation: "DG", - division_id: 6, - status: "IN_PROCESS", - team_leaders: [], description: "\ Data governance is the mechanism (i.e., structures, processes, and policies) for organizational staff and\ leadership to manage data throughout the data lifecycle, while ensuring its security, exploring\ @@ -294,6 +299,38 @@ activities. For the purpose of OPS, this portfolio covers projects that advance ACF’s progress in meeting\ its data governance goals. This portfolio is led by the OPRE Division of Data and Improvement.\ ", + }, + { // 9 + name: "Office Of The Director", + abbreviation: "OD", + division_id: 3, + status: "IN_PROCESS", + team_leaders: [], + description: "", + }, + { // 10 + name: "Privacy & Security", + abbreviation: "PS", + division_id: 8, + status: "IN_PROCESS", + team_leaders: [], + description: "", + }, + { // 11 + name: "Data Governance", + abbreviation: "DG", + division_id: 9, + status: "IN_PROCESS", + team_leaders: [], + description: "", + }, + { // 12 + name: "Not A Specific Portfolio", + abbreviation: "NON-OPRE", + division_id: 3, + status: "IN_PROCESS", + team_leaders: [], + description: "", } ], portfolio_url: [ diff --git a/backend/data_tools/data/user_data.json5 b/backend/data_tools/data/user_data.json5 index 80a2c20416..c7dc1be0f3 100644 --- a/backend/data_tools/data/user_data.json5 +++ b/backend/data_tools/data/user_data.json5 @@ -34,6 +34,16 @@ id: 7, name: "Non-OPRE Division", abbreviation: "OTHER", + }, + { + id: 8, + name: "Division of Data Privacy", + abbreviation: "DDP", + }, + { + id: 9, + name: "Division of Data Governance", + abbreviation: "DDG", } ], role: [ From d29704d06c71d6159f9aaa3520fce8db8075ba15 Mon Sep 17 00:00:00 2001 From: John DeAngelis Date: Thu, 16 Jan 2025 13:58:29 -0500 Subject: [PATCH 2/6] test: fix tests with new data Signed-off-by: John DeAngelis --- backend/ops_api/tests/ops/portfolio/test_division.py | 2 +- frontend/cypress/e2e/canDetail.cy.js | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/backend/ops_api/tests/ops/portfolio/test_division.py b/backend/ops_api/tests/ops/portfolio/test_division.py index 49bf12f51b..5c48171deb 100644 --- a/backend/ops_api/tests/ops/portfolio/test_division.py +++ b/backend/ops_api/tests/ops/portfolio/test_division.py @@ -22,7 +22,7 @@ def test_division_create(): def test_get_divisions_list(auth_client): response = auth_client.get("/api/v1/divisions/") assert response.status_code == 200 - assert len(response.json) == 7 + assert len(response.json) == 9 @pytest.mark.usefixtures("app_ctx") diff --git a/frontend/cypress/e2e/canDetail.cy.js b/frontend/cypress/e2e/canDetail.cy.js index 575397ad5a..5f6e1430b9 100644 --- a/frontend/cypress/e2e/canDetail.cy.js +++ b/frontend/cypress/e2e/canDetail.cy.js @@ -26,9 +26,9 @@ describe("CAN detail page", () => { cy.visit("/cans/502/"); cy.get("h1").should("contain", "G99PHS9"); // heading cy.get("p").should("contain", can502Nickname); // sub-heading - cy.get("span").should("contain", "Nicole Deterding"); // team member + cy.get("span").should("contain", "Sheila Celentano"); // team member cy.get("span").should("contain", "Director Derrek"); // division director - cy.get("span").should("contain", "Program Support"); // portfolio + cy.get("span").should("contain", "Data Governance"); // portfolio cy.get("span").should("contain", "Division of Data and Improvement"); // division }); it("CAN Edit form", () => { From 02a260bee739d96e8bfbfd9fed823af6fb617c8d Mon Sep 17 00:00:00 2001 From: John DeAngelis Date: Thu, 16 Jan 2025 14:41:00 -0500 Subject: [PATCH 3/6] feat: update initial data with new portfolios and divisions Signed-off-by: John DeAngelis --- backend/data_tools/initial_data/001-division.sql | 6 ++++-- backend/data_tools/initial_data/002-division_version.sql | 4 +++- backend/data_tools/initial_data/007-portfolio.sql | 9 +++++---- .../data_tools/initial_data/008-portfolio_version.sql | 9 +++++---- 4 files changed, 17 insertions(+), 11 deletions(-) diff --git a/backend/data_tools/initial_data/001-division.sql b/backend/data_tools/initial_data/001-division.sql index cc97a3cc48..fdbc89540f 100644 --- a/backend/data_tools/initial_data/001-division.sql +++ b/backend/data_tools/initial_data/001-division.sql @@ -1,7 +1,9 @@ INSERT INTO ops.division (id, name, abbreviation, created_on, updated_on) VALUES (1, 'Child Care', 'CC', current_timestamp, current_timestamp); INSERT INTO ops.division (id, name, abbreviation, created_on, updated_on) VALUES (2, 'Division of Economic Independence', 'DEI', current_timestamp, current_timestamp); INSERT INTO ops.division (id, name, abbreviation, created_on, updated_on) VALUES (3, 'Office of the Director', 'OD', current_timestamp, current_timestamp); -INSERT INTO ops.division (id, name, abbreviation, created_on, updated_on) VALUES (4, 'Division of Child and Family Development', 'DCFD', current_timestamp, current_timestamp); +INSERT INTO ops.division (id, name, abbreviation, created_on, updated_on) VALUES (4, 'Division of Child and Family Development', 'DFCD', current_timestamp, current_timestamp); INSERT INTO ops.division (id, name, abbreviation, created_on, updated_on) VALUES (5, 'Division of Family Strengthening', 'DFS', current_timestamp, current_timestamp); -INSERT INTO ops.division (id, name, abbreviation, created_on, updated_on) VALUES (6, 'Division of Data and Improvement', 'DDI', current_timestamp, current_timestamp); INSERT INTO ops.division (id, name, abbreviation, created_on, updated_on) VALUES (7, 'Non-OPRE Division', 'OTHER', current_timestamp, current_timestamp); +INSERT INTO ops.division (id, name, abbreviation, created_on, updated_on) VALUES (8, 'Division of Data Privacy', 'DDP', current_timestamp, current_timestamp); +INSERT INTO ops.division (id, name, abbreviation, created_on, updated_on) VALUES (9, 'Division of Data Governance', 'DDG', current_timestamp, current_timestamp); +INSERT INTO ops.division (id, name, abbreviation, created_on, updated_on) VALUES (6, 'Division of Data and Improvement', 'DDI', current_timestamp, current_timestamp); diff --git a/backend/data_tools/initial_data/002-division_version.sql b/backend/data_tools/initial_data/002-division_version.sql index 622f0c2386..8760ed5dba 100644 --- a/backend/data_tools/initial_data/002-division_version.sql +++ b/backend/data_tools/initial_data/002-division_version.sql @@ -1,7 +1,9 @@ INSERT INTO ops.division_version (id, name, abbreviation, created_on, updated_on, transaction_id, end_transaction_id, operation_type) VALUES (1, 'Child Care', 'CC', current_timestamp, current_timestamp, 1, null, 0); INSERT INTO ops.division_version (id, name, abbreviation, created_on, updated_on, transaction_id, end_transaction_id, operation_type) VALUES (2, 'Division of Economic Independence', 'DEI', current_timestamp, current_timestamp, 1, null, 0); -INSERT INTO ops.division_version (id, name, abbreviation, created_on, updated_on, transaction_id, end_transaction_id, operation_type) VALUES (3, 'Office of the Director', 'OD', current_timestamp, current_timestamp, 1, null, 0); +INSERT INTO ops.division_version (id, name, abbreviation, created_on, updated_on, transaction_id, end_transaction_id, operation_type) VALUES (3, 'Office of the Director', 'OD', null, current_timestamp, current_timestamp, 1, null, 0); INSERT INTO ops.division_version (id, name, abbreviation, created_on, updated_on, transaction_id, end_transaction_id, operation_type) VALUES (4, 'Division of Child and Family Development', 'DFCD', current_timestamp, current_timestamp, 1, null, 0); INSERT INTO ops.division_version (id, name, abbreviation, created_on, updated_on, transaction_id, end_transaction_id, operation_type) VALUES (5, 'Division of Family Strengthening', 'DFS', current_timestamp, current_timestamp, 1, null, 0); INSERT INTO ops.division_version (id, name, abbreviation, created_on, updated_on, transaction_id, end_transaction_id, operation_type) VALUES (6, 'Division of Data and Improvement', 'DDI', current_timestamp, current_timestamp, 1, null, 0); INSERT INTO ops.division_version (id, name, abbreviation, created_on, updated_on, transaction_id, end_transaction_id, operation_type) VALUES (7, 'Non-OPRE Division', 'OTHER', current_timestamp, current_timestamp, 1, null, 0); +INSERT INTO ops.division_version (id, name, abbreviation, created_on, updated_on, transaction_id, end_transaction_id, operation_type) VALUES (8, 'Division of Data Privacy', 'DDP', current_timestamp, current_timestamp, 1, null, 0); +INSERT INTO ops.division_version (id, name, abbreviation, created_on, updated_on, transaction_id, end_transaction_id, operation_type) VALUES (9, 'Division of Data Governance', 'DDG', current_timestamp, current_timestamp, 1, null, 0); diff --git a/backend/data_tools/initial_data/007-portfolio.sql b/backend/data_tools/initial_data/007-portfolio.sql index 08bfb9a061..e40ec1ea96 100644 --- a/backend/data_tools/initial_data/007-portfolio.sql +++ b/backend/data_tools/initial_data/007-portfolio.sql @@ -29,9 +29,10 @@ INSERT INTO ops.portfolio (id, name, abbreviation, status, division_id, descript Federal investment in home visiting — and related research and evaluation — has greatly expanded through the Maternal, Infant, and Early Childhood Home Visiting (MIECHV) Program, which was established in 2010. The MIECHV Program supports home visiting for expectant and new parents with children up to kindergarten entry age who live in communities that are at-risk for poor maternal and child health outcomes. Families choose to participate in home visiting programs, and partner with health, social service, and child development professionals to set and achieve goals that improve their health and well-being. MIECHV is administered by the Health Resources and Services Administration (HRSA) in collaboration with ACF. HRSA oversees the state and territory MIECHV Program, which provides grants to states, territories, and eligible non-profit organizations to develop and implement statewide home visiting programs. ACF oversees the Tribal MIECHV program, which provides grants to tribes, tribal organizations, and Urban Indian Organizations to develop, implement, and evaluate home visiting programs in American Indian and Alaska Native communities. In collaboration with HRSA and with ACF’s Tribal MIECHV program, ACF’s Office of Planning, Research, and Evaluation manages and partners on research, evaluation, and technical assistance activities related to MIECHV and home visiting. ', current_timestamp, current_timestamp); -INSERT INTO ops.portfolio (id, name, abbreviation, status, division_id, description, created_on, updated_on) VALUES (8, 'Program Support', 'PS', 'IN_PROCESS', 6, e' Evidence capacity” refers to the knowledge, skills, behaviors, and resources that enable an organization to build and use evidence in its work. OPRE’s Evidence Capacity Framework outlines five key dimensions of capacity: Evidence Culture, Evidence Infrastructure, Engagement, Human Capital, and Leadership. Examples of evidence capacity-building activities include learning agenda development; performance measurement design or improvement; analyzing administrative data and conducting targeted collection of data to answer operational questions; and providing training and technical assistance on evidence-related topics such as rapid cycle evaluation and continuous quality improvement. - -Many OPRE projects support the development of evidence capacity within ACF and among its grant recipients. For the purpose of OPS, this portfolio covers projects that advance ACF’s operational data and evidence capacity. This portfolio is led by the OPRE Division of Data and Improvement. ', current_timestamp, current_timestamp); -INSERT INTO ops.portfolio (id, name, abbreviation, status, division_id, description, created_on, updated_on) VALUES (9, 'Data Governance', 'DG', 'IN_PROCESS', 6, e' Data governance is the mechanism (i.e., structures, processes, and policies) for organizational staff and leadership to manage data throughout the data lifecycle, while ensuring its security, exploring opportunities to share data for evidence-building activities, and using data for programmatic, evaluation and research purposes. ACF’s goals related to data governance are to make data more usable, accessible, and protected to meet the operational and evidence-building data governance needs of ACF; meet the operational and evidence-building data governance needs of ACF offices; and promote the reuse of ACF data for evidence-building purposes at the state, local, tribal, territory, and grant recipient levels. +INSERT INTO ops.portfolio (id, name, abbreviation, status, division_id, description, created_on, updated_on) VALUES (8, 'Data Governance', 'DG', 'IN_PROCESS', 6, e' Data governance is the mechanism (i.e., structures, processes, and policies) for organizational staff and leadership to manage data throughout the data lifecycle, while ensuring its security, exploring opportunities to share data for evidence-building activities, and using data for programmatic, evaluation and research purposes. ACF’s goals related to data governance are to make data more usable, accessible, and protected to meet the operational and evidence-building data governance needs of ACF; meet the operational and evidence-building data governance needs of ACF offices; and promote the reuse of ACF data for evidence-building purposes at the state, local, tribal, territory, and grant recipient levels. The Data Governance Team within DDI has primary responsibility for coordinating ACF\'s data governance activities. For the purpose of OPS, this portfolio covers projects that advance ACF’s progress in meeting its data governance goals. This portfolio is led by the OPRE Division of Data and Improvement. ', current_timestamp, current_timestamp); +INSERT INTO ops.portfolio (id, name, abbreviation, status, division_id, description, created_on, updated_on) VALUES (9, 'Office Of The Director', 'OD', 'IN_PROCESS', 3, '', current_timestamp, current_timestamp); +INSERT INTO ops.portfolio (id, name, abbreviation, status, division_id, description, created_on, updated_on) VALUES (10, 'Privacy & Security', 'PS', 'IN_PROCESS', 8, '', current_timestamp, current_timestamp); +INSERT INTO ops.portfolio (id, name, abbreviation, status, division_id, description, created_on, updated_on) VALUES (11, 'Data Governance', 'DG', 'IN_PROCESS', 9, '', current_timestamp, current_timestamp); +INSERT INTO ops.portfolio (id, name, abbreviation, status, division_id, description, created_on, updated_on) VALUES (12, 'Not A Specific Portfolio', 'NON-OPRE', 'IN_PROCESS', 3, '', current_timestamp, current_timestamp); diff --git a/backend/data_tools/initial_data/008-portfolio_version.sql b/backend/data_tools/initial_data/008-portfolio_version.sql index 0328602799..a7d540b604 100644 --- a/backend/data_tools/initial_data/008-portfolio_version.sql +++ b/backend/data_tools/initial_data/008-portfolio_version.sql @@ -29,9 +29,10 @@ INSERT INTO ops.portfolio_version (id, name, abbreviation, status, division_id, Federal investment in home visiting — and related research and evaluation — has greatly expanded through the Maternal, Infant, and Early Childhood Home Visiting (MIECHV) Program, which was established in 2010. The MIECHV Program supports home visiting for expectant and new parents with children up to kindergarten entry age who live in communities that are at-risk for poor maternal and child health outcomes. Families choose to participate in home visiting programs, and partner with health, social service, and child development professionals to set and achieve goals that improve their health and well-being. MIECHV is administered by the Health Resources and Services Administration (HRSA) in collaboration with ACF. HRSA oversees the state and territory MIECHV Program, which provides grants to states, territories, and eligible non-profit organizations to develop and implement statewide home visiting programs. ACF oversees the Tribal MIECHV program, which provides grants to tribes, tribal organizations, and Urban Indian Organizations to develop, implement, and evaluate home visiting programs in American Indian and Alaska Native communities. In collaboration with HRSA and with ACF’s Tribal MIECHV program, ACF’s Office of Planning, Research, and Evaluation manages and partners on research, evaluation, and technical assistance activities related to MIECHV and home visiting. ', current_timestamp, current_timestamp, 1, null, 0); -INSERT INTO ops.portfolio_version (id, name, abbreviation, status, division_id, description, created_on, updated_on, transaction_id, end_transaction_id, operation_type) VALUES (8, 'Program Support', 'PS', 'IN_PROCESS', 6, e' Evidence capacity” refers to the knowledge, skills, behaviors, and resources that enable an organization to build and use evidence in its work. OPRE’s Evidence Capacity Framework outlines five key dimensions of capacity: Evidence Culture, Evidence Infrastructure, Engagement, Human Capital, and Leadership. Examples of evidence capacity-building activities include learning agenda development; performance measurement design or improvement; analyzing administrative data and conducting targeted collection of data to answer operational questions; and providing training and technical assistance on evidence-related topics such as rapid cycle evaluation and continuous quality improvement. - -Many OPRE projects support the development of evidence capacity within ACF and among its grant recipients. For the purpose of OPS, this portfolio covers projects that advance ACF’s operational data and evidence capacity. This portfolio is led by the OPRE Division of Data and Improvement. ', current_timestamp, current_timestamp, 1, null, 0); -INSERT INTO ops.portfolio_version (id, name, abbreviation, status, division_id, description, created_on, updated_on, transaction_id, end_transaction_id, operation_type) VALUES (9, 'Data Governance', 'DG', 'IN_PROCESS', 6, e' Data governance is the mechanism (i.e., structures, processes, and policies) for organizational staff and leadership to manage data throughout the data lifecycle, while ensuring its security, exploring opportunities to share data for evidence-building activities, and using data for programmatic, evaluation and research purposes. ACF’s goals related to data governance are to make data more usable, accessible, and protected to meet the operational and evidence-building data governance needs of ACF; meet the operational and evidence-building data governance needs of ACF offices; and promote the reuse of ACF data for evidence-building purposes at the state, local, tribal, territory, and grant recipient levels. +INSERT INTO ops.portfolio_version (id, name, abbreviation, status, division_id, description, created_on, updated_on, transaction_id, end_transaction_id, operation_type) VALUES (8, 'Data Governance', 'DG', 'IN_PROCESS', 6, e' Data governance is the mechanism (i.e., structures, processes, and policies) for organizational staff and leadership to manage data throughout the data lifecycle, while ensuring its security, exploring opportunities to share data for evidence-building activities, and using data for programmatic, evaluation and research purposes. ACF’s goals related to data governance are to make data more usable, accessible, and protected to meet the operational and evidence-building data governance needs of ACF; meet the operational and evidence-building data governance needs of ACF offices; and promote the reuse of ACF data for evidence-building purposes at the state, local, tribal, territory, and grant recipient levels. The Data Governance Team within DDI has primary responsibility for coordinating ACF\'s data governance activities. For the purpose of OPS, this portfolio covers projects that advance ACF’s progress in meeting its data governance goals. This portfolio is led by the OPRE Division of Data and Improvement. ', current_timestamp, current_timestamp, 1, null, 0); +INSERT INTO ops.portfolio_version (id, name, abbreviation, status, division_id, description, created_on, updated_on, transaction_id, end_transaction_id, operation_type) VALUES (9, 'Office Of The Director', 'OD', 'IN_PROCESS', 3, '', current_timestamp, current_timestamp, 1, null, 0); +INSERT INTO ops.portfolio_version (id, name, abbreviation, status, division_id, description, created_on, updated_on, transaction_id, end_transaction_id, operation_type) VALUES (10, 'Privacy & Security', 'PS', 'IN_PROCESS', 8, '', current_timestamp, current_timestamp, 1, null, 0); +INSERT INTO ops.portfolio_version (id, name, abbreviation, status, division_id, description, created_on, updated_on, transaction_id, end_transaction_id, operation_type) VALUES (11, 'Data Governance', 'DG', 'IN_PROCESS', 9, '', current_timestamp, current_timestamp, 1, null, 0); +INSERT INTO ops.portfolio_version (id, name, abbreviation, status, division_id, description, created_on, updated_on, transaction_id, end_transaction_id, operation_type) VALUES (12, 'Not A Specific Portfolio', 'NON-OPRE', 'IN_PROCESS', 3, '', current_timestamp, current_timestamp, 1, null, 0); From 0632c97c5be6b8b7ca40d2c0b295119503da93ec Mon Sep 17 00:00:00 2001 From: John DeAngelis Date: Thu, 16 Jan 2025 14:43:42 -0500 Subject: [PATCH 4/6] chore: removed commented data Signed-off-by: John DeAngelis --- backend/data_tools/data/portfolio_data.json5 | 32 -------------------- 1 file changed, 32 deletions(-) diff --git a/backend/data_tools/data/portfolio_data.json5 b/backend/data_tools/data/portfolio_data.json5 index 3d80cf0f04..1a45f3228a 100644 --- a/backend/data_tools/data/portfolio_data.json5 +++ b/backend/data_tools/data/portfolio_data.json5 @@ -244,38 +244,6 @@ to MIECHV and home visiting.\ ", }, -// { // 8 -// name: "Program Support", -// abbreviation: "PS", -// division_id: 6, -// status: "IN_PROCESS", -// team_leaders: [ -// { -// "tablename": "ops_user", -// id: 507 -// }, -// { -// "tablename": "ops_user", -// id: 508 -// }, -// { -// "tablename": "ops_user", -// id: 520 -// } -// ], -// description: "\ -// Evidence capacity” refers to the knowledge, skills, behaviors, and resources that enable an organization\ -// to build and use evidence in its work. OPRE’s Evidence Capacity Framework outlines five key dimensions of\ -// capacity: Evidence Culture, Evidence Infrastructure, Engagement, Human Capital, and Leadership. Examples\ -// of evidence capacity-building activities include learning agenda development; performance measurement\ -// design or improvement; analyzing administrative data and conducting targeted collection of data to answer\ -// operational questions; and providing training and technical assistance on evidence-related topics such as\ -// rapid cycle evaluation and continuous quality improvement.\n\nMany OPRE projects support the development\ -// of evidence capacity within ACF and among its grant recipients. For the purpose of OPS, this portfolio\ -// covers projects that advance ACF’s operational data and evidence capacity. This portfolio is led by the\ -// OPRE Division of Data and Improvement.\ -// ", -// }, { // 8 name: "Data Governance", abbreviation: "DG", From 6cca763d1616852b195f70fa75f98ca747fda15c Mon Sep 17 00:00:00 2001 From: John DeAngelis Date: Mon, 20 Jan 2025 09:33:52 -0500 Subject: [PATCH 5/6] chore: fix typo Signed-off-by: John DeAngelis --- backend/data_tools/initial_data/001-division.sql | 2 +- backend/data_tools/initial_data/002-division_version.sql | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/backend/data_tools/initial_data/001-division.sql b/backend/data_tools/initial_data/001-division.sql index fdbc89540f..5ac740b96d 100644 --- a/backend/data_tools/initial_data/001-division.sql +++ b/backend/data_tools/initial_data/001-division.sql @@ -1,7 +1,7 @@ INSERT INTO ops.division (id, name, abbreviation, created_on, updated_on) VALUES (1, 'Child Care', 'CC', current_timestamp, current_timestamp); INSERT INTO ops.division (id, name, abbreviation, created_on, updated_on) VALUES (2, 'Division of Economic Independence', 'DEI', current_timestamp, current_timestamp); INSERT INTO ops.division (id, name, abbreviation, created_on, updated_on) VALUES (3, 'Office of the Director', 'OD', current_timestamp, current_timestamp); -INSERT INTO ops.division (id, name, abbreviation, created_on, updated_on) VALUES (4, 'Division of Child and Family Development', 'DFCD', current_timestamp, current_timestamp); +INSERT INTO ops.division (id, name, abbreviation, created_on, updated_on) VALUES (4, 'Division of Child and Family Development', 'DCFD', current_timestamp, current_timestamp); INSERT INTO ops.division (id, name, abbreviation, created_on, updated_on) VALUES (5, 'Division of Family Strengthening', 'DFS', current_timestamp, current_timestamp); INSERT INTO ops.division (id, name, abbreviation, created_on, updated_on) VALUES (7, 'Non-OPRE Division', 'OTHER', current_timestamp, current_timestamp); INSERT INTO ops.division (id, name, abbreviation, created_on, updated_on) VALUES (8, 'Division of Data Privacy', 'DDP', current_timestamp, current_timestamp); diff --git a/backend/data_tools/initial_data/002-division_version.sql b/backend/data_tools/initial_data/002-division_version.sql index 8760ed5dba..e3f72846fa 100644 --- a/backend/data_tools/initial_data/002-division_version.sql +++ b/backend/data_tools/initial_data/002-division_version.sql @@ -1,7 +1,7 @@ INSERT INTO ops.division_version (id, name, abbreviation, created_on, updated_on, transaction_id, end_transaction_id, operation_type) VALUES (1, 'Child Care', 'CC', current_timestamp, current_timestamp, 1, null, 0); INSERT INTO ops.division_version (id, name, abbreviation, created_on, updated_on, transaction_id, end_transaction_id, operation_type) VALUES (2, 'Division of Economic Independence', 'DEI', current_timestamp, current_timestamp, 1, null, 0); INSERT INTO ops.division_version (id, name, abbreviation, created_on, updated_on, transaction_id, end_transaction_id, operation_type) VALUES (3, 'Office of the Director', 'OD', null, current_timestamp, current_timestamp, 1, null, 0); -INSERT INTO ops.division_version (id, name, abbreviation, created_on, updated_on, transaction_id, end_transaction_id, operation_type) VALUES (4, 'Division of Child and Family Development', 'DFCD', current_timestamp, current_timestamp, 1, null, 0); +INSERT INTO ops.division_version (id, name, abbreviation, created_on, updated_on, transaction_id, end_transaction_id, operation_type) VALUES (4, 'Division of Child and Family Development', 'DCFD', current_timestamp, current_timestamp, 1, null, 0); INSERT INTO ops.division_version (id, name, abbreviation, created_on, updated_on, transaction_id, end_transaction_id, operation_type) VALUES (5, 'Division of Family Strengthening', 'DFS', current_timestamp, current_timestamp, 1, null, 0); INSERT INTO ops.division_version (id, name, abbreviation, created_on, updated_on, transaction_id, end_transaction_id, operation_type) VALUES (6, 'Division of Data and Improvement', 'DDI', current_timestamp, current_timestamp, 1, null, 0); INSERT INTO ops.division_version (id, name, abbreviation, created_on, updated_on, transaction_id, end_transaction_id, operation_type) VALUES (7, 'Non-OPRE Division', 'OTHER', current_timestamp, current_timestamp, 1, null, 0); From 37884c70f2a95cb85ef2ea507b8800b80a002a63 Mon Sep 17 00:00:00 2001 From: John DeAngelis Date: Mon, 20 Jan 2025 11:08:17 -0500 Subject: [PATCH 6/6] chore: fix typo Signed-off-by: John DeAngelis --- backend/data_tools/initial_data/002-division_version.sql | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/backend/data_tools/initial_data/002-division_version.sql b/backend/data_tools/initial_data/002-division_version.sql index e3f72846fa..7aad8c9573 100644 --- a/backend/data_tools/initial_data/002-division_version.sql +++ b/backend/data_tools/initial_data/002-division_version.sql @@ -1,6 +1,6 @@ INSERT INTO ops.division_version (id, name, abbreviation, created_on, updated_on, transaction_id, end_transaction_id, operation_type) VALUES (1, 'Child Care', 'CC', current_timestamp, current_timestamp, 1, null, 0); INSERT INTO ops.division_version (id, name, abbreviation, created_on, updated_on, transaction_id, end_transaction_id, operation_type) VALUES (2, 'Division of Economic Independence', 'DEI', current_timestamp, current_timestamp, 1, null, 0); -INSERT INTO ops.division_version (id, name, abbreviation, created_on, updated_on, transaction_id, end_transaction_id, operation_type) VALUES (3, 'Office of the Director', 'OD', null, current_timestamp, current_timestamp, 1, null, 0); +INSERT INTO ops.division_version (id, name, abbreviation, created_on, updated_on, transaction_id, end_transaction_id, operation_type) VALUES (3, 'Office of the Director', 'OD',current_timestamp, current_timestamp, 1, null, 0); INSERT INTO ops.division_version (id, name, abbreviation, created_on, updated_on, transaction_id, end_transaction_id, operation_type) VALUES (4, 'Division of Child and Family Development', 'DCFD', current_timestamp, current_timestamp, 1, null, 0); INSERT INTO ops.division_version (id, name, abbreviation, created_on, updated_on, transaction_id, end_transaction_id, operation_type) VALUES (5, 'Division of Family Strengthening', 'DFS', current_timestamp, current_timestamp, 1, null, 0); INSERT INTO ops.division_version (id, name, abbreviation, created_on, updated_on, transaction_id, end_transaction_id, operation_type) VALUES (6, 'Division of Data and Improvement', 'DDI', current_timestamp, current_timestamp, 1, null, 0);