Skip to content
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

Closed
scolapasta opened this issue Dec 5, 2014 · 19 comments · Fixed by #6909
Closed

Deaccessioning: What should show in search card? #1221

scolapasta opened this issue Dec 5, 2014 · 19 comments · Fixed by #6909
Labels
Feature: Search/Browse Type: Bug a defect User Role: Curator Curates and reviews datasets, manages permissions UX & UI: Design This issue needs input on the design of the UI and from the product owner

Comments

@scolapasta
Copy link
Contributor

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?

@scolapasta
Copy link
Contributor Author

And maybe the deaccession reason? (is this reason searchable? Are other fields searchable?)

@eaquigley
Copy link
Contributor

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.

@scolapasta scolapasta assigned pdurbin and unassigned scolapasta Dec 5, 2014
@scolapasta scolapasta modified the milestones: Beta 11 - Dataverse 4.0, Dataverse 4.0: Final Dec 8, 2014
@scolapasta scolapasta modified the milestones: Beta 13 - Dataverse 4.0, Dataverse 4.0: Final Jan 23, 2015
@scolapasta scolapasta modified the milestones: Beta 13 - Dataverse 4.0, In Review - Dataverse 4.0, Beta 15 - Dataverse 4.0 Feb 6, 2015
@scolapasta scolapasta modified the milestones: Dataverse for Big Data - Part 1 , Beta 15 - Dataverse 4.0 Mar 2, 2015
@scolapasta scolapasta removed this from the 4.0.1 milestone Apr 27, 2015
@scolapasta scolapasta modified the milestones: 4.0.2, Candidates for 4.0.2 May 29, 2015
@scolapasta scolapasta modified the milestones: In Review, 4.0.2 Jul 6, 2015
@scolapasta scolapasta removed their assignment Jan 27, 2016
@scolapasta scolapasta removed this from the Not Assigned to a Release milestone Jan 28, 2016
@pdurbin pdurbin added Help Wanted: Code Mentor: pdurbin UX & UI: Design This issue needs input on the design of the UI and from the product owner and removed Effort 3: Large labels Jun 25, 2017
@pdurbin pdurbin added the User Role: Curator Curates and reviews datasets, manages permissions label Jul 4, 2017
@jggautier
Copy link
Contributor

jggautier commented Jul 9, 2018

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)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: Search/Browse Type: Bug a defect User Role: Curator Curates and reviews datasets, manages permissions UX & UI: Design This issue needs input on the design of the UI and from the product owner
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants