-
Notifications
You must be signed in to change notification settings - Fork 495
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
Deaccessioning: What should show in search card? #1221
Comments
And maybe the deaccession reason? (is this reason searchable? Are other fields searchable?) |
spoke to @posixeleni and we think it should have citation, default dataset icon (not a file thumbnail) and instead of description, have the reason for deaccessioning. As far as I know, the reason and no other fields for deaccession is searchable; @posixeleni and I agree that none of those fields for deaccession should be indexed and searchable. |
It seems that the only unaddressed suggestion in this github issue is about the thumbnails: The search card and landing pages of deaccessioned datasets should show only the default dataset icon (and not show whatever thumbnail the dataset had before it was deaccessioned). In Dataverse 4.9.1, the search card and landing pages of deaccessioned datasets do show the thumbnails that the dataset had before it was deaccessioned. When people who don't have permissions on the dataset use the deaccessioned dataset's URL (https://dataverse.harvard.edu/dataset.xhtml?persistentId=doi:10.7910/DVN/ZYPZPW) or persistent ID (https://doi.org/10.7910/DVN/ZYPZPW) to get to the dataset, they can see the dataset thumbnail. I imagine this could be a problem if the deaccession reason was related to data privacy concerns. @scolapasta, is the thumbnail issue the only unaddressed issue in this github issue? Could we open a new one for it (and close this one)? |
I deaccessioned a dataset and only I can see the search card (good). But it still shows the thumbnail and the description. - should it only show the citation?
The text was updated successfully, but these errors were encountered: