We maintain or support a number of codelists. Embedded codelists belong to IATI and can only be updated through an upgrade as their modification may have functional implications. Non-embedded codelists either belong to third parties or belong to IATI but can be updated, subject to consultation, as needed.
There are currently a number of issues requiring clarification:
- How best to handle versioning of codelists
- How to keep non embedded codelists up to date
- Should all external vocabularies be imported into their own IATI-duplicated codelist like OECD DAC CRS Sector codes
- Change status of vocabulary codelists from embedded to non-embedded?
- How do we ensure only valid lists get added as a codelist vocabulary
This paper is part of the Agenda for the IATI TAG 2016 Technical Consultation Workshop
#IATI #TAG2016
Can we separate out process from content here? I think we need to include stuff on management and documentation in the paper, including the principle of deprecation. What we do with particular codes can, I think, be handled by our existing (or improved) consultation process.
I think that makes sense.
So - better to have a separate paper on management of the Organisation
Registration Agency codelist? Or to include that as a section in a general
codelists paper?
Let me know how best to contribute to either option.