Date: Thu, 28 Mar 2024 12:43:33 -0400 (EDT) Message-ID: <596923744.28388.1711644213617@lyrasis1-roc-mp1> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_28387_939243714.1711644213617" ------=_Part_28387_939243714.1711644213617 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
JIRA Reference: https://jira.duraspace.org/browse/DS-587 (see also https://jira.duraspace= .org/browse/DS-429)
Proposed:
Here are some examples in our system:=
http://deepblue.lib.umich.edu/handl=
e/2027.42/58331
http://deepblue.lib.umi=
ch.edu/handle/2027.42/51548
http://deep=
blue.lib.umich.edu/handle/2027.42/57993
Our standard phrases are "Removed fro= m view by legal order." (haven't had to use that one yet!), "Removed from v= iew by the University of Michigan," and "Removed from view at request of th= e author."
DCAT review:<= span style=3D"color: rgb(0,0,0);"> While we rarely withdraw cont= ent, when we do, it's always been a problem that there is not a way to noti= fy the public why an item was withdrawn. I believe that adding a reason wou= ld allow better trust of the repository (i.e. the item hasn't just been wit= hdrawn for a random reason). Also, we sometimes have duplicate items deposi= ted and tend to withdraw a duplicate item. It would be useful to be able to= include a link to the remaining item. This would also be true for items th= at are withdrawn because a final copy has been made available.
The ticket is already assigned to Jos= e Blanco (University of Michigan) who developed a patch for this for the js= pui at Michigan. I don't know though if that is still a current assignment.=
DCAT initial assessment: Relevant; High priority=
Next steps: I think that we need to restart the =
discussion with the committers about this change. There are some added comp=
lications that were added by the committers (see the JIRA ticket) so I thin=
k it's worth a conversation about where this sits.