IATI Import mapping

Mandatory fields

There are several fields which are mandatory in order to publish your project in RSR, using IATI import:

IATI identifier;
Title;
Subtitle (special description type, or otherwise copied from title);
Status (not 'Suspended');
(Planned or actual) Start date;
Photo (document-link with an image file);
At least one funding, implementing or accountable participating organisation;
Project plan summary (a description);
Goals overview (a description with type 2);
A location with latitude and longitude;
A budget item.

Mapping

IATI activities `<iati-activities>`

This node contains information about the data set and is not directly mapped to elements within the RSR data structure. In order to import an IATI file into RSR, the version attribute is required and needs to be a valid IATI version. All IATI versions up to 2.02 are supported in RSR.

If the IATI file contains Akvo specific fields, please indicate the Akvo namespace as an attribute in this node: xmlns:akvo="http://akvo.org/iati-activities".

IATI activity `<iati-activity>`

This node contains activity level information that is mapped to the project level within RSR.

All IATI attributes in this node are supported in RSR. It is possible to specify one Akvo specific attribute in this node: akvo:publish. Set the value of this attribute to 'True' if the project should be published, and to 'False' otherwise. If not specified, we will assume that the project needs to be published.

IATI identifier `<iati-identifier>`

This node contains the IATI identifier that will be used to look up the corresponding project in RSR. If a project with this identifier does not yet exist in RSR, a new project will be created. Otherwise, the existing project will be updated.

Reporting organisation `<reporting-org>`

Within RSR the reporting organisation relates to the organisation that owns the content of the project. It is required that the reporting organisation is an existing organisation in RSR which is allowed to import projects.

The reporting organisation will solely be matched based on the IATI organisation identifier as specified in the ref attribute of this node.

Title `<title>`

Title fields within RSR are restricted to 200 characters. If the title specified has more than 200 characters, we will cut off the text and use the first 200 characters as the title. The full title will still be stored in a custom title field, but not displayed as such on the project page.

Descriptions `<description>`

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.

Subtitle `<description akvo:type="4">`

It is possible to indicate the subtitle in multiple ways:

When using the Akvo namespace, use the akvo:type="4" attribute.
Without the Akvo namespace, it is possible to indicate the subtitle by prepending Subtitle: or Project name: before the text in the node.
If none of these is used, we use the <title> node for the subtitle.

The subtitle text is limited to 200 characters. If the subtitle text has more than 200 characters, we store the full text in a custom subtitle field which is not displayed on the project page.

Project plan summary `<description akvo:type="5">`

It is possible to indicate the project plan summary in multiple ways:

When using the Akvo namespace, use the akvo:type="5" attribute.
Without the Akvo namespace, it is possible to indicate the project plan summary by prepending Project summary: before the text in the node.
If none of these is used, we use the first <description> node without a type attribute or with type="1" as an attribute.

The project plan summary is limited to 2000 characters. If the project plan summary has more than 2000 characters, we store the full text in a custom project plan summary field which is not displayed on the project page.

Goals overview `<description akvo:type="8">`

It is possible to indicate the goals overview in multiple ways:

When using the Akvo namespace, use the akvo:type="8" attribute.
Without the Akvo namespace, it is possible to indicate the project plan summary by using the type="2" attribute.
If none of these is used, we extract the titles for each of the <result> nodes and put these in a list.

The goals overview is not limited to any character limit.

Background `<description akvo:type="6">`

It is possible to indicate the background in multiple ways:

When using the Akvo namespace, use the akvo:type="6" attribute.
Without the Akvo namespace, it is possible to indicate the background by prepending Background: before the text in the node.
If none of these is used, we use the second <description> node without a type attribute or with type="1" as an attribute.

The background is not limited to any character limit.

Baseline situation `<description akvo:type="9">`

It is possible to indicate the baseline situation in multiple ways:

When using the Akvo namespace, use the akvo:type="9" attribute.
Without the Akvo namespace, it is possible to indicate the baseline situation by prepending Baseline situation: before the text in the node.
If none of these is used, we use the third <description> node without a type attribute or with type="1" as an attribute.

The baseline situation is not limited to any character limit.

Target group `<description akvo:type="3">`

It is possible to indicate the target group in multiple ways:

When using the Akvo namespace, use the akvo:type="3" attribute.
Without the Akvo namespace, it is possible to indicate the target group by using the type="3" attribute.

The target group is not limited to any character limit.

Project plan `<description akvo:type="7">`

It is possible to indicate the project plan in multiple ways:

When using the Akvo namespace, use the akvo:type="7" attribute.
Without the Akvo namespace, it is possible to indicate the project plan by prepending Project plan: before the text in the node.
If none of these is used, we use the fourth <description> node without a type attribute or with type="1" as an attribute.

The project plan is not limited to any character limit.

Sustainability `<description akvo:type="10">`

It is possible to indicate the sustainability in multiple ways:

When using the Akvo namespace, use the akvo:type="10" attribute.
Without the Akvo namespace, it is possible to indicate the sustainability by prepending Sustainability: before the text in the node.
If none of these is used, we use the fifth <description> node without a type attribute or with type="1" as an attribute.

The sustainability is not limited to any character limit.

Custom fields `<description akvo:type="99">`

It is possible to indicate any number of custom text fields in RSR, by using the akvo:type="99" attribute. The use of the Akvo namespace is required in this case. There are several additional attributes that can be specified:

akvo:label: The label of the custom field, as displayed in the RSR Project editor
akvo:section: The section of the custom field in the RSR Project editor
akvo:max-characters: The maximum number of characters for the custom field
akvo:help-text: The help text for the custom field in the RSR Project editor
akvo:mandatory: 'True' or 'False' to indicate the field should be mandatory in the RSR Project editor
akvo:order: The order (per section) in which the custom fields will be displayed in the RSR Project editor

Participating Organisations `<participating-org>`

This node records any partner organisations working on the activity. Based on the ref attribute, we will match the specified organisation to an organisation in RSR. If we are unable to match to an existing organisation in RSR based on this IATI organisation identifier, we will try to match the organisation based on the name specified in the text of the node.

If we could not match the organisation to any existing organisations in RSR, a new organisation will be created based on the specified IATI organisation identifier and organisation name.

If the partner is providing funding for the project, then the total amount provided can also be included within this node with the akvo:funding-amount attribute. We aim to work with publishers to replace this field over time with the more granular information available within the transaction node.

In case the akvo:funding-amount attribute is not specified, we will calculate the funding amount by dividing the total budget amount by the number of funding partners. E.g. a project with a total budget of €100,000 and 2 funding partners will result in a funding amount of €50,000 for each funding partner.

Activity Status `<activity-status>`

The structure for the project status in RSR is directly adopted from the IATI structure of the activity status.

Activity Date `<activity-date>`

We have adopted the 4 types of activity date from IATI in RSR: start and end, actual and planned. Do note that the planned end date must always occur after the planned start date, and similar for the actual dates.

Contact Information `<contact-info>`

The structure for contact information is directly adopted from the IATI structure. Therefore it is possible to store the contact type, organisation, department, person name, job title, telephone, email, website, and mailing address.

Activity Scope `<activity-scope>`

The scope determines the geographical spread of the activities being undertaken. This also has been ported directly into RSR from IATI.

Recipient Country `<recipient-country>`

This node identifies the countries that the project aims to benefit. This structure comes directly from the IATI standard.

Recipient Region `<recipient-region>`

This node identifies the regions that the project aims to benefit. This structure comes directly from the IATI standard.

Location `<location>`

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 there is an additional country field for each location. It is possible to specify this country in an <administrative> node with the country attribute. Since this field is deprecated in newer versions of IATI, we have alternatively also implemented a feature to extract the country from the <recipient-country> node and link it to the location. However, this only works when there is one <recipient-country> node.

Sector `<sector>`

RSR has fully adopted the OECD DAC sector codelists and will be using a combination of the 3 and 5 digit codes for projects in RSR.

Country Budget Items `<country-budget-items>`

Country budget items were not existing in RSR previously, so we have added these using the native IATI data structure.

Policy Marker `<policy-marker>`

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.