... | ... | @@ -2,9 +2,9 @@ |
|
|
|
|
|
## Procedural note
|
|
|
|
|
|
The workflow indicated below assumes that file fixity validation is required as part of the processing. It also assumes that a tranche is populated with asset-files on the drive on which it is initially created, rather than the tranche being copied to an external drive, then given to the digitisation provider who populates it, and returns it, so that it can be copied back to the original drive.
|
|
|
The workflow indicated below assumes that file fixity validation is required as part of the processing. It also assumes that a tranche is populated with asset-files on the drive drive on which the tranche was initially created, rather than scenario in which the "empty" tranche is copied to an external drive, then given to the digitisation provider who populates it, and returns the tranche on an external drive, so that the tranche can be copied back to the original drive.
|
|
|
|
|
|
If the latter is the case, each time the tranche is copied, the script that validates the checksums should be run in order to ensure that no corruption has resulted. So, in the latter case, the workflow will be slightly more complex.
|
|
|
If the latter is the case, each time the populated tranche is copied, the script that validates the checksums should be run, in order to ensure that no corruption has resulted from the copying. In this latter scenario, the workflow will be slightly more complex than the one indicated below.
|
|
|
|
|
|
Instructions on how to form the command line for each script can be found at the top of the script.
|
|
|
|
... | ... | |