Specify Remote Path on Copy #187
Description
Instead of specifying a remote path when the directory is indexed, as a follow up to #186 it may be helpful to be able to specify the path when copying, so a subset of files could be copied to one location, and a different subset to another location. In the index function (in dsi core Sync) the remote path isn't really used except to initialize the remote paths in the database, so later down the line if users want to change the remote location they would have to create another Sync object.
Thought process: if Sync objects are supposed to just define a linkage between local and remote data, it's fine as is, but if people should be using Sync objects to actively manage data and organize it in different ways, it may require additional features. Especially for my use case which would involve only querying and moving specific files.
If possible, it may even be useful to have many-to-one relationships between locations and files, if a file gets synced in multiple remote places (as opposed to just having one local<->remote relationship).