From af79a430b4504a7cadd975e2e47b5cdd0157ca14 Mon Sep 17 00:00:00 2001 From: Rob Harrison <48765695+robjharrison@users.noreply.github.com> Date: Tue, 2 Jan 2024 13:40:09 +0000 Subject: [PATCH] ssd refresh from dtoi-1555 --- CHANGELOG.md | 2 +- docs/README.html | 4 ++-- docs/existingreturnsmap.html | 2 +- docs/guidance.html | 2 +- .../returns_maps/ssd_annexa_plus_diagram.jpg | Bin 674 -> 1293848 bytes .../ssd_child_journey_diagram.jpg | Bin 674 -> 764171 bytes .../returns_maps/ssd_cin_census_diagram.jpg | Bin 674 -> 295909 bytes .../ssd_current_cla_cohort_diagram.jpg | Bin 674 -> 492074 bytes .../ssd_current_cp_cohort_diagram.jpg | Bin 674 -> 228914 bytes .../ssd_dfe_csc_dashboard_diagram.jpg | Bin 674 -> 445341 bytes .../ssd_riia_last_quarter_diagram.jpg | Bin 674 -> 869502 bytes .../imgs/returns_maps/ssd_ssda903_diagram.jpg | Bin 674 -> 730762 bytes docs/index.html | 2 +- docs/object_definitions.pdf | Bin 219656 -> 219656 bytes .../__pycache__/admin_tools.cpython-310.pyc | Bin 3851 -> 3851 bytes 15 files changed, 6 insertions(+), 6 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 80992fa8..ff561333 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,6 +1,6 @@ # Change log SSD Data Item Changes: -The complete change history for SSD data items in reverse chronological order, with pending|expected changes showing first.Agreed data item-level changes are assigned an identifier. A sub-set of the change details for the most recent change (if any) also appears within each objects metadata block(YAML).The current change log contains only sample data until we deploy the first pilot release.Note: Object-level change tracking is not yet available/in progress; feedback/suggestions welcomed.Last updated: 12/12/2023 12:35 +The complete change history for SSD data items in reverse chronological order, with pending|expected changes showing first.Agreed data item-level changes are assigned an identifier. A sub-set of the change details for the most recent change (if any) also appears within each objects metadata block(YAML).The current change log contains only sample data until we deploy the first pilot release.Note: Object-level change tracking is not yet available/in progress; feedback/suggestions welcomed.Last updated: 02/01/2024 13:38 | item_ref | old_item_ref | release_datetime | change_id | change_object_name | change_impact_title | change_status | change_type | change_source | change_impact_notes | |:-----------|:---------------|:-------------------|:------------|:----------------------|:------------------------|:----------------|:--------------|:----------------|:-------------------------------------------------------| diff --git a/docs/README.html b/docs/README.html index 73de2772..ab0656ec 100644 --- a/docs/README.html +++ b/docs/README.html @@ -103,7 +103,7 @@
Hertfordshire CC : Bid Lead | Knowsley CC : Steering Group | Data2Insight : Project Lead | East Sussex CC : Host Authority | Essex CC : Project Management | ADCS North West (hosted by Stockport Council)
+Hertfordshire CC : Bid Lead | Knowsley CC : Steering Group | Data2Insight : Project Lead | East Sussex CC : Host Authority | Essex CC : Project Management and Mosaic Pilot Development | ADCS North West (hosted by Stockport Council) | Blackpool CC : Mosaic Pilot Development | East Riding CC : Azeus Pilot Development
Repo forks, and direct involvement with the project are welcomed and you can find more information about Data2Insight on our website https://www.datatoinsight.org/
In brief, folders data, docs & sql are output folders. Python scripts within the tools folder generate those files with the exception of docs/admin which contains the import csv definitions of all data objects & relationships. tools/*.py are numbered to dictate their required run order when updating the specification. This workflow enables the entire project and all outputs to be instantly updated enabling full development transparency and ease of later updates both minor modifications and new modules/objects. It is anticipated that most LA's will only need to access the generated extract SQL files for their particular CMS.
diff --git a/docs/existingreturnsmap.html b/docs/existingreturnsmap.html index 95b4d962..99bc3d75 100644 --- a/docs/existingreturnsmap.html +++ b/docs/existingreturnsmap.html @@ -1 +1 @@ -This page shows subset views of the SSD data map towards core DfE returns, and below this the initial data mapping undertaken by the Standard Safeguarding Dataset project to understand the existing children's safeguarding data landscape.
Initial data mapping undertaken by the Standard Safeguarding Dataset. Please note that image quality will vary due to limitations on source files and page generator workflow.
This page shows subset views of the SSD data map towards core DfE returns, and below this the initial data mapping undertaken by the Standard Safeguarding Dataset project to understand the existing children's safeguarding data landscape.
Initial data mapping undertaken by the Standard Safeguarding Dataset. Please note that image quality will vary due to limitations on source files and page generator workflow.
This page shows detailed item-level guidance on data items within the Standard Safeguarding Dataset. Right click and open the image in a new browser tab to zoom/magnify/scroll object level detail. Data item id numbers [AAA000A] enable specific item/field referencing.
This is work in progress subject to frequent change; Data objects and item definitions are published here to support iterative development. Diagrams consisdered as conceptual interpretations, not a true relational/representational model
Note: Colour identifiers on Overview image indicate presence of at least one known change. See below tables for the item level changes/additions with granular colour-coding.