Brief Description
The non-free form fields for reporting_orgs - hq_country, region, organisation_type, default_licence_id - are validated against hard coded copies of the code lists which have been copied from the IATI SuiteCRM Registry, which also has them hardcoded: https://github.com/IATI/iati-suitecrm/blob/master/custom/Extension/application/Ext/Language/_override_en_us.IATI_Dropdowns.php
We need to think about how best to automate or sync the update process for these lists.
In the short term, to avoid the BDS rejecting records, if the lists are going to be updated by hand in the Registry, the BDS would need to have its lists updated first.
But longer term, we should pull these lists in.
There is similar infrastructure already in place that is (or used to be) used by some applications in the IATI system, and there is even a system of caching for them (uses https://github.com/IATI/redis-cacher).
Brief Description
The non-free form fields for reporting_orgs -
hq_country,region,organisation_type,default_licence_id- are validated against hard coded copies of the code lists which have been copied from the IATI SuiteCRM Registry, which also has them hardcoded: https://github.com/IATI/iati-suitecrm/blob/master/custom/Extension/application/Ext/Language/_override_en_us.IATI_Dropdowns.phpWe need to think about how best to automate or sync the update process for these lists.
In the short term, to avoid the BDS rejecting records, if the lists are going to be updated by hand in the Registry, the BDS would need to have its lists updated first.
But longer term, we should pull these lists in.
There is similar infrastructure already in place that is (or used to be) used by some applications in the IATI system, and there is even a system of caching for them (uses https://github.com/IATI/redis-cacher).