-
Notifications
You must be signed in to change notification settings - Fork 478
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: deaccessioner can not see metadata nor perform many actions #1267
Comments
You still can't see metadatas of the deaccessioned dataset as creator. |
Related to #1308. |
@sekmiller what's the correct state of this one? Should this be in Development? |
@djbrooke Can probably go directly into QA. There's nothing notable about the code changes. |
Had a brief discussion about this in standup 10/25. This is ready for code review, but the fix is on the file landing page branch. I'm going to move it to the bottom of the development column in Waffle for now. |
@sekmiller was this fixed by b5b5f31? |
@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. |
Based on feedback from @mcrosas, hid the "Share" button in deaccessioned view on dataset and file pgs. |
All good, closing. |
According to the Deaccessioning design doc, "Only the owner (others with permission) will have a link in the versions tab so that they may see the metadata/files associated with the deaccessioned version." (emphasis added)
Probably due to changes in permissions, it is not possible for anyone (even admin!) to see the metadata for the deaccessioned dataset. (There is no "Metadata" tab.) I'm sure an admin might be interested in looking into the details of why a dataset was deaccessioned, beyond the reason given on the version tab. They might want to look at the metadata or the files.
The dataset creator might want to create a new version of the dataset based on the deaccessioned version.
Screenshot:
The text was updated successfully, but these errors were encountered: