Full integration of the SDS

[tmfrnz]

We assume the following implementation of the requirements specified:

The key concepts of the SDS are

• Priority areas
• Key outcomes, grouped by priority areas
• Strategic outcomes, that specify specific targets for each of the key outcomes

We assume to introduce the above concepts as follows

• Introduce the 14 priority areas as a new concept and treat them similar to the existing human rights recommendations and SDG targets. This would result in an additional list view that would allow filtering, grouping and sorting the priority areas just like it is currently possible for SDG targets and recommendations
• Treat the 4 priority areas as categories within its own taxonomy and use them to categorise the key outcomes
• Treat the strategic outcomes as indicators that can be linked to the priority areas. Progress on these indicators can be documented using progress reports and reporting can be supported by assigning responsible staff to each of these indicators
• Further, new actions could be created and linked with each of the key outcomes. Likewise, key outcomes could be linked to any relevant and already existing actions that might have been specified to address human rights recommendations or SDG targets
• Any of the existing taxonomies could be configured to allow further categorising the key outcomes which would facilitate their management and tracking
• Finally, the functionality of the action and indicator views should be enhanced to allow filtering by “framework” (ie SDS, Human Rights, and SDGs)

The following diagram illustrates how the SDS concepts (red) could be integrated with the existing concepts (blue, light blue and purple) and structure (please note that the diagram only shows selected taxonomies (white with outline), other taxonomies (such as issues, people, organisations) have been omitted):

[tmfrnz]

If resources allow, we would, in order to make the information more easily accessible and provide different entry points, suggest introducing specific dashboard views for each of the three types of commitments or frameworks that Sadata is tracking

1. An “SDS dashboard” for providing an entry point and high level information on the SDS key outcomes and related actions and indicators
2. A “Human Rights dashboard” for providing an entry point to all the international Human Rights obligations and related actions and indicators
3. An “SDG dashboard” for an entry point to the SDGs and SDG targets and related actions and indicators

[tmfrnz]

Schema changes (also see diagram)

NEW table: frameworks

Fields:

• text: title (required)
• string: short_title
• text: description
• bool: has_indicators
• bool: has_measures
• bool: has_response

Endpoints/Permissions:

• Read: public (no authentication or role required for reading the frameworks)

Note: frameworks will need to be set up during configuration and will not be changeable by the user thereafter - same as taxonomies)

---

UPDATE table: taxonomies

Store if taxonomy is a core taxonomy of that framework. "tags_..." fields to be replaced with new taxonomy_frameworks table (see below)

New Field:

• integer: framework_id (FK)

Drop Fields:

• tags_recommendations
• tags_sdgtargets

---

UPDATE table: recommendations

Will be used to store both SDG Targets and HR Recs, to be considered our "objectives" table, eventually replacing and incorporating sdg_targets table. (Could/should alternatively be renamed to "objectives" or replaced with a new table "objectives" but we are not sure yet about the best name so let's stick to recommendations for now)

New Field

• integer: framework_id (FK)

---

NEW table recommendation_recommendations

To track inter-framework linkages, eventually replacing table sdgtarget_recommendations (that I suggest to keep for now)

Fields:

• integer: recommendation_id (FK)
• integer: other_recommendation_id (FK)

Endpoints/permissions (similar to sdgtarget_recommendations):

• Read: public (no authentication)
• Create: user role manager or admin (default application record)
• Delete: user role manager or admin (default application record)

---

NEW table recommendation_indicators

Eventually replacing sdgtarget_indicators table.

Fields:

• integer: recommendation_id (FK)
• integer: indicator_id (FK)

Endpoints/permissions (similar to sdgtarget_recommendations):

• Read: public (no authentication)
• Create: user role manager or admin (default application record)
• Delete: user role manager or admin (default application record)

---

NEW table taxonomy_frameworks

Stores which framework of recommendations can be tagged by which taxonomy, replacing the "tags_recommendations", "tags_sdgtargets" flags of the taxonomy table

Fields:

• integer: framework_id (FK)
• integer: taxonomy_id (FK)

Endpoints/Permissions:

• Read: public (no authentication or role required for reading the frameworks)

Note: frameworks will need to be set up during configuration and will not be changeable by the user thereafter - same as taxonomies)

---

NEW table: framework_frameworks

Stores which framework of recommendations can be linked with which other framework of recommendations

Fields:

• integer: framework_id (FK)
• integer: other_framework_id (FK)

Endpoints/Permissions:

• Read: public (no authentication or role required for reading the frameworks)

Note: frameworks will need to be set up during configuration and will not be changeable by the user thereafter - same as taxonomies)