When the V2.01 was implemented in AidStream, there were number of activities where passed the AidStream workflow, but with issues in couple of elements. Primarily because in previous IATI version, these elements were not mandatory. When these elements are not touched in v201, they would happily appear in the xml file.
Implement the schema validation in the workflow, which will catch these errors before the activity is tagged as "completed". This would catch the existing activity which misses some of these data (which are not compulsory in the previous IATI versions).
For the new activities, these problem would never happen, as all these validations are included as a part of the form validation.
All these issues will get resolved after the implementation of schema validation in each activity. But the organisation has to do the re-publishing first to get schema errors.
Background:
When the V2.01 was implemented in AidStream, there were number of activities where passed the AidStream workflow, but with issues in couple of elements. Primarily because in previous IATI version, these elements were not mandatory. When these elements are not touched in v201, they would happily appear in the xml file.
For e.g.
In sector, code is not mandatory in v105 http://iatistandard.org/105/activity-standard/iati-activities/iati-activity/sector/ but is now mandatory in v201. There are activities where sector code is missing and giving validation error https://github.com/younginnovations/aidstream/issues/135
Solution
Implement the schema validation in the workflow, which will catch these errors before the activity is tagged as "completed". This would catch the existing activity which misses some of these data (which are not compulsory in the previous IATI versions).
For the new activities, these problem would never happen, as all these validations are included as a part of the form validation.