-
Notifications
You must be signed in to change notification settings - Fork 500
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
Only show draft file card if file has changed from published version #528
Comments
Original Redmine Comment I asked Leonid about this ticket, specifically: Given a dataset with multiple versions... ...each dataset version has various files ...how easy is to know if a file has changed or not between dataset versions? There is no simple value to check. It sounds like we need to either:
Something like that... |
OK, works as described, closing |
We'll need to make datasetVersionId searchable per #2038. It sure seems like the rules about draft files established in #528 will have to change. :/ Issue #2460 created about database deadlocks. :( Issue #2464 created about having to edit metadata of a published dataset before we can delete a file via SWORD. :( Issue #2461 created about how the native API allows version less than v1.0 to be published. :(
Author Name: Philip Durbin (@pdurbin)
Original Redmine Issue: 3943, https://redmine.hmdc.harvard.edu/issues/3943
Original Date: 2014-05-07
Original Assignee: Philip Durbin
In #3795 multiple cards for datasets and files were introduced:
We're concerned, however, that when you take a published dataset and edit it, draft cards are created for each file in the published study. This might be overwhelming.
With screenshots, here is a sample publishing workflow where a published file turns gets a draft card perhaps prematurely because the description of the file is not changed until later:
Related issue(s): #380
Redmine related issue(s): 3795
The text was updated successfully, but these errors were encountered: