search

OCFL / Use-Cases

A repository to help capture, track, and discuss use cases for OCFL. Issues-only, please.
7 stars 0 forks source link

Recording correctly ingested bad data #30

Closed zimeon closed 6 years ago

zimeon commented 6 years ago

A file is included in a version of an OCFL object that is in some way corrupted (maybe a bad PDF or a badly encoded JPEG2000) although its digest is correct in the OCFL record so the OCFL object itself is entirely valid.

ahankinson commented 6 years ago

F2F 2018.09.05: The OCFL spec would not prevent recording badly encoded data. Validation tools MAY decide to log this, and the 'bad' file would be corrected by creating a new version with the corrected file.

Recording details of the corrections are out of scope. Prose may be used to record the reason for the intervention in a commit message or log file, but this could be free-form or in a custom machine-readable format.