Create a container for each collection and populate each with exported disk image objects

[kmichaelis]

• For each collection in the list resulting from the work in this ticket, use the API to create a collection-level container in LIBSAFE Go and populate the container metadata with the collection title and collection identifier

• Upload exported disk image objects (disk image, supplemental content files, supplemental metadata files, exported Keep metadata files) to the appropriate containers in LIBSAFE Go. Each object-level container should be named according the object's Keep-assigned pid.

[kmichaelis]

@alexBLR @katfish2 and I met with Julio at Libnova this morning. According to him, using S3 to migrate the content would be better than using the API (although the API should be able to handle large files). However, the S3 bug has not been resolved. If it doesn't get fixed in a timely manner we should plan to use the API for migration.

[rotated8]

I believe we have all the collections created- The mapping to containers exists in the disk_image_collections CSV- and uploading the objects is covered by #122. Is there any other work remaining for this ticket?

[kmichaelis]

@rotated8 I'm going to close #122 and update this one so we can check off the part that's done already. We can check off the second part when all the disk images are added to the folders.

[kmichaelis]

@rotated8 will talk to Beth about running the last largest file transfers on a server. After that Alex should be able to get the process going.