-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v2.03 bug: transaction/aid-type
and default-aid-type
mappings should include a @vocabulary
condition
#169
Comments
Linked to issue: IATI/IATI-Codelists#169
@PetyaKangalova please could you have a look through these tomorrow before we merge? And we'll see if rebuilding the iati-activities-schema.xsd pulls through the 2.03 added guidance onto the site :) |
This is now fixed and on the website. Good work all. |
Looks wrong on the website still. I’m expecting this:
…to instead say:
When it says that, then it’s clear that the fix for this is working. The IATI-Codelist submodule on IATI-Standard-SSOT was last updated a month ago, so that’s probably why. [Auto-deploying would save headaches.] |
@andylolz have a look now? |
Perfect! Thanks @amy-silcock. |
Originally raised on IATI discuss, so credit to @Eimis for spotting it 👏
In the
transaction/aid-type/@code
v2.03 docs, it currently says:That’s not true, though. Since v2.03, the value is only required to be on the AidType codelist if the relevant aid type vocabulary (
1
) is used.To fix this, the v2.03 mapping.xml file should be amended to add a condition to the
aid-type
anddefault-aid-type
vocabularies, similar to the condition used forsector
s.The text was updated successfully, but these errors were encountered: