Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support for moving files in Data Service #243

Open
dleehr opened this issue May 1, 2019 · 0 comments
Open

Support for moving files in Data Service #243

dleehr opened this issue May 1, 2019 · 0 comments
Assignees
@johnbradley

Comments

@dleehr
Copy link
Member

dleehr commented May 1, 2019

Issue was raised during microbiome meeting today about how when files are moved locally, ddsclient uploads a new copy (but does not delete the old one)

I recall in the design of ddsclient that we discussed how to notice file moves and that ddsclient is not a sync client. However, since real-world use does involve re-organizing directories, we should consider how to improve this case.

I think first, we could provide SDK support for PUT /api/v1/files/:id/move

Second, we could add a move command to the command-line to call this endpoint
Third, we could re-visit how to detect local filesystem moves and apply them remotely.
@johnbradley johnbradley self-assigned this Jun 3, 2019
@johnbradley johnbradley mentioned this issue Jun 4, 2019
Merged
johnbradley added a commit that referenced this issue Jun 11, 2019
@johnbradley
Add leading slash to remote paths
d2aef23 
In support of #243 adds leading slash to remote paths.
This allows users to naturally specify the top level 'directory'
of a project with '/'. Previously this was omitted to match
the DukeDS web portal.

Changes the download command arguments include/exclude to allow
leading slash or the current functionality of omitting the leading
slash.
@johnbradley johnbradley mentioned this issue Jun 11, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@johnbradley johnbradley

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@johnbradley @dleehr