Project export checksum
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Proposal
When exporting a project, after export is scheduled, the client is expected to poll for status until export is ready to be downloaded. When the export is completed, it would be make things easier for a client to include a checksum of the project export content at the status endpoint.
After a client has downloaded the data, it can better verify the content is not corrupt.
Suggested solution
When a project export is finished, the API already returns additional fields under _links. The suggested solution is when export_status="finished", the field crc32c: uint32 is added to root of response object, with the CRC32C calculated checksum. This algorithm is suggested due to being fast and collision is not critical, as the purpose is error detection.