Include context of errors (e.g. reporting the OCID)

[mrshll1001]

From a helpdesk issue

Currently when reporting structural errors the review tool reports the location of the error relative to the package e.g. releases/38/tender/tenderers. Since some packages are generated on the fly, and there may be complex mapping behind them, it may be helpful if it would also extract the OCID of the release with the issue rather than just its position in the array. This would support the publisher finding the offending release elsewhere to make the change.

[robredpath]

Just linking up to OpenDataServices/cove#167 where this was discussed in 2015(!)

An addition/alternative might be to provide line numbers for the JSON file. I suspect that ocid is actually easier, but I'm not sure!

[dwasyl]

For what it's worth, reporting the release id would be a lot more useful (at least to me) than a JSON line number.

The current data is okay, and I've handled it by converting the JSON to a spreadsheet and then finding the line number (since the package was dynamically generated), but that's not ideal.