Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: clarified google drive info and added next steps section

...

rclone copy dropbox:"Robert Birgeneau INT" /media/sf_BCShared01/processing/2022_061acc 

When transferring files from Google Drive (that do not include Google objects such as Docs, Sheets, and Slides) and additional analysis will most likely not be needed, such as a small transfer of word documents,  you can direct the output of Rclone to a folder that aligns with Archivematica's standard packaging structure. This will save some work later when preparing for Archivematica. Here is an example:

rclone copy googledrive:"Robert Birgeneau INT" /media/sf_BCShared01/processing/2022_061acc/objects/"

Extracting checksums

Some cloud providers have checksums stored in their system that you can extract and facilitate fixity checking. Some are unique to their system or some can be more standard types. Here is a general layout of the command to extract the checksums into a text file:

rclone hashsum [type of checksum] [remote source]:"folder_name or file" (same as used when copying) --output-file /path/to/output/file.txt 

...

Here is an example for Google Drive, because you can reuse md5 checksums in Archivematica, we have named can name the checksum file and store it in the convention that it will recognizeit's standard packaging and naming structure:

rclone hashsum md5 googledrive:"Robert Birgeneau INT" --output-file /media/sf_BCShared01/processing/2022_061acc/submissionDocumentation/checksum.md5
Note

Google objects, such as Docs, Sheets, and Slides, do not have checksums stored in Google Drive that can be extracted. If you have any of these in the content you're transferring, they will be downloaded as regular files, but they will not have checksums in the checksum file extracted from Google Drive. In these cases, we will not reuse the checksum file we create here in Archivematica and it should be named googledrive_checksums.txt in a location of your choosing.

Confirming fixity

In order to confirm fixity, there are number of options:

...

rclone check [remote name]:[source folder] /path/to/local_copy/of/source_folder

Next steps and packaging files

While Rclone exports the files from the cloud provider, under most circumstances, it doesn't perform the needed packaging or analysis that will be needed for processing the files. Proceed to the Logical Transfer section for next steps in processing this content.