Skip to content

Latest commit

 

History

History
25 lines (13 loc) · 1.78 KB

verify_OCA_bundle.md

File metadata and controls

25 lines (13 loc) · 1.78 KB

Verifying an OCA Bundle

Before the first use of an OCA Bundle after modification, it should be checked for errors such as incomplete or mismatched overlays. This avoids the misuse of accessing and analyzing data from corrupted OCA Bundles.

A function of the OCA Browser, currently hosted at the Human Colossus Foundation (HCF), can perform an integrity check of the OCA Bundle and provide information about any problems identified. Upload the OCA Bundle archive (.zip) file to the Validate Tab.

OCA validate function

If the integrity check passes, you will receive a Passed message with a brief overview of the overlays and JSON file information.

OCA Bundle passed integrity check

Otherwise, you will receive an error message. Common issues include missing files...

OCA Bundle failed with missing files

...or mismatched SAIDs. In the case below, the SAID of the capture base in an overlay file does not match the capture base JSON file.

OCA Bundle failed with mismatched SAIDs

Also, if you manually edited any of the JSON files, the hash value of the file contents would change. Then it will not match the stored SAID digest, leading to a malformed SAID problem.

OCA Bundle failed with malformed SAIDs

If the integrity check fails, you may want to re-download/re-generate the OCA Bundle or restore any manual modifications to the JSON files. Normally any JSON file in an OCA Bundle should not be manually added, edited, or deleted.