Jamie,
I haven’t merged buckets but I have moved content from one store to another. There isn’t any automated way to do it, but it is relatively straight forward since all of the file/s3 stores lay out content the same way. Basically you need to copy the content from one store to the other, with the same path/file names, and then edit the database to change the storageidentifier to match the new location. Because all of the data paths include the PID, e.g. a dataset’s files will be in /10.5072/FK2/ABCDEF, there won’t be any collisions with files for other datasets. With s3, the AWS client has a sync command that can be used to move content and the change in the db is a simple query – storageidentifiers for datasets prepend the store id to the PID, e.g. s31://10.5072/F2ABCDEF and the ones for files look like the store id and bucket followed by a number, e.g. s31://test-bucket:<number> . In both cases you just relace the old prefix for the one for the new store/bucket.
Hope that helps,
-- Jim
--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
dataverse-commu...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/dataverse-community/e0c338b5-163c-4988-8d06-515d3b05eef5n%40googlegroups.com.