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.

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

Support replacing files while in draft #7149

Closed
qqmyers opened this issue Jul 30, 2020 · 1 comment · Fixed by #7337
Closed

Support replacing files while in draft #7149

qqmyers opened this issue Jul 30, 2020 · 1 comment · Fixed by #7337

Comments

@qqmyers
Copy link
Member

qqmyers commented Jul 30, 2020

If I understand correctly, Dataverse's replace file capabilities are only possible post-publication and not within a draft Dataset.

QDR's curation workflow involves replacing files in the draft Dataset (e.g. to remove PII) and, in connection with #7068, there is interest in being able to replace a file in the draft version/prior to publication without changing the PID reserved for the Datafile. I'm considering modifying the existing replace mechanism to work in a draft Dataset, probably deleting the old file unless it is used in a previously published version. Is there interest in this in the community? Any design guidance/ alternative mechanisms/ other feedback?

(Looking at other issues - might be able to look into #4380 at the same time.)

@qqmyers
Copy link
Member Author

qqmyers commented Sep 10, 2020

In slack @scolapasta pointed out that the normal replace functionality generates a new DOI for the new file since the old DOI still refers to the original (assuming you have file DOIs on). Given that, it still seems to make sense to allow a draft-only file to be replaced and to allow any reserved DOI (after #7068) to be retained, but calling this something other than replace might make sense, e.g. updateDraftFile (suggestions welcome).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant