-
Notifications
You must be signed in to change notification settings - Fork 488
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
Deaccession latest published version prevents further edits, deaccession or create draft #1308
Comments
This seems like a duplicate of #1267. |
@eaquigley #1267, #1308 and #2363 are related and could be combined but they are separate: |
I'm adding notes from #2363 to this and changing the title and description to cover the more general case: Deaccessioning the latest published version (including all) of a dataset results in the edit button not being rendered so that a user cannot create new draft versions of the dataset and cannot deaccession other versions. |
eaquigley commented on Apr 29 in issue #3096 (which I am closing in favor of this issue).
|
Also deaccession related #1221. |
@sekmiller was this fixed by b5b5f31? I'm putting this in Code Review at https://waffle.io/IQSS/dataverse |
Talked over this in standup today. I'll check in with @sekmiller on Monday. |
@sekmiller and I just spoke about how b5b5f31 indeed should be a fix for this issue so he said this issue should go to QA. I associated it with pull request #3408. |
OK, works -according to design doc can only create a draft from a published, not deaccessioned version so that implies you cannot create a draft from a completely deaccessioned dataset. |
When a dataset is deaccessioned, I no longer could edit (so as to create a new version).
The text was updated successfully, but these errors were encountered: