STS Storage location

[kelshmo]

• Add Python equivalent to migrate data. @jkiang13 offered to do this.

• @DwayneJengSage can you clarify this limitation?

• I will add links to the sharing setting document and refer to write permissions on Synapse Folders as "edit" permission to keep language consistent.

[DwayneJengSage]

@DwayneJengSage can you clarify this limitation?

If a STS storage location is defined on a Folder, that Folder cannot be placed within another Folder hierarchy that also defines an STS storage location (even if they are the same storage location).

This is a corollary of the other restriction "If a parent Folder has an STS storage location, all sub-folders will have the same storage location". This is implemented server-side as "sub-folders cannot define storage locations at all". This allows us to keep things simple on the server-side, as we can always assume that the root of the STS hierarchy is the first folder that defines a storage location.

If users need to move files from two different STS folder hierarchies, the current workaround is to move the individual files from one folder to the other.

Is this something we want to capture in the docs?

[kelshmo]

@DwayneJengSage Since sub-folders inherit STS storage location permissions, it is confusing that the user cannot use the Move Folder mechanism to set-up their file hierarchy if the same storage location is defined. I think it is relevant to explicate the action the user should take (something like): "If a parent Folder has an STS storage location, all sub-folders will have the same storage location. Files cannot be added to an STS storage location using Move Folder. Instead, individual Files must be moved to the intended parent Folder ".