RSR_Partner IATI RSR_Comparison - adriancollier/demo GitHub Wiki
This node contains information about the data set and is not directly mapped to elements within the RSR data structure.
This node contains activity level information that is mapped to the project level within RSR. The only addition to IATI is the Publishing Status from RSR.
Within RSR the reporting org is predominantly the "Support Partner". We are working on a migration of this information to use the Content Owner identifier for projects instead.
When converting data to RSR, the Content Owner and the Support Partner will be populated from the Reporting Organisation.
Title fields within RSR are restricted to 45 charatcers. We also require a subtitle for the project that can be up to 75 characters long. With the use of the namespace we can accomodate both of these fields within the Title node.
The description section is where we have the most customisation to the IATI standard from RSR. We have added an additional codelist for adding more different types of descriptions.
We have many description fields within RSR that provide a granular opportunity to explain the activities being undertaken. These sections help to provide a consistent public narrative for activities of an organisation and all publishers within RSR.
Additionally we are also including Project Updates within the description node. Where these are described, additional identifying information is also included as meta data.
This node records any partner organisations working on the activity. In addition to the IATI identifying information, we have also added internal and partner identifiers to this node to provide some additional linking opportunities.
If the partner is providing funding for the project, then the total amount provided can also be included within this node. We aim to work with publishers to replace this field over time with the more granular information available within the transaction node.
This node is used to pass through the project identifiers known by RSR and any other processing system in the data chain.
The activity status is mapped directly to the project status field within RSR on a value basis.
We have adopted the 4 types of activity date from IATI in RSR - start/end, actual/planned.
We have historically only provided contact information at the organisation level within RSR, however with this migration we have adopted the project/activity level contact and have taken the structure directly from the IATI standard.
The scope determines the geographical spread of the activities being undertaken. This also has been ported directly into RSR from IATI.
This node identifies the countries that the project aims to benefit. This structure comes directly from the IATI standard.
This node identifies the regions that the project aims to benefit. This structure comes directly from the IATI standard.
The location node includes all the specific geographic information provided. The structure being provided by IATI gives options for entry of a variety of different types of locations - from areas or towns to individual buildings or features. Within RSR we have a more traditional address based system. The 2 are compatible, but we are still working on getting the storage and display consistent so that you can always determine what type of location you are looking at.
We have also used this node to identify locations that have been added as part of a project update. These have an additional attribute to allocate the Update ID to the content.
RSR worked with Categories and Focus Areas previously. IATI works with Sector codes, and so we are moving towards the sector direction.
We have taken the OECD DAC sector codelists and will be using a combination of the 3 and 5 digit codes for projects in RSR. We will be doing a full mapping and migration from the previous structure for existing RSR projects.
Country budget items were not existing in RSR previously, so we have added these using the native IATI data structure.
Policy markers have been added to RSR directly from IATI. We are looking at potentially expanding the existing codelist with additional markers defined by government level partners as used within their frameworks. This will be explicitly mentioned when it is implemented.
This node has been implemented directly form the IATI standard as it was not previously existing in RSR.
This node has been implemented directly form the IATI standard as it was not previously existing in RSR.
This node has been implemented directly form the IATI standard as it was not previously existing in RSR.
This node has been implemented directly form the IATI standard as it was not previously existing in RSR.
This node has been implemented directly form the IATI standard as it was not previously existing in RSR.
The budget node fits very nicely with the existing RSR structure, although have added date information within RSR that enables the reporting of budgets over time. Additionally we have an extra budget type codelist within RSR that we will be using to further refine the identification of budgets entered.
This node has been implemented directly form the IATI standard as it was not previously existing in RSR.
This node has been implemented directly form the IATI standard as it was not previously existing in RSR.
Transactions were not represented within the RSR data set, so we have implemented the IATI standard data set natively. We aim to increase the utilisation of this node within the data being published within RSR as we encourage more specific transaction information over general funding information at transaction level.
This node within IATI is used to link to additional documents for supporting evidence. Within RSR we have made good use of this by repurposing this node to not only link to supporting documents, but also images and video added to the project through updates.
The related activity is aimed to be the primary resource of linking activities together when published via RSR. We will be building visualisations and functionality to be able to make the most out of when these links are provided.
A large effort will need to be made on the data level to ensure that this detail is being provided within the publicised activities.
This node has been implemented directly form the IATI standard as it was not previously existing in RSR.
RSR had a results section containing Goals and Benchmarks. IATI contains a results structure of Results, Indicators and Periods. On a detailed level the 2 are very compatible with IATI to RSR causing no problems at all. Some data migration work still needs to be carried out to map from RSR to IATI on our existing data set.
Going forwards RSR has adopted the Results, Indicators and Period structure from IATI so there will be no further problems here.