Enable Dataset Deaccession

[eaquigley]

---

Author Name: Eleni Castro (@posixeleni)
Original Redmine Issue: 4031, https://redmine.hmdc.harvard.edu/issues/4031
Original Date: 2014-05-27
Original Assignee: Mike Heppler

---

We will need to enable the ability for datasets to be deaccessioned. Additionally, the SWORD Data Deposit API needs this enabled so that it can be backwards compatible.

Rules as discussed and to be implemented:
Deaccessioning Rules:
User may deaccession entire dataset, latest version, or selected version(s)
User will be asked for reason (Some generic to be selected from via option button or “Other” with a free text entry.)
Selecting “By Version” should leave user in same pop-up.
Deaccessioned versions will show up on the versions tab of the dataset page for anyone.
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.
Deaccessioned versions will not be part of the version differences (They will not be “selectable” for ad hoc version differences and they will be skipped for the purposes of comparing consecutive versions.
If a user creates a new draft it will be based on the most recent published version - deaccessioned versions will be skipped.
A new version created after a deaccessioned version will be required to be a major version.
Will implement url for deaccessioned version similar to 3.x.

---

Redmine related issue(s): 3385

---

[eaquigley]

---

Original Redmine Comment
Author Name: Steve Kraffmiller (@sekmiller)
Original Date: 2014-07-02T18:23:15Z

---

Logic for displaying deaccession link and dialog box entered. Passing to Mike to fix display based on user selections of radio buttons

[eaquigley]

---

Original Redmine Comment
Author Name: Philip Durbin (@pdurbin)
Original Date: 2014-07-08T19:47:34Z

---

Mike, could you also please look at/fix the blue label I put on the card that says "Deaccessioned"?

Here's my commit:

new indexing rules now that we have deaccessioning #4031 · 157cf23 · IQSS/dataverse - 157cf23

This is what I attempted to implement:

• If there are no published versions but there is a deaccessioned version, index the deaccessioned dataset version with the same permissions/discoverability as drafts (i.e. hidden from the public). Show a "Deaccessioned" label on the dataset card but don't show a facet.
• If there are any published versions, index the latest published version (like normal) and make sure there are no deaccessioned versions are indexed. (Delete them from the index.)

From https://docs.google.com/a/harvard.edu/document/d/1lFcwjtdGIqqQLYYnwtTI2GZNzmzYlrnMk2omGcXO9oY/edit?usp=sharing

[scolapasta]

Deaccession was delivered; individual tickets have been opened for specific issue.