Closed leostolk closed 3 years ago
Hi @stormnl,
We expect non technical users not to be able to solve schema errors in their files. We recommend they pass the purple error message on to their technical colleagues or tool provider:
We will discuss how to word the purple critical error message better.
The data in the two files is different. The error is caused in the one file by the @secondary-reporter attribute is blank as per the purple error message:
Also, please can Oxfam Intermon remove the duplicate activities from their reporting.
Hi Amy
Intermon just informed me that they corrected the file and removed the duplicated activity file greetings Leo
Hi @stormnl . Thank you for the update! Looking at both activity files, it looks like the critical errors have been fixed in your files :)
Do let me know if you think there is any improvement we can make to the messaging for that specific error? If not, I will close this issue.
We have this on our internal list as well to look into it as a future enhancement. It's a bit tricky to find the right format. For now, we have chosen to say: your technical person should be able to generate that schema validation output using xmllint or similar. If they're unable to do that, maybe get in touch with someone who can do schema validation ;-)
closing here
Oxfam Intermon has two activity files, one smaller and one larger, the second overlaps the first completely. The larger file get a significant number (± 50?) of 1 critical error. The same activities in the smaller file do not trigger a similar critical error.