Recipient country narrative and recipient region narrative & vocabulary missing from transaction_breakdown table

[stevieflow]

This activity: https://d-portal.org/q.xml?aid=XM-DAC-47066-CD.0033

Has the recipient-region:

<recipient-region code="419" percentage="100" vocabulary="2">
<narrative xml:lang="EN">Latin America and the Caribbean</narrative>
</recipient-region>

This is stored in the recipientregion table: https://datasette.tables.iatistandard.org/iati/recipientregion?_sort=rowid&iatiidentifier__exact=XM-DAC-47066-CD.0033 - with vocabulary

In transaction_breakdown however, there is no region_vocabulary, so this data is lost, and it appears that this transaction has no geographic nature:

https://datasette.tables.iatistandard.org/iati/transaction_breakdown?_sort=rowid&iatiidentifier__exact=XM-DAC-47066-CD.0033

---

This activity: https://d-portal.org/q.xml?aid=XM-DAC-41122-EAPRO,%20Thailand-420R/A0/10/777/001

Has:

<recipient-country percentage="100">
<narrative xml:lang="EN">EAPR</narrative>
</recipient-country>

Stored in recipientcountry: https://datasette.tables.iatistandard.org/iati/recipientcountry?_sort=rowid&iatiidentifier__exact=XM-DAC-41122-EAPRO%2C+Thailand-420R%2FA0%2F10%2F777%2F001 - note, no code, but there is a narrative and a percentage

and

<recipient-region percentage="0" vocabulary="1">
<narrative xml:lang="EN">REGIONAL-PROG</narrative>
</recipient-region>

Stored in recipientregion: https://datasette.tables.iatistandard.org/iati/recipientregion?_sort=rowid&iatiidentifier__exact=XM-DAC-41122-EAPRO%2C+Thailand-420R%2FA0%2F10%2F777%2F001 - again, no code, but there is a narrative and a percentage

However, for transaction_breakdown all the geographic data that is there is missing

https://datasette.tables.iatistandard.org/iati/transaction_breakdown?_sort=rowid&iatiidentifier__exact=XM-DAC-41122-EAPRO%2C+Thailand-420R%2FA0%2F10%2F777%2F001

Proposal

For transaction_breakdown include columns for:

• recipientcountry_narrative
• recipientregion_narrative
• recipientregion_vocabulary

Note - my guess is that this may further complicate how we split - although my assumption is that we only every split on each instant of recipientcountry and recipientregion, and so the extra data around vocabulary and narrative would not create new segments

@IATI/devs cc/ @IsabelBirds @siwhitehouse

[IsabelBirds]

This is a many to one issue - there can be multiple entries for the different vocabs for location.
Hence why sector in the trans_breakdown table only shows 5 digit dac codes, even if an internal sector vocab is also used.

I don't think this is practical unless we have a specific use case as we've discussed it before and it could grow and grow.