Rather than a plain text file, it would be better if the error log could be presented as a more readable html file.
However, rather than generate an html file directly, perhaps it could generate a JSON file and come with an html file that reads that JSON file. This would allow other applications to parse the error log directly from the JSON.
Rather than a plain text file, it would be better if the error log could be presented as a more readable html file.
However, rather than generate an html file directly, perhaps it could generate a JSON file and come with an html file that reads that JSON file. This would allow other applications to parse the error log directly from the JSON.
We would still include an html file in the zip package, perhaps using a similar template as the data.json html template - https://github.com/GSA/data.json-template
There might be some things here that would also apply to https://github.com/GSA/data.gov/issues/506.
We should also explore how to provide this information directly within the CKAN UI since it seems like it could be easy to miss within the zip file.